# AWS Lambda¶

This extension may be referenced by the qualified name envoy.filters.http.aws_lambda

Note

This extension is functional but has not had substantial production burn time, use only with this caveat.

This extension is not hardened and should only be used in deployments where both the downstream and upstream are trusted.

AWS Lambda configuration overview.

## extensions.filters.http.aws_lambda.v3.Config¶

[extensions.filters.http.aws_lambda.v3.Config proto]

AWS Lambda filter config

{
"arn": "...",
"invocation_mode": "..."
}

arn

(string) The ARN of the AWS Lambda to invoke when the filter is engaged Must be in the following format: arn:<partition>:lambda:<region>:<account-number>:function:<function-name>

(bool) Whether to transform the request (headers and body) to a JSON payload or pass it as is.

invocation_mode

(extensions.filters.http.aws_lambda.v3.Config.InvocationMode) Determines the way to invoke the Lambda function.

## Enum extensions.filters.http.aws_lambda.v3.Config.InvocationMode¶

[extensions.filters.http.aws_lambda.v3.Config.InvocationMode proto]

SYNCHRONOUS

(DEFAULT) ⁣This is the more common mode of invocation, in which Lambda responds after it has completed the function. In this mode the output of the Lambda function becomes the response of the HTTP request.

ASYNCHRONOUS

⁣In this mode Lambda responds immediately but continues to process the function asynchronously. This mode can be used to signal events for example. In this mode, Lambda responds with an acknowledgment that it received the call which is translated to an HTTP 200 OK by the filter.

## extensions.filters.http.aws_lambda.v3.PerRouteConfig¶

[extensions.filters.http.aws_lambda.v3.PerRouteConfig proto]

Per-route configuration for AWS Lambda. This can be useful when invoking a different Lambda function or a different version of the same Lambda depending on the route.

{
"invoke_config": "{...}"
}

invoke_config