AWS Podcast #739: Applying Multi-region Strategies on AWS
Sep 29, 2025
Join Jeff Ferris, AWS's resilience tech lead, and Scott Wainstock, a senior software development manager, as they dive into multi-region strategies. They discuss the prerequisites for adopting these strategies and highlight the importance of regional isolation. Hear about the challenges in operational readiness and building a culture of resilience, like the use of blameless reviews. Scott shares insights on the new Region Switch service that streamlines multi-region recovery, offering templates and guidance for startups to enhance their recovery planning.
AI Snips
Chapters
Transcript
Episode notes
Validate Multi-AZ First
- Do not adopt multi-region before you master multi-AZ in a single region and validate your operational practices.
- Only go multi-region when driven by business needs like compliance or latency, not because it exists.
Preserve Regional Isolation
- Multi-region requires strict logical and physical isolation to preserve availability benefits.
- Design so your stacks can stand alone and avoid architectures that negate regional separation.
Document Recovery Steps And Data Strategy
- Build a runbook that lists all recovery steps, dependencies, and startup order for cross-region failover.
- Decide and document your data replication strategy (synchronous vs asynchronous) and account for latency and consistency trade-offs.