Table of contents
No headings in the article.
What is VPC in Cloud Computing
VPC stands for Virtual Private Cloud, and you will see this service is present in almost every cloud, In AWS Cloud it is called AWS VPC, in Microsoft Azure they named it Virtual Private Link and in Google Cloud, they called it GCP VPC. VPC is one of the main services of every cloud service provider.
When we call it a Virtual Private Cloud, it means that we isolate our servers, databases or any resource that you create or deploy on the cloud, to your separate space, while present in the Cloud.
VPC in AWS
With the help of VPC, you can create your private infrastructure on the Cloud platform, you can customize your network configuration in AWS VPC. This VPC is dedicated to your AWS Account and it is separated from other VPCs in AWS Cloud.
AWS creates a default VPC for us, where we launch our resources on AWS Cloud, but when you create your own VPC it’s not the only thing, it is a mixture of so many components such as Subnets, Route Tables, Internet Gateway, and Nat Gateway. Before creating VPC on AWS or on any cloud platform you need to have a basic understanding of CIDR first, CIDR stands for Class Inter-Domain Routing, which is a method of allocating IP addresses.
Architecture and Components of VPC
VPC: In AWS VPC is regional service VPC is bound to specific region, You can create your VPC in a particular region, it’s not a global service like IAM. You can assign, both IPv4 and IPv6 ip addresses, to your VPCs and subnets means that you need to give a CIDR range of IP address while creating VPC (e.g 192.168.0.0/16 or 10.0.0.0/16) which is basically a range of IP address that you are going to use in VPC and within that range IP address are allotted to your resources which you are going to create in that VPC
Subnets: Inside VPC you create subnets, which are bound to specific availability zones in the region of your VPC, which helps us to launch resources in different availability zones in our VPC, we create subnets by allocating them a set IP address from our CIDR range that we used while we creation of our VPC. And remember that AWS reserves 5 IP addresses in each region.
If you select 10.0.0.0/16 CIDR range for your VPC, so it simply means that you get a 65,536 ip address means you can use this much amount of IP addresses in your VPC, you allocate a particular range of IP addresses from this CIDR to your subnet. You can deploy or create your resources such as instances or databases inside the subnets in your own VPC.
Mainly there are two types of Subnets in VPC Public Subnet and Private Subnet,
Public Subnet: In a public subnet you create or deploy resources that are exposed to outside networks.
Private Subnet: In a private subnet you can create or deploy resources that are not exposed to the outside world at all, you can only access them internally.
Route Tables: It contains a set of routes that used to know where network traffic from your subnet is directed. Each subnet is must associate with the route table.
Internet Gateway: Internet Gateway helps us to create public subnet, it basically provides internet connectivity to your subnet, which makes that subnet public. You can attach only one Internet Gateway to particular VPC.
NAT Gateway: It allows instances in present in private subnets to access the internet, which can be required for various purpose such server updation, patching, etc. You create NAT Gateway, in public subnet and attach it to your private subnets via Route Tables.
Create your private infrastructure on a public Cloud platform for your resources
Launch Instances in your subnet, with your own CIDR range (IP address range)
You can customize your routing configuration for your Subnets
You can create peering connections between two VPCs which having different CIDR range
You can also create Transit gateways to connect multiple VPCs together
You secure your resources by deploying or creating them in your isolated network, and assigning proper NACL rules.
So it's a quick wrap about VPC, See you in the next reading. Thank you!!