3 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
Problem solved: It was just a wrong security group associated with the load balancer. To find that the VPC flow logs were very helpful.
répondu il y a un an
0
Thanks for the answer. The ALB is Internet Facing. Where is the ALB located in the VPC ? Is it between the IGW and the subnets ? Is there a way to capture flows before they reach the ALB in the VPC ?
répondu il y a un an
ALB is between the Internet Gateway and the subnet.
What is the HTTP status code when accessing ALB?
504(Gateway Timeout)?
0
Are you creating ALB for internal use?
If accessed from the outside, it must be created with Internet Facing.
Contenus pertinents
- demandé il y a un an
- demandé il y a 10 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
I have exactly the same issue. The security group associated with the load balancer is the "default VPC security group", which have very permissive settings allowing all traffic on all ports. In what way was your security group wrong? I would be very grateful to hear more how you solved it. Thanks!