5 ms·
The truth is that major cloud providers such as Amazon AWS have begun to charge [more] for static, routed IPv4 addresses. Last I checked (a few years ago, I su
by AStonesThrow 2y ago
The truth is that major cloud providers such as Amazon AWS have begun to charge [more] for static, routed IPv4 addresses.
Last I checked (a few years ago, I suppose), AWS APIs were incapable of using IPv6 internally, so a VPC still needed to dual-stack it in order to use AWS cloud features. That may have changed by now.
- kijin 2y agoIPv4 prices peaked during the Covid pandemic, presumably because of sudden high demand. Amazon took this as an opportunity to increase prices. Now IPv4 prices are returning to pre-Covid long-term trends. But of course Amazon won't reflect that in their pricing table.
- throw0101c 2y ago> Amazon took this as an opportunity to increase prices. IPv4 prices peaked in early 2022; AWS started charging for public IPv4 in 2024 (announced in 2023): * https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/ https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address... If they had increased prices in 2022 (or at least announced in 2022), then I could see some kind of correlation, but give it was 1.5-2 years after, I doubt there is a connection.
- bluGill 2y agoi would expect aws needs a year or two from when they decide to charge for something new just to work out the details
- throw0101c 2y ago> i would expect aws needs a year or two from when they decide to charge for something new just to work out the details The price had already dropped, and was continuing to fall, when they announced the change, so if rising acquisition cost was the primary reason for adding the IPv4 charge, it had already went away. I think AWS has looked at a utilization graph and sees a time their current pool is get used up at current rates and doesn't want to go through the hassle of acquiring more IPv4 addresses, regardless of cost (even if it is "cheap"). I also think that they have statistic for their www.Amazon.com storefront, and maybe are seeing a good proportion from IPv6 and so figure that there's a 'critical mass' (especially mobile).
- bluGill 2y agoThere is a lot of lag in decisions like this so price falling isn't enough to say anything.
- ta1243 2y agoAWS is seeing growth rates reduce and needs to pump up their revenue. They're moving onto the "squeeze" part of the cycle.
- thayne 2y agoYep, lots of AWS apis don't work over ipv6, and many require making requests outside the VPC, so you need to have at least one ipv4 address for a NAT.
- cyberax 2y agoYou can use NAT64, it works with all the AWS services. Although it's pretty stupid that services like ECR don't have IPv6.
- thayne 2y agoNAT64 requires you to have a NAT with a public ipv4 address. Or possibly pay to use someone elses NAT.
- cyberax 2y agoAWS supports NAT64 automatically if you have an Internet gateway attached, you just need to set it up in the VPC settings.
- thayne 2y agohttps://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-nat64-dns64.html https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway... Says you need to have an AWS NAT for that to work. And AFAIK, setting up a NAT requires an ipv4 elastic ip. And it makes since that AWS would want customers to have their own IP for NAT64, so that if one customer does something to get the ip address blocklisted it doesn't impact other customers.
- cyberax 2y agoYes, you're correct. Though I don't think AWS cares too much about IP blocklist, you can always just get another elastic IP at any moment.