The AWS Health Dashboard reports AWS service events that may affect your account, resources, or organization. Use it to review operational issues, scheduled changes, and account notifications, then follow each event's details and recommended actions.

Open the signed-in account dashboard for account events, or the public Service health page for reported AWS service issues across Regions. The console is ready to use after sign-in; there is no separate dashboard to create or populate with widgets.

AWS Health Dashboard explained

What AWS Health reports

AWS Health sends event notices on behalf of AWS services. Events can describe ongoing service issues, upcoming changes to services or resources, and account notices such as security or billing notifications. Details can include the service, Region or Availability Zone, status, update timeline, description, and affected resources.

Public service events and account events

ViewWhat it showsAccess
Service healthPublicly reported events about AWS service availability. An event can appear even if you do not use that service or Region.Public page; no sign-in required.
Your account healthPublic events and events specific to your account, including affected resources when AWS identifies them.Signed-in dashboard.
Your organization healthEvents for accounts in an AWS Organization after an administrator enables organizational view.Signed-in dashboard; enable the feature from the management account.

“Personal Health Dashboard” is the former name for the account-focused experience; AWS rebranded it in 2022. The current console labels this area Your account health.

AWS Health is not workload monitoring

The dashboard reports AWS-published events; it does not collect CPU, memory, request latency, application logs, traces, custom metrics, or threshold alarms, and it has no user-built metric widgets. Use Amazon CloudWatch for workload metrics, alarms, dashboards, and logs. A clear Health dashboard does not establish that your workload is healthy.

Open and navigate AWS Health

Access requirements

Sign in to the AWS account you want to inspect and use an identity with permission to view AWS Health events. The console's organizational view is available for all AWS Support plans at no additional cost. The AWS Health API has separate Support plan requirements.

Find the relevant events

  1. Open the AWS Health Dashboard.
  2. Under Your account health, choose Open and recent issues for ongoing or recently closed issues, Scheduled changes for planned maintenance and lifecycle events, or Other notifications for account notices.
  3. Choose Event log for event history. Filter by service, Region, Availability Zone, category, status, time, or resource ID/ARN.
  4. Open an event and read its status, timeline, affected resources, and recommended actions.

See AWS's guide to viewing account events for current tabs and filters.

Enable organization-wide visibility

If you use AWS Organizations, enable Your organization health from the management account. Initial account loading runs in the background, and events created before enablement can take up to 24 hours to appear. Grant the required IAM and Organizations permissions; follow AWS's instructions for enabling organizational view.

Triage an AWS Health event

Check event scope and timing

Confirm the service, Region or Availability Zone, event category and status, and when it started or is scheduled. Read the event description and update timeline, then check the affected resources list. Public service events may not name resources in your account. The dashboard supports local time or UTC, so match its time zone to your incident timeline.

Correlate the event with workload telemetry

Compare the event's scope and timing with CloudWatch metrics, alarms, and logs for the same service, Region, and resources. Use application logs and traces to see how the event affected requests and dependencies. For concrete metric and alarm guidance, see the site's CloudWatch alarm guide and broader AWS monitoring guide.

When no event explains the symptoms

AWS Health reports events AWS publishes; it is not a continuous health check for every workload. If no matching event appears, continue with service metrics and alarms, application logs and traces, recent deployments or configuration changes, and service-specific diagnostics. The absence of a Health event alone does not rule out an AWS service, network, resource, or application problem.

Route Health events to other tools

Use the AWS Health API for programmatic access

The AWS Health API exposes event information to scripts and applications. AWS's current API reference lists Business Support+, Enterprise Support, and Unified Operations, with legacy-plan eligibility in Regions that have not transitioned. Check current requirements before designing an integration; you do not need the API to use the console.

Filter events with EventBridge

Amazon EventBridge can match AWS Health events and route them to targets such as SNS, SQS, or Lambda. This pattern matches operational issues and scheduled changes; add filters for services, Regions, or other event categories to fit your response process.

{
  "source": ["aws.health"],
  "detail-type": ["AWS Health Event"],
  "detail": {
    "eventTypeCategory": ["issue", "scheduledChange"]
  }
}

Test the rule with sample events and verify target permissions. AWS Health attempts durable, at-least-once delivery, so downstream handling must tolerate duplicates. Public events can take up to an hour to begin arriving after rule creation. A rule receives events for its account; use organizational view and delegated administrator configuration for organization-wide delivery. See AWS's EventBridge rule guide.

Choose and test a notification path

AWS User Notifications manages subscriptions for Health events. Public events are not included in managed Health notifications; use an EventBridge rule or a user-configured notification for those. Test patterns and destinations with sample events, confirm target permissions, and document who owns each rule. Start with notifications or ticket creation; automate resource changes only when the action is safe, scoped, and repeatable. See AWS's guide to monitoring Health events with EventBridge.

Troubleshooting AWS Health

Access denied in the console or API

  • Confirm that you signed in to the intended account.
  • For console access, check AWS Health read permissions and explicit denies from IAM policies, permission boundaries, or service control policies. AWS's IAM examples explain the required actions.
  • For an API SubscriptionRequiredException, verify that the account has a currently eligible Support plan; console access has separate requirements.

An event or resource is missing

  • Check every event tab, remove restrictive filters, and search the Event log for older events.
  • Confirm the account, service, Region, event category, and time zone. If organizational view was recently enabled, allow the initial account load and historical-event backfill to finish.
  • Read event details: public events may not list resources in your account, and not every workload issue produces an AWS Health event.

An EventBridge notification is not arriving

  • Check that the enabled rule is on the intended event bus and matches "source": ["aws.health"] and "detail-type": ["AWS Health Event"].
  • Compare the pattern with a sample event, then check target permissions, rule metrics, and target delivery or dead-letter queue details.

History and retention

The event log covers the previous 90 days; it is not historical workload-metric storage or predictive analysis. If your incident or audit process needs longer event retention, archive matching events in a system with an explicit retention policy.

Use events in incident and change operations

Review open issues during incidents and scheduled changes during maintenance planning. For production-impacting event types, record an owner, impact check, required action, deadline, and escalation path; confirm the impact with workload telemetry.

FAQs

What's the difference between AWS Health Dashboard and Personal Health Dashboard?

Personal Health Dashboard is the former name; the current console labels the signed-in account view Your account health.

What does the AWS Health Dashboard do?

It shows AWS-published public and account-specific events, including operational issues, scheduled changes, and account notifications.

How can I get alerts about AWS Health events?

Use AWS User Notifications for managed notices or EventBridge for filtered routing and automation; use a user-configured notification or EventBridge for public events.

How do I access the AWS Health Dashboard?

Sign in and open Your account health. Public events are available at Service health.

How can I check AWS service health?

Use Service health for public AWS events and CloudWatch for workload metrics, logs, and alarms.