AWS Health basics
AWS Health reports AWS events, such as outages and scheduled changes, that affect your account.
How it works
- AWS publishes events about services and resources.
- AWS Health shows the ones that affect your account.
- 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.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 3 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.