Virtual Private Cloud - VPC

All servers are present in virtual network or virtual private cloud (VPC).

A VPC can be divided into subnets.

Subnet rules are specific to each subnet. We can make one subnet as public to internet and other as a private.

We can let the servers be present in different subnets (but same vpc) can talk / communicate with each other.

Every EC2 instance should reside under a VPC. AWS automatically creates one default VPC per region. We can create any number of new VPCs if we want.

VPC Peering

• We can create Peers which can communicate with each other, regardless the subnet or VPC or Region in which they are residing in.
• VPC Peering is not supported if both servers have same private IP in their respective subnets.

We can connect to an instance in VPC through an “Internet Gateway”. Anyone can try to connect if internet gateway is enabled in VPC.

In order to make it a little bit private, we can prefer “Virtual Private Gateway” to our VPC instead of internet gateway. Virtual Private Gate allows only selected traffic to VPC. But still the route taken by the traffic is internet.

If we want the route also to be private and dedicated (non-shared) connection from client’s data center premises, “AWS Direct Connect” is the solution.