diff --git a/docs/reference/tab-widgets/troubleshooting/watermark/troubleshooting-watermark-widget.asciidoc b/docs/reference/tab-widgets/troubleshooting/watermark/troubleshooting-watermark-widget.asciidoc
new file mode 100644
index 0000000000000..43c888d3e352b
--- /dev/null
+++ b/docs/reference/tab-widgets/troubleshooting/watermark/troubleshooting-watermark-widget.asciidoc
@@ -0,0 +1,40 @@
+++++
+<div class="tabs" data-tab-group="host">
+  <div role="tablist" aria-label="Fix watermark issue">
+    <button role="tab"
+            aria-selected="true"
+            aria-controls="cloud-tab-watermark"
+            id="cloud-watermark">
+      Elasticsearch Service
+    </button>
+    <button role="tab"
+            aria-selected="false"
+            aria-controls="self-managed-tab-watermark"
+            id="self-managed-watermark"
+            tabindex="-1">
+      Self-managed
+    </button>
+  </div>
+  <div tabindex="0"
+       role="tabpanel"
+       id="cloud-tab-watermark"
+       aria-labelledby="cloud-watermark">
+++++
+
+include::troubleshooting-watermark.asciidoc[tag=cloud]
+
+++++
+  </div>
+  <div tabindex="0"
+       role="tabpanel"
+       id="self-managed-tab-watermark"
+       aria-labelledby="self-managed-watermark"
+       hidden="">
+++++
+
+include::troubleshooting-watermark.asciidoc[tag=self-managed]
+
+++++
+  </div>
+</div>
+++++
diff --git a/docs/reference/tab-widgets/troubleshooting/watermark/troubleshooting-watermark.asciidoc b/docs/reference/tab-widgets/troubleshooting/watermark/troubleshooting-watermark.asciidoc
new file mode 100644
index 0000000000000..322bd864c4981
--- /dev/null
+++ b/docs/reference/tab-widgets/troubleshooting/watermark/troubleshooting-watermark.asciidoc
@@ -0,0 +1,25 @@
+// tag::cloud[]
+
+* {ref}/docs-delete.html[Delete unused data].
+* {cloud}/ec-customize-deployment-components.html[Increase the disk size on your Hot data and Content tier (scale up)]
+
+NOTE: If your {es} cluster is unhealthy and reports a status of red, then increasing the disk size of your Hot data and Content tier may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then {cloud}/ec-get-help.html[reach out to Elastic support] and we will assist you with scaling up.
+
+Also, for future prevention, you can do below:
+
+* {cloud}/ec-customize-deployment-components.html[Increase the disk size on your Hot data and Content tier (scale up)]
+* Enable <<xpack-autoscaling,autoscaling>> for clusters deployed using our {ess}, {ece}, and {eck} platforms.
+* Update related <<index-lifecycle-management,ILM policy>> to push indices through to later <<data-tiers,data tiers>>
+
+// end::cloud[]
+
+// tag::self-managed[]
+As a long-term solution, we recommend you do one of the following best suited 
+to your use case: 
+
+* Add nodes to the affected <<data-tiers,data tiers>>
+* Upgrade existing nodes to increase disk space
+* Delete unneeded indices using the <<indices-delete-index,delete index API>>
+* Update related <<index-lifecycle-management,ILM policy>> to push indices through to later <<data-tiers,data tiers>>
+
+// end::self-managed[]
diff --git a/docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc b/docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc
index 2222d09c26db2..3e7c170b4707e 100644
--- a/docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc
+++ b/docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc
@@ -53,7 +53,7 @@ GET _cluster/allocation/explain
 [[fix-watermark-errors-temporary]]
 ==== Temporary Relief
 
-To immediately restore write operations, you can temporarily increase the 
+To immediately restore write operations, you may consider temporarily increasing the 
 <<disk-based-shard-allocation,disk watermarks>> and remove the 
 <<index-block-settings,write block>>.
 
@@ -102,19 +102,4 @@ PUT _cluster/settings
 [[fix-watermark-errors-resolve]]
 ==== Resolve
 
-As a long-term solution, we recommend you do one of the following best suited 
-to your use case: 
-
-* add nodes to the affected <<data-tiers,data tiers>>
-+
-TIP: You should enable <<xpack-autoscaling,autoscaling>> for clusters deployed using our {ess}, {ece}, and {eck} platforms.
-
-* upgrade existing nodes to increase disk space
-+
-TIP: On {ess}, https://support.elastic.co[Elastic Support] intervention may 
-become necessary if <<cluster-health,cluster health>> reaches `status:red`. 
-
-* delete unneeded indices using the <<indices-delete-index,delete index API>>
-
-* update related <<index-lifecycle-management,ILM policy>> to push indices 
-through to later <<data-tiers,data tiers>>
+include::{es-ref-dir}/tab-widgets/troubleshooting/watermark/troubleshooting-watermark-widget.asciidoc[]