Okay, so we're a month in and I'll just say -- this new charge just sucks. It appeared they were going to give accounts credit for one IP address, and indeed charges actually disappeared mid-month for a while, but then later on they came back.

It's about $3.50 a month per IP, but they will waive this fee during the initial "Free tier" year you get after signing up. I think this is worse, because like other free tier conversions, you'll have zero clue what things cost until your year is up.

Where before I had accounts where they would incur under $5/month of compute and storage charges, this is now edging up to double that. You are charged whether the machine is running or not, and also whether the IP is elastic or not.

Now, I get that in some cases AWS customers will spin up dozens of machines which don't need public IPs but because of the way AWS works be default, those instances will get public IPs. But the fact you can't use CloudFront against IPv6 boxes or private IPs -- forcing you to use IPv4 IPs you have to pay for -- is crappy.

There IS a way around this -- if your site is static, you can just put your pages into an S3 bucket and point CloudFront at that. And if your site is dynamic, you could use Serverless/Lambda to serve your content. But if you have a dynamic or Database backed site (using a traditional CMS like Wordpress), you have to use an IPv4 address to communicate out.