VPC - Manage Private Network on AWS

VPC is our own isolated network in the cloud.

Your resources always have to run in a VPC!

▪ We have a VPC for each Region

▪ VPC spans all the AZ (Subnet) in that Region

▪ Multiple VPCs in different Regions

▪ VPC is like a virtual representation of network infrastructure: Server setup, network configuration (router, firewall, DHCP etc.) moved to cloud

SUBNET

Subnet is a range of IP addresses in your VPC

It's like a private network inside a network:

We have a subnet for each Availability Zone:

Private and Public Subnets

▪ Based on firewall configuration we can have a private and/or public subnet:

▪ A subnet has a default range of internal(private) IP addresses

BUt : other services inside the vpc still have access

▪ When you create a new resource like EC2 instance then an IP address is assigned within this subnet's IP range

▪ For communication inside the VPC

• not for outside web traffic

• internal IP range on VPC level

Internet Gateway

▪ Using an internet gateway you can connect the VPC or its subnets to the outside internet

Security - Controlling Access

Of course, we need to secure our resources:

▪ Control access to your VPC

▪ Control access to your individual server instances

• secure your components

NETWORK ACCESS CONTROL LIST (NACL)

• Configure access on instance level = Security group

• Configure access on subnet level = NACL