A company has several development teams that share a single AWS account. The development team manager wants to automatically stop Amazon EC2 instances and receive notifications when resources are idle and are not tagged as production resources.
Which solution meets these requirements?
A Use a scheduled Amazon CloudWatch Events rule to filter for Amazon EC2 instance status checks and identify idle EC2 instances. Use the CloudWatch Events rule to target an AWS Lambda function to stop non-production instances and send notifications. B Use a scheduled Amazon CloudWatch Events rule to filter AWS Systems Manager events and identify idle EC2 instances and resources. Use the CloudWatch Events rule to target an AWS Lambda function to stop non-production instances and send notifications. C Use a scheduled Amazon CloudWatch Events rule to target a custom AWS Lambda function that runs AWS Trusted Advisor checks. Create a second CloudWatch Events rule to filter events from Trusted Advisor to trigger a Lambda function to stop idle non-production instances and send notifications. D Use a scheduled Amazon CloudWatch Events rule to target Amazon Inspector events for idle EC2 instances. Use the CloudWatch Events rule to target the AWS Lambda function to stop non-production instances and send notifications. Show Answer Answer Explanation AWS Trusted Advisor’s Low Utilization Amazon EC2 Instances check identifies underused EC2 instances and recommends stopping or terminating them. A scheduled Lambda function can run the relevant Trusted Advisor checks, while an EventBridge rule can filter Trusted Advisor check-result events and invoke a Lambda function that verifies the production tag, stops eligible instances, and sends notifications. EC2 status checks measure instance and system health, not resource idleness.
Learn more
Community Discussion