Are NLB's private IPs subject to change over its lifetime?

When I create an internal NLB and attach it to target instances in a set of private subnets, the NLB is assigned private IPs from these subnets. Are these IPs subject to change over the NLBs lifetime?

I'm aware that a public-facing NLB can be given a static elastic IP, but this is strictly about an internal NLB.

주제

네트워킹 및 콘텐츠 전송

태그

아마존 VPC 네트워킹 및 콘텐츠 전송 탄력적 로드 밸런싱

언어

English

stanbsky-cb

질문됨 일 년 전1103회 조회

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

전문가

Tushar_J

답변함 일 년 전

전문가

Brettski-AWS

검토됨 일 년 전

stanbsky-cb
일 년 전
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?

Are NLB's private IPs subject to change over its lifetime?

관련 콘텐츠