Create a VPC using Launch VPC Wizard

Hello Everyone

Welcome to CloudAffaire and this is Debjeet

In the last blog post, we had an introduction to VPC or Virtual Private Cloud.

https://cloudaffaire.com/virtual-private-cloud/

In this blog post, we are going to create a VPC using Launch VPC Wizard.

When you create an AWS account, AWS creates a VPC and allocates to your account. You can start using this default VPC with different AWS services. AWS also supports the creation of your own VPC. To create a VPC, you need to have some basic understanding of computer networks. You can follow below YouTube tutorial to clear your understanding of computer networks.

https://www.youtube.com/watch?v=UXMIxCYZu8o&t=35s

Create a VPC using Launch VPC Wizard

Step 1: Login to your AWS console and click ‘VPC’.

Step 2: Click ‘Launch VPC Wizard’

Note: One default VPC is already allocated to your AWS account.

Step 3: Click ‘Select’.

Note: AWS support 4 types of subnets for VPC. VPC with a Single Public Subnet, VPC with Public and Private Subnets, VPC with Public and Private Subnets and Hardware VPN Access, and VPC with a Private Subnet Only and Hardware VPN Access. In this demo, we are going to create VPC with only one Public Subnet.

Step 4: Provide the IPv4 CIDR block for your VPC and subnet and click ‘Create VPC’.

IPv4 CIDR block:

CIDR block for your VPC. You can create a publicly routable CIDR block or use the standard private CIDR ranges for your VPC.

IPv6 CIDR block:

You can associate a single IPv6 CIDR block to your VPC. The CIDR block uses a fixed prefix length of /56 and you cannot choose the range of addresses or the IPv6 CIDR block size.

VPC name:

Name of your VPC.

Public subnet’s IPv4 CIDR:

CIDR block for your subnet can be same as CIDR block for VPC in case of a single subnet.

Availability Zone:

The scope of your VPC is across availability zones in your region but you can define the subnet in a specific availability zone.

Subnet name:

Name of your subnet.

Service endpoints:

A VPC endpoint enables you to privately connect your VPC to supported AWS services and VPC endpoint services powered by PrivateLink without requiring an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection.

DNS hostnames:

Indicates whether the instances launched in the VPC get public DNS hostnames.

Note: This demo is for introductory purpose and advanced features will be covered in future blogs.

If everything is right, you will get a success message

Our VPC is created successfully.

To view your VPC, click ‘Your VPCs’.

To view the subnet, click ‘Subnets’.

Post demo cleanup: Navigate to ‘Your VPCs’, select the VPC that you have created and from ‘Action’ click ‘Delete’

To get more details on VPC, please follow the AWS VPC documentation

https://docs.aws.amazon.com/vpc/index.html

Hope you have enjoyed this article, in the next blog, we will create a VPC manually.