1 Answer
- Newest
- Most votes
- Most comments
1
NLB's private IPs will not change over its lifetime
When you create an internal load balancer, you can optionally specify one private IP address per subnet. If you do not specify an IP address from the subnet, Elastic Load Balancing chooses one for you. These private IP addresses provide your load balancer with static IP addresses that will not change during the life of the load balancer. You can't change these private IP addresses after you create the load balancer.
Reference: https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html
Relevant content
- Accepted Answerasked a year ago
- asked 8 months ago
- asked a year ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
Thank you for the prompt reply. I did see this in the docs, but I assumed I misunderstood it. Let me explain:
When I deployed this particular private NLB, it originally had EC2 instances present as targets across 3 AZs, and consequently, the NLB had private IPs in each AZ's corresponding subnet. Currently, I only have instances in one AZ, and the NLB now only has one IP associated with it.
This seems to run counter to the behaviour quoted from the docs above. Is there a part of the docs I've missed that describes such adjustments to NLB IPs across AZs?