- Newest
- Most votes
- Most comments
It's not clear from your comment where you have set the security group. If the security group on the EC2 instance only allows connections from your IP address then the health check will fail because you must allow connections from the load balancer. You don't have to allow connections from your IP address because from the instance perspective, connections will appear to come from the load balancer.
Okay it seems that changing the security group ips to 0.0.0.0 removed the 504 gateway timeout. My question now is how can I make this website only visible to me ? As for staging purposes I would always use the security group settings. I've also noticed that the Certificate is being shown as not secure even though I'm using the correct certificate in the load balancer.. causing the site, to have too many redirects ..
You can attach a security group to the ALB: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-update-security-groups.html
Relevant content
- asked 3 months ago
- asked 3 months ago
- asked 3 months ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Also something which I would like to mention is that the security groups are set to use my ip only since its a staging website. I don't know if this would interfere with the connection of the ALB and security group