You can reference this link on how to update the Elastic IP of a NLB: https://aws.amazon.com/premiumsupport/knowledge-center/elb-attach-elastic-ip-to-public-nlb/
I want to directly address your question about replacing the ElasticIP that you configured for the NLB. Once an NLB is created with an ElasticIP you can always add another node with an additional EIP for the purpose of resilience across zones. As mentioned before, this is covered here: https://aws.amazon.com/premiumsupport/knowledge-center/elb-attach-elastic-ip-to-public-nlb/.
This does not cover the use case that you are describing which is to replace the IP of the an existing NLB node(s). Unfortunately, once an NLB node is created, you cannot alter the ElasticIP associated with it. This is documented here:
As quoted from the documentation here: https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html:
"...When you create an internet-facing load balancer, you can optionally specify one Elastic IP address per subnet. If you do not choose one of your own Elastic IP addresses, Elastic Load Balancing provides one Elastic IP address per subnet for you. These Elastic 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 Elastic IP addresses after you create the load balancer..."
As such, you are correct. You will have to create the NLB again, if you want to alter ANY existing Elastic IP assignment to ANY existing NLB nodes.
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- EXPERTpublished 4 months ago