diff --git a/content/v2.0/security/secrets/_index.md b/content/v2.0/security/secrets/_index.md
index dba43f9a8..7e06958bb 100644
--- a/content/v2.0/security/secrets/_index.md
+++ b/content/v2.0/security/secrets/_index.md
@@ -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.
diff --git a/content/v2.0/security/secrets/use-vault.md b/content/v2.0/security/secrets/use-vault.md
index 7b7ca9934..1f6303fda 100644
--- a/content/v2.0/security/secrets/use-vault.md
+++ b/content/v2.0/security/secrets/use-vault.md
@@ -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.