Description
via slack: Explicitly mention that CPS is supported across regions and across cloud providers.
Probably surface in both admin and user docs. Check the blog post for any useful mentions and phrasing
Resources
N/A
Which deployment methods does this change impact?
Unknown
Feature differences
No response
What Elastic Stack release is this request related to?
N/A
Serverless release
No response
Collaboration model
Unknown
Point of contact.
Main contact: @
Stakeholders:
Elastic Docs AI Scoping 🤖
Docs issue scope
Summary
The issue asks to explicitly state that cross-project search (CPS) supports linking projects across different regions and across cloud providers — this should appear in both admin and user docs, with phrasing informed by the referenced blog post. There are no linked code PRs (Resources: N/A); this is a docs-only clarification for an existing feature. The blog post confirms CPS was designed to support cross-region and cross-cloud-provider linking (explicitly citing "regional data residency laws" as a motivator and noting future project-routing filtering by region/cloud provider). Current docs state that projects must be in the "same Elastic Cloud organization" but are silent on region and cloud provider restrictions.
Request accuracy
Accurate — the feature supports cross-region and cross-cloud-provider linking, but the docs do not state this explicitly.
Next action for author
Add explicit mention of cross-region and cross-cloud-provider support to the "Projects available for linking" requirements list in the admin config page, and to the "Project linking" section of the user overview page.
Impact: Medium
Scope boundary
No changes needed to the linking wizard page (cps-config-link-and-manage.md) — it already notes the UI filters by cloud provider and region, which implicitly confirms this support; a plain-language clarification in the requirements sections is what's missing.
Recommended documentation targets
Recommendations
- In
deploy-manage/cross-project-search-config.md, add a bullet to the "Projects available for linking" list explicitly stating that projects can be in different regions and on different cloud providers within the same organization.
- In
explore-analyze/cross-project-search.md, add a sentence in the "Project linking" section (or the intro paragraph) noting that linked projects can span regions and cloud providers.
- Optionally, update the
deploy-manage/_snippets/cps-definition.md snippet if a brief cross-region/cloud mention fits naturally, since it is transcluded in multiple pages.
Notes
- The blog post phrasing ("Elastic Cloud Serverless allows you to organize your data into dedicated projects whether you're isolating team environments, separating business units, or complying with regional data residency laws") offers ready-to-use doc phrasing for the user overview.
- No new pages or redirects are needed; these are additive updates to existing requirement/overview sections.
- No linked code PRs were provided; the scoping above is based on the issue description, the referenced blog post, and the existing docs structure.
Docs automation | From workflow: Issue Scope Analyzer
React with 👍 if helpful, 👎 if not.
Description
via slack: Explicitly mention that CPS is supported across regions and across cloud providers.
Probably surface in both admin and user docs. Check the blog post for any useful mentions and phrasing
Resources
N/A
Which deployment methods does this change impact?
Unknown
Feature differences
No response
What Elastic Stack release is this request related to?
N/A
Serverless release
No response
Collaboration model
Unknown
Point of contact.
Main contact: @
Stakeholders:
Elastic Docs AI Scoping 🤖
Docs issue scope
Summary
The issue asks to explicitly state that cross-project search (CPS) supports linking projects across different regions and across cloud providers — this should appear in both admin and user docs, with phrasing informed by the referenced blog post. There are no linked code PRs (Resources: N/A); this is a docs-only clarification for an existing feature. The blog post confirms CPS was designed to support cross-region and cross-cloud-provider linking (explicitly citing "regional data residency laws" as a motivator and noting future project-routing filtering by region/cloud provider). Current docs state that projects must be in the "same Elastic Cloud organization" but are silent on region and cloud provider restrictions.
Request accuracy
Accurate — the feature supports cross-region and cross-cloud-provider linking, but the docs do not state this explicitly.
Next action for author
Add explicit mention of cross-region and cross-cloud-provider support to the "Projects available for linking" requirements list in the admin config page, and to the "Project linking" section of the user overview page.
Impact: Medium
Scope boundary
No changes needed to the linking wizard page (
cps-config-link-and-manage.md) — it already notes the UI filters by cloud provider and region, which implicitly confirms this support; a plain-language clarification in the requirements sections is what's missing.Recommended documentation targets
Recommendations
deploy-manage/cross-project-search-config.md, add a bullet to the "Projects available for linking" list explicitly stating that projects can be in different regions and on different cloud providers within the same organization.explore-analyze/cross-project-search.md, add a sentence in the "Project linking" section (or the intro paragraph) noting that linked projects can span regions and cloud providers.deploy-manage/_snippets/cps-definition.mdsnippet if a brief cross-region/cloud mention fits naturally, since it is transcluded in multiple pages.Notes
Docs automation | From workflow: Issue Scope Analyzer
React with 👍 if helpful, 👎 if not.