Amazon VPC (Virtual Private Cloud) Fundamentals
- If the subnet has internet access then it is called PublicSubnet.
- If the subnet doesn’t have internet access then it is called PrivateSubnet.
- A subnet must reside entirely within one Availability Zone.
- An entire subnet must be contained within a single Availability Zone.
- Access between instances is managed by VPC Security Groups for both inbound and outgoing traffic (EC2 Security Groups can only define inbound rules).
- We can specify Subnet IP Routing with the aid of the Route Table.
- If a server/instance which is in a private subnet wants to reach the internet then it must have NAT in a public subnet.
Amazon VPC – Introduction to Amazon Virtual Private Cloud
Amazon VPC or Amazon Virtual Private Cloud is a service that allows its users to launch their virtual machines in a protected as well as isolated virtual environment defined by them. You have complete control over your VPC, from creation to customization and even deletion. It’s applicable to organizations where the data is scattered and needs to be managed well. In other words, VPC enables us to select the virtual address of our private cloud and we can also define all the sub-constituents of the VPC like subnet, subnet mask, availability zone, etc on our own.
- We can place the necessary resources and manage access to those resources in the VPC, a private area of Amazon that we control.
- A default “VPC” will be generated when we register an AWS account, allowing us to manage the virtual networking environment, the IP address, the construction of subnets, route tables, and gateways.