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.

    • UntouchedWagons@lemmy.caEnglish
      4·
      1 year ago

      I’ve tried using Hurricane Electric’s tunnels on pfsense but it just kills my internet connection and the only solution is to reboot

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

        It is very area dependent and what path your data takes. It just so happens that the pathway that my data takes to reach Hurricane Electric’s server in NYC is really optimal. I have latency comparable to a native IPv6 network. It’s certainly better than my ISP, Verizon’s, native IPv6 in my area where my data goes to Virginia and then back to NYC.