Skip to content

[Website]: Add link to new Resilience in Elastic Cloud Serverless page #9235

New issue
New issue
Open
Open
[Website]: Add link to new Resilience in Elastic Cloud Serverless page#9235
Labels
Team:AdminIssues owned by the Admin Docs Teamsource:webIssues originating from the elastic.co docstriagedTriage has been run on this issue

Description

@yetanothertw
yetanothertw
opened on Nov 5, 2026

Before you submit

  • This issue is about a documentation page, flow, or piece of content.

Type of issue

Missing information

What documentation page or section is affected

https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/serverless

What happened?

#8052 added a new Serverless page.

The Elastic Cloud Serverless page is the overview and entry point: what Serverless is, project types, creating a project, billing, security, and support. It touches on resilience in several places but never in one spot or in depth:

  • The Management free benefit says Elastic handles “data backups, and business continuity.”
  • How Serverless works describes the decoupled compute and storage architecture, which is the basis for the durability story.
  • Monitor and get support says you can’t take your own snapshots and can request an emergency restore through Support.
  • The region is fixed at project creation, which ties into the regional scope limitation.

The Resilience in Serverless page expands on those points. It’s also a sibling of “Resilience in ECH and ECE” in the Design for resilience section, so it’s the Serverless counterpart for people comparing deployment types.

Additional info

Potential spots where to add the link:

  • Monitor and get support is the best fit. It already discusses backups, business continuity, and emergency restore, and the resilience page’s “Data recovery” section covers the same ground. For example: “For details on durability, availability, and regional scope, refer to Resilience in Serverless.”
  • Management free in the list of benefits is a good place for an inline link on “business continuity.”
  • Learn more is the fallback, where it would sit alongside the FAQ and architecture blog.

Activity

  1. yetanothertw
    added
    source:webIssues originating from the elastic.co docs
    on Nov 5, 2026
  2. github-actions
    added
    needs-teamIssues pending triage by the Docs Team
    on Nov 5, 2026

  3. github-actions commented on Nov 5, 2026

    @github-actions
    github-actionsBot
    on Nov 5, 2026 – with GitHub Actions
    Contributor

    Elastic Docs AI Menu

    Check one box to run an AI workflow for this issue.

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

  4. github-actions commented on Nov 5, 2026

    @github-actions
    github-actionsBot
    on Nov 5, 2026 – with GitHub Actions
    Contributor

    ✅ ScopeBot finished. https://github.com/elastic/docs-content/actions/runs/42039358145

    Generated from Gh Aw Issue Scope

  5. github-actions
    added
    Team:AdminIssues owned by the Admin Docs Team
    triagedTriage has been run on this issue
    and removed
    needs-teamIssues pending triage by the Docs Team
    on Nov 5, 2026

  6. github-actions commented on Nov 5, 2026

    @github-actions
    github-actionsBot
    on Nov 5, 2026 – with GitHub Actions
    Contributor

    🟢 ScopeBot Results: Full assessment

    Summary

    The issue asks for a link from the Elastic Cloud Serverless overview to the new resilience page. The published overview already covers business continuity, backups, emergency restore, and the fixed regional choice, while the linked merged PR #8052 added the dedicated resilience page covering durability, availability, data recovery, and regional scope. The smallest change is therefore to add a contextual link in the overview’s Monitor and get support section, with an optional inline link in Benefits of Serverless projects if the team wants the business-continuity mention to lead readers there too.

    Request accuracy

    Accurate — the linked PR added the resilience page, and the published overview does not currently link to it from the relevant support/resilience content.

    Recommended docs targets

    Page URL Action Confidence Why this page?
    Elastic Cloud Serverless https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/serverless Update existing page High This is the overview and entry point named by the issue. Its Monitor and get support section discusses backups, business continuity, and emergency restore, making it the clearest place to link the dedicated resilience guidance.

    How to tackle this

    1. In the Monitor and get support section of the Elastic Cloud Serverless page, add a contextual link to Resilience in Elastic Cloud Serverless: https://www.elastic.co/docs/deploy-manage/production-guidance/availability-and-resilience/resilience-in-serverless
    2. Use link text that tells readers what they will learn, such as durability, availability, regional scope, and data recovery; keep the existing support and emergency-restore guidance intact.
    3. Optionally link the existing business continuity wording in Benefits of Serverless projects to the same page if the team wants the resilience guidance discoverable from both the benefit statement and the support section.
    4. Preview the page and check that the link renders in the intended section without duplicating the resilience page’s detailed content.

    Scope boundary

    No changes appear necessary to the resilience page, its parent Design for resilience page, or navigation because the merged PR already added and published those pages.

    Questions to go deeper

    • Should the new link appear only in Monitor and get support, or also on business continuity in Benefits of Serverless projects?
    • Should the surrounding sentence name all four topics (durability, availability, regional scope, and data recovery), or use the shorter term “resilience”?
    • Is there a preferred wording or link-label convention for cross-linking from overview pages to production-guidance pages?

    This scope reflects the issue as of this run. Comment /scope to run it again after the issue changes.

    Generated from Gh Aw Issue Scope · ◷

    Scope requested by @yetanothertw. Was it helpful? When the work closes, add the label ai-scope:helpful or ai-scope:unhelpful to this issue.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Team:AdminIssues owned by the Admin Docs Teamsource:webIssues originating from the elastic.co docstriagedTriage has been run on this issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions