Skip to content
This repository has been archived by the owner on Apr 23, 2020. It is now read-only.

S3 Assume Role #385

Open
rofc opened this issue Dec 11, 2018 · 1 comment
Open

S3 Assume Role #385

rofc opened this issue Dec 11, 2018 · 1 comment

Comments

@rofc
Copy link

rofc commented Dec 11, 2018

Is there any option to use an assume role with exhibitor 1.7.1? I'm using:

$ java -jar exhibitor-1.7.1.jar -c s3 --s3config bucket:key --s3credentials aws.properties

and the aws.properties looks like:

com.netflix.exhibitor.s3.access-key-id=####################
com.netflix.exhibitor.s3.access-secret-key=$$$$$$$$$$$$$$$$$$$$

is it possible to add something like:

com.netflix.exhibitor.s3.assume-role=arn:aws:iam::ACCOUNT_ID:role/ROLE_NAME

Thank you all in advance.
@rofc

@rofc
Copy link
Author

rofc commented Dec 12, 2018

I was able to assume an IAM Role using STS (with AWS_ACCESS_KEY_ID, AWS_SECRET_KEY and AWS_SESSION_TOKEN environment variables).

As described in AWS Java SDK Docs:

AWSCredentialsProvider implementation that provides credentials by looking at the: AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY) environment variables. If the AWS_SESSION_TOKEN environment variable is also set then temporary credentials will be used.

Since STS provides temporal and limited-privilege credentials, there is a need to use a very own ACCESS_KEY, SECRET_KEY and ROLE_ARN values for native assume-role solution.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant