AWS Limit监控解决方案

AWS 会保持每个账户的服务限制，以帮助保证 AWS 资源可用，以及最大程度降低新客户的账单风险。一些服务限制将随着您对 AWS 的使用逐渐自动提高，但大多数 AWS 服务都要求您手动申请提高限制。

我如何能获得更宽松的服务限制，以及如何根据扩展需要管理我的服务限制？

解决方法

AWS Limit Monitor解决方案会自动设置必要的服务，以在您接近限制时主动跟踪资源使用情况并发送通知。该解决方案易于部署，并利用AWS Trusted Advisor服务限制检查和服务配额来帮助您显示特定AWS服务的使用情况和限制，并集中管理您的限制。

借助AWS Limit Monitor，您可以通过电子邮件或Slack接收通知，使您可以请求增加限制或在达到限制之前关闭资源。

AWS Limit Monitor架构

该解决方案使用AWS Lambda自动刷新AWS Trusted Advisor服务限制检查，以通过API调用检索最新利用率和限制数据。Trusted Advisor将根据限制计算使用量，以确定状态是正常（使用率低于80％），警告（使用率在80％至99％之间）还是错误（使用率100％）。

如果您选择监视基于Amazon Elastic Compute Cloud（Amazon EC2）的虚拟中央处理器（基于vCPU）的限制，则模板将启动另一个Lambda函数，该函数每五分钟运行一次。该功能检查服务配额以检索每个AWS区域的vCPU使用率和限制数据。该函数根据限制计算vCPU使用率，以确定状态是"正常"（使用率低于80％），"警告"（使用率在80％至99％之间）还是"错误"（使用率100％）。

Amazon CloudWatch Events从Trusted Advisor和vCPU监视Lambda函数捕获状态事件，并使用一组CloudWatch Events规则将状态事件发送到您在解决方案的初始部署期间选择的所有目标：Amazon Simple Queue Service（Amazon SQS）队列，Amazon Simple Notification Service（Amazon SNS）主题（可选）或Slack通知的Lambda函数（可选）。如果在初始部署期间启用了Slack通知，则该解决方案将启动Lambda函数，该函数将通知发送到您现有的Slack。

CloudFormation template：

https://s3.amazonaws.com/solutions-reference/limit-monitor/latest/limit-monitor.template

AWS maintains service limits for each account to help ensure AWS resource availability and minimize billing risks for new customers. Some service limits will automatically increase gradually as you use AWS, but most AWS services require you to manually request limit increases.

How can I get more flexible service limits, and how can I manage my service limits according to scaling needs?

Solution

The AWS Limit Monitor solution automatically sets up necessary services to proactively track resource usage and send notifications when you approach limits. The solution is easy to deploy and leverages AWS Trusted Advisor service limit checks and service quotas to help you display usage and limits for specific AWS services, and centrally manage your limits.

With AWS Limit Monitor, you can receive notifications via email or Slack, allowing you to request limit increases or shut down resources before reaching limits.

AWS Limit Monitor Architecture

The solution uses AWS Lambda to automatically refresh AWS Trusted Advisor service limit checks to retrieve the latest utilization and limit data through API calls. Trusted Advisor calculates usage based on limits to determine whether the status is OK (usage below 80%), Warning (usage between 80% and 99%), or Error (usage at 100%).

If you choose to monitor Amazon Elastic Compute Cloud (Amazon EC2) based virtual central processor (vCPU-based) limits, the template launches another Lambda function that runs every five minutes. This function checks service quotas to retrieve vCPU usage and limit data for each AWS region. The function calculates vCPU usage based on limits to determine whether the status is "OK" (usage below 80%), "Warning" (usage between 80% and 99%), or "Error" (usage at 100%).

Amazon CloudWatch Events captures status events from Trusted Advisor and the vCPU monitoring Lambda function, and uses a set of CloudWatch Events rules to send status events to all targets you selected during the solution's initial deployment: Amazon Simple Queue Service (Amazon SQS) queue, Amazon Simple Notification Service (Amazon SNS) topic (optional), or Lambda function for Slack notifications (optional). If Slack notifications are enabled during initial deployment, the solution launches a Lambda function that sends notifications to your existing Slack.

CloudFormation template:

https://s3.amazonaws.com/solutions-reference/limit-monitor/latest/limit-monitor.template

返回技术博客

AWS Limit Monitoring Solution