You are viewing a free preview of this lesson.
Subscribe to unlock all 10 lessons in this course and every other course on LearningBro.
Amazon Virtual Private Cloud (VPC) lets you provision a logically isolated section of the AWS cloud where you can launch AWS resources in a virtual network that you define. You have complete control over your networking environment.
Without a VPC, your resources would be exposed to the public internet by default. VPC gives you:
A VPC is your private network in AWS. Key attributes:
10.0.0.0/16 — gives you 65,536 IP addresses)A subnet is a range of IP addresses within your VPC. Subnets are tied to a specific Availability Zone.
| Subnet Type | Internet Access | Use Case |
|---|---|---|
| Public subnet | Yes (via Internet Gateway) | Web servers, load balancers |
| Private subnet | No direct access | Databases, application servers |
Example layout:
VPC: 10.0.0.0/16
├── Public Subnet (10.0.1.0/24) — AZ-a — Web servers
├── Public Subnet (10.0.2.0/24) — AZ-b — Web servers
├── Private Subnet (10.0.3.0/24) — AZ-a — Database
└── Private Subnet (10.0.4.0/24) — AZ-b — Database
An Internet Gateway allows resources in public subnets to communicate with the internet. A VPC can have at most one IGW attached.
A NAT (Network Address Translation) Gateway allows resources in private subnets to access the internet (e.g., to download software updates) without exposing them to inbound internet traffic.
Route tables contain rules (routes) that determine where network traffic is directed.
Example route table for a public subnet:
| Destination | Target |
|---|---|
| 10.0.0.0/16 | local |
| 0.0.0.0/0 | igw-xxxx |
Example route table for a private subnet:
| Destination | Target |
|---|---|
| 10.0.0.0/16 | local |
| 0.0.0.0/0 | nat-xxxx |
Subscribe to continue reading
Get full access to this lesson and all 10 lessons in this course.