Re:I Followed the Official AWS Amplify Guide and Was Charged...
by cdchn on Thursday November 14, 2024 @07:35AM
(#42135609)
Cost Anomaly alerts do exactly this.
You can't even setup Cloudwatch alerts on your actual spend, the only metric available to you is "EstimatedCharges".
Re:I Followed the Official AWS Amplify Guide and Was Charged...
by oliwarner on Thursday November 14, 2024 @08:28AM
(#42135968)
Which is great if you understand them and set them up. The post here is an experience following an Amazon tutorial and without expecting it, ending up $$$ in debt.
Again, Amazon isn't stepping up to protect users from themselves. They could do a lot more.
Re:I Followed the Official AWS Amplify Guide and Was Charged...
by cdchn on Thursday November 14, 2024 @09:04AM
(#42136217)
They refunded him the money, without a lot of hassle. He toddled into a rough edge, bumped his head, Amazon made it better and apparently gave him a lollipop as well and sent him on his way. I think Amazon should get some credit here.
In the olden days if we spotted a customer ringing up a colossal bill, we would tell them. These huge Amazon bills are fast but still multiple days. They can trivially use rolling-projection windows to know when an account is having a massive spike.
They could use this foresight to call the customer, ensure they're informed, give them the choice about how to continue. This isn't atomic rocket surgery.
"Oh but profit" isn't an argument. They are thousands of dollars up before a problem occurs. The only money they lose is money gained through customer accident. Much of it forgiven to customers who cannot afford it. It's not happily spent. They can do better business.