Re:Keywhiz: Square's system for distributing and managing se...
by jamiesonbecker on Tuesday April 21, 2015 @03:17PM
(#9416348)
Instance profiles (credentials) are accessible to all users for the life of the instance. Until AWS provides an ability to lock down portions of instance metadata and/or a way to delete early in the boot process, it's much safer to bake your bootstrap key directly into the AMI as root (or specific user) visible only.
Re:Keywhiz: Square's system for distributing and managing se...
by toomuchtodo on Tuesday April 21, 2015 @04:41PM
(#9416930)
Good point. I've been using IAM roles to bake the AMIs with Packer, where the key is fetched during the bake process; perhaps I'll investigate sneaker if there's time tonight.
Thanks for rubber duckying this with me!
Re:Keywhiz: Square's system for distributing and managing se...
by zwily on Tuesday April 21, 2015 @03:26PM
(#9416428)
Yeah, perhaps as an additional block device you can mount with whatever permissions you want.
Re:Keywhiz: Square's system for distributing and managing se...
by jamiesonbecker on Tuesday April 21, 2015 @03:31PM
(#9416458)
right on, like the FUSE in question.. but securely mounting something remotely means storing a bootstrap key somewhere anyway. Turtles all the way down :)
I had been planning to do this with keys stored in S3 and IAM roles to retrieve the keys at instance boot time, stored in a ramdisk, but this saves all of that trouble.