← Back to Docs
Recipe

AWS Architecture Patterns

Production-grade patterns for deploying Meridian on AWS — from single-instance to multi-region active-active topologies.

Single‑Instance Starter

EC2 t3.medium running the Meridian loader behind an Application Load Balancer. Session state in ElastiCache Redis, license keys verified against DynamoDB. CloudWatch alarms on CPU > 80% trigger auto-scaling group expansion.

  • Route 53 → ALB → EC2 Auto Scaling Group (min 1, max 3)
  • ElastiCache (Redis 7) for session affinity
  • DynamoDB on‑demand for license ledger

Multi‑AZ High Availability

Spread across three Availability Zones. Aurora PostgreSQL cluster with reader endpoints handles license queries. S3 hosts signed payload artifacts behind CloudFront for global edge delivery.

  • Aurora Serverless v2 — scales to zero between check‑ins
  • CloudFront CDN with signed URLs for payload distribution
  • NAT Gateway per AZ for outbound licensing calls

Active‑Active Multi‑Region

Two regions with Global Accelerator routing users to the nearest healthy endpoint. DynamoDB Global Tables replicate license state with <1s lag. Route 53 health checks flip traffic on regional failure.

  • AWS Global Accelerator — static anycast IPs
  • DynamoDB Global Tables v2019 for conflict‑free replication
  • Lambda@Edge for geo‑steering header injection
All patterns assume Meridian loader v3.2+ with Ed25519 payload verification and offline grace caches. Adjust instance sizes based on your concurrent license‑check throughput.