Yeah, I did that, though in my case it was a bitbucket repo I thought was private, but somehow ended up public (obviously stupid to ever be checking in the keys at all).
All I had setup was a micro S3 instance I'd been using for some toy craigslist scraping & hadn't touched for months.
Then out of the blue I get an "urgent please check your account" email from amazon. Go check the AWS console, and what do you know -- maximum number of maxed-out instances instances churning away with 100% CPU usage in every region on earth. The charges were already about to $50,000 when I turned everything off.
I wrote a very, very apologetic email to amazon, and they forgave all the charges, for which I was very grateful.
All I had setup was a micro S3 instance I'd been using for some toy craigslist scraping & hadn't touched for months.
Then out of the blue I get an "urgent please check your account" email from amazon. Go check the AWS console, and what do you know -- maximum number of maxed-out instances instances churning away with 100% CPU usage in every region on earth. The charges were already about to $50,000 when I turned everything off.
I wrote a very, very apologetic email to amazon, and they forgave all the charges, for which I was very grateful.
Definitely a learning experience.