About This Architecture

Multi-tier AWS architecture spanning three availability zones with hybrid on-premises connectivity via Site-to-Site VPN, featuring a public-facing web tier with Application Load Balancer and Auto Scaling Group, private application tier with EFS shared storage, and RDS MySQL database in a private subnet. Traffic flows from Internet through IGW to ELB, which distributes requests to EC2 instances in public subnets; instances access shared EFS mounts and RDS via security group rules, while S3 bucket access is restricted to VPC endpoint. Lambda functions triggered by S3 PutObject events process uploads and log to CloudWatch, with SNS notifications for Auto Scaling events. This architecture demonstrates production-grade patterns: multi-AZ resilience, least-privilege security groups, VPC endpoints for private S3 access, and infrastructure-as-code readiness. Fork this diagram on Diagrams.so to customize CIDR ranges, instance types, or add additional services like ElastiCache or Secrets Manager. The design omits NAT Gateway to reduce costs in this educational context; production deployments should add NAT for outbound internet access from private subnets.

People also ask

How do I design a multi-tier AWS architecture with Auto Scaling, RDS, EFS, and on-premises VPN connectivity?

This diagram shows a three-tier AWS architecture spanning three availability zones: a public web tier with Application Load Balancer and Auto Scaling Group (min 1, desired 2, max 3 instances), a private application tier with EC2 instances accessing shared EFS storage via NFS, and a private data tier with RDS MySQL database. Site-to-Site VPN connects the on-premises network (192.168.10.0/24) to the