[luhn]

What's really offensive about this is that AWS does not have good enough IPv6 support for most customers to migrate off of IPv4, even if they want to.

ALB uses 2-4 IPv4 addresses. It supports dualstack, but not IPv6-only.

CloudFront does not support IPv6 origins.

All APIs except for a handful are IPv4-only, so you either need a VPC endpoint (priced per month per AZ per API) or an IPv4 address to communicate with them.

It frustrates me that I'll be paying for a bunch of IPv4 addresses that I don't need for any business reason, I only have them because they're necessary within the AWS ecosystem.

[kichik]

I find the lack of IPv6 support for their own APIs the most insulting. In my case, I would end up paying more for VPC Endpoints than I would for IPv4 addresses. There is no escaping from this new fee. I really hope they resolve this soon.

[fulafel]

It's also pretty ridiculous their reverse proxy (ALB) "dual stack" mode can't serve IPv6 clients unless your backend app server is also IPv6. This is so much worse than anything you'd set up yourself.

[zokier]

That doesn't seem right, for example this reddit thread (yeah, I know) says that ipv6 alb -> ipv4 target should work fine: https://old.reddit.com/r/aws/comments/1145bcw/dualstack_alb_...

[fulafel]

Like most of the people in the linked reddit thread, I read the docs (and web search results[1] and LLM answers) as requiring v6 behind the ALB too. Not taking the poster's word for it yet but could be worth another look.

[1] https://repost.aws/knowledge-center/elb-configure-with-ipv6

[zokier]

https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-su...

yeah, that's a sad table. AWS has gazillion services and handful have even basic dual-stack support and even fewer have ipv6-only support :(