AWS VPCS are now the default solution for running cloud VMS.

"Automatic weather station VPC subnet " popular interpretation

Key takeaways:

AWS VPCS are now the default solution for running cloud VMS.

Your VPC can still be the same as a traditional on-premises ARM hostingnetwork, but it will have more automation and scaling capabilities.

VPCS can be created by including all social public subnets or a combination of public/private subnets for the enterprise.

Amazon VPC, the core of AWS Cloud hosting, is a complex concept that can be difficult to understand, especially for developers with little experience operating infrastructure. Developers are the team members most involved in cloud projects, but in most projects, they still lack knowledge of infrastructure operations.

In this article, we'll discuss the different types of VPC Settings available in AWS. Then, together, we will understand the technical terms of VPCS and translate these technical terms into non-technical terms to Cloud platfrom providermake it easier for everyone to understand VPCS.

AWS began its "virtual network" journey with the introduction of "EC2 Classic," a first-generation AWS approach to creating EC2 instances in a "virtual network." Eventually, however, AWS dropped support for EC2 Classic. AWS discontinued support for EC2 Classic and introduced the "EC2 VPC" (aka AWS VPC Network).

One of the reasons AWS is dropping EC2 Classic is because your AWS network is shared with other AWS tenants. This means that the "virtual network" is not your private network (for your account). For teams that are used to running their own networks independently while hosting servers locally, this limitation is somewhat counterintuitive. This demand led AWS to come up with their second generation of "virtual networks" :EC2-VPC.

When you start an enterprise instance in an AWS account, virtual private cloudby default it will start on one of our systems' default VPCS and get both social public and private IP. How can they achieve this?

What is EC2-VPC?

Amazon VPC lets you define a virtual network in your own logically isolated area (AWS cloud), also known as a virtual private cloud (VPC). You can start AWS resources, such as instances, in a VPC. Your VPC is very similar to a traditional network, and you can run it from your own data center (taking advantage of using AWS's scalable infrastructure).

If your AWS account was created after December 4, 2013, it only supports EC2-VPC. In this case, AWS will create a default VPC for you in each AWS region. So unless you create a non-default VPC yourself and specify it when you start your instance, AWS will start your instance in the default VPC.

What happens during the creation of the default VPC?

When AWS creates a default VPC, it:

Create an IPv4 CIDR block sized VPC OF/16(172.31.0.0/16) that provides up to 65,536 private IPv4 addresses.

Create a default subnet of size u002F20 in each availability zone and provide each subnet with up to 4,096 addresses, some of which are reserved for our use.

Create an Internet gateway and connect it to the default VPC.

Create a primary routing table for your default VPC and set the rules for sending all IPv4 traffic to the Internet gateway. Set the rules for sending all IPv4 traffic destined for the Internet to the Internet gateway.

Create your own system default security group and associate it with your default VPC.

Create a default network access control list (ACL) and associate it with the default VPC.

Associate the default DHCP options for your AWS account with the default VPC.

A VPC can have a public or private subnet. You can learn more about these scenarios here.

Subnets are a key component of a VPC. A VPC can contain all public subnets or a combination of public u002F private subnets. A private subnet is a subnet that is not routed to an Internet gateway. You can configure a subnet as a pure VPN subnet by routing traffic through the virtual private gateway. You can learn more about enabling a VPN here.

How can a VPC connect to a subnet when an EC2 instance is being started?

As mentioned above, the VPC assigned to your account is a logically isolated network. Each compute resource (in other words, an AWS EC2 instance) will be started in "One" VPC.