Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I use AWS daily. It takes a few days to figure out those warnings are mostly there because some customer found out the hard way what they mean. You ignore them at your own peril.

And seriously:

> This action creates a copy of the object with updated settings and a new last-modified date. You can change the storage class without making a new copy of the object using a lifecycle rule.

I hate the AWS Console UI for a bunch of reasons, but short of making you type that sentence before you proceed, I'm not sure what AWS can do here.



Could they calculate and show an estimate of the monthly charges based on current objects in the bucket before and after the change in storage class? OP may still have clicked through w/o heeding, but I can see that as a potential improvement to the warning message where a user would then be forced to understand why it didn't affect pricing in the way they assumed it would.


While I would love to see AWS do this for most things, in this case, it would have resulted in a UI that said something like "Increased monthly cost expected to be $50", and I'm sure they would have read that as "Expected monthly cost change to $50"

But an estimated cost for many things in the console would be a welcome sanity check.


Creating a copy was not what resulted in the extra charge. It's a warning about a completely different thing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: