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.

  • The Doctor@beehaw.orgEnglish
    58·
    1 year ago

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

      • HousePanther@lemmy.goblackcat.comEnglish
        15·
        1 year 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·
          1 year 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.

            • tychosmoose@lemm.ee
              2·
              1 year ago

              Interesting. In NC here. Not sure if there’s a difference regionally. I was seeing that kind of RTT on ipv4, but ipv6 was slower. I’ll need to give it another try. The last time I did was at my last place where I had the BGW210. I have the BGW320 now and haven’t tried on that. Maybe that, or changes in their routing since then will make a difference.

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

      The same goes for my place of work. It’s going to be shit loads of fun when we are forcibly transitioned. I hope before that time I will be doing web development work and kissing my professional career in infrastructure good bye.

    • r00ty@kbin.life
      4·
      1 year ago

      Yeah, my company totally blocks ipv6 when the VPN is on. Not sure why they’re so backward for a tech company.

      • dan@upvote.au
        8·
        1 year ago

        Their network admins are old and don’t want to learn new stuff, or their networking equipment is old and they don’t want to replace it.

          • dan@upvote.au
            3·
            1 year ago

            I know, but it wasn’t commonly used until IPv4 depletion became a more serious issue.

            • jarfil@beehaw.org
              7·
              1 year ago

              I must’ve said this at least 10 years ago: the more people move to IPv6, the more IPv4 are left free, so the less reason for moving to IPv6.

              The “migration” could easily take several more decades.