From 386080c54dda9871e609384eec469f3877faad75 Mon Sep 17 00:00:00 2001 From: Josh Black Date: Wed, 2 Jul 2025 09:33:14 -0700 Subject: [PATCH] Clarify availability of AOP on non-raft backends (#31062) * clarify availability of AOP on non-raft backends * Update website/content/docs/concepts/adaptive-overload-protection/index.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- .../docs/concepts/adaptive-overload-protection/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/concepts/adaptive-overload-protection/index.mdx b/website/content/docs/concepts/adaptive-overload-protection/index.mdx index e9475a1c94..d4c274e57e 100644 --- a/website/content/docs/concepts/adaptive-overload-protection/index.mdx +++ b/website/content/docs/concepts/adaptive-overload-protection/index.mdx @@ -75,8 +75,8 @@ to avoid replication lag. Write overload protection was added in Vault Enterprise 1.17 as a beta feature and was disabled by default. Since Vault 1.18.0 it is enabled by default only -when using Raft Integrated Storage. Adaptive overload protection is disabled by -default for Consul and other storage backends. +when using integrated storage. Adaptive overload protection is not +available for Consul and other storage backends. To disable the feature use the [`adaptive_overload_protection` configuration stanza](/vault/docs/configuration/adaptive-overload-protection).