CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/DevOps & SRE

πŸ› οΈ DevOps & SRE Β· Network

Multi-Region Active-Active Network

A network layout for running an application in two regions at once, with global load balancing, private links between regions and replicated databases.

More DevOps & SRE templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Users are routed to the nearest healthy region
  • Regions connect over a private backbone, not the internet
  • Databases replicate both ways

Prompt used

Network for a multi-region active-active setup: a global load balancer with health checks routes users to Mumbai or Singapore. Each region has a VPC with public subnets for load balancers and private subnets for app servers and databases. The two VPCs are connected with a transit gateway peering. Aurora Global Database replicates between regions and Redis uses active-active replication. Label each link.

Mermaid code
flowchart TD
subgraph ext_grp["Internet"]
glb["Global Load Balancer"]
end
subgraph mum_vpc["Mumbai VPC"]
subgraph mum_pub["Public Subnet 10.1.1.0/24"]
mum_alb["Mumbai Application Load Balancer"]
end
subgraph mum_priv_app["Private App Subnet 10.1.2.0/24"]
mum_app["Mumbai App Servers"]
end
subgraph mum_priv_db["Private DB Subnet 10.1.3.0/24"]
mum_aurora["Aurora Primary DB"]
mum_redis["Mumbai Redis Node"]
end
end
subgraph sg_vpc["Singapore VPC"]
subgraph sg_pub["Public Subnet 10.2.1.0/24"]
sg_alb["Singapore Application Load Balancer"]
end
subgraph sg_priv_app["Private App Subnet 10.2.2.0/24"]
sg_app["Singapore App Servers"]
end
subgraph sg_priv_db["Private DB Subnet 10.2.3.0/24"]
sg_aurora["Aurora Secondary DB"]
sg_redis["Singapore Redis Node"]
end
end
subgraph backbone["AWS Transit Gateway"]
tgw_peering["Transit Gateway Peering"]
end
glb -->|"HTTPS 443 with Health Checks"| mum_alb
glb -->|"HTTPS 443 with Health Checks"| sg_alb
mum_alb -->|"HTTP 8080"| mum_app
sg_alb -->|"HTTP 8080"| sg_app
mum_app -->|"PostgreSQL 5432"| mum_aurora
mum_app -->|"Redis 6379"| mum_redis
sg_app -->|"PostgreSQL 5432"| sg_aurora
sg_app -->|"Redis 6379"| sg_redis
mum_aurora <-->|"Aurora Global Database Replication"| sg_aurora
mum_redis <-->|"Active-Active Replication via TGW"| tgw_peering
tgw_peering <-->|"Active-Active Replication via TGW"| sg_redis

Inside this diagram

A network diagram with 10 components in 10 zones and 11 connections.

Zones and their devices

  • Internet: Global Load Balancer
  • Public Subnet 10.1.1.0/24: Mumbai Application Load Balancer
  • Private App Subnet 10.1.2.0/24: Mumbai App Servers
  • Private DB Subnet 10.1.3.0/24: Aurora Primary DB and Mumbai Redis Node
  • Public Subnet 10.2.1.0/24: Singapore Application Load Balancer
  • Private App Subnet 10.2.2.0/24: Singapore App Servers
  • Private DB Subnet 10.2.3.0/24: Aurora Secondary DB and Singapore Redis Node
  • AWS Transit Gateway: Transit Gateway Peering

Connections

  • Global Load Balancer β†’ Mumbai Application Load Balancer: HTTPS 443 with Health Checks
  • Global Load Balancer β†’ Singapore Application Load Balancer: HTTPS 443 with Health Checks
  • Mumbai Application Load Balancer β†’ Mumbai App Servers: HTTP 8080
  • Singapore Application Load Balancer β†’ Singapore App Servers: HTTP 8080
  • Mumbai App Servers β†’ Aurora Primary DB: PostgreSQL 5432
  • Mumbai App Servers β†’ Mumbai Redis Node: Redis 6379
  • Singapore App Servers β†’ Aurora Secondary DB: PostgreSQL 5432
  • Singapore App Servers β†’ Singapore Redis Node: Redis 6379
  • Aurora Primary DB β†’ Aurora Secondary DB: Aurora Global Database Replication
  • Mumbai Redis Node β†’ Transit Gateway Peering: Active-Active Replication via TGW
  • Transit Gateway Peering β†’ Singapore Redis Node: Active-Active Replication via TGW

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

FlowchartDevOps & SRE

GitOps Deployment Flow

How a code change reaches production with GitOps: CI builds and tests, the image tag is written to a config repo, and Argo CD syncs the cluster to match Git.

C4 ArchitectureProDevOps & SRE

Observability Stack (Metrics, Logs, Traces)

A complete observability setup: OpenTelemetry collects metrics, logs and traces from services, which are stored separately and viewed together in Grafana with alerting.

State MachineDevOps & SRE

Incident Lifecycle

The stages of a production incident from the first alert to the postmortem, with severity escalation along the way.

SequenceDevOps & SRE

Incident Response Sequence

Who does what when production breaks: monitoring pages the on-call engineer, an incident channel is opened, customers are updated and the fix is rolled out.

DeploymentProDevOps & SRE

Blue-Green Deployment

A blue-green setup where a new version is deployed next to the live one and traffic is switched only after it passes checks, allowing instant rollback.

FlowchartDevOps & SRE

Infrastructure as Code Pipeline

How infrastructure changes are made safely with Terraform: plan on pull request, policy checks, approval, apply and drift detection.