We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
The current aws-lambda present assumes that the lambda is behind an API Gateway (tries to distinguish between v1 and v2). But there are other infrastructure configuration options and it is possible to have the lambda behind an ALB (see https://aws.amazon.com/blogs/networking-and-content-delivery/lambda-functions-as-targets-for-application-load-balancers/)
The event format is slightly different in that case. ALB can also have a multi value header option turned on or off (https://docs.aws.amazon.com/elasticloadbalancing/latest/application/lambda-functions.html#enable-multi-value-headers) which changes the event format as well.
Related to #505 (split presets into different one for these use cases) and #79 (lambda-edge support)
This repo does a good job at distinguishing between the different event formats and normalizing it: https://github.com/dougmoscrop/serverless-http
The text was updated successfully, but these errors were encountered:
aws-lambda-alb
Moving to the unified tracker: #2973
Sorry, something went wrong.
No branches or pull requests
Describe the feature
The current aws-lambda present assumes that the lambda is behind an API Gateway (tries to distinguish between v1 and v2). But there are other infrastructure configuration options and it is possible to have the lambda behind an ALB (see https://aws.amazon.com/blogs/networking-and-content-delivery/lambda-functions-as-targets-for-application-load-balancers/)
The event format is slightly different in that case. ALB can also have a multi value header option turned on or off (https://docs.aws.amazon.com/elasticloadbalancing/latest/application/lambda-functions.html#enable-multi-value-headers) which changes the event format as well.
Related to #505 (split presets into different one for these use cases) and #79 (lambda-edge support)
This repo does a good job at distinguishing between the different event formats and normalizing it: https://github.com/dougmoscrop/serverless-http
Additional information
The text was updated successfully, but these errors were encountered: