REL01-BP02: Manage service quotas across accounts and regions
If you are using multiple AWS accounts or AWS Regions, ensure that you request the appropriate quotas in all environments in which your production workloads run. Consider quotas for disaster recovery, development, and testing.
Implementation guidance
Managing service quotas across multiple AWS accounts and regions is critical for ensuring consistent availability and performance of your workloads. Different environments may have varying quota requirements, and some quotas are account-specific or region-specific, requiring coordinated management to prevent service disruptions during normal operations, scaling events, or disaster recovery scenarios.
Key steps for implementing this best practice:
- Establish multi-account and multi-region quota inventory:
- Map all AWS accounts and regions used by your organization
- Document quota requirements for each environment (production, staging, development, DR)
- Identify shared quotas vs. account-specific and region-specific quotas
- Create quota dependency maps between accounts and regions
- Establish quota baseline requirements for each environment type
- Implement centralized quota management:
- Create a centralized quota management system across accounts and regions
- Establish quota governance policies and approval workflows
- Implement automated quota synchronization between environments
- Create quota templates for different environment types
- Establish quota change management processes
- Design for quota distribution and sharing:
- Distribute workloads across multiple accounts to leverage separate quota pools
- Use multiple regions to access regional quota limits
- Implement quota pooling strategies for shared resources
- Design failover mechanisms that consider quota availability
- Plan for quota requirements during disaster recovery scenarios
- Monitor quotas across all environments:
- Implement unified quota monitoring across accounts and regions
- Create consolidated dashboards for multi-account quota visibility
- Set up cross-account alerting for quota utilization
- Monitor quota usage patterns across different environments
- Track quota increase requests and approvals across accounts
- Automate quota management workflows:
- Implement automated quota provisioning for new accounts and regions
- Create automated quota increase request workflows
- Establish quota compliance checking and enforcement
- Implement quota drift detection and remediation
- Automate quota reporting and audit processes
- Plan for disaster recovery and scaling scenarios:
- Ensure disaster recovery regions have adequate quotas
- Plan for quota requirements during traffic failover
- Consider quota needs for auto-scaling scenarios
- Implement quota pre-warming for disaster recovery
- Test quota availability during disaster recovery exercises
Implementation examples
Example 1: Multi-account quota management system
Example 2: Cross-region quota coordination system
Example 3: AWS Organizations-based quota governance
Example 4: Disaster recovery quota pre-warming script
AWS services to consider
Benefits of managing service quotas across accounts and regions
- Consistent availability: Ensures adequate quotas are available across all environments and regions
- Disaster recovery readiness: Guarantees sufficient capacity for failover scenarios
- Simplified governance: Provides centralized management and visibility across multiple accounts
- Proactive scaling: Enables coordinated quota increases across environments
- Cost optimization: Prevents over-provisioning while ensuring adequate capacity
- Compliance assurance: Maintains consistent quota policies across the organization
- Reduced operational overhead: Automates quota management across multiple environments
- Improved reliability: Prevents service disruptions due to quota limitations during scaling or failover