vault1.15.5

Vault lets operators securely access and manage secrets such as database credentials, external-service API keys, and credentials used for service-oriented architecture communication. It stores these values while helping teams control access, handle key rotation, and maintain detailed audit logs. By bringing these concerns into one service, it makes it easier to understand which users or systems are accessing particular secrets across platform-specific environments.

The Canonical-maintained snap includes the vault command-line client and the vaultd daemon for running a local Vault server. The daemon is disabled by default and does not start automatically; it reads /var/snap/vault/common/vault.hcl, which is initially populated with a default configuration. A SIGHUP reloads configuration without a full restart, while variables in /var/snap/vault/common/vault.env are sourced before the daemon starts.

For HTTPS, configure certificate and key paths in vault.hcl instead of tls_disable = 1, then set VAULT_ADDR; additional behavior is controlled through Vault’s TCP listener settings. The snap targets Linux systems with snapd and supports amd64, arm64, s390x, ppc64el, i386, and armhf architectures, including Ubuntu, Fedora, Debian, and other major Linux distributions. Its built-in web UI is available on amd64 and arm64, while the s390x build omits it because Node.js is unavailable for compiling the frontend assets, making ui = true ineffective there. The current version is 1.15.5, and the software is freeware.