I tried to setup an IPv6-only VPC last month and ran into lots of edge cases. For example, Terraform's aws provider doesn't support the http_protocol_ipv6 metadata option for EC2 instances, you can only set it in a launch template. It's a two year old issue: https://github.com/hashicorp/terraform-provider-aws/issues/2...

I'm glad to see AWS driving people towards IPv6, but the tooling and documentation need to get a lot better.

This is essentially a broad price increase without saying it as things stand today. Most AWS services require IPv4 and in most cases even if you don't require IPv4 there isn't even a way to turn it off.

Example: if you run load balancers you are going to pay for every single IPv4 address with no way to turn it off, even if you are IPv6-only. This means an ALB with 3 AZs (What AWS recommends), went from 20/mo to 32/mo and no amount of planning or optimizations can lower that cost.

$0.005 per hour per IP, or $43.8 per year, is expensive. Too expensive.

It should be noted that this brings AWS in line (slightly above) with GCP ($0.004/hr) and Azure ($0.0036/hr). It's still a frustrating change, though.

To me this signals the arrival of the point that all cloud lock in "paranoid dinosaurs" were warning about all these years.

Its all gonna get worse from here now that the market is settled. It was inevitable that they would have to start eating thier clients to keep the stock market happy.

It's better to buy your own IPv4 addresses :) The price of single IPv4 address, is about the same as renting it for a year from AWS for $43.

One solution is CloudFlare Automatic IPv6 Gateway https://blog.cloudflare.com/introducing-cloudflares-automati...

Wow this is a huge price increase for AWS. Its kind of shocking that they are raising prices for IPv4 addresses instead of offering a discount for hosts that are not using a public IPv4 address. Very un-aws like.