Every architecture review with a compliance checkbox that says "multi-region" eventually produces the same slide: two regions, an arrow between them, and the word active-active in bold. The slide is fine. What the slide hides is that Netflix needed three years, a custom DNS control plane, and a purpose-built cache invalidation protocol to make active-active real — and that was for a workload (video streaming) whose data model is unusually forgiving. Stripe, whose data model is the least forgiving thing in the industry (money), still runs a single write region per shard set and spends its multi-region engineering on movement rather than multi-master writes.

This guide is the pattern catalog behind the slide: what active-active actually requires, the four patterns that have shipped at scale, what they cost at 2026 prices, and — most importantly — the decision tree for when active-passive with a fast data layer, or plain pilot light, is the honest answer.

First, the vocabulary: active-active is an RTO story, not a downtime story

The current AWS Well-Architected Reliability Pillar (REL13-BP02) orders multi-Region disaster recovery strategies by increasing cost and decreasing recovery objectives:

StrategyRPORTORecovery Region runsThe honest description
Backup and restoreHours (PITR can reach ~5 min)≤ 24 hoursNothing until disasterYou redeploy from IaC and restore data. Cheap, slow, rarely tested.
Pilot lightMinutesTens of minutesCore data services onlyDatabase and object storage are live and replicating; compute is a template.
Warm standbySecondsMinutesA scaled-down full stackEverything is running, small. Recovery is "scale up and shift traffic."
Multi-Region active-activeNear zeroPotentially zeroThe full workload, both/all regionsNo "recovery" event at all — but only if your data layer can accept writes in multiple regions without corrupting itself.

Read the RPO column carefully. The pillar's own note is the most under-read sentence in the entire DR literature: "Data replication is useful for data synchronization and will protect you against some types of disaster, but it will not protect you against data corruption or destruction unless your solution also includes options for point-in-time recovery." An active-active database happily replicates your DELETE bug to every region in about half a second. That is not a footnote — it is the reason Stripe's write path is single-master and why we will spend most of this guide on the data tier.

The availability arithmetic that motivates the whole exercise, at 2026 prices:

99.9%   ->  525.60 min/year   (8.8 hours)
99.99%  ->   52.56 min/year   (under an hour)
99.999% ->    5.26 min/year   (one bad deploy, twice a year
                               ... maybe)