AWS Lambda

Release date 2026/07/02

Feature

• Added a preserve_lambda_api_error_code config field. When enabled, Kong returns the same HTTP status code the Lambda API returned (4xx or 5xx), with a sanitized body.

Bugfix

• Fixed an issue where empty JSON array bodies ([]) were incorrectly converted to objects ({}) when using is_proxy_integration=true and empty_arrays_mode=correct alongside the Exit Transformer plugin.

• Fixed an issue where a 500 error occurred when is_proxy_integration was enabled and the Lambda function returned null values in headers or multiValueHeaders. Null values are now converted to empty strings.

Release date 2026/06/04

Bugfix

• Fixed an issue where a 500 error occurred when is_proxy_integration was enabled and the Lambda function returned null values in headers or multiValueHeaders. Null values are now converted to empty strings.

• Fixed an issue where empty JSON array bodies ([]) were incorrectly converted to objects ({}) when using is_proxy_integration=true and empty_arrays_mode=correct alongside the exit-transformer plugin.

Release date 2026/04/07

Feature

• Added ssl_verify config field to control SSL certificate verification when connecting to AWS APIs.

Bugfix

• Fixed an issue where Lambda responses with empty or null body caused 500 errors when is_proxy_integration is enabled.

• Fixed an issue where headers from Lambda proxy responses were not merged correctly, causing case-insensitive header deduplication to fail. User-supplied headers now properly overwrite existing headers regardless of casing.

Release date 2026/06/30

Bugfix

• Fixed an issue where empty JSON array bodies ([]) were incorrectly converted to objects ({}) when using is_proxy_integration=true and empty_arrays_mode=correct alongside the exit-transformer plugin.

• Fixed an issue where a 500 error occurred when is_proxy_integration was enabled and the Lambda function returned null values in headers or multiValueHeaders. Null values are now converted to empty strings.

Release date 2026/02/01

Bugfix

• Fixed an issue where Lambda responses with empty or null body caused 500 errors when is_proxy_integration is enabled.

Release date 2025/12/18

Bugfix

• added a verbose error level logging for better debugging of AWS Lambda invocation issues.

Release date 2026/02/26

Bugfix

• added a verbose error level logging for better debugging of AWS Lambda invocation issues.

• Fixed an issue where Lambda responses with empty or null body caused 500 errors when is_proxy_integration is enabled.

Release date 2025/10/01

Feature

• Added support for AWS API Gateway payload v2. A new configuration field awsgateway_compatible_payload_version has been added to control the version of the payload.

Bugfix

• Fixed an issue where the AWS Gateway compatible payload generated by the plugin did not include the resource field in some cases.

Release date 2026/05/11

Bugfix

• Fixed an issue where a 500 error occurred when is_proxy_integration was enabled and the Lambda function returned null values in headers or multiValueHeaders. Null values are now converted to empty strings.

• Fixed an issue where empty JSON array bodies ([]) were incorrectly converted to objects ({}) when using is_proxy_integration=true and empty_arrays_mode=correct alongside the exit-transformer plugin.

Release date 2026/02/26

Bugfix

• added a verbose error level logging for better debugging of AWS Lambda invocation issues.

Release date 2025/10/23

Bugfix

• Fixed an issue where the AWS Gateway compatible payload generated by the plugin did not include the resource field in some cases.

Release date 2025/07/03

Bugfix

• A warning message was added during schema validation on those plugins that contain a function name that does not comply with AWS Lambda’s FunctionName pattern.

Release date 2026/02/11

Bugfix

• added a verbose error level logging for better debugging of AWS Lambda invocation issues.

Release date 2025/10/10

Bugfix

• Fixed an issue where the AWS Gateway compatible payload generated by the plugin did not include the resource field in some cases.

Release date 2025/03/27

Bugfix

• Fixed an issue that occurred when is_proxy_integration was enabled, where Kong’s response could behave incorrectly when the response was changed after the execution of the AWS Lambda plugin. The Content-Length header in the lambda function response is now ignored by the AWS Lambda plugin.

Release date 2024/12/12

Bugfix

• Fixed an issue in proxy integration mode that caused internal server error when the multiValueHeaders is null.

Release date 2024/09/11

Feature

• A new configuration field empty_arrays_mode is now added to control whether Kong should send [] empty arrays (returned by Lambda function) as [] empty arrays or {} empty objects in JSON responses.`

• Added support for a configurable STS endpoint with the new configuration field aws_sts_endpoint_url.

Bugfix

• Fixed an issue that the plugin does not work with multiValueHeaders defined in proxy integration and legacy empty_arrays_mode.

• Fixed an issue that the version field is not set in the request payload when awsgateway_compatible is enabled.

Release date 2024/11/26

Feature

• Added support for a configurable STS endpoint with the new configuration field aws_sts_endpoint_url.

Release date 2024/07/09

Feature

• A new configuration field empty_arrays_mode is now added to control whether Kong should send [] empty arrays (returned by Lambda function) as [] empty arrays or {} empty objects in JSON responses.`

Release date 2024/05/28

Bugfix

• Fixed an issue where the latency attributed to AWS Lambda API requests was counted as part of the latency in Kong.

Release date 2024/10/11

Feature

• Added support for a configurable STS endpoint with the new configuration field aws_sts_endpoint_url.

Release date 2024/07/09

Feature

• A new configuration field empty_arrays_mode is now added to control whether Kong should send [] empty arrays (returned by Lambda function) as [] empty arrays or {} empty objects in JSON responses.`

Release date 2024/07/09

Feature

• A new configuration field empty_arrays_mode is now added to control whether Kong should send [] empty arrays (returned by Lambda function) as [] empty arrays or {} empty objects in JSON responses.`

Release date 2023/11/08

Bugfix

• let plugin-level proxy take effect on EKS IRSA credential provider

• Cache the AWS lambda service by those lambda service related fields

Release date 2024/11/15

Feature

• Added support for a configurable STS endpoint with the new configuration field aws_sts_endpoint_url.

Release date 2023/12/15

Feature

• the AWS-Lambda plugin has been refactored by using lua-resty-aws as an underlying AWS library. The refactor simplifies the AWS-Lambda plugin code base and adding support for multiple IAM authenticating scenarios.

Bugfix

• let plugin-level proxy take effect on EKS IRSA credential provider

• Cache the AWS lambda service by those lambda service related fields

Release date 2023/05/19

Feature

• Added the configuration parameter disable_https to support scheme configuration on the lambda service API endpoint.#9799

Release date 2023/02/28

Feature

• Added the configuration parameter aws_imds_protocol_version, which lets you select the IMDS protocol version. This option defaults to v1 and can be set to v2 to enable IMDSv2.#9962

Release date 2022/12/06

Feature

• Added requestContext field into awsgateway_compatible input data#9380

Bugfix

• Fixed an issue that was causing inability to read environment variables in ECS environment.#9460

• Specifying a null value for the isBase64Encoded field in lambda output now results in a more obvious error log entry with a 502 code.#9598

Release date 2022/09/09

Feature

• Added support for cross-account invocation through the aws_assume_role_arn andaws_role_session_name configuration parameters.#8900

• The plugin now accepts string type statusCode as a valid return when working in proxy integration mode.#8765

• The plugin now separates AWS credential cache by the IAM role ARN.#8907

Bugfix

• Removed the deprecated proxy_scheme field from the plugin’s schema.#8566

• Changed the path from request_uri to upstream_uri to fix an issue where the URI could not follow a rule defined by the Request Transformer plugin.#9058 #9129

Breaking Change

• The AWS region is now required. You can set it through the plugin configuration with the aws_region field parameter, or with environment variables.

• The plugin now allows host and aws_region fields to be set at the same time, and always applies the SigV4 signature.#8082

Release date 2023/09/18

Feature

• the AWS-Lambda plugin has been refactored by using lua-resty-aws as an underlying AWS library. The refactor simplifies the AWS-Lambda plugin code base and adding support for multiple IAM authenticating scenarios.

Release date 2023/03/28

Feature

• Added the configuration parameter aws_imds_protocol_version, which lets you select the IMDS protocol version. This option defaults to v1 and can be set to v2 to enable IMDSv2.#9962

Release date 2022/10/12

Bugfix

• Fixed an issue where the plugin couldn’t read environment variables in the ECS environment, causing permission errors.

Release date 2022/08/05

Feature

• Added support for cross-account invocation through the aws_assume_role_arn andaws_role_session_name configuration parameters.#8900

Release date 2022/05/27

Feature

• When working in proxy integration mode, the statusCode field now accepts string datatypes.

Release date 2022/03/02

Bugfix

• Fixed incorrect behavior when configured to use an HTTP proxy and deprecated the proxy_scheme config attribute for removal in 3.0.#8406