Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modularize AWS Credentials provisioning #79

Open
jrnt30 opened this issue Apr 11, 2014 · 3 comments
Open

Modularize AWS Credentials provisioning #79

jrnt30 opened this issue Apr 11, 2014 · 3 comments

Comments

@jrnt30
Copy link

jrnt30 commented Apr 11, 2014

Similar to #74 we use an alternate method for providing AWS credentials to our application. Per AWS best practices, we use IAM roles to provide automatic rotation of the credential keys autoatmaically (http://docs.aws.amazon.com/AWSSdkDocsJava/latest/DeveloperGuide/java-dg-roles.html).

We are currently using the AWSCredentialsProviderChain with values similar to https://github.com/aws/aws-sdk-java/blob/master/src/main/java/com/amazonaws/services/s3/AmazonS3Client.java#L294

By abstracting out the actual credentials creation into a factory, it would allow a lot of customization and custom credentials schemes.

@kgjohnso
Copy link

+1
Would be nice to be able to easily use credentials from the IMDS - Instance Metadata Service.
http://docs.aws.amazon.com/AWSSdkDocsJava/latest/DeveloperGuide/java-dg-roles.html

@qc00
Copy link

qc00 commented Sep 3, 2014

+1 I have an implementation for this that uses AWSCredentialsProvider to replace the user name and password pair. This is necessary because the instance profile credentials changes regularly. Currently my code did it via reflection, but native support will be helpful.

@sksastry
Copy link

+1 Would be a great step toward AWS best practices http://java.awsblog.com/post/Tx27W1S3VWL232L/Credentials-Best-Practices. Thank you!

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

No branches or pull requests

4 participants