News for hackers. Stuff that matters.
Re:EC2's most dangerous feature by abofh on Sunday October 09, 2016 @09:25AM (#12671092)
Most of it is - your instance ID, network position, etc, will never change after boot (or 'start' if you stop it) - so caching it is just fine. There's very little that will change on a running instance except of course, the IAM credentials referred to in this article (as they expire within 90 minutes IIRC).
Re:EC2's most dangerous feature by jamiesonbecker on Sunday October 09, 2016 @11:00AM (#12671475)
The irony is that the attempt to make the instance creds secure by rotation actually prevent protecting them in this fashion. A local file, readable only by root, w/ embedded keys is actually far more secure than the current implementation.
Re:EC2's most dangerous feature by TheDong on Monday October 10, 2016 @01:26AM (#12675223)
It's easy to implement that yourself. Generate a pair of IAM keys and drop it on the filesystem or bake it in the ami or application or whatever.

What they have reduces the duration of a vulnerability so that if you know someone had access to your machine at some point in time, you cna figure out from there how long their keys would have lasted and scope down the timeframe to start digging with in cloudtrail