Manage service quotas and constraints

For cloud-based workload architectures, there are service quotas (which are also referred to as service limits). These quotas exist to prevent accidentally provisioning more resources than you need and to limit request rates on API operations so as to protect services from abuse. There are also resource constraints, for example, the rate that you can push bits down a fiber-optic cable, or the amount of storage on a physical disk.

If you are using AWS Marketplace applications, you must understand the limitations of those applications. If you are using third-party web services or software as a service, you must be aware of those limits also.

Best practices

• REL01-BP01 Aware of service quotas and constraints
• REL01-BP02 Manage service quotas across accounts and regions
• REL01-BP03 Accommodate fixed service quotas and constraints through architecture
• REL01-BP04 Monitor and manage quotas
• REL01-BP05 Automate quota management
• REL01-BP06 Ensure that a sufficient gap exists between the current quotas and the maximum usage to accommodate failover