The server works fine via the Amazon assigned DNS entry, but I cannot reach it (using a browser) via the Elastic IP address Amazon assigned the box. Ping does not work either. I am trying to confirm it is reachable before I add the IP address to my own DNS entries.

link|improve this question
Is the elastic IP address different from the DNS IP address? – Robert Harvey Feb 3 at 16:33
1  
Are you sure you're using your elastic IP and not your private, could-local IP? – Piotr Justyna Feb 3 at 16:34
@Robert - Hi, well the aws.*** address will not lookup via ping, (but works in the browser) so I am actually at a loss on how to find out. I tried ping and I tried a few internet sites that do a lookup. – Guido Anselmi Feb 3 at 16:42
@Piotr - Yep. It's the "Elastic IP Address" not the Private IP Address. It also is used by Amazon in the header for the status tabs. – Guido Anselmi Feb 3 at 16:43
Guido, does it have a public DNS and instance ID assigned? – Piotr Justyna Feb 3 at 16:46
show 7 more comments
feedback

migrated from stackoverflow.com Feb 3 at 16:51

This question came from our site for professional and enthusiast programmers.

3 Answers

Things to check:

  • Your elastic IP associated with your instance?
  • Your security group of instance permits incoming connections?
  • Your instance firewall permits incoming connections?
  • Your application listens?
link|improve this answer
feedback

Just adding this reply as it might help other EC2 Newbies. If the Public DNS for your EC2 instance is: Public DNS: ec2-46-137-53-149.eu-west-1.compute.amazonaws.com you can access the instance using the numeric portion of the DNS Address. In the above case http://46.137.53.149/

Obviously you will need to have the relevant TCP Port open in the security group/profile associated with your instance as mentioned above.

The private IP (e.g. 10.235.47.101) is not accessible from outside the AWS network and is only useful when you have a cluster of EC2 nodes and want faster communication between them.

link|improve this answer
feedback

Couple questions: what port are you trying to access? Do you have that port open on the security groups? Do you have an application listening on that port?

If I had to guess your security groups are not setup right. Make sure to open them to the correct ip addresses or to the world (0.0.0.0/0) if you are going access that port from multiple IPs.

If all that is not it, then dissociate and reallocate the IP to the instance.

link|improve this answer
@Chan-da-man- Yes ports are open and there is an app listening. Exact same URL except domain name swapped with IP. – Guido Anselmi Feb 3 at 18:04
When you ping the full amazon cname does it come back with the elastic ip? – chantheman Feb 4 at 17:50
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.