Three-tier web application architecture demonstrating AWS auto-scaling under adversarial load, with stateless EC2 instances in an Auto Scaling Group fronted by an Application Load Balancer. Traffic flows from the internet through the ALB into a public subnet, then to backend Python instances in a private subnet, with all state persisted to an encrypted EBS volume and database server in a separate data subnet. CloudWatch monitors CPU utilization in real time, triggering scale-out when demand exceeds 70%, while security groups enforce least-privilege access between tiers. This workshop-grade design illustrates horizontal scaling best practices, the critical role of AMIs in rapid instance provisioning, and the single point of failure risk of EC2-based databases—highlighting why production deployments should use RDS Multi-AZ or managed clusters. Fork this diagram to customize subnets, scaling policies, or database tier, then download as .drawio or .svg to embed in runbooks and architecture documentation.