Fix Incoming! Empty S3 buckets won't be able to make your AWS bill explode

Haven't read into this too much, but I think the affected person that made this get attention was a solo dev that was prototyping a solution for one of his customers.

And the reason he raised a stink was because he had a huge bill, as the name he chose for his bucket was by chance the same an open source project used as a sample bucket name, so whenever someone deployed it without first customising the config, it was pinging his bucket and getting a 403.

Edit: Here's his original medium post / Archive

Given the timing i suspect this was the article that drove the change. It was shared quite a bit over past few weeks.

This is why most of our thornier bugs eventually get fixed.