EC2 instance 'took too long to respond'

node.js git amazon-web-services amazon-ec2 aws-security-group
Harry picture Harry · Aug 23, 2017 · Viewed 10.7k times · Source

I have a site built on NodeJS, which I am currently trying to deploy on the free tier on AWS.

So far I have created an instance, launched it, I can connect via SSH (console) to my instance, and have successfully pulled my files from my Git repository. However, when I try to browse my public DNS, I get: ec2-54-252-151-208.ap-southeast-2.compute.amazonaws.com:8080 took too long to respond.

I have also had a look at the settings on security group (as recommended on a different post) and ensured that inbound and outbound 'HTTP' and 'HTTPS' traffic are allowed (screenshot below):

Inbound settings: Inbound settings

Outbound settings: enter image description here

Any ideas on what else could be causing this issue? I would greatly appreciate your help. Thanks.

Answer

BryceH picture BryceH · Aug 23, 2017

It looks like you need to add port 8080 to your inbound IP rules.

Related questions

avoid rebuilding node_modules in elastic beanstalk

We have a fairly simple node.js app, but due to AWS Elastic Beanstalk deployment mechanism, it takes about 5 minutes to roll-out a new version (via git aws.push) even after a single file commit. I.e. the commit itself (…

Read More
Do I commit the package-lock.json file created by npm 5?

npm 5 was released today and one of the new features include deterministic installs with the creation of a package-lock.json file. Is this file supposed to be kept in source control? I'm assuming it's similar to yarn.lock and composer.…

Read More
How to add /usr/local/bin in $PATH on Mac

When I do 'open .profile' in the terminal I have the following: export PATH=$PATH:/usr/local/git/bin Now I installed node.js for Mac and it says, Make sure that /usr/local/bin is in your $PATH. How …

Read More