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 tomschlick on Monday August 31, 2015 @06:02PM (#10149355)

> or at least prevent it from spinning up any new instances

This is the answer I would like to see implemented. If they can detect the key they can put a freeze on the account so that only existing resources are available.

They should also have a timeline of all created instances in every zone so you can see what has happened in the last x hours and kill all instances at once.

[ Parent | on HN ]

Re:How a bug in VS2015 exposed my source code on GitHub and ... by voltagex_ on Monday August 31, 2015 @07:14PM (#10149703)

Two things would make controlling these situations easier:

* Allow me to see all instances in all regions from a single screen

* When accounts are first created for AWS, set up some sane default IAM policies and/or hire some UI designers to fix that godawful mess.

[ Parent | on HN ]