aws-vault: Can't use --prompt=terminal with --ec2-server

~$ aws-vault --debug exec dev --ec2-server
2022/03/10 10:51:03 aws-vault v6.6.0
2022/03/10 10:51:03 Loading config file /Users/fernando/.aws/config
2022/03/10 10:51:03 Parsing config file /Users/fernando/.aws/config
2022/03/10 10:51:03 [keyring] Considering backends: [keychain]
aws-vault: error: exec: Can't use --prompt=terminal with --ec2-server. Specify a different prompt driver

$ aws-vault --version
v6.6.0

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 12
Comments: 16 (7 by maintainers)

Most upvoted comments

This breaking change is a bummer - we use aws-vault within a docker container, ‘terminal’ is the only option…

So I’m really not sure how to handle terminal input when using a server, do you have any thoughts or ideas?

Could it not just work the way it used to? Ask for 2FA input at launch then start erroring when re-auth in required…

+11

danwashusen on Apr 26, 2022

$ aws-vault  --debug exec dev --prompt=osascript --server
2022/03/11 11:10:19 aws-vault v6.6.0
2022/03/11 11:10:19 Loading config file /Users/fernando/.aws/config
2022/03/11 11:10:19 Parsing config file /Users/fernando/.aws/config
2022/03/11 11:10:19 [keyring] Considering backends: [keychain]
2022/03/11 11:10:19 [keyring] Querying keychain for service="aws-vault", keychain="aws-vault.keychain"

that seems to work fine. what can we do to fix this in aws-vault natively, and avoid and extra parameter that wasn’t needed a week ago?

thanks for the help!

FernandoMiguel on Mar 11, 2022

@FernandoMiguel ah so it’s the “default” as terminal that is the problem

Just regular vanilla iTerm2. Nothing fancy about it, and no recent update there. Something changed with aws vault and no warning on the changelog.

FernandoMiguel on Mar 10, 2022

This breaking change is a bummer - we use aws-vault within a docker container, ‘terminal’ is the only option…

So I’m really not sure how to handle terminal input when using a server, do you have any thoughts or ideas?

Could it not just work the way it used to? Ask for 2FA input at launch then start erroring when re-auth in required…

The whole point of --ec2-server and --ecs-server is to refresh credentials asynchronously in the background. If you don’t need that refreshing behaviour, why are you using --ec2-server and --ecs-server?

mtibben on Dec 19, 2022