AWS to charge customers for public IPv4 addresses from 2024
www.theregister.com
Perhaps that'll focus your minds on speeding up your adoption of IPv6, eh?

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.

  • cwagner@lemmy.cwagner.me
    3·
    1 year ago

    My ISP doesn’t give me v6 without giving up real v4. GitHub according to posts does not support v6. I think we are still a while away from v6 in “the west”.

    • r00ty@kbin.life
      7·
      1 year ago

      That’s a really stupid thing for that ISP to do. It doesn’t make sense. IPv6 costs them virtually nothing, yes the real IP costs them. But they’re stretching out the time they need to provide it by putting conditions behind the ipv6 allocation.

      Look up in this thread and just get an ipv6 tunnel, I used tunnels for 5 years between 2011 and 2015, until my ISP provided IPv6. While bigger businesses aren’t going to go ipv6 only any time soon, I think smaller server operators might just do that to save money. When the cost of the IP becomes a larger part of the cost of the service.

      • cwagner@lemmy.cwagner.me
        2·
        1 year ago

        I know I can install a tunnel, but I don’t see the benefit with everything supporting v4 any way. Hell, I myself use 3 v4 addresses.

        And I agree that it’s weird, but what can I do. Biggest cable internet provider in Germany.