Release date 2026/06/04
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
Added ssl_verify config field to control SSL certificate verification when connecting to AWS APIs.
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/02/01
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
added a verbose error level logging for better debugging of AWS Lambda invocation issues.
Release date 2026/02/26
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
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.
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
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
added a verbose error level logging for better debugging of AWS Lambda invocation issues.
Release date 2025/10/23
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
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
added a verbose error level logging for better debugging of AWS Lambda invocation issues.
Release date 2025/10/10
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
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
Fixed an issue in proxy integration mode that caused internal server error when the multiValueHeaders is null.
Release date 2024/09/11
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.
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
Added support for a configurable STS endpoint with the new configuration field aws_sts_endpoint_url.
Release date 2024/07/09
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
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
Added support for a configurable STS endpoint with the new configuration field aws_sts_endpoint_url.
Release date 2024/07/09
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
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
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
Added support for a configurable STS endpoint with the new configuration field aws_sts_endpoint_url.
Release date 2023/12/15
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.
let plugin-level proxy take effect on EKS IRSA credential provider
Cache the AWS lambda service by those lambda service related fields
Release date 2022/09/09
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
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
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
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 2022/10/12
Fixed an issue where the plugin couldn’t read environment variables in the ECS environment, causing permission errors.
