Re: AWS IAM Roles

James Bayer


i think you'll find the approach being implemented by david takes us down
the path that enables a IAM roles best-practice recommended by amazon. IAM
credentials can be provided by the AWS metadata service inside the bosh
director instance [1] and the credentials rotated transparently to the bosh
configuration since the AWS SDK knows to use the metadata service to
retrieve credentials.


On Fri, Aug 7, 2015 at 11:53 AM, Sean Keery <skeery(a)> wrote:

I would like to see the use of the valet key pattern in this case instead
of using the latest credentials. That way my CI can commit the BOSH
deployment manifest to source control and I can trace any changes which use
that unique key (ideally just one.) It also let's me eliminate a spiff
merge of the credentials from a separate repository.


On Tue, Aug 4, 2015 at 10:43 PM, James Bayer <jbayer(a)> wrote:

dave rocamora has been looking into this a bit and getting some advice
from dmitriy:

On Tue, Aug 4, 2015 at 4:43 PM, Danny Berger <dpb587(a)> wrote:

Hi - I'm interested in being able to assign IAM Roles
to my AWS VMs. My goal is to avoid AWS credentials in my deployment
manifests and, instead, let my deployed jobs utilize the AWS metadata
endpoint to retrieve the latest credentials.

I'm also hoping such a change might eventually work for micro/boshes
that bosh-init creates, avoiding the need to manually rotate those powerful

I imagine this as a new, AWS-specific cloud option for resource pools.
Is this something which would be considered as a PR, and are there any
particular considerations I should take before implementing this?



Danny Berger

Thank you,

James Bayer

Sean Keery
Senior Solutions Architect
Pivotal <> Cloud Foundry Solutions
Mobile: 970.274.1285 | skeery(a)
LinkedIn: @zgrinch <> | Twitter:
@zgrinch <> | Github: @skibum55

Thank you,

James Bayer

Join { to automatically receive all group messages.