1/7
Installing and testing the Vault binary
(T/F) Vault is platform agnostic
True. Vault can run on bare metal, virtual machines, within Kubernetes, locally, etc.
Order of operations for installing and setting up Vault
Install Vault (brew, build, package manager, etc.)
Create configuration file(s)
Initialize vault (vault init)
Unseal vault
Benefits of Vault Dev mode. (vault server -dev)
Quickly run Vault without configuration
Automatically initialize and unseal
Enables the UI
Provides an unseal key
Automatically logs in as root
In short, this is great for trying out new features in Vault or POCing
Drawbacks of Vault Dev mode.
Non-persistent, in-memory storage
Insecure/No TLS
Sets listener to localhost:8200
Always mounts a kv v2 secret engine
provides a root token
TLDR, this is insecure and brittle.
Running Vault in Production
Deploy one or more persistent nodes via HCL configuration files
Select a storage backend based on preference/requirements
Multiple Vault nodes will be configured as a cluster
Deploy “close” to applications
Ideally, the provisioning of Vault will be automated in some manner
How to manage running Vault service
SystemCTL or Windows service manager
For linux, you’ll need a systemd file.
(T/F) Single node Vault is a recommended configuration for production Vault
FALSE. There is no redundancy or scalability here.