3 ms·

I actually had this happen to my personal AWS account a month ago. Someone had gotten ahold of one of my security keys and I stupidly didn't have 2-FA enabled.

I actually had this happen to my personal AWS account a month ago. Someone had gotten ahold of one of my security keys and I stupidly didn't have 2-FA enabled. They spun up dozens of EC2's with high-end GPU's mining crypto and managed to rack up a $600 bill before AWS flagged it and halted activity + contacted me by email. I was surprised to learn that AWS support does not have any sort of automated tooling for large-scale service wipes. I asked them just to nuke any AWS service attached to my name, as I had no personal projects or databases I needed to keep. They couldn't do this, and it was a lot of hand-cleaning and using some public tools from Github. I refused to pay the $600 and now my AWS account is permanently closed. Lesson learned: If you have your credit card attached to something, immediately enable 2-FA.

blacksmith_tb 1y ago
Also, never expect AWS support to actually help with anything around billing or account setup, I had to close out an org on a project that was EOL and it was like pulling teeth, their answer to every roadblock was "you should have known you'd need to have the credentials of your former employees, because we might have demanded their payment info too, as backup" etc. I ended up having to spin back up several email accounts so I could impersonate people who'd left years earlier, just to close their accounts (including add payment info to their accounts in order to close them... mind boggling).