What should the solutions architect do to meet this requirement?
Use Amazon CloudWatch to monitor the Sample Count statistic for each service in the ECS cluster. Set an alarm for when the math expression sample count/SERVICE_QUOTA(service)*100 is greater than 80. Notify the development team by using Amazon Simple Notification Service (Amazon SNS).
Use Amazon CloudWatch to monitor service quotas that are published under the AWS/Usage metric namespace. Set an alarm for when the math expression metric/SERVICE_QUOTA(metric)*100 is greater than 80. Notify the development team by using Amazon Simple Notification Service (Amazon SNS).
Create an AWS Lambda function to poll detailed metrics from the ECS cluster. When the number of running Fargate tasks is greater than 80, invoke Amazon Simple Email Service (Amazon SES) to notify the development team.
Create an AWS Config rule to evaluate whether the Fargate SERVICE_QUOTA is greater than 80. Use Amazon Simple Email Service (Amazon SES) to notify the development team when the AWS Config rule is not compliant.
Explanations:
This option incorrectly monitors the sample count for each service instead of the total number of running tasks in Fargate. It also lacks direct reference to the ECS service quotas.
This option effectively monitors the service quotas published under the AWS/Usage namespace, specifically tracking the total number of tasks and comparing it to the service quota. It sets an alarm when usage exceeds 80% and can notify the development team via SNS.
While polling metrics using a Lambda function is a viable method, it introduces unnecessary complexity and does not leverage the built-in CloudWatch alarms and service quota monitoring, making it less efficient than the correct option.
AWS Config is not the appropriate service for monitoring Fargate service quotas in real-time; it focuses on resource compliance and configuration changes rather than usage metrics. Thus, it cannot directly notify the team based on quota usage.