Cloud giant AWS will start charging customers for public IPv4 addresses from next year, claiming it is forced to do this because of the increasing scarcity of these and to encourage the use of IPv6 instead.

It is now four years since we [1]officially ran out of IPv4 ranges to allocate, and since then, those wanting a new public IPv4 address have had to rely on address ranges being recovered, either from from organizations that close down or those that return addresses they no longer require as they migrate to IPv6.

If Amazon's cloud division is to be believed, the difficulty in obtaining public IPv4 addresses has seen the cost of acquiring a single address rise by more than 300 percent over the past five years, and as we all know, the business is [2]a little short of cash at the moment , so is having to pass these costs on to users.

[3]

"This change reflects our own costs and is also intended to encourage you to be a bit more frugal with your use of public IPv4 addresses and to think about accelerating your adoption of IPv6 as a modernization and conservation measure," writes AWS Chief Evangelist Jeff Barr, on the company [4]news blog .

[5]

[6]

The update will come into effect on February 1, 2024, when AWS customers will see a charge of $0.005 (half a cent) per IP address per hour for all public IPv4 addresses. These charges will apparently apply whether the address is attached to a service or not, and like many AWS charges, appear inconsequential at first glance but can mount up over time if a customer is using many of them.

These charges will apply to all AWS services including EC2, Relational Database Service (RDS) database instances, Elastic Kubernetes Service (EKS) nodes, and will apply across all AWS regions, the company said.

[7]

However, customers will not be charged for IP addresses that they own and bring to AWS using Amazon's BYOIP feature. AWS offers a free tier for EC2, and this will include 750 hours of public IPv4 address usage per month for the first 12 months, starting from the same date the charges do.

To try and help customers get a handle on how this might affect their AWS bill, the company said it is adding information on public IPv4 addresses to the AWS Cost and Usage Report (CUR). It also unveiled a new feature of Amazon VPC IP Address Management (IPAM) called [8]Public IP Insights , which is intended to simplify analysis and auditing of public IPv4 addresses.

10 years later

It is now more than a decade since IPv6 was [9]officially launched , but adoption has been slow and gradual as many organizations saw little need to change at first, especially when managing a migration from the older standard to the new one was likely to be complex.

Although the world officially ran out of unallocated IPv4 addresses in 2019, according to the European regional Internet registry RIPE, it [10]posted figures last year showing that the IPv4 routing table still has six times as many entries as that for IPv6.

However, this apparent disparity may be slightly misleading, it claimed, as internet registries have taken advantage of the massive 128-bit address space of IPv6 to ensure that "organizations receive blocks that are, in many cases, large enough to cover all their future addressing needs" when allocating new address ranges, whereas IPv4 saw ever smaller allocation sizes as the address space filled up.

[11]IPv6 for Dummies: NSA pushes security manual on DoD admins

[12]Reverse DNS queries may reveal too much, computer scientists argue

[13]Microsoft to kill off old access rules in Exchange Online

[14]OVHcloud opens up Bring Your Own IP service for IPv4 failover

"Even once all networks have deployed and announced IPv6, we can expect the routing table to be smaller than that for IPv4," RIPE claimed.

RIPE also quoted IPv6 adoption by end users last year, as estimated by Google and APNIC, the regional internet address registry for the Asia-Pacific region, as being between 30 percent and 40 percent.

[15]

But as The Register wrote back when IPv4 addresses officially ran out, it is going to be with us for a good few years yet. RIPE was predicting then that it might take "five to 10 years" before the world starts to truly abandon the IPv4 address space. Four years of that have already passed, and IPv4 still seems to be going as strong as ever. ®

Get our [16]Tech Resources



[1] https://www.theregister.com/2019/11/25/ipv4_addresses_gone/

[2] https://www.theregister.com/2023/04/28/cloud_slowdown_hits_amazon_as/

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZMfap2aVQCMDVQoSxcd9TgAAA9g&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZMfap2aVQCMDVQoSxcd9TgAAA9g&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZMfap2aVQCMDVQoSxcd9TgAAA9g&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZMfap2aVQCMDVQoSxcd9TgAAA9g&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[8] https://docs.aws.amazon.com/vpc/latest/ipam/view-public-ip-insights.html

[9] https://www.theregister.com/2012/06/05/ipv6_launch_day/

[10] https://labs.ripe.net/author/wilhelm/ipv6-10-years-out-an-analysis-in-users-tables-and-traffic/

[11] https://www.theregister.com/2023/01/25/nsa_ipv6_guidelines/

[12] https://www.theregister.com/2022/09/29/reverse_dns_queries_reveal_too/

[13] https://www.theregister.com/2022/09/28/microsoft_exchange_online_cars/

[14] https://www.theregister.com/2022/09/07/ovhcloud_ipv4/

[15] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZMfap2aVQCMDVQoSxcd9TgAAA9g&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[16] https://whitepapers.theregister.com/