このページは、まだ日本語ではご利用いただけません。翻訳中です。
古いプラグインバージョンのドキュメントを閲覧しています。
Changelog
Kong Gateway 3.10.x
- Fixed an issue that occurred when 
is_proxy_integrationwas enabled, where Kong Gateway’s response could behave incorrectly when the response was changed after the execution of the AWS Lambda plugin. TheContent-Lengthheader in the lambda function response is now ignored by the AWS Lambda plugin. 
Kong Gateway 3.9.x
- Fixed an issue in proxy integration mode that caused an internal server error when the 
multiValueHeaderswas null. 
Kong Gateway 3.8.x
- Added support for a configurable STS endpoint with the new configuration field 
aws_sts_endpoint_url. #13388 - Added the configuration field 
empty_arrays_modeto control whether Kong should send[]empty arrays (returned by Lambda function) as[]empty arrays or{}empty objects in JSON responses. #13084 - Fixed an issue where the plugin didn’t work with 
multiValueHeadersdefined in proxy integration and legacyempty_arrays_mode. #13381 - Fixed an issue where the 
versionfield wasn’t set in the request payload whenawsgateway_compatiblewas enabled. #13018 
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-awsas 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_httpsconfiguration 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 tov1and can be set tov2to enable IMDSv2. #9962 
Kong Gateway 3.1.x
- Added a 
requestContextfield intoawsgateway_compatibleinput data. #9380 
Kong Gateway 3.0.x
- The 
proxy_schemeconfiguration parameter has been removed from the plugin. - The plugin now allows both 
aws_regionandhostto be set at the same time. 
Kong Gateway 2.8.x
- The 
proxy_schemeconfiguration 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_arnandaws_role_session_nameconfiguration parameters. #8900 - Kong Gateway 2.8.4.0: Backported the parameter
aws_imds_protocol_versioninto 2.8.x. - Kong Gateway 2.8.4.3: The AWS Lambda plugin has been refactored by using 
lua-resty-awsas 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_keyandconfig.aws_secretparameter values will be encrypted. 
Kong Gateway 2.6.x
- The AWS region can now be set with the environment variables: 
AWS_REGIONorAWS_DEFAULT_REGION. - Added support for configurable body base64 encoding via the 
base64_encode_bodyparameter, which istrueby default. 
Kong Gateway 2.2.x
- Added support for 
isBase64Encodedflag in Lambda function responses. 
Kong Gateway 2.1.x
- Added 
hostconfiguration to allow for custom Lambda endpoints.