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

Per request config #273

Open
beno opened this issue Nov 24, 2018 · 1 comment
Open

Per request config #273

beno opened this issue Nov 24, 2018 · 1 comment

Comments

@beno
Copy link

beno commented Nov 24, 2018

For role based access, ExAws needs to work with dynamic KEYs and SECRETs on a per request basis.

See https://github.com/ex-aws/ex_aws/wiki/IAM:-AWS-Role-Based-Access-for-users-with-MFA-(MultiFactorAuthentication) for details.

Currently arc is only capable to use the fixed credentials from config, making it incompatible with IAM roles. Overriding the config values at runtime (Application.put_env) is not an option, since the 'root account' credentials must be preserved.

Am I seeing this correctly? I think maybe passing in a config S3 option or defining/calling a config function in Arc.Definition could fix this. Thoughts?

@eprothro
Copy link

I'm not sure I understand the motivation for dynamic keys and secrets per-request.

However I agree that I'd like to be able to define an IAM role with ex_aws config and this role be assumed and used by arc

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

2 participants