Skip to main content

AWS Solutions Library

Guidance for Automating Service Quota Management on AWS

Go to sample code

Overview

This Guidance shows how to automatically monitor and receive alerts on service quota usage across single or multiple AWS accounts. Effectively managing your AWS service quotas is crucial for maintaining operational continuity and preventing unexpected disruptions to your business-critical applications. This Guidance provides an automated and comprehensive quota management strategy, helping you reduce the impact of potential service limitations.

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Download the architecture diagram

Deploy with confidence

Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs. 

Go to sample code

Well-Architected Pillars

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

EventBridge and Lambda provide a serverless model that enables you to build an event-driven architecture and automate workflows for quota management. The EventBridge automation invokes a Lambda function to capture usage data and quota values of various AWS services and resources at regular intervals. It also automates notifications to your cloud administrators so that they can perform remediation if needed. This approach reduces the operational burden of managing infrastructure and maintaining custom integrations.

Read the Operational Excellence whitepaper 

This Guidance uses AWS Identity and Access Management (IAM) policies that are scoped down to the minimum permissions required for services to function properly. This limits unauthorized access to resources. Additionally, in a multi-account environment, this Guidance uses a cross-account EventBridge integration with scoped-down policies, permitting communication between spoke and management accounts only when needed.

Read the Security whitepaper 

Amazon SNS enables an event-driven architecture, and its built-in retry mechanism supports successful event delivery. Additionally, DynamoDB synchronously replicates data across three facilities in an AWS Region, providing high availability and data durability. As a result of this quota management automation, you can take quick corrective actions to prevent productivity impairments and downtime.

Read the Reliability whitepaper 

DynamoDB is a fully managed NoSQL database that provides fast, consistent performance at any scale. Lambda automatically scales resources up and down based on the demand, improving responsiveness. Together, they enable this Guidance to handle high event volume with low latency, without the need for you to manage traffic.

Read the Performance Efficiency whitepaper 

Lambda and DynamoDB are serverless and automatically scale to manage resource utilization, so you only need to pay for the resources consumed in serving requests. The event traffic in this Guidance is not continuous (instead occurring at configurable intervals), so a scalable model keeps idle resources from causing unnecessary costs.

Read the Cost Optimization whitepaper 

Lambda and DynamoDB are serverless and support efficient, automatic resource scaling based on demand. By optimizing resource utilization and avoiding resource consumption while idle, these services reduce energy waste, all without requiring you to manage infrastructure.

Read the Sustainability whitepaper 

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.