Expect the unexpected: Building resilience with AWS
summary
Claims an automated DR system that reduces RTO from weeks to minutes and cuts DR ops overhead ~50% by orchestrating failover and failback across regions. It uses Step Functions and Lambda, integrates with CI/CD to pre-provision networking, identity and tooling, and supports backup/restore, pilot‑light and warm‑standby patterns. CloudWatch/CloudTrail record timings for audits. Multiple client deployments report it is customizable, scalable, and turns multi‑region recovery from a manual months‑long exercise into repeatable minutes.
AI-written summary · about
chapters (9)
- 0:00Introduction and agenda
- 1:29Why resilience matters
- 3:14AWS resilience pillars
- 5:40Shared responsibility model
- 6:24PWC’s resilience journey
- 8:08Multi-region design considerations
- 10:17Pre-recovery steps
- 11:20DR Orchestrator solution
- 13:52Q&A and conclusion
related talks
41mResiliency and data residency
47mBuilding Resilience
32mDisaster recovery strategies for increased resiliency
14mDisaster Recovery preparedness
56mSelf-service disaster recovery for AWS with Druva
19mPreparing for disaster: going Multi-Region
26mA proactive approach to resilience in modern apps
41mWays to optimize Cloud Disaster Recovery cost