Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release: Gateway 3.4.3.13 #8015

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion app/_data/kong_versions.yml
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@
pcre: 8.45
lua_doc: true
- release: "3.4.x"
ee-version: "3.4.3.12"
ee-version: "3.4.3.13"
ce-version: "3.4.2"
edition: "gateway"
luarocks_version: "3.0.0-0"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -36,9 +36,11 @@ Before you enable the AWS IAM authentication, you must configure your AWS RDS da

{:.warning}
> **Warning:** You **can't** change the value of the environment variables you used to provide the AWS credential after booting {{site.base_gateway}}. Any changes are ignored.
{% if_version gte:3.8.x %}
{% if_version gte:3.4.x %}
{% unless page.release == "3.5.x" or page.release == "3.6.x" or page.release == "3.7.x" %}
- If you want to assume a role, make sure the original IAM role that Kong uses has the correct permission to assume the role of the target IAM role, and the target IAM role has the correct permission to connect to the database using IAM authentication.
- If you have users with non-public VPC networks and private VPC endpoints (without private DNS names enabled), you can configure an AWS Service Token Service (STS) endpoint globally with `vault_aws_sts_endpoint_url` or on a custom AWS Vault entity with `sts_endpoint_url`.
{% endunless %}
{% endif_version %}

- **Assign an IAM policy to the {{site.base_gateway}} IAM role**. For more information, see [Creating and using an IAM policy for IAM database access](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.IAMPolicy.html) in the Amazon RDS documentation.
Expand Down Expand Up @@ -76,7 +78,8 @@ KONG_PG_IAM_AUTH=off # This line can be omitted because off is the default value
KONG_PG_RO_IAM_AUTH=on
```

{% if_version gte:3.8.x %}
{% if_version gte:3.4.x %}
{% unless page.release == "3.5.x" or page.release == "3.6.x" or page.release == "3.7.x" %}
If you want to [assume a role](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html), also set the following environment variables:

```bash
Expand All @@ -98,7 +101,7 @@ KONG_PG_RO_IAM_AUTH_ROLE_SESSION_NAME=<role_session_name>
# Optional, same as KONG_PG_IAM_AUTH_STS_ENDPOINT_URL
KONG_PG_RO_IAM_AUTH_STS_ENDPOINT_URL=https://your.endpoint.to.aws.sts.service.amazonaws.com
```

{% endunless %}
{% endif_version %}

### Enable AWS IAM authentication in the configuration file
Expand Down
46 changes: 44 additions & 2 deletions app/gateway/changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -2511,10 +2511,52 @@ was called multiple times in a request lifecycle.
* Bumped `curl` from 8.3.0 to 8.4.0
* Bumped `nghttp2` from 1.56.0 to 1.57.0


## 3.4.3.12
## 3.4.3.13
**Release Date** 2024/10/04

### Features
#### Core

* Added support for AWS IAM role assuming in AWS IAM Database Authentication, with the following new configuration fields: `pg_iam_auth_assume_role_arn`, `pg_iam_auth_role_session_name`, `pg_ro_iam_auth_assume_role_arn`, and `pg_ro_iam_auth_role_session_name`.

* Added support for a configurable STS endpoint for RDS IAM Authentication, with the following new configuration fields: `pg_iam_auth_sts_endpoint_url` and `pg_ro_iam_auth_sts_endpoint_url`.

* Added support for a configurable STS endpoint for AWS Vault. This can either be configured by `vault_aws_sts_endpoint_url` as a global configuration, or `sts_endpoint_url` on a custom AWS Vault entity.

#### Plugins

* [**AWS Lambda**](/hub/kong-inc/aws-lambda) (`aws-lambda`):
* Added support for a configurable STS endpoint with the new configuration field `aws_sts_endpoint_url`.

* [**Rate Limiting Advanced**](/hub/kong-inc/rate-limiting-advanced/) (`rate-limiting-advanced`)
* Increased the time resolution of sliding window weight calculation.

### Fixes
#### Core

* Fixed an issue where the Vault secret cache got refreshed during `resurrect_ttl` time and could not be fetched by other workers.
* Moved internal Unix sockets to a subdirectory (`sockets`) of the Kong prefix.
* Shortened the names of internal Unix sockets to avoid exceeding the socket name limit.
* Fixed an issue where `luarocks-admin` was not available in `/usr/local/bin`.
* Fixed an issue where analytics could break when the value type of rate limiting-related headers was not `integer`.
* Fixed an issue where the IAM auth token was not refreshed when the underlying AWS credential expired.

#### Plugins

* [**OpenTelemetry**](/hub/kong-inc/opentelemetry) (`opentelemetry`)
* Fixed an issue where `header_type` being `nil` caused a log message concatenation error.

* [**Rate Limiting Advanced**](/hub/kong-inc/rate-limiting-advanced/) (`rate-limiting-advanced`)
* Fixed an issue where the sync timer could stop working due to a race condition.

### Dependencies

* Bumped `LPEG` from 1.0.2 to 1.1.0 to keep the version consistent across all active branches.
The version bump includes fixes like UTF-8 ranges, a larger limit for rules and matches, accumulator capture, and more.
* Bumped `lua-resty-aws` to 1.5.3 to fix a bug related to the STS regional endpoint.
* Made the RPM package relocatable with the default prefix set to `/`.

## 3.4.3.12
**Release Date** 2024/08/08

### Deprecations
Expand Down
Loading