AWS Health: Account & Service Events

AWS Health separates public service status from events that affect your account

AWS Health communicates events about AWS services, resources and planned changes. Public service events describe broader AWS service conditions and can be viewed without an account through the public Service health experience. Signed-in account health adds account-specific events that can identify services or resources affected in your environment. That personalization is the important difference: a regional service issue is general awareness, while an account-specific event can tell an operator that a particular resource needs attention.

Health events carry structured attributes including service, event type code, category, status, Region and scope. Current AWS Health EventBridge schemas include categories such as issue, accountNotification, investigation and scheduledChange, and statuses such as open, closed and upcoming. Planned lifecycle events can provide advance notice of changes such as version retirement or required resource action, turning the dashboard into an operations planning input rather than only an outage page.

Affected resources and organization view make Health actionable at scale

Account events can include an affected-resources view, helping an operator move from 'AWS reports a condition' to 'these resources in this account are impacted.' The signed-in Health event log currently provides a rolling historical view, while unresolved planned lifecycle events have separate documented behavior. For long-term operational records, teams should route important events into their own incident, notification or archival workflows rather than assuming the console is a permanent event store.

AWS Health integrates with AWS Organizations through organizational view. Once enabled, the management account or a registered delegated administrator can receive a centralized feed of Health events for member accounts. This is especially valuable for platform teams that manage hundreds of workload accounts: central operators can see cross-account impact while workload teams continue to receive events locally.

EventBridge turns Health notifications into operational workflows

AWS Health emits events to Amazon EventBridge, allowing rules to match event attributes and route them to supported targets. An organization might notify an operations channel for planned lifecycle events, open an IT service-management item for affected production resources, or start an automation when a specific event type is received. Event-driven handling avoids relying on an engineer to repeatedly refresh the Health dashboard during an incident or maintenance window.

The AWS Health API offers programmatic access to Health information, but entitlement is tied to current AWS Support-plan requirements. AWS documentation in 2026 lists Business Support+, Enterprise Support and Unified Operations for API access. Because support plans and feature entitlements can change, automation designs should verify current plan requirements rather than treating a certification-era support-plan name as permanent.

• Use the public Service health view for broad AWS service conditions and signed-in account health for personalized impact.
• Organizational view aggregates member-account events for central operations.
• Use EventBridge when Health events should automatically notify people or trigger workflows.