-
Notifications
You must be signed in to change notification settings - Fork 815
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
Can't use --prompt=terminal with --ec2-server on Linux #1227
Comments
I am running into the same issue. We are using AWS Identity Center as SSO solution. It would be ideal if the background process would just open a browser window to re-authenticate if the session expires. Currently, there is no way to make this work since |
Until a fix is available - I have developed a gnarly workaround that can help us folks who are not using MFA yet. You need to fake the availability of an alternate prompt driver and tell aws-vault to use it. AWS Vault uses the presence of executables in the system path in order to determine which prompt drivers are available. For example, to determine if Line 19 in e22aea1
It's just looking for an executable with the right name in the system path to determine availability. So in my case, I duplicated a valid system executable, placed it in my user-specific binary directory and gave it the right name for kdialog:
I haven't tried using a shell script instead of a binary - with the appropriate permissions and shebang line it would probably work. On my system I do have such a directory already added to my PATH. So now, the following works without issue:
You could optimize this workaround a little more with two more tricks:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
v7.2.0
..aws/config
(redacted if necessary)aws-vault --debug
(redacted if necessary)The
--debug
output.The only prompt driver available on Linux is
terminal
. I have no choice to overcome the issue. I found this one is similar to #888The text was updated successfully, but these errors were encountered: