[ECH] Add data loss warning admonition for found-snapshots repository

[kunisen]

Summary

Closes https://github.com/elastic/support-tech-lead/issues/1841

Adds a prominent important admonition near the top of the ECH snapshot
repositories page to make clear that found-snapshots has no backup,
deletions are permanent (including searchable snapshots), and the path to
redundancy is to configure a custom repository.

Note: coordinates with #7212
(Stef Nestor). If both PRs merge, the bullet added by #7212 under
Considerations could be removed to avoid duplication.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

cc @stefnestor @jakommo

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: queued.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md

[github-actions]

Docs review summary

Focus areas

• Style and clarity: One minor preposition error in the new admonition ("in this page" → "on this page") — see inline comment. The rest of the added prose is clear, direct, and technically specific.
• Jargon: No unexplained jargon introduced. found-snapshots is quoted in monospace as expected.
• Frontmatter and applies_to: No description field in frontmatter — pre-existing gap, not introduced by this PR.
• Content type fit: The important admonition is well-placed and appropriate for a high-severity data-loss warning.
• Parent issue satisfaction: Satisfied. The admonition prominently surfaces the no-backup, permanent-deletion, and searchable-snapshot caveat, and points users to the custom-repository path for redundancy.

Nits

• Vale flags several pre-existing issues in untouched lines: multiple uses of may (should be can or might), just (line 17), older versions → earlier versions (line 45), disable (line 85), and wordiness in lines 133–144. These are all in content not touched by this PR.

Notes

• mapped_pages warning from Vale is expected for this file and does not require action.

Generated by Docs review agent for issue #7251 · 30.7 AIC · ⌖ 10.8 AIC · ⊞ 10.7K

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[yetanothertw]

I know this suggestion is longer but I think it adds a bit more context around why this is important. Please feel free to tweak it if anything is not accurate:

Suggested change

	The underlying `found-snapshots` repository managed by {{ech}} has no backup. Elastic does not enable soft deletion at the cloud provider storage level. Any snapshot deletions — including [searchable snapshots](./searchable-snapshots.md#back-up-restore-searchable-snapshots) — are permanent and cannot be recovered by Elastic.
	{{ech}} registers the built-in `found-snapshots` repository on every deployment and uses it along with the `cloud-snapshot-policy` SLM policy for automated snapshots. This repository is your backup on {{ech}}. Snapshot data exists only in this repository and {{ech}} does not mirror it to separate storage or retain deleted snapshots through storage-level versioning or soft delete.
	When you delete a snapshot from `found-snapshots`, that data is removed from the repository and cannot be recovered. This also applies to [searchable snapshots](searchable-snapshots.md#back-up-restore-searchable-snapshots) stored in `found-snapshots`.

[yetanothertw]

A little more clarification + link:

Suggested change

	If you require additional redundancy, follow the guidance on this page to configure your own snapshot repository and take backups.
	If you need additional redundancy beyond the default repository, [configure a custom snapshot repository](#ess-repo-types) and take additional snapshots to storage you control.