- Newest
- Most votes
- Most comments
Can you access the instance directly via the ALB hostname? If this works, the problem is between Route 53 and ALB, otherwise it's between ALB and the EC2 instance. In that case, verify security groups, target groups, possible health checks.
Sounds like you do not have the DNS record setup in your zone in route53..
Does the DNS Name for your website resolve?
UPDATE Make sure the SG on the ALB allows access from 0.0.0.0/0 on HTTP/HTTPS and on your EC2 SG make sure it allows access from the ALB SG on port HTTP/HTTPS
Yes I do, when I edit the A record on route 53 and change it to my ec2 instance elastic ip, the site opens. But when I changed the same A record to the loadbalancer that has a target group with the ec2 instance using alias the site won't come up at all.
Ok, I would take a look at your security groups on your ALB and your EC2. Make sure the SG on the ALB allows access from 0.0.0.0/0 on HTTP/HTTPS and on your EC2 SG make sure it allows access from the ALB SG on port HTTP/HTTPS
Thanks it worked, it was sg issue. efong.xyz
Relevant content
- asked 4 years ago
- asked a month ago
- asked 9 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Where can I find the ALB hostname please?
On the ALB its self
Do you mean the ALB DNS value? If that's the case, it wasn't reaching the instance. I don't know if you can guide me to start from afresh in building everything from the ec2 instance to adding a SSL cert on the domain?