Closed Wesam18 closed 5 years ago
Could you try aws-vault exec work --session-ttl=8h --assume-role-ttl=1h --server -- CMD.EXE
and let us know if that works?
Yes, that work
Needed the workaround suggested by @lox - but it seems like it's working otherwise!
Just one note: Powershell ISE doesn't work - not sure why.
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.
I have the same problem actually. It can be fixed with the above command. Maybe we should detect whether we are running windows and command
is an empty string and then just set command=cmd
?
works with Cmder terminal as well
aws-vault exec dev-admin -- cmder.exe
and have the following environments:
I have attempted to run aws-vault exec myProfile -- CMD.EXE and it kicks me out of my WSL2 instance OR it goes back to my windows terminal (if I ctrl C I go back to WSL2). Normal aws-vault exec myProfile gets the executable not found in %PATH% as above
I am experiencing the same as @adamosimpson21's error. Any luck ?
Running aws-vault with --server mode is failing and show below error
aws-vault: error: exec: "": executable file not found in %PATH%
OS: Windows 10 Command used:
aws-vault exec work --session-ttl=8h --assume-role-ttl=1h --server
where` work
is the profile name.