Scribd
Upload
33 views5 pages

Activity 01 - Creating A VPC:: The Remaining 5 IP's Are Used For Below Purposes

The document discusses setting up a VPC with public and private subnets across two availability zones. It includes activities for creating the VPC, subnets, internet gateway, route tables and configuring security groups. Questions are answered around IP address allocation, placement of resources and connectivity testing.

Uploaded by

AbhilashMadala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
33 views5 pages

Activity 01 - Creating A VPC:: The Remaining 5 IP's Are Used For Below Purposes

The document discusses setting up a VPC with public and private subnets across two availability zones. It includes activities for creating the VPC, subnets, internet gateway, route tables and configuring security groups. Questions are answered around IP address allocation, placement of resources and connectivity testing.

Uploaded by

AbhilashMadala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Activity 01 – Creating a VPC:

Activity 02 - Creating Subnets:

Why is the available number of IPs showing as 251, where are the rest 5 IPs used?

The remaining 5 IP’s are used for below purposes:

Sensitivity: Internal & Restricted


10.0.0.0: Network address.

10.0.0.1: Reserved by AWS for the VPC router.

10.0.0.2: Reserved by AWS. The IP address of the DNS server is always the base of the VPC network
range plus two; however, we also reserve the base of each subnet range plus two. For VPCs with
multiple CIDR blocks, the IP address of the DNS server is located in the primary CIDR. For more
information, see Amazon DNS Server.

10.0.0.3: Reserved by AWS for future use.

10.0.0.255: Network broadcast address. We do not support broadcast in a VPC, therefore we reserve
this address.

Why have we created two private and public in different subnets? Should we not create both Public
subnets in one AZ and both Private in another AZ?

As we want High Availability of the resources we have created subnets in different AZ’s.

Activity 03 - Create Internet gateway:

Activity 04 - Create Route table (public) and assign to relevant Subnets:

You would see that all four subnets that you created are associated with the main route table, why?

Initially when we create the subnets these will be associated with Main route table.we can route the
route table to the subnet based on the requirement.

Sensitivity: Internal & Restricted


VPC Lab -- Part 02 of 02:

Did you notice that your MyAppServer has got a public IP and public DNS while MyDBServer has not,
why?

Why are both are running in the same AZ?

We have created MyAppServer in Public subnet and MyDBServer in Private subnet, due to this
MyAppserver is having Public IP and MYDBServer is not having Public IP.

As we have created both the servers in Subnet01, these servers are running in same AZ.

Sensitivity: Internal & Restricted


Activity 06 - Verifying the connectivity:

Connecting to MyAppServer:

Connecting to MyDBServer:

Sensitivity: Internal & Restricted


Creation of Bastion network:

Enabling NAT gateway to Private subnet:

Connection to MyDBServer:

Sensitivity: Internal & Restricted

You might also like