- Newest
- Most votes
- Most comments
To remove public IPv4 addresses from load balancers and NAT gateways, you can follow these steps:
Create a new VPC with IPv6 enabled and new subnets that support IPv6.
Launch new EC2 instances in the new VPC/subnets. You can omit the public IPv4 assignment during launch.
Create new load balancers and NAT gateways in the new VPC. Load balancers and NAT gateways launched in an IPv6 enabled VPC will not be assigned public IPv4 addresses.
Update DNS records and security groups to point to the new resources.
Terminate the old resources like instances, load balancers, NAT gateways that were using public IPv4 addresses.
To edit the IP address type of an existing load balancer to dualstack, the VPC and subnets must support IPv6. This allows the load balancer to be accessible over both IPv4 and IPv6.
You can only update the load balancer to IPv4 only or Dualstack. You can't change an internet-facing Load Balancer to an internal Load Balancer. It's the same for NAT Gateway. You would have to recreate them.
Hi I'm not sure I understand your response. I am not trying to change an internet-facing load balancer to internal.
I am am trying to remove the public IP from my internet-facing load balancers, and my internal load balancers.
Relevant content
- Accepted Answerasked 10 months ago
- Accepted Answerasked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 years ago
Hi Giovanni
Thank you for this response.
Agreed, when following the steps on the console, those are the options I see.
To confirm, it's not possible to remove a public IP from a load balancer and nat_gateway and just have a private IP assigned to it? I'm asking this in case moving to IPv6 is not an option for me right now.