Environment Variables

All configuration is done through environment variables, set either in your Dockerfile or as Lambda function configuration.

Reference Table

VariableDescriptionDefault
AWS_LWA_PORTTraffic port your app listens on (falls back to PORT)8080
AWS_LWA_READINESS_CHECK_PORTReadiness check portSame as AWS_LWA_PORT
AWS_LWA_READINESS_CHECK_PATHReadiness check path/
AWS_LWA_READINESS_CHECK_PROTOCOLReadiness check protocol: http or tcphttp
AWS_LWA_READINESS_CHECK_HEALTHY_STATUSHTTP status codes considered healthy (e.g. 200-399 or 200,201,204,301-399)100-499
AWS_LWA_ASYNC_INITEnable asynchronous initializationfalse
AWS_LWA_REMOVE_BASE_PATHBase path to remove from request pathNone
AWS_LWA_ENABLE_COMPRESSIONEnable gzip/br compression (buffered mode only)false
AWS_LWA_INVOKE_MODEInvoke mode: buffered or response_streambuffered
AWS_LWA_PASS_THROUGH_PATHPath for non-HTTP event payloads/events
AWS_LWA_AUTHORIZATION_SOURCEHeader name to replace with AuthorizationNone
AWS_LWA_ERROR_STATUS_CODESHTTP status codes that cause Lambda invocation failure (e.g. 500,502-504)None
AWS_LWA_LAMBDA_RUNTIME_API_PROXYProxy URL for Lambda Runtime API requestsNone

Deprecated Variables

The following non-namespaced variables are deprecated and will be removed in v2.0. Migrate to the AWS_LWA_ prefixed versions.

DeprecatedReplacement
HOSTN/A
READINESS_CHECK_PORTAWS_LWA_READINESS_CHECK_PORT
READINESS_CHECK_PATHAWS_LWA_READINESS_CHECK_PATH
READINESS_CHECK_PROTOCOLAWS_LWA_READINESS_CHECK_PROTOCOL
REMOVE_BASE_PATHAWS_LWA_REMOVE_BASE_PATH
ASYNC_INITAWS_LWA_ASYNC_INIT
AWS_LWA_READINESS_CHECK_MIN_UNHEALTHY_STATUSAWS_LWA_READINESS_CHECK_HEALTHY_STATUS

PORT is not deprecated and remains a supported fallback for AWS_LWA_PORT.