AWS · Reliability & Scaling
Multi-Region High Availability & DR
Cross-region active/passive failover with Route 53 DNS routing, primary and secondary VPCs, and database replication. This diagram is written in ArchLex and passes AWS provider checks.
Diagram and source
provider aws
direction LR
validation normal
account global-core {
region us-east-1 {
vpc primary-vpc {
subnet app-subnet-1 {
app_primary: ecs
db_primary: rds
cache_primary: elasticache
app_primary > cache_primary
app_primary > db_primary
}
}
}
region us-west-2 {
vpc failover-vpc {
subnet app-subnet-2 {
app_secondary: ecs
db_replica: rds
app_secondary > db_replica
}
}
}
}
global_dns: route53
global_dns -[routes]->|primary| app_primary
global_dns -[routes]->|failover| app_secondary
db_primary -[replicates]-> db_replicaWhat is in this diagram.
Resources
- app_primary Amazon ECS
- db_primary Amazon RDS
- cache_primary Amazon ElastiCache
- app_secondary Amazon ECS
- db_replica Amazon RDS
- global_dns Amazon Route 53
Relationships
- app_primary connects cache_primary
- app_primary connects db_primary
- app_secondary connects db_replica
- global_dns routes app_primary
- global_dns routes app_secondary
- db_primary replicates db_replica
Boundaries
- account global-core
- region us-east-1
- region us-west-2
- vpc primary-vpc
- vpc failover-vpc
- subnet app-subnet-1
- subnet app-subnet-2
Render it yourself.
Save the source as multi-region-dr.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.
npx @archlex/cli render multi-region-dr.arch --output multi-region-dr.svgRelated examples.
- Kubernetes Autoscaled Resilient APIService and Deployment protected by horizontal autoscaling and a disruption budget
- Cloudflare AWS/GCP Origin SteeringPreferred AWS and fallback GCP origin intent, without asserting verified health or steering policy
- Minimal Vertical SliceRDS Proxy, RDS Database, and ECS Service
- Display Labels & Named InstancesInstance names and custom display labels distinguishing primary and replica databases