News for hackers. Stuff that matters.

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

Re:How a bug in VS2015 exposed my source code on GitHub and ... by nsxwolf on Monday August 31, 2015 @06:23PM (#10149472)
There's a huge amount of value in a service that insulates you from mistakes like this. You really, really have to know what you're doing with EC2 because it is a loaded gun.

Personally, I don't like using things that are covered in spring loaded booby traps that require eternal hypervigilance in order to avoid nasty financial consequences. Certainly not when deploying something that would be right at home on something like Heroku.

[ Parent | on HN ]
Re:How a bug in VS2015 exposed my source code on GitHub and ... by Alupis on Monday August 31, 2015 @06:25PM (#10149490)
> You really, really have to know what you're doing with EC2 because it is a loaded gun.

That's a fair point, but keep in mind the article author was given several warnings that something was wrong, but failed to correct the problem each time (which resulted in the huge bill he ultimately received).

At what point is the responsibility on the author here?

[ Parent | on HN ]
Re:How a bug in VS2015 exposed my source code on GitHub and ... by chrismcb on Wednesday September 02, 2015 @02:45AM (#10157757)
The author deleted the old key and created a new one and changed his password as soon as he was notified. How did he fail to correct the problem? What else should he have done?
[ Parent | on HN ]