Try it now and let us know what you think. Switch to the new look >>
You can return to the original look by selecting English in the language selector above.
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 |
1,000 |
|
Function and layer storage |
75 GB |
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 (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 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) |
10 |
|
|
512 MB |
|
File descriptors |
1,024 |
|
Execution processes/threads |
1,024 |
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.
