Mission Control

🌍 Region Expansion Planner

Current: us-east-1

Multi-region expansion analysis β€” cost comparison, DynamoDB Global Tables setup, Lambda@Edge trade-offs, compliance matrix, and latency estimates.

πŸ’° Cost Comparison: us-east-1 vs eu-west-1

πŸ‡ΊπŸ‡Έ us-east-1 β€” Current baseline

~$12–18/mo
Lambda (500K inv)$0.60
DynamoDB PAY_PER_REQUEST$4.50
CloudFront CDN$2.00
API Gateway$1.75
S3 storage$0.50

πŸ‡ͺπŸ‡Ί eu-west-1 β€” Replica estimate

~$16–24/mo
Lambda (500K inv, +10% pricing)$0.66
DDB Global Tables replication WCU+$2.50
CloudFront EU PoP$2.40
API Gateway eu-west-1$1.93
Cross-region data transfer~$1.50

Estimates assume identical traffic profile. DynamoDB Global Tables adds ~$1.875 per million WCUs replicated. Actual billing depends on traffic pattern and AWS promotional pricing.

πŸ—„ DynamoDB Global Tables Setup

4 CLI commands to enable Global Tables replication to eu-west-1:

# 1. Verify table exists in us-east-1 (must be PAY_PER_REQUEST or provisioned with streams) aws dynamodb describe-table --table-name eggs --region us-east-1 # 2. Enable DynamoDB Streams on each table (required for Global Tables) aws dynamodb update-table --table-name eggs --region us-east-1 \ --stream-specification StreamEnabled=true,StreamViewType=NEW_AND_OLD_IMAGES # 3. Create replica in eu-west-1 (repeat per table) aws dynamodb update-table --table-name eggs --region us-east-1 \ --replica-updates '[{"Create":{"RegionName":"eu-west-1"}}]' # 4. Verify replication status aws dynamodb describe-table --table-name eggs --region us-east-1 \ --query 'Table.Replicas'

⚠ Global Tables v2 requires streams. Repeat step 2–3 for all tables: eggs, ducklings, spaceducks, birth_certificates, connections, audit_log.

⚑ Lambda@Edge vs Regional Lambda Trade-offs

FactorLambda@EdgeRegional Lambda (eu-west-1)
Execution locationCloudFront PoP (150+ locations)Fixed AWS region
Cold start latencyHigher β€” no VPC, but per-PoP cold startsLower β€” warm pools per region
Max memory128 MB (viewer) / 10 GB (origin)10 GB
Max timeout5s (viewer) / 30s (origin)15 min
VPC access❌ Not supportedβœ… Full VPC support
DynamoDB accessVia API only (no SDK VPC endpoint)Direct SDK + VPC endpoint
Pricing$0.60/M requests + durationStandard Lambda pricing
Best for Space DuckAuth redirects, A/B testing, geo-routingBeak API, peck protocol, data ops
RecommendationPartial β€” edge routing onlyPrimary for Beak API

πŸ›‘ Data Residency Compliance Matrix

RegulationApplies tous-east-1 Onlyeu-west-1 ReplicaNotes
GDPREU users' personal data ⚠ At risk βœ“ Compliant EU personal data must stay in EU (or explicit consent). Current us-east-1 may not satisfy Art. 44-49 SCCs without DPA.
CCPACalifornia residents βœ“ OK βœ“ OK CCPA focuses on disclosure/deletion rights, not geographic storage. Both regions are acceptable.
APRAAustralian entities ⚠ Review needed ⚠ Review needed CPS 234 requires risk assessment for offshore data. Neither us-east-1 nor eu-west-1 meets APRA's offshore notification threshold without a written risk acceptance.
ISO 27001All data βœ“ AWS certified βœ“ AWS certified AWS eu-west-1 is ISO 27001:2022 certified. Operator must maintain their own controls.

⏱ Estimated Latency Improvement

London (UK) β†’ us-east-1 (current)~85–120ms RTT
London (UK) β†’ eu-west-1 Dublin (proposed)~12–25ms RTT
Paris (FR) β†’ us-east-1~95–130ms RTT
Paris (FR) β†’ eu-west-1~18–35ms RTT
Sydney (AU) β†’ us-east-1~200–240ms RTT
Sydney (AU) β†’ ap-southeast-2 (future)~15–30ms RTT
EU region latency gain~75–100ms improvement per request

RTT estimates are typical values. Actual latency depends on user ISP, CloudFront PoP selection, and Lambda cold-start frequency. Beak API calls and peck protocol handshakes benefit most.