-
Notifications
You must be signed in to change notification settings - Fork 821
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
aws-vault configure #601
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sounds like this is still a great feature proposal! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still an interesting feature request it seems? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Commenting to avoid closure. |
AWS SSO roles and accounts you have access to frequently change. I find myself having to manually juggle with my It would be nice to have this feature in aws-vault, but I'm unsure what it would look like:
@mtibben feel free to share if you have an opinion |
Hey @christophetd I don't have an opinion as I don't use this feature at this time |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hey @christophetd if you wish to implement this, feel free to open a PR. As I don't intend to implement at this time I will close for now. |
I was too hasty to close this ticket - with 37 👍 it does seem to have some support. While I don't plan to implement this at this time, I'll leave this open for now |
Now that v6 adds SSO support, it is missing an important security feature:
aws-vault configure
a user to has to
aws sso configure
to create the profile in~/.aws/config
if they don't want to create it by hand.by doing so, a long term session json will be left under
~/.aws/sso/
If aws-vault is able to run the configure command and store the keys directly into the keychain, no sensitive files are left on disk
The text was updated successfully, but these errors were encountered: