Today, I am disucssing the VPC concept in the for of example/story so everyone can understand the concept of VPC in easy way.
Below are the points in the form of example/story.
AWS acquire a land called that land Region.
Inside the region AWS build a Data Center.
AWS said, hey ABC company we can host your applications inside the DC [This is the story of back in 2013-14]
Again inside the data center there will be multiple physical server.
Now if you will focus in above statement that we have multiple physical servers inside one data center, isn't it a security breach?
Yes, it may be a security breach because all the machines inside one data center.
Now, here VPC concept comes.
To overcome this issue AWS created a secure community which is known as VPC.
Now whatever request will come it will be created inside the VPC.
Now there will be a Question, How do you define the size of VPC?
We can define the size of VPC using IP address Range, which is (0-65536)
We have to split the IP address range, and this splitting is known as Subnet.
Also we need a Gateway to enter to the VPC.
After entering the Gateway first thing user will access is Public Subnet.
Public subnet will connect to the internet using internet gateway.
Route Table will decide how request should go to the application.
Above everything whatever we have discussed is a type of example and below is exact VPC walkthrough
Amazon Virtual Private Cloud (AWS VPC) Benefits & Components
In this post, I will give you a walkthrough of Amazon Virtual Private Cloud (AWS VPC) that can help you understand how to implement AWS VPC and how to do that in relation to your infrastructure.
What is AWS VPC?
AWS VPC is one of the most popular and widely used services of Amazon Web Services. This is generally because Amazon VPC is mostly related to the security concepts in the cloud and access to the data inside a third-party data center. AWS VPC is a private subsection of AWS in which you can place AWS resources such as EC2 instances and databases. You have full control over who has access to the resources that you place inside the AWS Virtual Private Cloud.
Virtual Private Cloud (VPC) is a logically isolated network from another virtual network in the AWS cloud where you can launch the AWS resources.
It gives all the benefits of the traditional network that you have for your own data center.
Resources and applications are accessed through IPv4 or IPv6 in your AWS VPC.
It gives the benefit of scalable infrastructure in the AWS environment.
It gives you complete control over your virtual network.
VPC vs Private Cloud
AWS VPC is a public cloud service that provides a private cloud-like experience, whereas a private cloud is a dedicated cloud environment hosted on-premises or in a colocation facility.
The following table summarises the main differences between AWS VPC and private cloud:
Types of AWS VPCs in AWS Cloud
Default VPC
Non-default VPC
The default VPC is a virtual network that is automatically created for the customer’s AWS account when EC2 resources are provisioned for the first time. A non-default (also known as Customer VPC) is not created automatically when EC2 resources are provisioned, and the customer must create their own VPC. The AWS system automatically creates the default VPC, whereas the customer/nondefault VPC must be manually configured by each customer and resources must be provisioned. When a new instance is launched without first allocating a subnet, the Default VPC is assigned.
Another significant advantage of Default VPC is that it includes Internet access by default, as well as an internet gateway and public subnets with corresponding route tables. This feature is not enabled by default in non-default VPC. In fact, in non-default VPCs, public IPv4 addresses are not assigned. In terms of numbers, only VPC is available per region, whereas customer VPC is limited to 5 by default for each region.
Benefits Of Using AWS Virtual Private Cloud
EC2 Instance security group membership can be changed while it is running.
Static IPv4 is assigned to Instances that persist across the start and stop.
Create a layered network of resources.
A single-tenant hardware option is available to run EC2 Instances.
Access Control List (ACL) is an additional security layer to protect Instances.
Multiple IPv4 can be assigned to your Instances.
Control both inbound and outbound traffic of Instances.
Multiple network interfaces can be attached to EC2 Instances.
