Building Resilience
summary
Case study of OwnID’s DRP delivers concrete choices: RPO 10s and RTO 20 minutes, implemented as a pilot‑light/near‑warm standby using Terraform modules, GitHub Actions for dual-region CD, RDS cross‑region read replica promoted on failover, secret replication and dual S3 buckets (deployed from CI) while Redis session cache is intentionally not replicated. Route53 DNS health checks + pre‑provisioned CloudFront distributions avoid control‑plane failures; synthetic tests run twice daily against a writable test DB to validate the plan and keep the DR environment healthy.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:31Why disaster recovery matters
- 6:08Business impact analysis
- 11:55Active vs passive DR strategies
- 15:35Filtering DR scope
- 16:58High-level DR architecture
- 19:31Handling data components
- 26:02Global services pitfalls
- 31:04Terraform implementation
- 34:21Documenting execution plan
- 35:04Maintaining DR environment
- 36:53Testing resilience tools
- 40:04Key takeaways summary
- 43:18Q&A session
related talks
14mExpect the unexpected: Building resilience with AWS
55mEngineer application resilience with compliance in mind
41mResiliency and data residency
14mDisaster Recovery preparedness
48mRTO & RPO – Best Practices in Hybrid Architectures
42mImplementing resiliency with Cloud Operations
25mData protection design for business continuity
41mWays to optimize Cloud Disaster Recovery cost