Vault Playground
Secure, store, and tightly control access to tokens, passwords, certificates, encryption keys for protecting secrets, and other sensitive data using a UI, CLI, or HTTP API.
Playground Parameters
Dev mode
Vault is configured to run in dev mode by default, meaning:
- Initialized and unsealed - The server will be automatically initialized and unsealed.
- In-memory storage - All data is stored (encrypted) in-memory.
- KV engine enabled at
secret/
If you'd prefer to run the service "normally", see the Setup without dev mode section.
For more feature demos, check out the Other playgrounds section.
You can read more about the properties of the dev server here.
Connecting
Connect to Vault using the following command:
vault status
💡 The terminal session should be configured to connect the locally running service.
The root token for connecting from other clients (e.g., the embedded UIs) is iximiuz.
Configuration
To experiment with custom configurations, place your config files in the following location: /etc/vault.d/config.d/
Ensure they're owned by the service user:
chown -R vault:vault /etc/vault.d/config.d/
Other playgrounds
Other playgrounds showcasing features not available here: coming soon!
Setup without dev mode
If you choose to run the service in "normal" mode (i.e. Dev mode disabled), a few extra steps are needed to replicate the dev mode setup.
These steps are outlined in this tutorial.
tl;dr
Review the contents of /opt/playground/vault/setup.sh, then run it.