Skip to main content
Welcome. This guide explains AWS Health and the Personal Health Dashboard—key tools for incident detection and automated response on AWS. You’ll learn the differences between the public Service Health Dashboard and the account-specific Personal Health Dashboard, the types and structure of Health events, how EventBridge receives and routes those events, recommended permissions and IAM considerations, common notification targets, practical incident-response use cases, and best practices for testing and observability. Key topics covered:
  • Dashboard types and where to look for AWS-initiated events
  • Event structure and representative JSON payloads
  • EventBridge routing patterns and example event patterns
  • Permissions and Organizations integration for programmatic access
  • Notification targets, automation patterns, and recommended best practices
A presentation slide titled "AWS Health and Personal Health Dashboards" showing four info cards. The cards summarize topics like AWS Health event sources, dashboard types, EventBridge integration, and exam focus.

Health Dashboard vs Personal Health Dashboard

  • Service Health Dashboard (global, public)
    • Public, region-level status for AWS services: https://status.aws.amazon.com
    • Best first step to check for AWS-wide or regional outages before deep troubleshooting.
  • Personal Health Dashboard (account-specific, authenticated)
    • Requires signing in to the AWS Console and navigating to Personal Health Dashboard.
    • Provides account- and resource-level timelines, affected resources, and guidance for AWS-initiated events.
A presentation slide comparing the AWS Service Health Dashboard and the Personal Health Dashboard, listing each one's scope, access requirements, use cases, and URL/location. The left box describes the global, public Service Health Dashboard and the right box describes the account-specific, authenticated Personal Health Dashboard.

Types of AWS Health Events

AWS Health events typically fall into these categories:
  • Service events — outages, API throttling, degraded performance.
  • Scheduled changes — instance retirements, planned maintenance windows.
  • Account notifications — billing alerts, quota increases/decreases, or account-specific advisories.
  • Other notifications — product launches, deprecations, and general announcements.
Personal Health Dashboard retains up to 90 days of historical events in the console, so consider archiving events if you need longer-term retention.
A slide titled "Types of AWS Health Events" showing four colored categories—Service Events, Scheduled Changes, Account Notifications, and Other Notifications—each with example items. Examples include EC2 API throttle, S3 outages, instance retirements, billing alerts, and product launches (with a note about 90 days of event retention).

Event Structure (example)

AWS Health events follow a consistent structure with fields such as eventTypeCode, eventTypeCategory, service, startTime, endTime, accountId, and affectedEntities. Below is a representative Health event JSON:
When delivered through EventBridge, Health events typically have a source of aws.health and a detail object that contains the fields shown above. Use that structure to design EventBridge rules and event patterns that match the right events for your automation or alerts.

EventBridge Integration

EventBridge receives AWS Health events by default in AWS commercial regions—no separate enablement step is required (this is a common exam distractor). Events are usually delivered within seconds. Create EventBridge rules that match Health events and route them to targets such as Lambda, SNS, SQS, Step Functions, or Systems Manager to implement notifications or automated remediation. Examples of practical EventBridge event patterns: Match any AWS Health event:
Match health events for EC2:
Match scheduled-change category events:
Match a specific eventTypeCode (e.g., EC2 instance retirement):
Match specific service, category, and region:
Use EventBridge to:
  • Trigger a Lambda for custom remediation (reboot, replace instance, adjust autoscaling).
  • Send a notification via SNS (email, SMS when using SNS + EventBridge).
  • Orchestrate multi-step responses with Step Functions.
  • Kick off Systems Manager automation runbooks.
A diagram titled "EventBridge Rule – Examples" showing Amazon EventBridge in the center routing events to AWS services (AWS Lambda, Amazon SNS, Amazon Step Functions, Amazon Systems Manager, and Amazon SQS). Each service has a short caption describing its role (e.g., running custom logic, delivering notifications, orchestrating workflows, executing automation, and asynchronous processing).

EventBridge Pattern Examples (quick reference)

Note: When creating rules, start with broader filters and iteratively narrow them to ensure you don’t miss events.

Permissions, API Access, and Organizations

Programmatic access to Personal Health Dashboard data via the AWS Health API requires a Business or Enterprise support plan. Developer and Basic support plans do not grant API access to Personal Health Dashboard data.
To call the Health API (e.g., DescribeEvents, DescribeEventDetails, DescribeAffectedEntities), your account must have Business or Enterprise support enabled.
For Organizations:
  • Use organization-scoped Health API actions (for example, health:DescribeEventsForOrganization and health:DescribeEventDetailsForOrganization) to aggregate and view events across member accounts.
  • Configure cross-account access and minimal IAM permissions to allow a centralized account to query organization-level Health events.
Permissions you’ll commonly grant for health automation:
A slide titled "Permissions and IAM Requirements" showing four blue rounded boxes with AWS Health IAM actions. The boxes list health:DescribeEvents (list health events), health:DescribeEventDetails (view event details), health:DescribeAffectedEntities (list affected resources), and health:DescribeEventsForOrganization (organization view).

Notification Capabilities and Targets

EventBridge rules can route Health events to many targets. Common choices:
  • Console: Personal Health Dashboard for interactive investigation.
  • EventBridge → SNS: Email/SMS push notifications (EventBridge triggers SNS).
  • Lambda: Run custom remediation or enrichment logic.
  • Step Functions: Orchestrate complex, multi-step incident response flows.
  • Systems Manager: Execute automation runbooks or create OpsCenter items.
  • SQS: Buffer events for asynchronous processing.
  • OpsCenter / ServiceNow integrations: Create incident tickets automatically.
  • Organizations: Aggregate and route member-account events to a centralized responder account.
A slide titled "Notification Capabilities" showing four colorful feature tiles: Console Notifications, EventBridge Routing, OpsCenter Integration, and Multi-Account View, each with a brief description. A small footer notes there is no native SMS and suggests using EventBridge + SNS for text alerts.

Use Cases and Incident Response

Common automation patterns triggered by Health events:
  • Proactive maintenance: automatically replace or drain EC2 instances scheduled for retirement.
  • Service disruption response: trigger failover, scale out, or change routing during AWS service degradations.
  • Security response: isolate compromised instances, rotate keys after credential-exposure notifications.
  • Capacity and quota monitoring: notify or throttle deployments when quota changes occur.
  • Audit and compliance: archive Health events to S3 for long-term retention and audit trails.
A presentation slide titled "Incident Response – Use Cases" showing four colored use-case boxes: Proactive Maintenance, Service Disruption Response, Security Event Response, and Capacity Planning. Each box has a short description (EC2 retirement automation, outage/failover management, credential rotation and security actions, and monitoring/automating quota changes).

Monitoring, Troubleshooting, and Best Practices

When validating Health-driven automation:
  • Test EventBridge rules with sample events from the Personal Health Dashboard — the console provides sample event payloads you can use.
  • Start with broader event patterns and iteratively narrow them to avoid missed detections.
  • Use SNS message filtering and structured message formats to reduce noise and avoid alert fatigue.
  • Archive event payloads to S3 (or a data lake) for forensic analysis beyond the console retention window.
  • Monitor EventBridge metrics and CloudWatch for rule invocations, failed invocations, and throttling.
  • Use CloudWatch Logs and AWS X-Ray for debugging Lambda or Step Functions workflows.
Always validate EventBridge event patterns and end-to-end automation in a test environment before deploying to production—overly restrictive patterns or JSON syntax errors are common reasons for missed events.
A presentation slide titled "Monitoring and Troubleshooting — Common Troubleshooting Issues" showing a flow from an orange "Root Cause" box to a green "Solution" box. It lists the root cause as incorrect event pattern syntax or overly restrictive filters, recommends testing patterns with sample events from the Health console, and suggests using EventBridge Sandbox and starting with broad patterns.
Recommended architectural pattern (example):
  • Health events → EventBridge rule → Lambda (custom logic)
  • Lambda may invoke Step Functions for complex orchestration
  • Step Functions or Lambda can publish to SNS for alerts, call Systems Manager runbooks, and archive events to S3
This flow can be linear or branch depending on the response logic, severity, and required human-in-the-loop steps.
A slide titled "Best Practices" showing five recommendation boxes (Enable Organizational View, Specific EventBridge Rules, SNS Message Filtering, Long-Term Event Archival, Test Automation Workflows). Below it is an architectural flow diagram from Health Event through AWS EventBridge, Lambda, Step Functions, SNS, Systems Manager to Amazon S3 (archive).

Integration With Other AWS Services

Common integrations that improve visibility and response:
  • Systems Manager OpsCenter: create incidents and link automation runbooks.
  • Security Hub: surface security-related AWS Health events into a consolidated dashboard.
  • CloudWatch: collect metrics and logs for event-driven functions and measure remediation success.
  • Service Catalog: gate or block deployments when certain Health events are active.
  • Cost Explorer / Billing tools: correlate billing or quota notifications with operational events.
A presentation slide titled "Integration With Other AWS Services" showing five colored boxes for Systems Manager OpsCenter, Security Hub, CloudWatch, Service Catalog, and Cost Explorer. Each box contains a short note describing how that service integrates with or responds to health and security events.

Comparison With Other Monitoring Services

Remember these distinct purposes when selecting tools: Use AWS Health for AWS-initiated incidents and timelines; use CloudWatch/CloudTrail/Config for customer-driven telemetry and auditing.
A slide titled "Comparison With Other Monitoring Services" showing a table that compares AWS services (AWS Health, CloudWatch, CloudTrail, AWS Config) across columns like Purpose, Data Source, Use When, and Cannot. It summarizes each service’s role, data sources, typical use cases, and limitations.
Thanks for reading. Further reading and references:

Watch Video