AWS Architecture Blog·July 16, 2026Prioritized AWS Health Alerts with User Notifications and EventBridge
This article outlines an AWS solution for prioritizing and routing AWS Health alerts using AWS User Notifications and Amazon EventBridge. It addresses the common operational challenge of alert fatigue by filtering non-critical events and separating urgent issues from informational updates, improving response times for critical incidents.
Read original on AWS Architecture BlogOperating critical workloads on AWS requires diligent monitoring of AWS Health events, which range from operational issues to scheduled maintenance and deprecation notices. The challenge lies in the undifferentiated stream of these notifications, making it difficult for operations teams to quickly identify and respond to truly urgent events without being overwhelmed by noise.
Solution Architecture for Prioritized Alerting
The proposed solution employs a two-layer filtering and prioritization strategy for AWS Health events:
- Filtering Layer: Event rules are configured to match AWS Health events exclusively for services critical to the organization (e.g., AWS Direct Connect, Amazon Connect, Amazon RDS). All other events are suppressed.
- Prioritization Layer: Remaining events are categorized into two tiers using AWS User Notifications configurations:
- CRITICAL: Matches events with `eventTypeCategory` as `issue` or `scheduledChange`. These are delivered immediately as individual notifications.
- INFORMATIONAL: Catches all other events (e.g., `accountNotification`). These are batched within a five-minute window and delivered as grouped summaries.
Infrastructure as Code
The entire solution is deployable via a single AWS CloudFormation template, supporting different deployment modes for single accounts or organization-wide scope, and offering optional custom email formatting via Amazon SNS and EventBridge.