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

Support role_arn and source_profile when reading aws credentials #172

Open
alza-bitz opened this issue Feb 2, 2021 · 4 comments · May be fixed by #260
Open

Support role_arn and source_profile when reading aws credentials #172

alza-bitz opened this issue Feb 2, 2021 · 4 comments · May be fixed by #260

Comments

@alza-bitz
Copy link

Hi there,

It seems the library doesn't yet support role-based access, it only supports aws_access_key_id and aws_secret_access_key unless I missed something?

Supporting role_arn and source_profile would allow users to connect using different roles into different aws accounts etc etc.

Thanks 🙂

@ian-moore
Copy link

There is a profile-credentials-provider which uses a profile name.

(defn profile-credentials-provider

@scarytom
Copy link

scarytom commented May 11, 2021

I agree with @alzadude, this seems unsupported. When calling profile-credentials-provider and specifying the name of a profile that is defined with a source_profile like bar is below then it fails.

sample credentials file:

[foo]
aws_access_key_id=AWDFASDFASEFAWEFWEF
aws_secret_access_key=324er923r890seufosiufw489ufoufresoifus

[bar]
role_arn = arn:aws:iam::123456789012:role/Administrator
source_profile = foo

@MiyamotoAkira
Copy link

MiyamotoAkira commented Nov 3, 2021

I needed this to work, so I wrote some code using the Assume Role with STS example provided by Cognitect, and butchering a copy of the profile-credentials-provider as a first dirty version:
gist client.clj

I will improve that for my use, but in case someone needs to do something similar.

filipesilva added a commit to filipesilva/aws-api that referenced this issue Dec 10, 2024
@filipesilva filipesilva linked a pull request Dec 10, 2024 that will close this issue
@filipesilva
Copy link

Took a stab at it in #260, but only noticed at PR time that the repo doesn't accept PRs :/

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

Successfully merging a pull request may close this issue.

5 participants