AWS for DevOps — Networking (VPC)

Chapter 4 — Networking (VPC)

A VPC (Virtual Private Cloud) is your isolated network on AWS. Every resource — EC2 instances, RDS databases, Lambda functions, ECS containers — runs inside a VPC. Understanding VPCs is essential for designing secure, highly available architectures.

This chapter covers:

Section	Topic
4.1	VPC Basics
4.2	Subnets & Route Tables
4.3	Internet & NAT Gateways
4.4	Security Groups vs NACLs
4.5	VPC Peering & Endpoints
4.6	Practice Exercises

The Big Picture

  ┌─────────────── VPC: 10.0.0.0/16 ─────────────────────────┐
  │                                                            │
  │  ┌── Public Subnet 10.0.1.0/24 (AZ-a) ──┐                │
  │  │  Internet Gateway ← Route Table        │                │
  │  │  ALB, NAT Gateway, Bastion             │                │
  │  └────────────────────────────────────────┘                │
  │                                                            │
  │  ┌── Private Subnet 10.0.10.0/24 (AZ-a) ─┐               │
  │  │  NAT Gateway ← Route Table              │               │
  │  │  App Servers (EC2 / ECS)                │               │
  │  └─────────────────────────────────────────┘               │
  │                                                            │
  │  ┌── Private Subnet 10.0.20.0/24 (AZ-a) ─┐               │
  │  │  No internet route                      │               │
  │  │  RDS, ElastiCache                       │               │
  │  └─────────────────────────────────────────┘               │
  │                                                            │
  │  (Same pattern repeated in AZ-b and AZ-c)                 │
  └────────────────────────────────────────────────────────────┘

By the end of this chapter, you will be able to design and build a production-grade VPC with public and private subnets across multiple availability zones.

---

Start with → VPC Basics