Skip to content

Create a new page for Serverless cloud id - #7825

Merged
yetanothertw merged 10 commits into
mainfrom
cloud-id-serverless-345
Sep 30, 2026
Merged

yetanothertw merged 10 commits into
mainfrom
cloud-id-serverless-345

Conversation

@yetanothertw

@yetanothertw yetanothertw commented Aug 6, 2026 •

Copy link
Copy Markdown
Member

Summary

Fixes #5150 and #345

The existing Find your Cloud ID page is ECH-only. Serverless projects also expose a Cloud ID (and an Elasticsearch endpoint / API keys), but the UI paths differ.

This PR:

The new page includes the following info:

  • covers the three connection concepts: Elasticsearch endpoint, API key, and Cloud ID (definition list + how-tos for finding the details).
  • API keys: high-level entry points only, with a link to the existing Serverless API keys page (no duplicated procedure).
  • Next steps point to Beats, Logstash, Elastic Agent, language clients, and the ingest overview (in the context of the purpose for which you'd want to connect your projects and tools/clients).

Generative AI disclosure

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

Cursor's auto agent to find similar or contradictory information within the existing docset.

@github-actions

github-actions Bot commented Aug 6, 2026

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 7, 2026 •

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

✅ 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
yetanothertw marked this pull request as ready for review August 7, 2026 13:05
@yetanothertw
yetanothertw requested a review from a team as a code owner August 7, 2026 13:05

@florent-leborgne florent-leborgne left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, we can afford to not describe all of the methods I think. Just a few non-blocking adjustments to match the UI updates that landed today...

Just simply commenting to not block anything:)

Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated

@shainaraskas shainaraskas left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall, this lgtm, but i worry about duplication with this page: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/7825/solutions/elasticsearch-solution-project/search-connection-details

wonder if anything nice can be taken from there, or if we should be snippetizing this so one or the other doesn't fall out of date

are there any places where this page should be cross-referenced? probably all links to find-cloud-id should be paired with a find-connection-details link if they apply to serverless.

side-quest:

one advantage of optimizing toward a single page for both ech + serverless is that these pages can share one link (and the old cloud id links can redirect to a surface that directly addresses both deployment types). another big thing is that the help link for cloud ID links to the ECH only page, which is not ideal

current placement is also more like one-time config rather than a place people would want to reference on an ongoing basis

Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/find-cloud-id.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated
@yetanothertw

Copy link
Copy Markdown
Member Author

Thanks both, it seems like this needs a bit more work, so I'll set it back into draft mode and address your feedback.

@yetanothertw
yetanothertw marked this pull request as draft August 12, 2026 08:34
@yetanothertw

Copy link
Copy Markdown
Member Author

Related to #7954

@shainaraskas

Copy link
Copy Markdown
Member

also related #8590

@yetanothertw
yetanothertw marked this pull request as ready for review September 30, 2026 11:01
@yetanothertw
yetanothertw requested review from a team as code owners September 30, 2026 11:01
Comment thread deploy-manage/deploy/elastic-cloud/find-connection-details-serverless.md Outdated

@leemthompo leemthompo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

search-connection-details.md snippet-ization LGTM

@yetanothertw
yetanothertw added this pull request to the merge queue Sep 30, 2026
Merged via the queue into main with commit 3553ce2 Sep 30, 2026
12 checks passed
@yetanothertw
yetanothertw deleted the cloud-id-serverless-345 branch September 30, 2026 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Equivalent of Cloud ID page but for Serverless

4 participants