Vault stores and controls access to secrets, issues short-lived dynamic credentials for databases and clouds, and provides encryption-as-a-service - all behind identity-based policies and a full audit log.
Why teams use it
- Central, audited secret storage instead of secrets scattered in env files
- Dynamic, short-lived credentials that expire automatically
- Encryption-as-a-service so apps never hold key material
Install it
docker run --cap-add=IPC_LOCK -p 8200:8200 -e VAULT_DEV_ROOT_TOKEN_ID=root hashicorp/vault
export VAULT_ADDR=http://127.0.0.1:8200 VAULT_TOKEN=root
vault statusA first working config
Enable KV, write a secret, and define a least-privilege policy.
vault secrets enable -path=secret kv-v2
vault kv put secret/app/db password=s3cr3t
cat <<EOF | vault policy write app -
path "secret/data/app/*" { capabilities = ["read"] }
EOFRun and verify
vault kv get secret/app/db
# dynamic, expiring database credentials
vault read database/creds/app-roleMistakes to avoid early
- Running the dev server (in-memory, unsealed) in anything but demos
- Long-lived root tokens instead of scoped auth methods
- No audit device enabled, so access is untraceable
Want senior help putting HashiCorp Vault to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.