Quotas & Limits Overview
1. Introduction
AWS Serverless offers a range of services that allow developers to build applications without managing infrastructure. However, these services have quotas and limits that can affect the scalability and reliability of your applications.
Note: Understanding quotas and limits is essential to optimize resource usage and avoid service interruptions.
2. Key Concepts
- Quotas: These are the maximum values that can be allocated for specific resources in a given AWS service.
- Limits: These refer to the constraints imposed on the use of AWS resources, such as the maximum number of concurrent executions for AWS Lambda.
- Service Limits: Default limits set by AWS that can usually be increased through a support request.
3. Quotas & Limits
Here are some key quotas and limits for several AWS Serverless services:
AWS Lambda
- Maximum execution timeout: 15 minutes
- Concurrent executions: 1,000 (default)
- Memory allocation: 128 MB to 10,240 MB
AWS API Gateway
- Maximum requests per second: 10,000 (default)
- Maximum payload size: 10 MB
4. Best Practices
To effectively manage quotas and limits, consider the following best practices:
- Monitor your service quotas using AWS CloudWatch.
- Request limit increases proactively if you anticipate growth.
- Implement retries and exponential backoff for failed requests.
5. FAQ
What should I do if I reach a service limit?
If you reach a service limit, you can request a limit increase through the AWS Support Center.
How can I monitor my quotas and limits?
You can use AWS CloudWatch to set up alarms that notify you when you are approaching your service limits.