AWS Lambda limits - AWS Lambda

AWS Lambda limits

AWS Lambda limits the amount of compute and storage resources that you can use to run and store functions. The following limits apply per-region and can be increased. To request an increase, use the Support Center console.

Resource Default limit

Concurrent executions


Function and layer storage

75 GB

Elastic network interfaces per VPC


For details on concurrency and how Lambda scales your function concurrency in response to traffic, see AWS Lambda function scaling.

The following limits apply to function configuration, deployments, and execution. They cannot be changed.

Resource Limit

Function memory allocation

128 MB to 3,008 MB, in 64 MB increments.

Function timeout

900 seconds (15 minutes)

Function environment variables

4 KB

Function resource-based policy

20 KB

Function layers

5 layers

Function burst concurrency

500 - 3000 (varies per region)

Invocation frequency per Region (requests per second)

10 x concurrent executions limit (synchronous – all sources)

10 x concurrent executions limit (asynchronous – non-AWS sources)

Unlimited (asynchronous – AWS service sources)

Invocation frequency per function version or alias (requests per second)

10 x allocated provisioned concurrency

This limit only applies to functions that use provisioned concurrency.

Invocation payload (request and response)

6 MB (synchronous)

256 KB (asynchronous)

Deployment package size

50 MB (zipped, for direct upload)

250 MB (unzipped, including layers)

3 MB (console editor)

Test events (console editor)


/tmp directory storage

512 MB

File descriptors


Execution processes/threads


Limits for other services, such as AWS Identity and Access Management, Amazon CloudFront (Lambda@Edge), and Amazon Virtual Private Cloud, can impact your Lambda functions. For more information, see AWS service limits and Using AWS Lambda with other services.