Vault secures, stores, and tightly controls access to
tokens, passwords, certificates, API keys, and other
secrets in modern computing. Vault handles leasing, key
revocation, key rolling, and auditing. Through a unified
API, users can access an encrypted Key/Value store and
network encryption-as-a-service, or generate AWS IAM/STS
credentials, SQL/NoSQL databases, X.509 certificates,
SSH credentials, and more.
- security ›
Vault secures, stores, and tightly controls access to tokens,
passwords, certificates, API keys, and other secrets in modern
computing. Vault handles leasing, key revocation, key rolling, and
auditing. Through a unified API, users can access an encrypted
Key/Value store and network encryption-as-a-service, or generate
AWS IAM/STS credentials, SQL/NoSQL databases, X.509 certificates,
SSH credentials, and more.
About the Charm
This charm installs Vault from the Ubuntu Snap Store and
supports the PostgreSQL and MySQL storage backends. Note that Vault itself
does not support PostgreSQL 10, so neither does this charm. If you're
deploying on bionic, you'll need to deploy a 9.x version of PostgreSQL.
After deploying and relating the charm to postgresql, install
the vault snap locally and use "vault init" to create the
master key shards and the root token, and store them safely.
Network Spaces support
The vault charm directly supports network binding via the 'access'
extra-binding and the 'cluster' peer relation. These allow the Vault
API and inter-unit Cluster addresses to be configured using Juju
- (boolean) Once unsealed, automatically generate a self-signed root CA rather than waiting for an action to be called to either generate one or process a signing request to act as an intermediary CA. Note that this will use all default values for the root CA cert. If you want to adjust those values, you should use the generate-root-ca action instead.
- (string) The snap channel to install from.
- (boolean) Set this option only if you are deploying to an environment that does not support the mlock(2) system call. When this option is set, vault will be unable to prevent secrets from being paged out, so use it with extreme caution.
- (string) DNS record to use for DNS HA with MAAS. Do not use vip setting if this is set.
- (string) Hostname to be used for the API URL. This hostname should exist as a DNS record and be resolvable by the charms that will consume the relation with vault.
- (string) A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.
- (string) Comma separated list of nagios servicegroups for the service checks.
- (string) DEPRECATED. Use snap-http-proxy and snap-https-proxy model configuration settings. HTTP/HTTPS web proxy for Snappy to use when accessing the snap store.
- (string) DEPRECATED. Use snap-store-proxy model configuration setting. The address of a Snap Store Proxy to use for snaps e.g. http://snap-proxy.example.com
- (string) How often snapd handles updates for installed snaps. The default (an empty string) is 4x per day. Set to "max" to check once per month based on the charm deployment date. You may also set a custom string as described in the 'refresh.timer' section here: https://forum.snapcraft.io/t/system-options/87
- (string) The SSL Root CA certificate, base64-encoded.
- (string) The SSL certificate, base64-encoded.
- (string) The SSL chain certificate, base64-encoded.
- (string) The SSL key, base64-encoded.
- (boolean) FOR TESTING ONLY. Initialise vault after deployment and store the keys locally.
- (string) Virtual IP to use api traffic. You can provide up to two addresses configured on the access or external bindings. If neither binding is used then you can only provide one address that must be configured on the default space.