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.

  • flip@lemmy.nbsp.one
    94·
    1 year ago

    Hopefully this will push IPv6 adoption further. It is a clusterfuck how long IPv6 exists and how often one has to still fall back to IPv4.

    • HousePanther@lemmy.goblackcat.comEnglish
      19·
      1 year ago

      This is my thought. It’s about time greater adoption of IPv6 happens. As much as I don’t like corporations getting greedier, in this case however, Amazon is doing us a favor by spurring IPv6 adoption on.

      • dan@upvote.auEnglish
        14·
        1 year ago

        IPv6 is already relatively widespread in the USA (and many other countries) on the client-side, especially on mobile networks.

        • T-Mobile’s network is almost entirely IPv6-only, using 464XLAT for connectivity to legacy IPv4-only servers.
        • The majority of traffic to Facebook (around 62%) is via IPv6. https://www.facebook.com/ipv6
        • As of June 2022, 73% of Comcast and 72% of AT&T customers had IPv6 connectivity. https://www.worldipv6launch.org/measurements/
        • People that play online games often try to use IPv6 to avoid NAT, as it reduces latency.

        The main issue is that a lot of sites aren’t available over IPv6. Hopefully Amazon helps push that along.

        • HousePanther@lemmy.goblackcat.comEnglish
          7·
          1 year ago

          I have IPv6 connectivity through Verizon FiOS. The trouble is that in my area it is poorly implemented and markedly slower than IPv4. I would much rather use 6 but not at a performance penalty.

        • Magnus Åhall@lemmy.ahall.se
          5·
          1 year ago

          In Sweden we have just one ISP for non-commercial customers providing native IPv6 adresses (Bahnhof) on fiber connections, and even then we can’t get a static prefix from them.

          Not quite sure on the mobile ISPs though.

            • Magnus Åhall@lemmy.ahall.se
              1·
              1 year ago

              I guess that means able to access services on the Internet over IPv6, not me being able to get a /64 and providing services myself to others.

              Sort of ok for phones I guess, although not as great if someone doesn’t have access to fiber and have to use a mobile link in a residential environment.

              Bahnhof actually just provides NAT:ed fiber connections as well as default, but will issue a public, unique IP if asked (at no additional cost).

      • r00ty@kbin.life
        6·
        1 year ago

        I suspect greed is involved. But since the new allocation of ipv4 hasn’t been possible for quite some time in US and Europe. I think the price of those IPs that are assigned to providers is going to gradually rise.

        And to think, I remember when I got a business ISDN account for my old office. They pretty much just gave you a free (well included in the price) /24 without even asking.

        Different times.