🌐 Multi-Region Readiness
Failover preparedness, DR configuration, and cross-region status assessment · Galaxy
Active Regions
1/1
us-east-1 primary
DR Readiness
28%
Not production-ready
RTO Target
4h
Recovery time objective
RPO Target
1h
Recovery point objective
🗺️ Region Status
Lambda✅ Active · v39
API Gateway✅ Active
DynamoDB✅ 4 tables active
Cognito✅ User pool active
SES⚠️ Sandbox
SNS⚠️ Sandbox
Step Functions✅ Active
EventBridge✅ Active
Lambda○ Not deployed
API Gateway○ Not deployed
DynamoDB○ No tables
Cognito○ Not configured
SES○ Not configured
Route53○ No health checks
DynamoDB Global○ Not enabled
CloudFront✅ Global (all regions)
⏱️ RPO / RTO Assessment
Current Capabilities
No DR region configured — manual recovery required. Estimated manual RTO: 4–8h
Target (Post-DR Setup)
Achievable with DynamoDB Global Tables + us-west-2 replica + Route53 failover
🚧 DR Readiness Gaps
🔴
No DR region deployedus-west-2 has no Lambda, API Gateway, or DynamoDB configured. Manual recovery from us-east-1 only.
🔴
DynamoDB Global Tables not enabledData is single-region only. Cross-region replication not active. Data loss on region failure.
🟠
No Route53 health checks or failover routingDNS does not automatically route to a backup. Manual DNS update required on failover.
🟠
No cross-region Lambda deployment pipelineDeployment scripts are single-region. Deploying to us-west-2 requires manual steps.
🟡
No S3 cross-region replication for static assetsCloudFront serves globally but origin is single-region S3. Consider multi-region S3 origin.
📋 DR Readiness Checklist
CloudFront global CDN✅ Ready
S3 static assets backup⚠️ Single region
DynamoDB Global Tables❌ Not enabled
Lambda DR replica❌ Not deployed
API Gateway DR❌ Not deployed
Cognito user pool export⚠️ Not automated
Route53 health check failover❌ Not configured
Manual recovery runbook✅ Documented
Backup & restore tested⚠️ Not tested