From 78aaa3ca92f964ba4cacc42e1afbe6752c0266bd Mon Sep 17 00:00:00 2001 From: Scott Miller Date: Mon, 6 Feb 2023 19:25:14 -0600 Subject: [PATCH] Add a note that multi-cluster ENT setups can avoid this risk (#19024) * wip * all-seals * typo * add note about unreplicated items * italics * word-smithing --- website/content/docs/concepts/seal.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/content/docs/concepts/seal.mdx b/website/content/docs/concepts/seal.mdx index f514d3e79..52702f3e4 100644 --- a/website/content/docs/concepts/seal.mdx +++ b/website/content/docs/concepts/seal.mdx @@ -128,6 +128,10 @@ To mitigate this risk, we recommend careful controls around management of the se mechanism, for example using [AWS Service Control Policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) or similar. +With Vault Enterprise secondary clusters (disaster or performance) can have a +seal configured independently of the primary, and when properly configured guards +against *some* of this risk. Unreplicated items such as local mounts could still +be lost. ## Recovery Key