skills.rest
aws
awsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

aws-resilience-lifecycle

Orchestrates the AWS resilience lifecycle across Resilience Hub v2, FIS, and Application Recovery Controller.

2.5k|282|Updated Apr 23, 2026
Search Tags:#AWS#chaos engineering#fault injection#Resilience#Disaster Recovery#fis#resilience hub
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-resilience-lifecycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-resilience-lifecycle
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/resilience-skills/aws-resilience-lifecycle
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-resilience-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams struggle to connect resilience policy definition, fault-injection testing, and operational recovery controls into one coherent program, often marking findings resolved without proving fixes work. This Skill guides the end-to-end Define → Test → Operate workflow so resilience findings are validated with real experiments before closure.

Core Features & Use Cases

  • Integrated Lifecycle Orchestration: Sequences Resilience Hub v2 (NGRH) policy creation and failure-mode assessment, FIS experiment validation, and ARC routing controls and zonal autoshift into a gated workflow.
  • Hallucination-Resistant API Reference: Provides canonical AWS CLI operations for resiliencehubv2, fis, route53-recovery-control-config, and arc-zonal-shift, with a table of common wrong API names mapped to correct ones.
  • Validation-First Finding Resolution: Enforces that NGRH findings are marked RESOLVED only after an FIS experiment confirms recovery within RTO/RPO targets, preventing paper compliance.
  • Use Case: A platform team wants to know if they are "done" after resolving Resilience Hub findings. The Skill walks them through validating each fix with a fault-injection experiment, then setting up ARC routing controls and zonal autoshift for ongoing operational resilience.

Quick Start

Ask the agent to guide you through the full AWS resilience lifecycle for your service, from creating a Resilience Hub policy through FIS experiment validation to ARC operational controls.

Frequently Asked Questions about aws-resilience-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an end-to-end resilience program on AWS?▼

Follow the Define, Test, Operate lifecycle: create a Resilience Hub v2 policy and run a failure-mode assessment, validate untested findings with FIS experiments, then configure ARC routing controls and zonal autoshift. This Skill sequences and gates each phase while delegating mutations to companion skills.

How do I validate Resilience Hub findings before marking them resolved?▼

Run an FIS experiment that reproduces the failure mode and confirm the system recovers within its RTO/RPO objectives before calling update-failure-mode-finding with status RESOLVED. Marking findings resolved without fault-injection validation is paper compliance, not proven resilience.

What is the correct AWS CLI command to start a Resilience Hub v2 assessment?▼

Use aws resiliencehubv2 start-failure-mode-assessment with the --service-arn parameter. All v2 assessment operations include failure-mode in the name, so commands like start-assessment or list-findings do not exist and will fail.

Which FIS action should I use to simulate an AZ or region failure?▼

For AZ failure, use aws:ec2:terminate-instances filtered by AZ or aws:ecs:drain-container-instances; for regional service unavailability, use aws:fis:inject-api-unavailable-error. Always verify current action IDs with aws fis list-actions since FIS actions change over time.

When should I not use this resilience lifecycle skill?▼

Do not use it to remediate a single specific finding, which belongs to the failure-mode assessment skill, or when one service is explicitly named, such as asking only which FIS experiment to run. It is designed for the integrated multi-service lifecycle, not isolated tasks.

Can I run FIS experiments in production safely?▼

Yes, but treat fault injection as a privileged, potentially destructive operation requiring change-management authorization. Every experiment must have CloudWatch alarm stop conditions to bound blast radius, a least-privilege execution role, and explicit user confirmation before starting.

Related Skills

Explore More Software Engineering Skills→
librefanglibrefang
10

aws

Architect and deploy AWS infrastructure using CloudFormation, CDK, and the AWS CLI.

Official
Advanced
orqesaorqesa

investor_reporting

Establish monthly investor updates, KPI dashboards, and quarterly board decks.

Official
Intermediate
itsmostafaitsmostafa
1.1k

cloudwatch

Automate AWS CloudWatch monitoring setup for logs, metrics, alarms, and dashboards.

Community
Intermediate
amadeus-dlcamadeus-dlc
5

amadeus-environment-provisioning

Runs the environment-provisioning stage in isolation without advancing the main workflow.

Official
Advanced