Considerations - AWS Limit Monitor

Considerations

Supported service quota checks

The AWS Limit Monitor uses AWS Trusted Advisor to check usage against service quotas. For a list of service quotas that Trusted Advisor checks, refer to the Trusted Advisor FAQs. For a list of the default service quotas and how to request a quota increase, refer to AWS service quotas.

Amazon Elastic Compute Cloud (Amazon EC2) is transitioning On-Demand Instance quotas from the current instance count-based quotas to the new virtual central processing unit-based (vCPU-based) On-Demand Instance quotas to simplify the limit management experience for AWS customers. You can also opt in to vCPU-based instance quotas. For more information, refer to EC2 On-Demand Instance Limits. The Limit Monitor can also monitor vCPU-based On-Demand Instance quotas.

Customization

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

Notifications

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, refer to 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.

Solution updates

Update the main stack

Take the following steps to update your main AWS CloudFormation stack to the current version.

  1. From your main account where the primary AWS Limit Monitor template is deployed, sign in to the AWS CloudFormation console.

  2. From the Stacks page, select your primary AWS Limit Monitor stack and choose Update.

  3. On the Update stack page, verify that Replace current template is selected.

    • In the Specify template section, select Amazon S3 URL.

    • Copy the link of the latest template.

    • Paste the link in the Amazon S3 URL box.

    • Verify that the correct template URL shows in the Amazon S3 URL text box and choose Next.

  4. On the Specify stack details page, under Parameters, review the parameters for the template and modify them as necessary. Refer to Step 1. Launch the stack for details about the parameters.

  5. Choose Next.

  6. On the Configure stack options page, choose Next.

  7. On the Review page, review and confirm the settings. Be sure to check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

  8. Choose View change set and verify the changes.

  9. Choose Update stack to deploy the stack.

You can view the status of the stack in the AWS CloudFormation console in the Status column. You should see a status of UPDATE_COMPLETE in approximately five minutes.

Update the spoke stack

Take the following steps to update the spoke AWS CloudFormation stack in your secondary accounts to the current version.

  1. From your secondary account where the AWS Limit Monitor spoke template is deployed, sign in to the AWS CloudFormation console.

  2. From the Stacks page, select your primary AWS Limit Monitor stack and choose Update.

  3. On the Update stack page, verify that Replace current template is selected.

    • In the Specify template section, select Amazon S3 URL.

    • Copy the link of the latest template.

    • Paste the link in the Amazon S3 URL box.

    • Verify that the correct template URL shows in the Amazon S3 URL text box and choose Next.

  4. On the Specify stack details page, under Parameters, review the parameters for the template and modify them as necessary. Refer to Step 1. Launch the stack for details about the parameters.

  5. Choose Next.

  6. On the Configure stack options page, choose Next.

  7. On the Review page, review and confirm the settings. Be sure to check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

  8. Choose View change set and verify the changes.

  9. Choose Update stack to deploy the stack.

Repeat these steps to update additional secondary accounts containing the spoke template.

About Node.js versions

AWS Limit Monitor version 5.3.0 and earlier versions use the Node.js 8.10 runtime, which reached end-of-life on December 31, 2019. AWS Lambda now blocks both the create operation and the update operation. For more information, refer to Runtime Support Policy in the AWS Lambda Developer Guide. To continue using this solution with the latest features and improvements, you must update the stack.

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 quotas for all Regions in the account.