VPC Fundamentals
Introduction
A VPC (Virtual Private Cloud) is your own isolated network within AWS. It's where your
EC2 instances, databases, and other resources live. Understanding VPCs is essential
because almost everything you deploy needs network connectivity configured correctly.
Why This Matters
In test automation, you probably didn't think much about networking — your tests ran
on machines that "just worked" on the network. In cloud infrastructure, you design
the network from scratch.
Real-world MLOps scenarios:
- Training jobs need to reach S3 (public endpoint or VPC endpoint?)
- Model serving needs to be accessible from the internet (public subnet + load balancer)
- Databases should NOT be accessible from the internet (private subnet)
- Your Kubernetes cluster nodes need to talk to each other and to AWS services
Understanding VPCs prevents the frustrating "why can't my service reach X?" debugging
sessions and helps you design secure architectures where only what needs to be public is public.
Tasks
Hint: VPC → Your VPCs → look for the one marked 'default'
Hint: Delete in order: subnets, route tables, IGW, then VPC