Exploring Private Subnets - No connection to instances

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

Type **EC2** in the search bar and click on **EC2** to view the EC2 Dashboard

On the EC2 dashboard click on **Instances** from the left bar to view the EC2 instances

Select the **Private-EC2-instance** from the Instances

Scroll to the horizontal section of the **Private-EC2-instance**, and click on the **Networking** tab to view the Networking details

In the **Networking** tab, under the **Subnet ID** click on the **my-private-subnet** link

**Subnets** wizard will open, select the **my-private-subnet**

Under the Public IPv4, click on the copy widget to copy the public ipv4 address of **Private-EC2-instance**

Now Open the **Command Prompt** from your local machine

Type the command [[ping ]]followed by the IPv4 address. for example [[ping 18.266.251.31 ]]and hit enter

You will be seeing **Request timed out.** message on screen

Go back to the Management console and under the horizontal section of the **Private-EC2-instance** click on **Security** tab

Scroll to the **Security groups** section and click on the **ec2-security-group** link

**ec2-security-group** wizard will open

Scroll to the Inbound rules section and click on the **Edit inbound rules** button

Click on **Add rule** button

Choose the Type as **All ICMP - IPv4**

Choose Source as **Anywhere-IPv4**

Click on **Save rules** button to save the Inbound rule