A media company runs thousands of EC2 instances and uses Slack plus a shared email inbox for team communications. A DevOps engineer must forward all AWS-scheduled EC2 maintenance notifications to the Slack channel and the shared inbox. Notifications must include the instances’ Name and Owner tags. Which approach satisfies these requirements?

The correct approach leverages Amazon EventBridge to detect AWS Health events, specifically EC2 maintenance notifications. EventBridge can filter these events and route them to an Amazon SNS topic. An AWS Lambda function subscribed to this SNS topic can then process the notification, extract the required Name and Owner tags from the instance details (which are included in AWS Health events), and format the message for delivery to both the Slack channel and the shared email inbox. Incorrect options: Integrating AWS Trusted Advisor with AWS Config is not designed for real-time AWS Health event detection and notification. Trusted Advisor focuses on cost optimization, performance, security, and fault tolerance, not direct event forwarding. Monitoring EC2 health via CloudWatch metrics and triggering a Lambda from a CloudWatch alarm is not suitable for scheduled maintenance notifications. CloudWatch alarms are typically for operational metrics exceeding thresholds, not for proactive AWS service announcements. Enabling AWS Support integration with AWS CloudTrail and creating a CloudTrail lookup event is incorrect. CloudTrail logs API activity, not AWS Health events. While it records actions, it doesn't directly provide the structured maintenance notifications needed here.