Complete Architecture Overview
Now that we have covered the major components, let us put it all together and see the complete picture of how a production AWS architecture looks — using our school analogy one final time.
╔══════════════════════════════════════════════════════════════════════╗
║ AWS ACCOUNT ║
║ (The School System) ║
║ ║
║ ┌────────────────────────────────────────────────────────────────┐ ║
║ │ REGION: ap-south-1 │ ║
║ │ (Mumbai School Campus) │ ║
║ │ │ ║
║ │ INTERNET ←→ INTERNET GATEWAY ←→ VPC (The Campus Walls) │ ║
║ │ │ ║
║ │ ╔══════════════════╗ ╔══════════════════╗ │ ║
║ │ ║ AZ-1 ║ ║ AZ-2 ║ │ ║
║ │ ║ (Building A) ║ ║ (Building B) ║ │ ║
║ │ ║ ║ ║ ║ │ ║
║ │ ║ ┌──────────────┐ ║ ║ ┌──────────────┐ ║ │ ║
║ │ ║ │PUBLIC SUBNET │ ║ ║ │PUBLIC SUBNET │ ║ │ ║
║ │ ║ │(Science Wing)│ ║ ║ │(Arts Wing) │ ║ │ ║
║ │ ║ │ │ ║ ║ │ │ ║ │ ║
║ │ ║ │ Web Server │ ║ ║ │ Web Server │ ║ │ ║
║ │ ║ │ (EC2) │ ║ ║ │ (EC2) │ ║ │ ║
║ │ ║ │ │ ║ ║ │ │ ║ │ ║
║ │ ║ │ NAT Gateway │ ║ ║ │ NAT Gateway │ ║ │ ║
║ │ ║ └──────────────┘ ║ ║ └──────────────┘ ║ │ ║
║ │ ║ ║ ║ ║ │ ║
║ │ ║ ┌──────────────┐ ║ ║ ┌──────────────┐ ║ │ ║
║ │ ║ │PRIVATE SUBNET│ ║ ║ │PRIVATE SUBNET│ ║ │ ║
║ │ ║ │(Admin Block) │ ║ ║ │(Admin Block) │ ║ │ ║
║ │ ║ │ │ ║ ║ │ │ ║ │ ║
║ │ ║ │ App Server │ ║ ║ │ App Server │ ║ │ ║
║ │ ║ │ Database │ ║ ║ │ Database │ ║ │ ║
║ │ ║ │ (RDS) │ ║ ║ │ (RDS) │ ║ │ ║
║ │ ║ └──────────────┘ ║ ║ └──────────────┘ ║ │ ║
║ │ ╚══════════════════╝ ╚══════════════════╝ │ ║
║ │ │ ║
║ │ IAM: Controls who can access all of this │ ║
║ │ CloudWatch: Monitors health of everything │ ║
║ │ Route 53: DNS — maps domain to servers │ ║
║ └────────────────────────────────────────────────────────────────┘ ║
╚══════════════════════════════════════════════════════════════════════╝