Error in accessing Public IPv4 addresses of the EC2 instances and ALB DNS from the AWS Console

0

Hello Team,

I have an AWS Free Tier account. By following the Onboarding to AWS guide (https://aws.amazon.com/getting-started/onboarding-to-aws/), I created two EC2 instances and one ALB. However, I am encountering the following issues:

EC2 Instance Issues:

When I try to open or access the Public IPv4 addresses of the instances from the AWS Console, the page attempts to load but fails with the error: "This site can’t be reached. 54.234.104.18 took too long to respond." This happens for both the EC2 instances. However, when I RDP into the EC2 instances and try to access their Public IPv4 addresses from within, they open without any issues. The Security Configuration for the EC2 instances is as follows: Enter image description here
Enter image description here

ALB Issue:

After creating the ALB and Target Groups, following the same AWS Onboarding link, when I try to access the ALB DNS name by copying and pasting it into a browser, I receive an error, "This site can’t be reached. my-alb-1801654594.us-east-1.elb.amazonaws.com took too long to respond." Enter image description here Enter image description here

Could someone kindly help me debug and resolve these issues?

Regards, Subhasish

1 Answer
0

Hello.

Is the web server (Apache, Nginx, etc.) process running in EC2?
As long as you look at the EC2 security group, there seems to be no problem.
Also, if you are using Windows Server, please check whether HTTP communication is allowed in Windows Firewall.
https://repost.aws/knowledge-center/ec2-windows-unable-connect-port

profile picture
EXPERT
answered 25 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions