How a bug in VS2015 exposed my source code on GitHub and cost me $6,500

Re:How a bug in VS2015 exposed my source code on GitHub and ... by mhuffman on Monday August 31, 2015 @06:17PM (#10149439)

Maybe not, but it think it is the web service company's responsibility to alert and contact you on suspicious activity ... like a sudden $6,000 jump in service usage of spot instances in regions you have never used before.

I mean a quick automated email would be enough for you to take action. The way it is set up now, you pay for it and humbly beg Amazon to deduct those charges if they see fit.

[ Parent | on HN ]

Re:How a bug in VS2015 exposed my source code on GitHub and ... by Alupis on Monday August 31, 2015 @06:19PM (#10149450)

I agree, and it seems this sort of thing is already in place on AWS, but the author didn't heed the first two warnings. Short of just blocking things from happening and risking inconveniencing other customers, I don't see much more AWS could have done that would be reasonable.

[ Parent | on HN ]

Re:How a bug in VS2015 exposed my source code on GitHub and ... by runamok on Tuesday September 01, 2015 @12:25AM (#10150726)

You can easily set up billing alerts in cloudwatch to do this. I have done so. I agree by default it should prompt you to do so during the aws on boarding process.

[ Parent | on HN ]