Skip to main content
In this lesson we’ll explore AWS Resilience Hub — a centralized service for defining, assessing, testing, and improving the resilience and disaster recovery posture of applications running on AWS. Resilience Hub helps you translate business recovery targets (RTO/RPO) into actionable infrastructure changes, tests, and runbooks. What is a disaster?
  • Any event that causes significant loss of operation, data, or functionality in your cloud environment.
  • Causes include natural disasters (earthquake, flood), system failures, misconfiguration, human error, or deliberate attacks (DDoS, intrusion).
  • Business impact: data loss, reduced availability, security exposure, and disruption to continuity.
A side-by-side "Resilience Hub" diagram of AWS accounts showing resources in two regions (us-east-1 and ap-south-1) before and after a disaster. The "after" panel highlights failures in the ap-south-1 region with red warning icons.
To reduce these risks, follow the AWS Well-Architected Framework and implement a documented disaster recovery plan. Common mitigations include:
  • Regular backups and immutable snapshots.
  • Multi-AZ and multi-region deployments for critical services.
  • Strong security controls and least-privilege IAM.
  • Automated monitoring, alerting, and runbooks for recovery.
Useful references:
Recovery Point Objective (RPO) is the maximum acceptable age of the data you can tolerate losing. Recovery Time Objective (RTO) is the maximum amount of time allowed to restore a business process after a disruption. Use these to set measurable resilience targets.
A slide titled "Resilience Hub" showing a timeline of an incident with markers for RPO (left) and RTO (right), and labels for "Data loss" and "Downtime" around a central cloud recovery icon and a hazard symbol. The horizontal axis is time and the vertical axis indicates a return to normal operation.
How AWS Resilience Hub works (overview)
  1. Describe your application and the resources to protect.
  2. Attach resiliency policies (set RTO/RPO and disruption-specific targets).
  3. Run automated assessments to identify gaps and dependencies.
  4. Implement remediation (infrastructure, alarms, backups, runbooks).
  5. Test and validate recovery with controlled experiments.
  6. Continuously monitor, re-assess, and improve.
Describing an application You can provide Resilience Hub with the resources that make up your application in several ways:
A screenshot of an "Step 1: Describe the Application and Resources" screen (AWS Resilience Hub) showing an "Application structure" panel. It displays selectable options like CloudFormation stacks (selected), Resource groups, AppRegistry, Terraform state files, and Existing application.
Assessment and resiliency policies
  • After the application is defined, Resilience Hub analyzes resource relationships and failure domains (AZ vs region).
  • Attach a resiliency policy to set targets for different disruption types (for example: AZ outage vs regional outage).
  • Run an assessment that evaluates your application against the policy and returns a scored report.
What the assessment report provides:
  • Pass/fail scoring for resiliency objectives and an overall resilience score.
  • Affected resources and dependency paths that impact recovery.
  • Concrete recommendations: configuration changes, alarms to add, test plans, and SOPs.
A slide titled "Step 2: Define and Assess" showing three colored circular icons and labels: Define Resilience Policies (purple, document icon), Run Assessments (orange, play icon), and Review Assessments (green, magnifying-glass with pulse icon).
Iterate to improve
  • Implement the recommended changes (infrastructure updates, monitoring, backups, runbooks).
  • Re-run assessments to verify the improvements and close gaps.
  • Repeat periodically or after significant changes to application architecture.
Testing and validation Resilience Hub supports controlled resilience testing to validate recovery procedures and measure actual RTO/RPO. Typical integrations:
  • AWS Fault Injection Simulator (FIS) to execute fault scenarios.
  • Amazon CloudWatch to monitor and trigger alarms.
  • AWS Systems Manager and Step Functions to automate recovery steps and runbooks.
Key features and benefits Best practices
  • Define realistic RTO and RPO based on business impact and cost trade-offs.
  • Use automation to remediate common issues and to run repeatable tests.
  • Maintain up-to-date runbooks and SOPs linked to Resilience Hub recommendations.
  • Integrate resilience testing into your CI/CD pipeline for frequent validation.
Links and references

Watch Video