3 ms·

I don't know, maybe there's a legitimate UX issue here, but the author also said it only took them an hour of reading up on Glacier to resolve. That seems a rea

I don't know, maybe there's a legitimate UX issue here, but the author also said it only took them an hour of reading up on Glacier to resolve. That seems a reasonable amount of effort to have put upfront. It also speaks to poor attention to detail when a small company starting out can accidentally overlook ~$1000 per month in unexpected charges. I expect AWS to maybe help out if someone fat fingers a number and, I don't know, accidentally spins up 1000 m5.24xlarge instances for half a day. I don't expect them to step in like that for a problem sustained over the course of months.

mattashii 6y ago
> It also speaks to poor attention to detail when a small company starting out can accidentally overlook ~$1000 per month in unexpected charges. This. I manage a 15k/month AWS account, and if the expected expenditures of any day are > 15$ off the normal, I try to find out what happened. Especially after changing stuff in S3 and EC2; as with our usage patterns they should have predictable billing. > I expect AWS to maybe help out if someone fat fingers a number and, I don't know, accidentally spins up 1000 m5.24xlarge instances for half a day. I've once reserved instances in the wrong region, but (luckily) found this out the same day, and got it refunded the day after. Would have been the equivalent of a year of salary down the drain otherwise.