You are browsing documentation for an outdated plugin version.
Changelog
Kong Gateway 3.7.x
- Fixed an issue where the latency attributed to AWS Lambda API requests was counted as part of the latency in Kong Gateway. #12835
Kong Gateway 3.5.x
-
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 adds support for multiple IAM authenticating scenarios. #11350 -
Plugin-level proxy configuration now takes effect when fetching IAM credentials in an EKS environment with IRSA. This improvement allows the EKS IRSA credential provider (
TokenFileWebIdentityCredentials
) to correctly route requests through the plugin-level proxy configuration when obtaining credentials from the AWS STS service. #11551 -
The plugin now caches the AWS Lambda service by lambda service related fields. #11821
Kong Gateway 3.3.x
- Added the
disable_https
configuration field to support HTTP connections to a lambda service. #9799
Kong Gateway 3.2.x
- Added the configuration parameter
aws_imds_protocol_version
, which lets you select the IMDS protocol version. This option defaults tov1
and can be set tov2
to enable IMDSv2. #9962
Kong Gateway 3.1.x
- Added a
requestContext
field intoawsgateway_compatible
input data. #9380
Kong Gateway 3.0.x
- The
proxy_scheme
configuration parameter has been removed from the plugin. - The plugin now allows both
aws_region
andhost
to be set at the same time.
Kong Gateway 2.8.x
- The
proxy_scheme
configuration parameter is deprecated and planned to be removed in 3.x.x. - Kong Gateway 2.8.1.3: Added support for cross-account invocation through the
aws_assume_role_arn
andaws_role_session_name
configuration parameters. #8900 - Kong Gateway 2.8.4.0: Backported the parameter
aws_imds_protocol_version
into 2.8.x. - Kong Gateway 2.8.4.3: The AWS Lambda plugin has been refactored by using
lua-resty-aws
as an underlying AWS library. The refactor simplifies the AWS Lambda plugin codebase and adds support for multiple IAM authenticating scenarios.
Kong Gateway 2.7.x
- Starting with Kong Gateway 2.7.0.0, if keyring encryption is enabled,
the
config.aws_key
andconfig.aws_secret
parameter values will be encrypted.
Kong Gateway 2.6.x
- The AWS region can now be set with the environment variables:
AWS_REGION
orAWS_DEFAULT_REGION
. - Added support for configurable body base64 encoding via the
base64_encode_body
parameter, which istrue
by default.
Kong Gateway 2.2.x
- Added support for
isBase64Encoded
flag in Lambda function responses.
Kong Gateway 2.1.x
- Added
host
configuration to allow for custom Lambda endpoints.