Support EC2 IAM Role SessionToken about s3-resource HOT 9 CLOSED

hi @vito, this is a quite simple ticket that will benefit the people that uses IAM roles a lot.
Why not doing it if it takes a few hours and the vault secrets option looks nice but this is easier and is a quick win. thanks

from s3-resource.

@vito can you consider opening this back up? IAM roles are really useful, whilst using vault would be ideal, It is not desirable to use it in every use case.

from s3-resource.

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

• #121141611 Support EC2 IAM Role SessionToken

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

from s3-resource.

Thinking of closing this and concourse/semver-resource#16 in favor of concourse/concourse#291 - in lieu of Vault's support for IAM roles: hashicorp/vault#307

from s3-resource.

Hi @vito - I agree that using something like Vault would be a good way to standardize key management. Would this be transparent to me as an AWS IAM Role user, or an additional piece of infrastructure I'd need to manage? Thanks for the follow up.

from s3-resource.

Vault is a server you'd need to deploy, and I imagine you'd just give its EC2 instance the necessary IAM roles. Admittedly we haven't explored it enough yet for me to give you more solid answers, but we'll be starting on it in the coming week.

from s3-resource.

Sounds good - looking forward to what you find out. Thanks again.

from s3-resource.

@fquirce I understand it can be frustrating, but I'm opposed to merging in things that are going against Concourse's intended direction so long as we have the correct direction planned. There's no real reason for anyone to be blocked on us merging this in given that you can just override the s3 resource type with your own in your pipeline.

from s3-resource.

Closing per what I mentioned before - we should at least consolidate discussion in to #291, which so far has no one talking about IAM roles.

from s3-resource.