Exploring Private Subnets - No connection to instances
- Hafeez Baig |
- 25 steps |
- 2 minutes
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 **EC2** in the search bar and click on **EC2** to view the EC2 Dashboard
3
On the EC2 dashboard click on **Instances** from the left bar to view the EC2 instances
4
Select the **Private-EC2-instance** from the Instances
5
Scroll to the horizontal section of the **Private-EC2-instance**, and click on the **Networking** tab to view the Networking details
6
In the **Networking** tab, under the **Subnet ID** click on the **my-private-subnet** link
7
**Subnets** wizard will open, select the **my-private-subnet**
8
Under the Public IPv4, click on the copy widget to copy the public ipv4 address of **Private-EC2-instance**
9
Now Open the **Command Prompt** from your local machine
10
Type the command [[ping ]]followed by the IPv4 address. for example [[ping 18.266.251.31 ]]and hit enter
11
You will be seeing **Request timed out.** message on screen
12
Go back to the Management console and under the horizontal section of the **Private-EC2-instance** click on **Security** tab
13
Scroll to the **Security groups** section and click on the **ec2-security-group** link
14
**ec2-security-group** wizard will open
15
Scroll to the Inbound rules section and click on the **Edit inbound rules** button
16
Click on **Add rule** button
17
Choose the Type as **All ICMP - IPv4**
18
Choose Source as **Anywhere-IPv4**
19
Click on **Save rules** button to save the Inbound rule
