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.

Sign up for GitHub

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

docs(aws-lambda): add new disable_https field #5486

Merged
merged 3 commits into from
Apr 27, 2023
Merged

docs(aws-lambda): add new disable_https field #5486

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ad485be
docs(aws-lambda): add new disable_https field
windmgc Apr 25, 2023
4698800
add changelog entry
windmgc Apr 27, 2023
6bc7210
phrasing adjustment for changelog
lena-larionova Apr 27, 2023
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
10 changes: 10 additions & 0 deletions app/_hub/kong-inc/aws-lambda/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,6 +199,12 @@ params:
datatype: integer
description: |
The TCP port that the plugin uses to connect to the server.
- name: disable_https
minimum_version: "3.3.x"
required: false
default: false
datatype: boolean
description: Whether to disable HTTPS to connect with the AWS Lambda Function service endpoint. This is useful for local test scenarios by using the [AWS SAM CLI tool](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html).
- name: keepalive
required: true
default: '`60000`'
Expand Down Expand Up @@ -526,6 +532,10 @@ Have fun leveraging the power of AWS Lambda in Kong!

## Changelog

**{{site.base_gateway}} 3.3.x**
* Added the `disable_https` configuration field to support HTTP connections to a lambda service.
[#9799](https://github.com/Kong/kong/pull/9799)

**{{site.base_gateway}} 3.1.x**
* Added a `requestContext` field into `awsgateway_compatible` input data.
[#9380](https://github.com/Kong/kong/pull/9380)
Expand Down