Create a new page for Serverless cloud id by yetanothertw · Pull Request #7825 · elastic/docs-content

yetanothertw · 2026-08-06T17:39:12Z

Summary

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:

introduces a dedicated Serverless page
adds a link to it on the existing ECH page

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

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.

Fixes [#5150](#5150) and [#345](elastic/docs-content-internal#345) It adds a new page specific to Serverless, equivalent to [Find your Cloud ID](https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/find-cloud-idthat exists for ECH.

github-actions · 2026-08-06T22:27:38Z

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 · 2026-08-07T07:56:11Z

🔍 Preview links for changed docs

github-actions · 2026-08-07T07:56:16Z

✅ 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.

florent-leborgne

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:)

florent-leborgne · 2026-08-11T16:18:51Z

+**Cloud ID**
+:   A unique, encoded string that represents your project's {{es}} endpoint (and, where applicable, {{kib}} endpoint) in a compact form. Compatible clients can use it instead of configuring host URLs individually: the client resolves those endpoints from the Cloud ID.
+
+## Find your {{es}} endpoint and Cloud ID [_find_elasticsearch_endpoint]


FYI, this is changing as we speak in serverless, it just landed today

It's still in the help menu though so this is still technically correct

florent-leborgne · 2026-08-11T16:20:37Z

+
+## Create an API key [_create_api_key]
+
+You can create an API key from your project's home page, or open the **API keys** page from the navigation menu or with the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).


Suggested change

You can create an API key from your project's home page, or open the **API keys** page from the navigation menu or with the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).

You can create an API key from your project's **API keys** page. You can access it from the navigation menu or with the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).

I'd limit it to this method, since it's not true for all project types that it's on the home page (just looked in observability)

Or I noticed it's now also under connection details in another tab

florent-leborgne · 2026-08-11T16:21:39Z

+  - id: cloud-serverless
+---
+
+# Find your project connection details [serverless-connection-details]


I'd put the full Serverless substitution in the title too

florent-leborgne · 2026-08-11T16:25:14Z

+
+**Cloud ID**
+:   A unique, encoded string that represents your project's {{es}} endpoint (and, where applicable, {{kib}} endpoint) in a compact form. Compatible clients can use it instead of configuring host URLs individually: the client resolves those endpoints from the Cloud ID.
+


should we add something like a note for example that talks about the other endpoints available when managing the project from the cloud UI? Like the kibana endpoint & others, to disambiguate

shainaraskas

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

shainaraskas · 2026-08-11T18:01:18Z

+
+4. To copy the **Cloud ID**, enable **Show Cloud ID**, then copy the value.


would prob sit the image below step 4

would also probably prefer the path florent pointed out because a help menu seems less friendly

shainaraskas · 2026-08-11T18:03:18Z

+## Create an API key [_create_api_key]
+
+You can create an API key from your project's home page, or open the **API keys** page from the navigation menu or with the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+
+For steps, privileges, and key types, refer to [Serverless project API keys](/deploy-manage/api-keys/serverless-project-api-keys.md).


you can access serverless with two types of API keys: these, and cloud API keys. at minimum, we should have a pointer to cloud API keys here

cloud api keys let you manage the project at the "cloud" level, and also can be used anywhere the serverless project api key is used if the correct access is granted

shainaraskas · 2026-08-11T18:10:20Z

+
+# Find your project connection details [serverless-connection-details]
+
+When you connect clients and tools to a {{serverless-full}} project, these are the main connection details you'll work with:


this page should link back to the cloud id page too - not sure which one will rank better

shainaraskas · 2026-08-11T18:10:37Z

 # Find your Cloud ID [ec-cloud-id]

+::::{note}
+This page is for {{ech}} deployments. If you're using a {{serverless-full}} project, refer to [Find your project connection details](find-connection-details-serverless.md).


Suggested change

This page is for {{ech}} deployments. If you're using a {{serverless-full}} project, refer to [Find your project connection details](find-connection-details-serverless.md).

This page is for {{ech}} deployments. If you're using a {{serverless-full}} project, refer to [](find-connection-details-serverless.md).

shainaraskas · 2026-08-11T18:11:27Z

+* [Beats for {{es-serverless}}](beats://reference/serverless/beats.md): Configure Beats to send logs, metrics, and other data using your {{es}} endpoint and API key.
+* [Sending data to {{es-serverless}}](logstash://reference/connecting-to-serverless.md): Configure {{ls}} to send data to your project.
+* [Install {{agent}}](/reference/fleet/install-elastic-agents.md): Collect and ship data with {{agent}} and Fleet.
+* [{{es}} language clients](/reference/elasticsearch-clients/index.md): Connect applications to your project with an official client library.
+* [Ingest: Bring your data to Elastic](/manage-data/ingest.md): Browse other ingest options, from APIs and connectors to OpenTelemetry.


Suggested change

* [Beats for {{es-serverless}}](beats://reference/serverless/beats.md): Configure Beats to send logs, metrics, and other data using your {{es}} endpoint and API key.

* [Sending data to {{es-serverless}}](logstash://reference/connecting-to-serverless.md): Configure {{ls}} to send data to your project.

* [Install {{agent}}](/reference/fleet/install-elastic-agents.md): Collect and ship data with {{agent}} and Fleet.

* [{{es}} language clients](/reference/elasticsearch-clients/index.md): Connect applications to your project with an official client library.

* [Ingest: Bring your data to Elastic](/manage-data/ingest.md): Browse other ingest options, from APIs and connectors to OpenTelemetry.

* [Beats for {{es-serverless}}](beats://reference/serverless/beats.md): Configure Beats to send logs, metrics, and other data using your {{es}} endpoint and API key.

* [Sending data to {{es-serverless}}](logstash://reference/connecting-to-serverless.md): Configure {{ls}} to send data to your project.

* [](/reference/fleet/install-elastic-agents.md): Collect and ship data with {{agent}} and Fleet.

* [](/reference/elasticsearch-clients/index.md): Connect applications to your project with an official client library.

* [](/manage-data/ingest.md): Browse other ingest options, from APIs and connectors to OpenTelemetry.

shainaraskas · 2026-08-11T18:11:41Z

+
+You can create an API key from your project's home page, or open the **API keys** page from the navigation menu or with the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+
+For steps, privileges, and key types, refer to [Serverless project API keys](/deploy-manage/api-keys/serverless-project-api-keys.md).


key types is kind of irrelevant in the context of creating your own key

also we can rely on autolink here

Suggested change

For steps, privileges, and key types, refer to [Serverless project API keys](/deploy-manage/api-keys/serverless-project-api-keys.md).

For steps, privileges, and key types, refer to [](/deploy-manage/api-keys/serverless-project-api-keys.md).

shainaraskas · 2026-08-11T18:18:47Z

+**Cloud ID**
+:   A unique, encoded string that represents your project's {{es}} endpoint (and, where applicable, {{kib}} endpoint) in a compact form. Compatible clients can use it instead of configuring host URLs individually: the client resolves those endpoints from the Cloud ID.
+
+## Find your {{es}} endpoint and Cloud ID [_find_elasticsearch_endpoint]


we should also expose the cloud console pathway - this info is also available on the specific project's page under https://cloud.elastic.co/projects (click "manage", then look for connection alias for endpoints ... not sure if cloud id is available through this pathway)

yetanothertw · 2026-08-12T08:30:39Z

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 added 2 commits August 6, 2026 18:35

Create a new page for Serverless cloud id

53643ec

Fixes [#5150](#5150) and [#345](elastic/docs-content-internal#345) It adds a new page specific to Serverless, equivalent to [Find your Cloud ID](https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/find-cloud-idthat exists for ECH.

Add note+link to the new page on the equivalent ECH page

e4e4c1a

Merge branch 'main' into cloud-id-serverless-345

2540a43

github-actions Bot deployed to docs-preview August 7, 2026 07:58 View deployment

yetanothertw marked this pull request as ready for review August 7, 2026 13:05

yetanothertw requested a review from a team as a code owner August 7, 2026 13:05

yetanothertw requested review from florent-leborgne and ppf2 August 7, 2026 13:05

yetanothertw mentioned this pull request Aug 7, 2026

Equivalent of Cloud ID page but for Serverless #5150

Open

florent-leborgne reviewed Aug 11, 2026

View reviewed changes

shainaraskas approved these changes Aug 11, 2026

View reviewed changes

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


		## Create an API key [_create_api_key]

		You can create an API key from your project's home page, or open the API keys page from the navigation menu or with the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).


		Cloud ID
		: A unique, encoded string that represents your project's {{es}} endpoint (and, where applicable, {{kib}} endpoint) in a compact form. Compatible clients can use it instead of configuring host URLs individually: the client resolves those endpoints from the Cloud ID.


		4. To copy the Cloud ID, enable Show Cloud ID, then copy the value.


		# Find your project connection details [serverless-connection-details]

		When you connect clients and tools to a {{serverless-full}} project, these are the main connection details you'll work with:

	This page is for {{ech}} deployments. If you're using a {{serverless-full}} project, refer to [Find your project connection details](find-connection-details-serverless.md).
	This page is for {{ech}} deployments. If you're using a {{serverless-full}} project, refer to [](find-connection-details-serverless.md).


		You can create an API key from your project's home page, or open the API keys page from the navigation menu or with the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).

		For steps, privileges, and key types, refer to [Serverless project API keys](/deploy-manage/api-keys/serverless-project-api-keys.md).

Uh oh!

Conversation

yetanothertw commented Aug 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Generative AI disclosure

Uh oh!

github-actions Bot commented Aug 6, 2026

Elastic Docs AI PR menu

Uh oh!

github-actions Bot commented Aug 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Preview links for changed docs

Uh oh!

github-actions Bot commented Aug 7, 2026

✅ Elastic Docs Style Checker (Vale)

Uh oh!

florent-leborgne left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shainaraskas left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

yetanothertw commented Aug 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

yetanothertw commented Aug 6, 2026 •

edited

Loading

github-actions Bot commented Aug 7, 2026 •

edited

Loading