Cross Region

--- title: "Cross-Region Deployment" description: "Multi-region deployment patterns for Aurora Enterprise with active-passive and active-active configurations." icon: "globe" ---

Overview

Cross-region deployment provides disaster recovery and low-latency access across geographic regions. Aurora Enterprise supports two primary patterns through its cluster control-plane and database replication.

Active-Passive Pattern

In an active-passive setup, one region handles all traffic while the other stands by:

• Primary region runs Aurora with full replica count
• Secondary region runs with reduced capacity
• DNS failover (Route 53, Cloudflare, Google Cloud DNS) redirects traffic on primary failure
• Shared PostgreSQL and Redis across regions, or use cross-region replication

Cluster Configuration

# Primary region
cluster:
  enabled: true
  node_id: "us-east-1-node"
  region: "us-east"
  failover_mode: "active_passive"

# Secondary region
cluster:
  enabled: true
  node_id: "us-west-1-node"
  region: "us-west"
  failover_mode: "active_passive"

Active-Active Pattern

For zero-downtime across region failures:

• Each region runs independent Aurora instances
• Regional load balancers route traffic to the nearest Aurora
• PostgreSQL logical replication keeps databases in sync
• Each region has its own Redis cache (cache miss = acceptable latency hit)

# Region 1
cluster:
  enabled: true
  node_id: "us-east-1-node"
  region: "us-east"
  failover_mode: "active_active"
  advertise_url: "https://aurora-east.example.com"

# Region 2
cluster:
  enabled: true
  node_id: "eu-west-1-node"
  region: "eu-west"
  failover_mode: "active_active"
  advertise_url: "https://aurora-west.example.com"

DNS Routing

Use any global DNS load balancer:

Health check endpoint: GET /health on each Aurora node.

Database Replication

Considerations

• Database latency — Cross-region database operations add to request processing time
• Cache locality — Each region should have its own Redis; cache misses are acceptable
• Configuration sync — Configuration must be synchronized across regions (YAML, environment variables)
• Monitoring — Monitor and alert on cross-region replication lag
• Compliance — Ensure data residency requirements are met per region

Related

• Cluster and HA — Cluster configuration and failover modes
• Sizing and Redundancy — Capacity planning and database HA
• Compliance — Data residency controls