> #2 has essentially no downsides and is radically simpler. If you're with AWS, you'll be charged for IPv4 public addresses: * https://aws.amazon.com/blogs/aw

> #2 has essentially no downsides and is radically simpler. If you're with AWS, you'll be charged for IPv4 public 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... If you want to 'own' IPv4 addresses, that'll cost you as well: * https://auctions.ipv4.global https://auctions.ipv4.global Certainly some will be needed for 'legacy' purposes for the foreseeable future, but the more you can reduce the use of them at your edge, the less money you'll be shelling out.