Limit Monitor on AWS
AWS Limit Monitor


Supported Service Limit Checks

The AWS Limit Monitor leverages AWS Trusted Advisor to check usage against service limits. For a list of service limits that Trusted Advisor checks, see the Trusted Advisor FAQs. For a list of the default service limits and how to request a limit increase, see AWS Service Limits.


By default, this solution checks all service limits that Trusted Advisor checks. You can modify the AWS CloudFormation template mappings to specify which service limits you want to check in both the primary and secondary accounts. For more information, see Change the Monitored Services.


You can specify whether you want to receive notifications. If you choose to receive notifications, you can choose whether you want to be notified for WARN, ERROR, or both status events. If you choose not to receive notifications, the solution still stores usage information in Amazon DynamoDB.

Slack Integration

This solution includes an optional configuration to send notifications to your existing Slack channel. To use this feature, you must have an existing Slack channel, and you must specify parameters for the Slack webhook and channel. These parameters are stored in the AWS Systems Manager Parameter Store, which provides secure, hierarchical storage for configuration data management and secrets management. If you specify parameters that exist in the Parameter Store, the solution will use the existing parameters. It will not create new ones.

If you specify parameters that don’t already exist in Parameter Store, the solution will create the parameters with dummy values. Then, you must add your unique Slack webhook URL to the solutions the Parameter Store to receive Slack notifications. For more information, see Step 3.

        Sample Slack Notification

Figure 2: Sample Slack Notification

Amazon SQS Dead-Letter Queue

The Limit Monitor solution also deploys an Amazon Simple Queue Service (Amazon SQS) dead-letter queue. The Limit Summarizer AWS Lambda function attempts to process messages three times. If it cannot process the message after three attempts, the message is sent to the dead-letter queue where you can debug.

Regional Deployments

You must launch this solution’s AWS CloudFormation templates in the US East (N. Virginia) Region. However, once deployed, the solution will monitor limits for all regions in the account.