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.

Sign up for GitHub

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

Jump to bottom

Support aws-cli's AWS_CREDENTIAL_EXPIRATION envar #1103

Closed
1 task done
jaklan opened this issue Jan 1, 2023 · 1 comment · Fixed by #1124
Closed
1 task done

Support aws-cli's AWS_CREDENTIAL_EXPIRATION envar #1103

jaklan opened this issue Jan 1, 2023 · 1 comment · Fixed by #1124

Comments

@jaklan
Copy link

jaklan commented Jan 1, 2023 •
edited
Loading

  • I am using the latest release of AWS Vault

After merging and releasing aws/aws-cli#7398, the official envar supported by aws-cli is AWS_CREDENTIAL_EXPIRATION, so I believe it should replace AWS_CREDENTIALS_EXPIRATION.

❯ AWS_PROFILE=some-profile aws configure export-credentials --format env
export AWS_ACCESS_KEY_ID=[redacted]
export AWS_SECRET_ACCESS_KEY=[redacted]
export AWS_SESSION_TOKEN=[redacted]
export AWS_CREDENTIAL_EXPIRATION=2023-01-01T18:18:38+00:00
@jaklan
Copy link
Author

jaklan commented Jan 1, 2023 •
edited
Loading

Also important due to that:

when envars are set, aws configure export-credentials just utilise them. So AWS_CREDENTIAL_EXPIRATION variable has to be set by granted (or any other tool) and then aws configure export-credentials would work correctly

aws/aws-cli#7388 (comment)

@mtibben mtibben mentioned this issue Feb 3, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support aws-cli's AWS_CREDENTIAL_EXPIRATION 99designs/aws-vault
1 participant
@jaklan