aws-health-events
ALWAYS use this skill in the beginning of any incident investigation, root cause
aws · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add aws/tools-for-devops-agent --skill aws-health-events技能说明
name: aws-health-events description: ALWAYS use this skill in the beginning of any incident investigation, root cause analysis, or operational troubleshooting. This skill retrieves and analyzes AWS Health events (service issues, scheduled changes, and account notifications) to identify AWS-side events that may explain or correlate with observed operational issues. Activate this skill when investigating an issue and you observe service degradation, elevated error rates, latency spikes, connection failures, throttling, capacity issues, deployment-related failures, alarms, or any operational event or issue. This skill searches AWS Health events by service, time window, region, and status to surface active or recent service disruptions, scheduled maintenance, and account-specific notifications that inform the current investigation. Also activate when a user requests a health event summary or report for their account over a specified time period. metadata: author: udid-aws version: "1.0.0" aws-devops-agent-skills.agent-types: "Chat tasks, Incident RCA" aws-devops-agent-skills.aws-services: "AWS Health" aws-devops-agent-skills.technical-domains: "Operations"
AWS Health Event Review
Use this skill when investigating an incident and you need to check for AWS-side service events that may be causing or contributing to the observed issue. Also use this skill when a user requests a summary report of AWS Health events over a configurable time period.
When to Use This Skill
Incident Investigation (automatic activation):
- An active incident may be caused by an AWS service disruption or degradation.
- You observe service degradation, elevated error rates, latency spikes, connection failures, throttling, or capacity issues.
- You need to determine whether an AWS-side event is the root cause or a contributing factor to the current incident.
- You want to correlate observed symptoms with known AWS Health events.
Chat Reporting (on-demand activation):
- A user requests a health event summary or report for their account.
- A user wants to review the health posture of their AWS environment over a specific time period.
- A user asks about recent AWS service issues affecting their account or region.
Prerequisites
- The account must have an AWS Business Support+, Enterprise Support, or Unified Operations support plan to access the AWS Health API.
- The agent must have permissions to call the following IAM actions:
health:DescribeEventshealth:DescribeEventDetailshealth:DescribeAffectedEntitieshealth:DescribeEventTypes
- The AWS Health API is only available in the us-east-1 region. All API
calls must target the
us-east-1endpoint regardless of where the affected resources are located. - Health event data is available for up to 90 days. Events older than 90 days cannot be retrieved via the API.
Step 1: Gather Incident Context
Before searching Health events, extract key details from the current incident:
- Affected AWS services — identify the service(s) experiencing issues (e.g., EC2, RDS, Lambda, ELB, ECS).
- Timeframe — determine when the incident started and its current duration. Use ISO 8601 timestamps.
- Affected resources — collect specific resource identifiers (instance IDs, ARNs, endpoint names, cluster names).
- Region and availability zone — identify the AWS region and, if known, the specific availability zone(s) affected.
- Symptoms — note the observed symptoms (latency spikes, 5xx errors, connection timeouts, throttling, capacity errors).
Use these details as filter criteria in subsequent steps.
Step 2: Search Health Events
Use the AWS Health API DescribeEvents operation to retrieve events matching
the incident context. All calls must target the us-east-1 endpoint.
API call pattern
aws health describe-events \
--region us-east-1 \
--filter '{
"services": ["<SERVICE_CODE>"],
"startTimes": [{"from": "<ISO-8601-start>"}],
"regions": ["<affected-region>"],
"eventStatusCodes": ["open", "closed"],
"eventTypeCategories": ["issue", "scheduledChange", "accountNotification"]
}' \
--max-results 100
Filtering strategies
| Strategy | How to Apply |
|---|---|
| By service | Use the services filter with the AWS Health service code (e.g., EC2, RDS, ELASTICLOADBALANCING), because service-specific events are most likely to correlate with the incident. |
| By time range | Use startTimes with a from value set to 7 days before the incident start, because events that started before the incident may still be active and causing impact. |
| By region | Use the regions filter to scope events to the affected region, because regional events are more likely to impact the specific resources under investigation. |
| By availability zone | Use the availabilityZones filter when the incident is isolated to a specific AZ, because AZ-scoped events have the highest correlation with AZ-specific failures. |
| By status | Include both open and closed statuses, because recently closed events may have caused residual impact that is still being observed. |
| By event scope | Include both ACCOUNT_SPECIFIC and PUBLIC events, because public service events affect all accounts in the region while account-specific events target your resources directly. |
Pagination handling
- Follow the
nextTokenfrom each response to retrieve subsequent pages. - Continue paginating until
nextTokenis null or a maximum of 500 events have been collected. - Set
maxResultsto 100 per page for efficient retrieval.
Step 3: Filter Relevant Events
Before retrieving full event details, filter the events returned in Step 2 to
identify only those relevant to the current investigation. This avoids
unnecessary DescribeEventDetails calls for events that are clearly unrelated.