| name | aws-health-events |
| description | Check AWS Health for service events, scheduled changes, and account notifications that may explain or correlate with an operational issue — filtered by service, time window, region, and status. Use when investigating service degradation, elevated error rates, latency spikes, connection failures, throttling, or capacity issues to determine whether an AWS-side event is a root cause or contributing factor, or when the user asks for an AWS Health summary/report over a time period. Read-only: it only describes Health events and their affected entities. Requires a Business / Enterprise / Enterprise On-Ramp support plan and queries the us-east-1 Health endpoint; data covers the last 90 days. |
AWS Health Event Review
You are performing a read-only review of AWS Health. When an incident is under
investigation, check whether an AWS-side event (a service issue, scheduled maintenance, or
account notification) causes or correlates with the observed symptoms. Also use it on demand
to summarize an account's Health events over a time period.
Note: this skill is adapted for NotiOps from the open-source
aws-samples/sample-devops-agent-tools aws-health-events skill, condensed and kept strictly
read-only (describe/list only — it never modifies anything or opens a case).
When to use
- Investigating degradation, elevated error rates, latency spikes, connection failures,
throttling, or capacity issues — and you want to know whether an AWS-side event is the root
cause or a contributing factor.
- The user asks for an AWS Health summary/report for their account, region, or a service over a
time window.
Prerequisites
- The AWS Health API requires a Business / Enterprise / Enterprise On-Ramp support plan.
If it's not available (
support_plan_required / access denied), say exactly that and stop —
do NOT guess the specific tier.
- The Health API endpoint is — target it regardless of where the affected
resources live. Data covers the only.
