- Newest
- Most votes
- Most comments
Hello.
EC2 can be changed to IPv6 only.
https://aws.amazon.com/jp/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/
However, ALB cannot be configured for IPv6 only as of May 2024, so it will be a dual stack configuration using IPv4 and IPv6.
In other words, you cannot erase public IPv4 when using ALB.
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-ip-address-type.html
https://repost.aws/knowledge-center/elb-configure-with-ipv6
What would happen with those clients that don't have IPv6 yet?
I think it is possible for IPv4-only clients to access the application if the ALB is dual stacked.
As Riku_Kobayashi correctly stated, internet-facing ALBs can now be configured without public IPv4 addresses. To answer you question about IPv4 clients, this would make them unable to connect. The way you can make the setup work without your users losing access is by placing a CloudFront distribution in front of your ALB.
CloudFront shares its public IPv4 address space across vast numbers of different customers' distributions (when using the default SNI-only mode for HTTPS, which you should also do), and that's why you aren't charged for public IPv4 addresses, despite your site being accessible over IPv4 via CloudFront.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
update You can now create ALBs that do not use public IPv4. https://aws.amazon.com/about-aws/whats-new/2024/05/application-load-balancer-ipv6-internet-clients/