logoalt Hacker News

hoppyluketoday at 11:34 AM2 repliesview on HN

My estimate was only $21M (vs ~$0.01 average bill). Wish I had checked status sooner and saved myself the panic!

My process went: verify email is not phishing (it was), login to console and check dashboard (same amount), attempt to understand cost (cost management kept contradicting itself), try to log support ticket and only on that part did I notice the status notification. At least I can breathe again now!


Replies

thinkindietoday at 1:48 PM

A friend of mine went through the same - he got an alert for bill over budget, he logged in and boom 107M$.

I was on the phone with him and we checked that he didn’t leak any APIs keys but no traffic at all. I even thought of a breach at a vendor he uses for some s3 stuff before I found this thread on HN.

zengineertoday at 12:23 PM

same process, same near heart attack - especially some days ago I had malicious activity on my platform and thought that now they actually found something.

Apparently you can trigger an Action (e.g. prevent uploads) when the billing alert triggers, but then my platform wouldn't work anymore, just because AWS had an issue. Also insane that Amazon still hasn't send an email to clarify.