Skip to content

Add support for consuming credential_process in 'aws-vault exec'. #1087

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

Merged
merged 1 commit into from
Feb 3, 2023

Conversation

jmczerk
Copy link
Contributor

@jmczerk jmczerk commented Dec 6, 2022

The AWS CLI supports calling an external credential provider via the credential_process configuration option. However, as stated in the AWS CLI Docs:

NOTE: Unlike with assume role credentials, the AWS CLI will NOT cache process credentials. If caching is needed, it must be implemented in the external process.

I have a use case where I must call an external process to obtain a credential. I wish to cache this credential to avoid repeated API calls and 2FA prompts. Rather than rolling my own caching, I would prefer to make use of aws-vault for this purpose.

This PR implements the equivalent credential_process logic in aws-vault exec. I am aware of the existing use case of using credential_process from the AWS CLI to invoke aws-vault; I have attempted to differentiate these use cases in my edits to USAGE.md.

@jmczerk jmczerk force-pushed the feature/credential_process branch from dcff960 to 9319cc8 Compare December 19, 2022 15:03
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 this pull request may close these issues.

2 participants