153

AWS: IPv4 addresses cost too much, so you’re going to pay (www.theregister.com)

submitted 11 months ago by pnutzh4x0r@lemmy.ndlug.org to c/technology@beehaw.org

55 comments fedilink hide all child comments

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.

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 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.

you are viewing a single comment's thread
view the rest of the comments

[-] drwho@beehaw.org 59 points 11 months ago

I'm going on professional year 24 of clients requiring that IPv6 be deactivated on every device in their network. Whee.

[-] negativenull@negativenull.com 42 points 11 months ago

My current ISP still does not offer IPv6 🤦 🤦 🤦

[-] housepanther@lemmy.goblackcat.com 15 points 11 months ago

Verizon, my ISP, offers IPv6 in my area but the implementation is broken and it ends up being an order of magnitude slower than simply using IPv4 and HE as an IPv6 tunnel broker.

[-] tychosmoose@lemm.ee 5 points 11 months ago

AT&T is the same. And the last time I looked they don't give you enough address space to host your own subnet. You get a /64 instead of a /56. And it's slower than ipv4.

Every few months I try it out, complain and then switch it off.