AWS Lambda
Developer Guide

AWS Lambda Limits

This section discusses AWS Lambda limits.

List of AWS Lambda Limits

Every Lambda function is allocated with a fixed amount of specific resources regardless of the memory allocation, and each function is allocated with a fixed amount of code storage per function and per account.

The following table lists the runtime resource limits for a Lambda function per invocation.

AWS Lambda Resource Limits

ResourceDefault Limit
Ephemeral disk capacity ("/tmp" space)512 MB
Number of file descriptors 1,024
Number of processes and threads (combined total)1,024
Maximum execution duration per request300 seconds
Invoke request body payload size (RequestResponse)6 MB
Invoke request body payload size (Event)128 K
Invoke response body payload size (RequestResponse)6 MB

The following table lists service limits for deploying a Lambda function.

AWS Lambda Deployment Limits

ItemDefault Limit
Lambda function deployment package size (.zip/.jar file)50 MB
Total size of all the deployment packages that can be uploaded per region75 GB
Size of code/dependencies that you can zip into a deployment package (uncompressed zip/jar size)250 MB

AWS Lambda Limit Errors

Functions that exceed any of the limits listed in the previous limits tables will fail with an exceeded limits exception. These limits are fixed and cannot be changed at this time. For example, if you receive the exception CodeStorageExceededException or an error message similar to "Code storage limit exceeded" from AWS Lambda, you need to reduce the size of your code storage.

To reduce the size of your code storage

  1. Remove the functions that you no longer use.

  2. Reduce the code size of the functions that you do not want to remove. You can find the code size of a Lambda function by using the AWS Lambda console, the AWS Command Line Interface, or AWS SDKs.