A Pragmatic Multi-Region Strategy for Small Teams
Last reviewed . Tool versions and defaults may have changed since, so check the commands against current docs.
How a small team moved from single-region risk to a simple active/passive multi-region setup without doubling complexity.
On this page
Multi-region can easily become a science project. This is what worked for a five-person platform team supporting a SaaS product.
Starting Point: Single Region, Shared VPC
We began with everything in one AWS region: RDS, EKS, S3, and a shared VPC.
- RTO/RPO were theoretical.
- Failover docs existed, but no one had run them end-to-end.
Step 1: Read Replicas and S3 Replication
- Added a read replica of RDS in a second region.
- Enabled S3 cross-region replication for critical buckets.
- Agreed on an RPO of 15 minutes.
Step 2: Terraform Modules for Two Regions
Instead of cloning the entire stack, we:
- Created a region-aware module for shared resources.
- Used workspaces to differentiate primary vs secondary.
```hcl module "vpc" { source = "./modules/vpc" region = var.region primary = var.is_primary } ```
Step 3: DNS and Runbooks
- Used Route53 failover records with health checks on a lightweight
/healthzendpoint. - Wrote an explicit runbook:
- who can declare a disaster,
- which Terraform workspaces to apply,
- how to flip DNS and confirm.
We didn’t solve every theoretical edge case, but we can now lose a region and recover in under an hour with a plan the team has actually rehearsed.
Cite this article
Kiril Urbonas (2025). A Pragmatic Multi-Region Strategy for Small Teams. DevOpsNess. https://www.devopsness.com/blog/a-pragmatic-multi-region-strategy-for-small-teams
[A Pragmatic Multi-Region Strategy for Small Teams](https://www.devopsness.com/blog/a-pragmatic-multi-region-strategy-for-small-teams) (Kiril Urbonas, DevOpsNess, 2025-03-04)
More from Cloud
Explore more articles in this category
.NET 8 Support Ends November 10: The Lambda and Azure Functions Checklist
.NET 8, .NET 9, the Lambda dotnet8 runtime and the Azure Functions in-process model all lose support on November 10, 2026. Inventory commands, the isolated-worker migration and a CI gate.
Google Cloud's europe-west2 Outage: One Zone Lost Power and the Region Stalled for 6 Hours
On October 20, 2026, europe-west2-b lost power when its generators never started. Cross-zone control-plane timeouts then degraded the whole London region. What happened and the gcloud audit to run now.
Lambda Python 3.10 Is Deprecated Today: Find Every Function and Move to 3.13
AWS deprecated the Lambda python3.10 runtime on October 31, 2026. Functions keep running, patches stop. The inventory commands, IaC diffs and AL2023 gotchas for moving to python3.13.
You might have missed
Evergreen posts worth revisiting.