- Newest
- Most votes
- Most comments
Hello,
As you are not able to connect to one of the NLB IP for this NLB, I would request you check that there should be backend target present in the same AZ as of this NLB node then only the connection will be successful.
If you only have one target then make sure that NLB attribute cross-zone is enable for this NLB, so that both node can connect to the same target. If there is target present for the NLB node than only we can connect to that NLB node.
[] Network Load Balancers - Availability Zones - https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#availability-zones
"After you enable an Availability Zone, the load balancer starts routing requests to the registered targets in that Availability Zone. Your load balancer is most effective if you ensure that each enabled Availability Zone has at least one registered target."
Thanks
Thanks. For this particular scenario, we have 1 target behind the NLB, but the NLB is provisioned to multiple AZs. Enabling the cross-zone feature on the NLB allows this to work again.
Relevant content
- Accepted Answerasked 2 months ago
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago