AWS devopsagent documentation change
Summary
Added new 'Example: Incident filtering skill' section showing how to automatically skip low-priority incidents during maintenance windows
Security assessment
The new incident filtering example focuses on operational efficiency during maintenance, not security vulnerabilities or security features. No security-related content was added or modified.
Diff
diff --git a/devopsagent/latest/userguide/about-aws-devops-agent-devops-agent-skills.md b/devopsagent/latest/userguide/about-aws-devops-agent-devops-agent-skills.md index 088fb49cc..4fbd3ff94 100644 --- a//devopsagent/latest/userguide/about-aws-devops-agent-devops-agent-skills.md +++ b//devopsagent/latest/userguide/about-aws-devops-agent-devops-agent-skills.md @@ -7 +7 @@ -What are SkillsWhy use SkillsHow Skills workSkill structureExample: Complete skillCreating SkillsManaging SkillsMigrating from Runbooks +What are SkillsWhy use SkillsHow Skills workSkill structureExample: Complete skillExample: Incident filtering skillCreating SkillsManaging SkillsMigrating from Runbooks @@ -170,0 +171,28 @@ The following example shows a complete, well-formed skill for investigating RDS +## Example: Incident filtering skill + +Skills targeted to the **Incident Triage** agent type can define criteria for automatically skipping incidents. Use this to filter incidents that don't require investigation. When a new incident matches the skip criteria, AWS DevOps Agent marks it as **Skipped**. The system provides a reason explaining why it was filtered. + +The following example shows a skill that skips low-priority incidents during scheduled maintenance: + +**SKILL.md:** + + + --- + name: skip-scheduled-maintenance + description: Skip low-priority incidents during a scheduled maintenance window. + Use this skill to automatically filter MEDIUM and LOW severity alarms that + fire during planned maintenance, avoiding unnecessary investigations for + expected disruptions. + --- + + # Skip Scheduled Maintenance + + Skip all incidents that meet BOTH of the following criteria: + + 1. The incident arrived between **2025-03-15 02:00 UTC** and **2025-03-15 06:00 UTC** + 2. Severity is MEDIUM or LOW + + Do NOT skip HIGH or CRITICAL severity incidents, even during the maintenance window. + +When you create this skill, select **Incident Triage** as the agent type. This ensures the skill is only evaluated during the triage phase. +