From 08b51f4f4bfd88688ed6e792812da4c8275e0027 Mon Sep 17 00:00:00 2001
From: Nick Clough <54546473+nclough@users.noreply.github.com>
Date: Fri, 29 May 2026 13:08:22 -0500
Subject: [PATCH] Update elastic-cloud-hosted-planning.md

Adding small note to add awareness about what snapshots don't include for people who want to use a single node cluster
---
 .../deploy/elastic-cloud/elastic-cloud-hosted-planning.md      | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md b/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md
index ce4eb3ed4e..611f22b620 100644
--- a/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md
+++ b/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md
@@ -42,6 +42,9 @@ The data in your {{es}} clusters is also backed up every 30 minutes, 4 hours, or
 Clusters that use only one availability zone are not highly
 available and are at risk of data loss. To safeguard against data loss,
 you must use at least two availability zones.
+
+Note: Snapshots do not restore all configurations (e.g., custom repositories).
+Review the full [snapshot contents](https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore#snapshot-contents) list to understand recovery limitations.
 ::::