DOP-C02 Practice Question 48: AWS Health Scheduled Change Events

AWS Health publishes these notices as events: "You can use Amazon EventBridge to detect and react to AWS Health events. Then, based on rules that you create, EventBridge invokes one or more target actions when an event matches the values that you specify in a rule." The documentation names this very use case: "you can use AWS Health to receive email notifications if you have AWS resources in your AWS account that are scheduled for updates, such as Amazon Elastic Compute Cloud (Amazon EC2) instances", and lists SNS topics and Lambda functions among the supported targets, which covers both the channel alert and the ticket. Health "delivers events on a *durable* basis", so the team stops depending on someone reading a mailbox.

Option A reacts far too late. A system status check fails once the instance is already impaired; the point of a scheduled-change notice is to act *before* that happens.

Option B monitors something unrelated. Config rules evaluate resource configuration against a desired state; whether an instance is managed by Systems Manager says nothing about AWS having scheduled maintenance for it.

Option D is narrower and slower. Polling DescribeInstanceStatus covers EC2 only, so Health events for other services are missed entirely, and an hourly poll adds up to an hour of delay plus code to own and de-duplicate against.

Reference: Monitoring events in AWS Health with Amazon EventBridge