Not able to ping AWS EC2 Instance

+1 vote
I have an EC2 instance running on my AWS and when I am try to ping from my local box it shows that it is not available. How can I make it functional (Pingable)?
Apr 17, 2018 in Azure by Flying geek
• 3,150 points
643 views

2 answers to this question.

+1 vote
Best answer
The custom ICMP rule in the security groups is quite a different, try the following rule, see if it works because it worked for me:
Type: All ICMP
Protocol: TCP
Port range: 0 - 65535
Source: Anywhere - 0.0.0.0/0

After doing this you must be able to ping other instances. Then you should see something like this:
PING 10.0.0.15 (10.0.0.15): 56 data bytes
64 bytes from 10.0.0.14: icmp_seq=1 ttl=64 time=3.9 ms
64 bytes from 10.0.0.14: icmp_seq=2 ttl=64 time=3.9 ms
64 bytes from 10.0.0.14: icmp_seq=3 ttl=64 time=10.6 ms
64 bytes from 10.0.0.14: icmp_seq=4 ttl=64 time=40.6 ms
64 bytes from 10.0.0.14: icmp_seq=5 ttl=64 time=3.8 ms
64 bytes from 10.0.0.14: icmp_seq=6 ttl=64 time=5.3 ms
64 bytes from 10.0.0.14: icmp_seq=7 ttl=64 time=6.5 ms
64 bytes from 10.0.0.14: icmp_seq=8 ttl=64 time=3.5 ms
64 bytes from 10.0.0.14: icmp_seq=9 ttl=64 time=21.0 ms
64 bytes from 10.0.0.14: icmp_seq=10 ttl=64 time=3.5 ms
64 bytes from 10.0.0.14: icmp_seq=11 ttl=64 time=3.5 ms
64 bytes from 10.0.0.14: icmp_seq=12 ttl=64 time=59.7 ms
64 bytes from 10.0.0.14: icmp_seq=13 ttl=64 time=3.5 ms
64 bytes from 10.0.0.14: icmp_seq=14 ttl=64 time=3.5 ms
64 bytes from 10.0.0.14: icmp_seq=15 ttl=64 time=4.8 ms
64 bytes from 10.0.0.14: icmp_seq=16 ttl=64 time=3.1 ms
64 bytes from 10.0.0.14: icmp_seq=17 ttl=64 time=3.1 ms
64 bytes from 10.0.0.14: icmp_seq=18 ttl=64 time=3.0 ms
64 bytes from 10.0.0.14: icmp_seq=19 ttl=64 time=3.1 ms

--- 10.0.0.14 ping statistics ---
20 packets transmitted, 19 packets received, 5% packet loss
round-trip min/avg/max = 3.0/9.9/59.7 ms

This is it, hope it works!
answered Apr 17, 2018 by Cloud gunner
• 4,260 points

selected Aug 21, 2018 by Priyaj
0 votes

You have to edit the Security Group to which your EC2 instance belongs and allow access (or alternatively create a new one and add the instance to it).

By default everything is denied. The exception you need to add to the Security Group depends on the service you need to make available to the internet.

If it is a webserver you will need to allow access to port 80 for 0.0.0.0/0 (which means any IP address).

To allow pinging the instance you need to enable ICMP traffic.

The AWS Web Console provides some of the most commonly used options in the relevant dropdown list.

answered Aug 21, 2018 by Priyaj
• 56,520 points

Related Questions In Azure

0 votes
1 answer

Not being able to get user consent - OAuth2 with AzureAD

The problem you are running in to ...READ MORE

answered Jun 8, 2018 in Azure by cloudie_crank
• 1,610 points
112 views
0 votes
1 answer

The user or administrator has not consented to use the application-Send interactive authorization request

An admin must consent to the permissions. ...READ MORE

answered Aug 23, 2018 in Azure by club_seesharp
• 3,450 points
338 views
0 votes
1 answer

Error: The subscription is not registered to use namespace 'Microsoft.DataFactory

In Azure, for each functionality there's a ...READ MORE

answered Aug 24, 2018 in Azure by null_void
• 3,220 points
66 views
0 votes
1 answer

Chrome's default HTML5 player is not working when video is uploaded to Azure Storage.

I don't know much about Windows Storage, ...READ MORE

answered Apr 23 in Azure by Prerna
• 1,940 points
50 views
+1 vote
4 answers

Where to find the Microsoft.IdentityModel dll?

I finally found this Nuget package: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM, which ...READ MORE

answered Oct 23, 2018 in Azure by Trisha
506 views
+13 votes
2 answers

Git management technique when there are multiple customers and need multiple customization?

Consider this - In 'extended' Git-Flow, (Git-Multi-Flow, ...READ MORE

answered Mar 26, 2018 in DevOps & Agile by DragonLord999
• 8,380 points
147 views
0 votes
1 answer