- Newest
- Most votes
- Most comments
For a load balancer to be provisioned without public IP addresses, its scheme needs to be set to internal, and not internet-facing https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/how-elastic-load-balancing-works.html#load-balancer-scheme
When you create a load balancer, you must choose whether to make it an internal load balancer or an internet-facing load balancer.
The nodes of an internet-facing load balancer have public IP addresses.
The nodes of an internal load balancer have only private IP addresses.
I don't think it's possible to make the change to an existing load balancer on-the-fly, I think a replacement load-balancer would have to be provisioned with the scheme set at creation time.
Hello.
As of March 2024, I think ALB can only be configured as IPv4-only or dual stack using IPv4 and IPv6, so I don't think you can delete public IPv4 even if you change the settings on the subnet.
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-ip-address-type.html
https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-support.html
It’s only PUBLIC IPv4 that’s being charged now not private IPV4.
https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
Relevant content
- asked 8 months ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 5 days ago
- AWS OFFICIALUpdated a year ago
Thank you! I'll try this way again.
But what is the difference between an internal load balancer and an internal face load balancer? Is there no significant difference in traffic requests from clients?
Internal load balancer can only be reached by clients inside the same VPC (or peered VPCs, or across Direct Connect etc.), subject to security group rules & NACLs allowing it.
Internet-facing load balancer has a publicly routable IP address which can be reached over the internet, again subject to security groups and NACLs.