35 ms·

When AWS rolled out plans to start charging for IPv4 addresses: https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/ https:/

When AWS rolled out plans to start charging for IPv4 addresses: https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/ https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address... "As you may know, IPv4 addresses are an increasingly scarce resource and the cost to acquire a single public IPv4 address has risen more than 300% over the past 5 years. This change reflects our own costs and is also intended to encourage you to be a bit more frugal with your use of public IPv4 addresses and to think about accelerating your adoption of IPv6 as a modernization and conservation measure." Their move disgusted me and I moved from AWS to OCI.

knollimar 9mo ago
What disgusted you about it? I'm out of the loop
- jdsully 9mo ago
  They hadn't bothered to add ipv6 support to most of their services and the ones that did have it usually were only dual stack - still requiring an ipv4 address.
  - knollimar 9mo ago
    That sounds like a failure in every direction. I see why you moved
  - huslage 9mo ago
    They didn't require you to have a public IPv4 address. Just an IPv4 address.
    - pixl97 9mo ago
      Which requires dual-stack and all the issues that come with it, especially with private addresses.
- newsoftheday 9mo ago
  It was clearly a corporate money grab, not an altruistic motion as they made it sound.