What problem does it solve?
Setting up AWS Resilience Hub v2 for the first time involves many ordered API calls — creating resilience policies with SLO targets, registering systems and user journeys, onboarding services with input sources, and running failure mode assessments — and mistakes in sequencing or parameters cause failed assessments and confusing errors.
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 recommendations from the SEEMS failure-category framework.
- Security guardrails: Enforces least-privilege invoker roles, confused-deputy condition keys, and SSE-KMS/TLS recommendations for Terraform state and report S3 buckets.
- 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 see whether the architecture can meet those targets.
Quick Start
Ask the agent to set up AWS Resilience Hub v2 for your service with a specific availability target, RTO/RPO values, and an input source such as a CloudFormation stack ARN.
