8 curated AWS design scenarios with visual architectures, reference solutions, applied heuristics, and common exam traps. The way AWS actually tests you.
A retail company is migrating its on-prem PHP web app to AWS. They want HA with sub-minute failover, stateless scaling, and MySQL backend. What does the architecture look like?
A startup wants a REST API that costs $0 when idle and scales to thousands of requests/sec without ops overhead. They store JSON documents and need sub-50ms reads.
A healthcare company has a 5-minute RTO and 1-minute RPO for their core application. They run in us-east-1 today. Design the DR architecture for region failure.
An e-commerce site needs to ingest 100K clicks/sec, enrich each event with user context, feed both a real-time dashboard (5-second latency) and a daily warehouse for BI.
A healthcare SaaS serves 500+ clinics. Each clinic's data must be fully isolated; a data leak between tenants would trigger HIPAA liability. Design the isolation model that's still cost-efficient.
An engineering team has 15 dev environments running 24/7, costing $4K/month. They're only actively used during business hours (9-5, Mon-Fri). Cut the cost without losing data.
Users upload photos to your site. Each photo needs: thumbnail generation, content moderation, EXIF extraction, and ML tagging. Upload API must respond in under 1 second.
A bank needs to connect its on-prem datacenter (Mumbai) to AWS ap-south-1 with dedicated bandwidth, low predictable latency, encrypted traffic, and HA across two physical paths. They have multiple VPCs that need to reach on-prem.