[apenney]

We had something similar happen with lifecycle rules, moving an entire bucket to glacier: end result was > $200k and AWS weren’t especially helpful on our attempts to refund us.

We were unaware that changes via a rule still count as an api hit per object, despite all happening in the backend. I’m sure we can’t be the only people hit by this.

[thitcanh]

The reality is that Amazon makes big bucks off the complete opacity of their costs. If you offer a UI where a click costs money, you should also display price.

But that's just my opinion. Maybe others like buying things from a menu without prices.

DigitalOcean emailed me once when I left my single $5/month instance open by mistake. AWS would never do that even for thousands.

[viraptor]

I almost did that. Someone double checking the plans raised that as an issue and instead we went with a lifecycle at some specific age rule which didn't try moving everything at once.

And yes, it's both fairly well documented and something that can catch you by surprise at the same time.

[mikeyla85]

Damn, that's insane.

Would it be so hard for them to redesign AWS to tell you what something's going to cost before you do it?