Re:Open Guide to Amazon Web Services
by voganmother42 on Tuesday October 11, 2016 @05:01PM
(#12688491)
we use iam roles and credstash(dynamodb and kms) for retrieving database credentials. My comment was mostly in terms of the fact we cannot control the rotation for roles, say in the event of a breach like where someone committed keys to github and I can explicitly expire/rotate(assuming those keys were not themselves temporary and have not already expired :))
I believe you can actually [0]. In a production setting it's a lot harder to accidentally leak the credentials - my concern would be if someone compromised the instance or if it was tricked into opening the instance store up to the net, such as a badly configured nginx instance (how you'd do that accidentally though I have no idea)
[0] http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use...
Re:Open Guide to Amazon Web Services
by voganmother42 on Tuesday October 11, 2016 @05:28PM
(#12688665)
Good point! slightly less granular than per key but still very helpful, thanks!
You've also got to go to the trouble of getting the credentials on your box to start with. With instance roles, you can launch an instance and have it immediately capable of doing what your application needs. In the case of most applications my company runs, the instance profile is enough and no further security credentials are required. When database credentials are required, they're retrieved via S3, authenticated by the instance profile.