A DevOps engineer wants to automate remediation for EC2 instances that require a restart after receiving AWS Health maintenance notifications. The engineer created an EventBridge rule. How should that rule be configured so the instances are restarted automatically?

The correct approach is to configure an Amazon EventBridge rule that directly responds to AWS Health events. AWS Health is the service that provides notifications about events that might affect your AWS resources, including scheduled maintenance for EC2 instances. By setting the event source to AWS Health, specifying the service as EC2, and filtering for instance maintenance event types, the rule will trigger precisely when a restart is needed. Targeting a Systems Manager document (SSM Document) that restarts the EC2 instance is the most direct and efficient way to automate the remediation. SSM Documents can execute predefined actions, including restarting instances, without requiring custom code. Incorrect options: Setting the event source to Systems Manager with an event type for maintenance windows is incorrect because AWS Health is the primary source for maintenance notifications, not Systems Manager maintenance windows in this context. Targeting a Lambda function that registers an automation task to restart the instance during a maintenance window adds unnecessary complexity and delay. The goal is immediate remediation upon notification, not scheduling for a future window. Setting the event source to EC2 is incorrect because EC2 itself doesn't directly emit the maintenance notifications; AWS Health does.