The next few months may be hard for you. AWS will start charging for ipv4 on February 1st, so it’s likely that either a mass migration is coming or prices for many services will increase accordingly to pass that cost along to customers.
I run a very small site for a local club from an AWS Nano instance. Minimum cost is important. When AWS announced that they would begin charging for public IPv4 addresses, I enabled IPv6 on the subnet (which was tricky), updates the DNS record, and removed the IPv4 address.
In my case, no one notices or cares because they almost always access the site through their cell phones.
I was implementing IPv6 networking at an ISP/VPS provider in my 20s including customized Xen network startup scripts(because they didn't support v6 or VLANS).
AWS doesn't have good enough IPv6 support for an exodus from IPv4. ALB does not support IPv6-only. Cloudfront only supports IPv4 origins. API Gateway only supports IPv4.
The IPv4 price is still tiny, and you anyway have to pay for it since going IPv6-only is not viable for a service in 2024 still. It's not going to significantly move the needle towards IPv6. And the price hikes will also be tiny.
Well, my employer’s AWS bill is in the region of $20m/year and the additional IPv4 tax is on track for adding an additional $250k to that for no benefit at all.
Well, 1.25% is quite tiny. And I'd bet you're not moving to IPv6 anyway, at least not entirely, since a good amount of people are probably accessing your services over IPv4-only connections.
Given that this was AWS doing what their top two competitors were already doing, and that for most people it’s smaller than the price hikes GCP customers have had last year and coming February 1st, I’m skeptical that anyone significant is going to make this the issue they leave over.
