Overview - Limit Monitor on AWS

Overview

To help provide highly-available, reliable, and robust services to all of our customers, as well as minimize billing risk for new customers, Amazon Web Services (AWS) maintains service limits for each account. Nearly every AWS service is regulated in terms of how many resources you can launch within a specific AWS Region at a given time. However, there are times when even the most experienced AWS customers can unexpectedly hit service limits.

To help customers more actively track their AWS resource usage against service limits, AWS offers the AWS Limit Monitor solution, a reference implementation that automatically provisions the services necessary to proactively track resource usage and send notifications as you approach limits. The solution is easy-to-deploy and leverages AWS Trusted Advisor Service Limits checks and Service Quotas to help you display your usage and limits for specific AWS services, and centrally manage your limits. With the AWS Limit Monitor, you can receive email notifications or notifications can be sent to your existing Slack channel, enabling you to request limit increases or shut down resources before the limit is reached.

You can also use this solution to automatically monitor Amazon Elastic Compute Cloud (Amazon EC2) virtual central processing unit-based (vCPU-based) On-Demand Instance limits. For more information, see Supported Service Limit Checks.

Note

To use this solution, each account must have a Business- or Enterprise-level AWS Support plan in order to gain access to the Trusted Advisor Service Limits checks.

Cost

You are responsible for the cost of the AWS services used while running the AWS Limit Monitor. The total cost for running this solution depends on the interval at which you run the AWS Lambda functions, and the number of accounts you monitor, and whether you use this solution to monitor vCPU-based instance limits.

If you do not use this solution to monitor vCPU limits, the cost for running this solution in your primary account in US East (N. Virginia) is approximately $2.36 per month, and $0.89 per month per secondary account as of the date of publication.

If you use this solution to monitor vCPU limits, the cost for running this solution in your primary account in US East (N. Virginia) is approximately $9.50 per month, and $8.03 per month per secondary account as of the date of publication.

Prices are subject to change. For full details, see the pricing webpage for each AWS service you will be using in this solution.