Which solution meets these requirements?
Create an Amazon CloudWatch alarm to monitor Service Quotas. Configure the alarm to invoke an AWS Lambda function to request a quota increase when the alarm reaches the threshold.
Create an AWS Config rule to monitor Service Quotas. Call an AWS Lambda function to remediate the action and increase the quota.
Create an Amazon CloudWateh alarm to monitor the AWS Health Dashboard. Configure the alarm to invoke an AWS Lambda function to request a quota increase when the alarm reaches the threshold.
Create an Amazon CloudWatch alarm to monitor AWS Trusted Advisor service quotas. Configure the alarm to publish a message to an Amazon Simple Notification Service (Amazon SNS) topic to increase the quota.
Explanations:
This option correctly suggests using an Amazon CloudWatch alarm to monitor service quotas. When the threshold is reached, it invokes an AWS Lambda function that can request a quota increase, thus automating the process.
AWS Config rules are used to monitor compliance and configuration changes, not service quotas. While it can trigger Lambda functions for remediation, it doesn’t directly monitor service quotas, making it unsuitable for this requirement.
Monitoring the AWS Health Dashboard with CloudWatch alarms does not directly relate to service quotas. The Health Dashboard provides information about service disruptions and does not manage or increase service quotas. Therefore, this option is incorrect.
Monitoring AWS Trusted Advisor service quotas with CloudWatch alarms does not provide an automatic mechanism to increase quotas. While it can notify via Amazon SNS, it does not automate the quota increase itself, which is a critical requirement here.
I organize that the answer is:
Create an Amazon CloudWatch alarm to monitor Service Quotas. Configure the alarm to invoke an AWS Lambda function to request a quota increase when the alarm reaches the threshold.