Merge pull request #536 from influxdata/cloud-secrets
Add note on storing secrets in Vault in Cloudpull/541/head
commit
cd4da537a5
|
@ -13,6 +13,10 @@ There are two options for storing secrets with InfluxDB:
|
|||
- By default, secrets are Base64-encoded and stored in the InfluxDB embedded key value store, [BoltDB](https://github.com/boltdb/bolt).
|
||||
- You can also set up Vault to store secrets. For details, see [Store secrets in Vault](/v2.0/security/secrets/use-vault).
|
||||
|
||||
{{% cloud-msg %}}
|
||||
By default, all secrets added to InfluxDB Cloud are stored in the InfluxDB Cloud Vault cluster.
|
||||
{{% /cloud-msg %}}
|
||||
|
||||
## Use secrets in a query
|
||||
Import the `influxdata/influxd/secrets` package and use the `secrets.get()` function
|
||||
to populate sensitive data in queries with secrets from your secret store.
|
||||
|
|
|
@ -12,6 +12,10 @@ weight: 201
|
|||
to tokens, passwords, certificates, and other sensitive secrets.
|
||||
Store sensitive secrets in Vault using the InfluxDB built-in Vault integration.
|
||||
|
||||
{{% cloud-msg %}}
|
||||
By default, all secrets added to InfluxDB Cloud are stored in the InfluxDB Cloud Vault cluster.
|
||||
{{% /cloud-msg %}}
|
||||
|
||||
## Start a Vault server
|
||||
|
||||
Start a Vault server and ensure InfluxDB has network access to the server.
|
||||
|
|
Loading…
Reference in New Issue