Skip to content

docs: add resilience in Elastic Cloud Serverless page - #8052

Open
pete-naylor wants to merge 2 commits into
mainfrom
docs/serverless-resilience-page
Open

docs: add resilience in Elastic Cloud Serverless page#8052
pete-naylor wants to merge 2 commits into
mainfrom
docs/serverless-resilience-page

Conversation

@pete-naylor

Copy link
Copy Markdown
Contributor

Summary

Adds a new page documenting resilience in Elastic Cloud Serverless, covering:

  • Data durability — stateless storage architecture and object storage replication
  • High availability — automatic zone distribution and SLA link
  • Data recovery — Elastic-managed recovery data; notes that self-service recovery is planned
  • Regional scope — resilience is regional; no built-in multi-region or cross-region replication

Also updates the parent "Design for resilience" page (availability-and-resilience.md) to include serverless: in applies_to and add a link to the new page, and adds the new page to toc.yml.

Changes

  • deploy-manage/production-guidance/availability-and-resilience/resilience-in-serverless.md — new page
  • deploy-manage/production-guidance/availability-and-resilience.md — add serverless: to applies_to; add link to new page
  • deploy-manage/toc.yml — add new page after resilience-in-ech.md

Notes for reviewer

Follows the structure and conventions of resilience-in-ech.md. Avoids "snapshot/backup/restore" terminology for Serverless data recovery per product naming guidance — uses "recovery data" and "self-service data recovery" instead.

Preview

@pete-naylor
pete-naylor requested a review from a team as a code owner August 21, 2026 22:50
@pete-naylor pete-naylor added the documentation Improvements or additions to documentation label Aug 21, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

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

  • Review docs changes (docs-review). Status: not started.

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

@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 1 suggestion found

💡 Suggestions (1): Optional style improvements. Apply when helpful.
File Line Rule Message
deploy-manage/production-guidance/availability-and-resilience.md 69 Elastic.Wordiness Consider using 'also' instead of 'In addition'.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant