Sha256: 0201e3a7df133c2748ee48d0358a76bffa7e0b08141918ab28d1c481c426fac4
Contents?: true
Size: 1.15 KB
Versions: 3
Compression:
Stored size: 1.15 KB
Contents
#### [Back](../README.md) ## Vault ### Prerequisites Before using Vault, you should have the client installed: - Download the binary for your OS - Unzip it and run `chmod +x vault && sudo mv vault /usr/local/bin/vault` - Check if the Vault is installed by running `vault -v` ### Deployment To deploy Vault, use `./bin/vault-deploy.sh` ### Connection - Export your Vault's IP using `export VAULT_ADDR=http://*vault_ip*:8200` - Run `vault init` to initialize the vault - Store the keys displayed after init - Unseal the vault by running `vault unseal` three times using three keys from the previous step - Authenticate to the vault with `vault auth` using the root token you got from `vault init` [Optional] - Try to store a dummy secret: `vault write secret/handshake knock=knock` - Read it: `vault read secret/handshake` ### Usage with Concourse Before using Vault with Concourse you should mount a secrets backend with `vault mount -path=concourse kv` To add new secrets accessible for Concourse use `vault write concourse/main/*secret_name* value="*secret_value*"` #### It's recommended to create a separate token for Concourse by using `vault token-create`
Version data entries
3 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
kite-0.2.0 | tpl/aws/docs/vault.md |
kite-0.1.0 | tpl/aws/docs/vault.md |
kite-0.1.0 | tpl/gcp/docs/vault.md |