Easy ReviewDOP-C02
Incident and Event Response17

Health

Find affected resources and route AWS Health events across Regions.

AWS Health basics

AWS Health reports AWS events, such as outages and scheduled changes, that affect your account.

How it works

  1. AWS publishes events about services and resources.
  2. AWS Health shows the ones that affect your account.
  3. You plan around changes or respond to issues.

Exam cues

  • If the question says AWS service events affecting your resources, think AWS Health.

Remember

  • Events about services and accounts.

Trap: AWS Health shows AWS-side events; CloudWatch monitors your own resources’ metrics.

From the AWS docs (4)
  • AWS Health gives ongoing visibility into resource performance and the availability of AWS services and accounts, through events that explain how changes might affect applications.
  • AWS Health account-specific events concern an account and its resources.
  • The Affected resources tab lists resource IDs or ARNs when available.
  • The AWS Health Dashboard service health page needs no sign-in or AWS account, shows service history for the last 12 months and has an RSS feed; your account health requires signing in.

Account events and affected resources

AWS Health reports service events and changes that can affect AWS resources. The account dashboard helps a team find the specific resources involved.

How it works

  1. Review open issues, scheduled changes, notifications, or the event log in the account dashboard.
  2. Select an event to see its description, update timeline, Region, status, and affected resource count.
  3. Open Affected resources to find resource IDs or Amazon Resource Names (ARNs), which identify AWS resources.

Exam cues

  • If the question says a maintenance notice identifies instances, think account-specific eventAn account-specific event concerns an AWS account and its resources. and Affected resources, because the event concerns the account’s resources.
  • If the question says a regional service is impaired, think public eventA public event describes regional service availability without being specific to an account., because public events describe regional service availability rather than a particular account.
  • If the question says an Amazon EKS cluster version is approaching the end of standard support, think AWS Health, because EKS sends a notice to accounts with affected clusters.
  • If the question says anyone needs service history without an AWS account, think the service health page, because it is public and needs no sign-in.

Remember

  • The service health page shows 12 months of service history. Account health requires sign-in.
  • The AWS Health Dashboard is available to all AWS customers at no additional cost, including on Basic Support.

Trap: A public event is not proof that a particular account resource is affected. Check the account-specific event and affected resources.

From the AWS docs (6)
  • AWS Health account-specific events concern an account and its resources.
  • Public events describe regional service availability and are not specific to an account.
  • The account dashboard offers open and recent issues, scheduled changes, other notifications, and an event log.
  • Event details include the service, status, Region, category, description, update timeline, and affected resource count.
  • Amazon EKS sends a notice through AWS Health when an account has clusters running a Kubernetes version approaching the end of standard support.
  • The AWS Health Dashboard is available to all AWS customers at no additional cost, on every Support plan.

EventBridge routing and Region coverage

AWS Health sends events to Amazon EventBridge so rules can route matching events to notification or automation targets.

How it works

  1. Create a regional EventBridge rule with the exact source aws.health. A rule is a filter that selects events and sends matches to a target.
  2. Optionally filter eventScopeCode for PUBLIC or ACCOUNT_SPECIFIC. Rules receive notifications for their own account.
  3. Choose a target such as an SNS topic, a Lambda function, or an SQS queue. For example, an SNS topic can notify subscribers.
  4. For resilient regional coverage, create rules in the affected and backup Regions and deduplicate by eventArn and communicationId. Deduplication prevents repeated processing of the same communication. A paginated event has a distinct communication IDA communication ID identifies an AWS Health event communication and includes the page number for paginated messages. per page.

Exam cues

  • If the question says an EBS-backed EC2 instance has a retirement notice, think EventBridge and Systems Manager Automation, because a rule can trigger stop and start for a Systems Manager managed instance.
  • If the question says an IAM access key was publicly exposed, think the AWS_RISK_CREDENTIALS_EXPOSED event and a Step Functions response, because the workflow can remove the key and notify the security team.
  • If the question says one rule must capture account-specific eventsAn account-specific event concerns an AWS account and its resources. across the standard AWS partition, think the Oregon simplified integration, because it aggregates those events without high availability.
  • If the question says global Health events, think N. Virginia, because a rule there is required for global events.

Remember

  • In the standard partition, Oregon is the backup for other Regions; N. Virginia is the backup for Oregon.
  • Account-specific events go to the affected and backup Regions regardless of the affected Region’s rules.
  • Public eventsA public event describes regional service availability without being specific to an account. reach the backup Region only if a valid rule exists in the affected Region.
  • Health attempts delivery to EventBridge at least once.
  • The top-level region is the delivery Region; detail.eventRegion is the impacted Region.

Trap: A backup rule alone does not capture public events from an affected Region without a valid rule there. The simplified integration also excludes public events.

Route an AWS Health event
12AWS HealthEventBridgeSNS
  1. AWS Health sends an event to EventBridge.

  2. A matching rule sends the event to an SNS topic.

From the AWS docs (18)
  • EventBridge rules match AWS Health events and invoke targets such as SNS, Lambda, and SQS.
  • The source value aws.health matches both public and account-specific Health events; aws.health* does not.
  • The eventScopeCode field distinguishes PUBLIC from ACCOUNT_SPECIFIC events in EventBridge.
  • EventBridge rules receive Health notifications for their own AWS account.
  • AWS Health attempts durable delivery to EventBridge at least once.
  • Create an EventBridge rule in each Region whose AWS Health events you want to receive.
  • In the standard AWS partition Oregon backs up other Regions, while N. Virginia backs up Oregon.
  • Public events reach the backup Region only when a valid rule exists in the affected Region.
  • Account-specific events are sent to both affected and backup Regions regardless of rules in the affected Region.
  • AWS recommends deduplicating backup events using the event ARN and communicationId.
  • The event schema uses eventArn for the event identifier and detail.eventRegion for the impacted Region.
  • The top-level region field identifies the Region to which the notification was delivered.
  • communicationId identifies a communication and includes a page number for paginated events.
  • A single Oregon rule can capture account-specific events from all standard partition Regions but does not provide high availability or public events.
  • A rule in N. Virginia is required to receive global AWS Health events.
  • A rule can invoke Systems Manager Automation to stop and start a Systems Manager managed EBS-backed EC2 instance scheduled for retirement.
  • AWS Health generates AWS_RISK_CREDENTIALS_EXPOSED when AWS detects a publicly exposed IAM access key.
  • An event rule can invoke a Step Functions workflow that deletes an exposed IAM key, summarizes recent API activity, and sends an SNS notification.

Organizational view and lifecycle status

AWS Health organizational viewOrganizational view shows AWS Health events centrally across an AWS organization. brings events from across an AWS organization into one view. It supports a delegated administrator so a member account can access those events for daily operations.

How it works

  1. Enable organizational view for an organization with all features enabled.
  2. Delegate administrator access to a member account to use the aggregated view.
  3. For a planned lifecycle event, check the affected resource status. The status list can take time to reflect a change.
  4. Use the account event log to review recent account events.

Exam cues

  • If the question says a team needs a central view without daily use of the management account, think organizational view and a delegated administrator, because a member account can access aggregated events.
  • If the question says a resource still shows Pending after remediation, think delayed status refresh, because the affected resources list is not updated immediately.
  • If the question asks how far back to look for account events, think the account event log, because it covers the past 90 days.

Remember

  • Organizational view requires all features enabled in the organization.
  • Planned lifecycle resource statuses are Pending, Unknown, or Resolved. The list usually refreshes every 24 hours but can take up to 72 hours.
  • The account event log covers the past 90 days.

Trap: A resource can still show Pending after remediation while the affected resources list catches up.

From the AWS docs (4)
  • Organizational view aggregates Health events across an AWS organization and supports a delegated administrator.
  • Organizational view requires an organization with all features enabled.
  • Planned lifecycle event resource statuses are Pending, Unknown, or Resolved and usually refresh every 24 hours but can take up to 72 hours.
  • The account event log shows events from the past 90 days.

Flashcards

tap to flip
Answer

·

All 17 cards as a list

An administrator wants to know whether an AWS service event affects the company's own resources. Where do they look?

AWS Health (the AWS Health Dashboard).

A scheduled AWS maintenance event affects particular instances. Where can a team find the affected resources?

Open the account-specific AWS Health event and its Affected resources tab.

Where can anyone, without an AWS account, see the status and 12-month history of AWS services?

The service health page of the AWS Health Dashboard. Your account health needs sign-in.

How do public AWS Health events differ from account-specific events?

Public events describe regional service availability; account-specific events concern the account and its resources.

Where can a team find an AWS notice that an Amazon EKS cluster's Kubernetes version is approaching the end of standard support?

AWS Health Dashboard. Amazon EKS sends a notice for accounts with affected clusters.

Does a company on AWS Basic Support get the AWS Health Dashboard view of events affecting its account?

Yes. The AWS Health Dashboard is available to all AWS customers at no additional cost.

How can a team receive notifications for AWS Health events affecting its account?

Create an EventBridge rule matching source aws.health and target an SNS topic.

An AWS Health notice schedules retirement of an EBS-backed EC2 instance. How can a team automate the stop and start?

Match the event with an EventBridge rule targeting Systems Manager Automation. The instance must be managed by Systems Manager.

An AWS Health public event must reach an EventBridge backup rule. What is required in the affected Region?

A valid EventBridge rule in the affected Region. Without it, public events are not sent to the backup Region.

How can an AWS Health integration avoid duplicate processing from primary and backup Regions?

Deduplicate using eventArn and communicationId; Health attempts delivery at least once.

A team needs all standard partition account-specific AWS Health events through one EventBridge rule. What is the tradeoff?

Use the simplified integration in Oregon. It does not provide high availability or public events.

How can a team automate response to an exposed IAM access key reported by AWS Health?

Match AWS_RISK_CREDENTIALS_EXPOSED with an event rule and invoke a Step Functions remediation workflow.

Which Region needs an EventBridge rule to receive global AWS Health events?

US East (N. Virginia).

An AWS Health event arrives in a backup Region. Which field identifies the impacted Region?

detail.eventRegion. The top-level region identifies the delivery Region.

A team needs a central view of AWS Health events across an organization without using its management account for daily work. What should it use?

Enable organizational view and delegate administrator access to a member account. The organization must have all features enabled.

After remediation of a planned AWS Health lifecycle event, can an affected resource remain listed as pending?

Yes. Resource status usually refreshes every 24 hours, but can take up to 72 hours.

How far back does the AWS Health account event log show events?

The past 90 days.

You finished every topic of DOP-C02!

Your badge turned gold. Next step: book the exam on AWS. Once you pass, add yourself to Who passed.

Share

Share that you finished this certification

I finished every topic of AWS Certified DevOps Engineer - Professional (DOP-C02) on Easy Review. Come study too!