In July 2016, we selected Vault to store credentials.
The kv engine contains the following paths:
* ops/secrets: credentials like passwords, API tokens, private keys deployed to servers - a reference for machines * ops/internal: credentials to third-party services internally shared amongst ops - a reference for humans * ops/privacy: privacy information
Secrets are directly and manually managed in Vault. If we need to run a disaster recovery procedure, we'll roll any secret by defining them again and deploy from rOPS those new secrets.
Personal identity information (PII) shared inside the Nasqueron Operations squad are more convenient to manage as a repository.
Such access to the repository is restricted to commit data, and ensure this data is deployed to the servers needing it. Any other use isn't allowed.
Information to the repository is then published in Vault, and referred in rOPS as Vault credentials.
Note: The ops/privacy path is only intended for PII of current or previous members of the Ops SIG, like IP addresses allowed to connect to restricted resources like the ops VPN. This is not acceptable to put 3rd party information in this repository.
Services listening to private IPs use the Vault PKI to generate certificates:
- pki_root: root CA, certificate available at https://api.nasqueron.org/infra/security/pki/root/ca
- pki_vault: intermediate CA used for Vault itself
Certificates should be issued short-term and frequently renewed by automated services.
Encryption as a service is available for applications under /transit path.
Applications should use a policy restricting to a subpath for that app, not to the whole engine.
Get a secret through Salt
The information in the ops/secrets and ops/privacy kv engines are integrated in the Salt pillar:
ext_pillar: # Credentials to deploy to servers - vault: conf: path=ops/secrets nesting_key: credentials # Personal identity information from Nasqueron Operations SIG members - vault: conf: path=ops/privacy nesting_key: privacy
You can then access to this information in Salt states using the following references:
|Category||Example of path in Vault||Example of pillar key in Salt|
The ops/internal paths aren't accessible through Vault.
If we need to recover Vault, two solutions are available:
- restore the storage, to keep data (credentials, certificates including the root CA one)
- recreate it from scratch through the roles/vault/bootstrap unit
Connecting to Vault
curl: (60) SSL certificate problem
Curl is compiled against a certificate bundle (
curl-config --ca for the path). That bundle doesn't contain the pki_root certificate. We deploy this certificate in /etc/ssl/certs, but curl won't check there if not instructed to.
If you build an immutable environment like a container, add the certificate to the bundle.
On other machines, create a curl configuration file in ~/.curlrc (it doesn't seem currently possible to create a system one) with
If you've still the issue after that, check two thinsg:
curl -v, the path should correctly there:
* CApath: /etc/ssl/certsin addition to a CAfile.
file /etc/ssl/certs/* | grep -i nasqueronyou should have a result ; if not, put the certificate in /usr/local/share/certs and relaunch the tool to link it in /etc/ssl/certs, for example
certctl rehashon FreeBSD (needs root access).
- Secrets in pillar/credentials/zr.sls have been migrated to Vault under ops/secrets/<key>