VPC and Subnet Demo - Create EC2 instances in Custom VPC Subnets | Scribe

VPC and Subnet Demo - Create EC2 instances in Custom VPC Subnets

  • Hafeez Baig |
  • 57 steps |
  • 7 minutes
  • Amazon Web ServicesAmazon Web Services
information ordinal icon
Refer to the following guide to learn how to use IAM in the cloud\ <https://scribehow.com/shared/Creating_an_IAM_User_and_User_Group_in_AWS_Management_Console__hWNiiXlcRJKFqYZZEJD-cg>
1
Sign in to **AWS Management Console** as an **IAM User** **Pre-requisite** - Ensure you have selected the AWS region closest to your location\ For this guide, we will be using us-east-2 (Ohio) as a preferred choice
2
Type **VPC** in the search bar and click on **VPC** to view the VPC Dashboard
3
On **VPC** Dashboard , under the **Resources by Region** click on the VPCs
4
**Your VPCs** wizard will open, viewing the available VPCs
5
On the right side click on the **Create VPC** button
6
**Create VPC** wizard will open, choose the **VPC only** option and give the **Name tag** as "**my-custom-vpc**" and under the **IPv4 CIDR block** options, select **IPv4 CIDR manual input**
7
Provide IPv4 CIDR as "**69.208.0.0/16**" but you're free to specify one as you like, then under the **IPv4 CIDR block** section click on **No IPv6 CIDR block** and for the **Tenancy** section from the dropdown select the **Default** option
8
Scroll the page and click on the **Create VPC** button
9
"**my-custom-vpc**" has been successfully created
10
On the left bar click on the **Subnets**
11
On the right side click on he **Create subnet** button
12
**Create subnet** wizard will open, under the **VPC ID** select the vpc "**my-custom-vpc**" from the dropdown
13
Under the **Subnet settings** provide the Subnet name as "**my-private-subnet**"
14
Scroll to the **Availability Zone** select the **US East(Ohio)/ us-east-2a** from the dropdown
15
Scroll to the **IPv4 VPC CIDR block** section and select the "**69.208.0.0/16**" from the dropdown
information ordinal icon
**Why /16 Subnet?** Think of a /16 subnet as a large address space that can accommodate up to 65,536 IP addresses. Visualize it as a massive pool of available addresses, allowing you to create numerous smaller subnets within it. This means you have ample room to divide and allocate IP addresses for different purposes or services within your AWS infrastructure.
16
Scroll to the **IPv4 subnet CIDR block** section and write "**69.208.0.0/24**"
information ordinal icon
**Why /24 Subnet?** Consider a /24 subnet as a smaller, more specific portion of a network with a maximum capacity of 256 IP addresses. Picture it as a neighbourhood block where each house represents an individual IP address. With a /24 subnet, you have enough addresses to assign to devices within a localized area, such as a specific department or service in your AWS environment.
17
Scroll the page and click on the **Create subnet** button