I'm running the latest CentOS and I need Hashicorp Vault 1.6.3 to run as a service. I'm currently using the kv/secret background, so I can use
Vault kv put secret/test/hello foo=bar
In order to store secrets. When running vault as a server, it blocks. I need the Vault server to automatically start as a service whenever the server is rebooted, it really shouldn't be blocking if possible. It's been about three years since I've used Vault so I may just be dense here.
So I guess what I need to ask is:
How do I start Vault when my server reboots.
Should it be blocking and, if no, how do I prevent this?
Vault is both a service and a command line tool in the same binary. So you can keep using
vault
on the command line, and create a plain old Linux service for Vault to run. It will "block" over there, but that's what services are for.Depending on where you are at now, you could start with Hashicorp's intructions to configure systemd to create a Vault service.
The service should look like this