New – AWS Public IPv4 Address Charge + Public IP Insights | Amazon Web Services
aws.amazon.com
We are introducing a new charge for public IPv4 addresses. Effective February 1, 2024 there will be a charge of $0.005 per IP per hour for all public IPv4 addresses, whether attached to a service or not (there is already a charge for public IPv4 addresses you allocate in your account but don’t attach to […]
    • @[email protected]English
      3•1 year ago

      Well the spec was created in 1995 and the 6bone(tunnel based testing network created in 1996) was shutdown in 2006 due to the increase in native routing. That is IPv6 had a sufficient internet presence that the test network no longer felt necessary…and here we are almost 20 years later…soooooooooooo…yeahhhhhhh. Tbh IPv6 has existed for basically the entire existence of the wide spread use of the Internet yet it was never deployed back then.

  • @orangeboatsEnglish
    5•1 year ago

    Meanwhile, GitHub is still IPv4 only…

  • @iwasgodonceOPEnglish
    4•1 year ago

    Would be nice if lambda supported ipv6 for outbound connections, I’ve been waiting a while.

  • @eleitlEnglish
    2•1 year ago

    Hetzner has been doing it for a while.

  • @[email protected]English
    2•1 year ago

    Honestly what I find kinda crazy about this is the price of $0.005/hr is the same cost as the cheapest EC2 instance, meaning you can get an entire server(low power but still) or a single IP address. Interestingly GCP also charges for in use IPv4 which I didn’t know, last I used GCP they only charged for IPs you weren’t using