aws-vault: error: Server failed: exit status 1

[FernandoMiguel]

$ aws-vault server --debug
2017/12/20 11:49:21 Loading config file /Users/fernando/.aws/config
2017/12/20 11:49:21 Parsing config file /Users/fernando/.aws/config
aws-vault: error: Server failed: exit status 1

$ aws-vault --version
v4.1.0

MacOS 10.13.3 Beta (17D20a)

[astanciu]

maybe run with sudo since it binds on port 80?

[lox]

aws-vault server isn't meant to be run directly, it should be an invisible command. What are you trying to do @FernandoMiguel?

[FernandoMiguel]

@astanciu if it requires sudo, my expectations is that it should ask for it when needed

@lox was trying to run in server mode, and that option showed in the help menu, so I tried.

After poking a bit I found the -s in the exec command too, and that seems to work for most cases. Couldn't get it to work with terraform and assume roles, but without server mode it works fine.

But back to your question, if it is supposed to be an invisible command why is it listed as one of the options of --help?

[astanciu]

How is it supposed to be run then? The docs are not clear on this.

[FernandoMiguel]

Exactly. The way I found is aws-vault exec profile --server

…

-- Fernando Miguel

On 22 Dec 2017 14:16, "Alex Stanciu" ***@***.***> wrote: How is it supposed to be run then? The docs are not clear on this. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#207 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKRrkzGantg2sv5HZC73nDfFTq0TygDks5tC7nVgaJpZM4RISLj> .

[astanciu]

@FernandoMiguel and even that is a bit unconventional. It appears to start a new shell session and the server is running in the background. Would be nice if this was cleaned up a bit. An option to run server as daemon/background, otherwise show server logs would be good.

[lox]

Yup, I hear you, it's not well documented or clear. The design has been carefully thought over though, and is the way it is for good reason. I've started a PR that will improve the docs and make this clearer, check out #208.

[lox]

I'm going to close this one. We will work on docs in #208, but as it stands this is the expected behaviour of manually calling the server command.