AWS Lambda Limits - sitapriyanka/aws GitHub Wiki

AWS Lambda limits the amount of compute and storage resources that you can use to run and store functions. https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html

• AWS Lambda limits on Maximum time the code executes. max 300 ms

• Aws Lambda limits on the maximum storage that your code can use max 3008 MB

• AWS lambda limits on the throughput if your lambda is runs in a vpc. lambda needs multiple ips to run . so in a vpc there is a limit on multiple interfaces. i.e 250 COLd START:

• A new **execution context **is created in the background every time you deploy a new version of your code, go a long time without any invocations, or when the number of concurrent invocations increases. Starting a new execution context requires AWS Lambda to download your code, initialize a runtime environment, and load your code. This process is called a cold-start. Depending on the size of your deployment package, the runtime environment, and your configuration, a cold-start could take from a few milliseconds to a few seconds. Therefore, applications with very strict requirements concerning response times are not good candidates for AWS Lambda.

• the default limit for the maximum size of the compressed deployment package (zip file) is 50 MB. When executing your Lambda function, you can use up to 500 MB non-persistent disk space mounted to /tmp.