resilience-hub-getting-started

Configures AWS Resilience Hub v2 policies, systems, services, and failure mode assessments.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/dennisvink/yolomancer --skill resilience-hub-getting-started-dennisvink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resilience-hub-getting-started
Source: https://github.com/dennisvink/yolomancer/tree/main/skills/aws/specialized-skills/resilience-skills/resilience-hub-getting-started
Command: npx skills add https://github.com/dennisvink/yolomancer --skill resilience-hub-getting-started-dennisvink

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up AWS Resilience Hub v2 for the first time involves a long sequence of interdependent API calls — creating resilience policies with SLO targets, registering systems and user journeys, onboarding services with input sources, and running failure mode assessments — where a single misconfigured parameter or missed step breaks the workflow. ## Core Features & Use Cases - Guided end-to-end setup: Walks through a 10-step procedure covering policy creation with availability/RTO/RPO targets, system and user journey registration, service onboarding with invoker IAM roles, and input source configuration (CloudFormation stacks, resource tags, Terraform state, or EKS clusters). - Failure mode assessment execution: Starts asynchronous assessments, polls for completion, and presents findings grouped by severity with infrastructure, observability, and testing recommendations. - Security and troubleshooting guidance: Enforces least-privilege invoker roles, confused-deputy condition keys, SSE-KMS encryption for Terraform state and reports, and diagnoses common issues like stuck assessments or NOT_ACHIEVABLE results. - Use Case: A platform engineer wants to onboard a tier-1 checkout service with a 99.99 availability SLO and 5-minute RTO, then run a first failure mode assessment to identify single points of failure before a launch review. ## Quick Start Set up AWS Resilience Hub v2 for my checkout-api service with a 99.99 availability target, 5-minute multi-AZ RTO, and a CloudFormation stack as the input source, then run a failure mode assessment.

Frequently Asked Questions about resilience-hub-getting-started

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

FAQPage Schema
How do I get started with AWS Resilience Hub v2?

Follow the guided setup procedure: create a resilience policy with availability and RTO/RPO targets, create a system and user journey, register your service with an invoker IAM role, add input sources, then start a failure mode assessment. Each step uses the resiliencehubv2 AWS CLI commands or the AWS MCP server.

How do I create a resilience policy with RTO and RPO targets?

Run aws resiliencehubv2 create-policy with --availability-slo, --multi-az, and optionally --multi-region parameters specifying rtoInMinutes, rpoInMinutes, and a disasterRecoveryApproach such as ACTIVE_ACTIVE or HOT_STANDBY. Omit the multi-region flag entirely if you have no multi-region targets.

What input sources does AWS Resilience Hub v2 support?

Resilience Hub v2 supports four input source types: CloudFormation stack ARNs, resource tags, Terraform state files in S3, and EKS clusters with namespaces. You must add at least one input source before running a failure mode assessment.

Why is my Resilience Hub assessment stuck in IN_PROGRESS?

Assessments run asynchronously and typically take around 10 minutes, longer for large services. If stuck beyond 30 minutes, check the errorCode field — common causes are INVALID_PERMISSIONS or CMK_ACCESS_DENIED on cross-account roles — and verify input sources point to valid resources.

What does NOT_ACHIEVABLE mean in a Resilience Hub assessment?

NOT_ACHIEVABLE means your current architecture cannot meet the policy's SLO targets. You must make infrastructure changes such as adding redundancy or multi-region deployment before testing, since FIS experiments cannot fix a fundamentally insufficient architecture.

Does this skill cover FIS experiments or ARC routing controls?

No. The skill covers Resilience Hub v2 setup, policies, service onboarding, and failure mode assessments only. AWS Fault Injection Service experiments and Application Recovery Controller routing controls are explicitly out of scope.