1 Answer
- Newest
- Most votes
- Most comments
0
As you noted, for each NLB, it gets a static per AZ. The IPs stay the same during the lifetime of the NLB. Therefore, the client can technically using those IPs directly.
As you mentioned, the might be events that impact an entire AZ. When that happens, the static IP of the NLB in that AZ usually would be removed from the DNS (DNS health check). When that happens, if the clients have that "bad" IP hard coded somewhere and keep connecting to it, they would still experience problem. That is why, DNS is preferred. If the clients has to use the static IP directly, some fail over logic need to be built into the client side so that it can switch over to another AZ's NLB static IP, when a single AZ failure happens.
answered 3 years ago
Relevant content
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 7 months ago
Just a question related to the topic. Once the AZ is recovered, the static IP of that AZ is the same as before? If not, associating manually an EIP to an AZ will not change it in case of failure?
Thanks!