VPC enables us to launch Amazon services to a Virtual network. This virtual network is owned by its own data centers with the benefits of using AWS services.
In each account by default, VPC is already configured. The default VPC is used for testing purposes. The custom VPC is used for more secure network defined in the private subnet. The instances created in default VPC can’t communicate by default. Hardware VPN connection is used for connecting instance to the data center.
VPC Peering
VPC Peering is a networking connection between two VPCs. Peering helps to route traffic between VPC.
How do the instances communicate?
- VPCs in the same network.
- VPCs in the same account.
- VPCs in the different AWS account
- VPCs in the different region, this is called as “Inter-region VPC peeing connection”.
A VPC peering helps in the transfer of data.
NAT devices use connectivity from internet to Instance and prevent private network data to the internet.
AWS provides two types of devices
— NAT Gateway
— NAT Instance.
NAT Gateway is a fully managed service. It should launch public subnet.
How to create a VPC from the AWS Console
- Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
- On the VPC dashboard, choose Launch VPC Wizard.
- Select the option to choose VPC with Public and Private Subnets.
- In the “Specify the details of your NAT gateway” section, add the allocation ID for an Elastic IP address in your account.
- Choose to Create VPC.
VPC End Point Diagram
If you require help, contact SupportPRO Server Admin
