Menu
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:
Outbound settings:
Any ideas on what else could be causing this issue? I would greatly appreciate your help. Thanks.
833
There are many possible causes of slow or unresponsive EC2 instances when CPU and memory aren't fully used, including: Problems with an external service that your instance relies on. Disk thrashing. Network connectivity issues.
For use cases that require low latency and high single-flow bandwidth, use a cluster placement group to achieve up to 10 Gbps for instances in the same placement group. Alternatively, set up multiple paths between two endpoints to achieve higher bandwidth using Multipath TCP (MPTCP).
The following are common reasons why EC2 Instance Connect might not work as expected: EC2 Instance Connect doesn't support the OS distribution. The EC2 Instance Connect package isn't installed on the instance. There are missing or incorrect AWS Identity and Access Management (IAM) policies or permissions.
It looks like you need to add port 8080 to your inbound IP rules.
66
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
