Skip to content

Doc: Update cloud terminology #17653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
+10 −6
Open

Doc: Update cloud terminology #17653

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c92f2f7
Doc: Update cloud terminology
karenzone May 9, 2025
4a2969d
Update docs/docset.yml
karenzone May 9, 2025
8f37d46
More fixes
karenzone May 19, 2025
52e28dd
Add period to close the sentence.
karenzone May 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/docset.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ subs:
version: "9.0.0"
logstash-ref: "https://www.elastic.co/guide/en/logstash/current"
ecloud: "Elastic Cloud"
ech: "Elastic Cloud Hosted"
esf: "Elastic Serverless Forwarder"
ess: "Elasticsearch Service"
serverless-full: "Elastic Cloud Serverless"
Expand Down Expand Up @@ -45,5 +46,5 @@ subs:
stack-version: "9.0.0"
major-version: "9.x"
docker-repo: "docker.elastic.co/logstash/logstash"
ess-leadin-short: "Our hosted Elasticsearch Service is available on AWS, GCP, and Azure, and you can try it for free at https://cloud.elastic.co/registration"
ess-leadin: "You can run Elasticsearch on your own hardware or use our hosted Elasticsearch Service that is available on AWS, GCP, and Azure. Try the Elasticsearch Service for free: https://cloud.elastic.co/registration."
ess-leadin-short: "Elastic Cloud Hosted is available on AWS, GCP, and Azure, and you can try it for free at https://cloud.elastic.co/registration."
ess-leadin: "You can run Elasticsearch on your own hardware or use Elastic Cloud Hosted, available on AWS, GCP, and Azure. Try Elastic Cloud Hosted for free: https://cloud.elastic.co/registration."
2 changes: 1 addition & 1 deletion docs/reference/advanced-pipeline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -374,7 +374,7 @@ Notice that the event now contains geographic location information:
```


### Indexing Your Data into Elasticsearch [indexing-parsed-data-into-elasticsearch]
### Indexing your data into Elasticsearch [indexing-parsed-data-into-elasticsearch]

Now that the web logs are broken down into specific fields, you’re ready to get your data into Elasticsearch.

Expand Down
7 changes: 5 additions & 2 deletions docs/reference/connecting-to-cloud.md
View file
Open in desktop
Copy link
Contributor

@vishaangelova vishaangelova May 20, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

On line 22:

  • In {{ls}} uses the Cloud ID, found in the Elastic Cloud web console, to build the Elasticsearch and Kibana hosts settings., is it perhaps hosts’ settings?

  • There’s a missing period at the end of the last sentence + maybe remove should, and add a comma after To add a label: To add a label, prefix your Cloud ID with a label and a : separator in this format "<label>:<cloud-id>”.

This is probably out of scope, though, so not sure if it’s OK to point these out now.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Always OK to point things out. 😄

Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,15 @@ mapped_pages:
- https://www.elastic.co/guide/en/logstash/current/connecting-to-cloud.html
---

# Sending data to Elastic Cloud (hosted Elasticsearch Service) [connecting-to-cloud]
# Sending data to {{ech}} [connecting-to-cloud]

Our hosted {{ess}} on [Elastic Cloud](https://cloud.elastic.co/) simplifies safe, secure communication between {{ls}} and {{es}}. When you configure the Elasticsearch output plugin to use [`cloud_id`](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md#plugins-outputs-elasticsearch-cloud_id) with either the [`cloud_auth` option](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md#plugins-outputs-elasticsearch-cloud_auth) or the [`api_key` option](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md#plugins-outputs-elasticsearch-api_key), no additional SSL configuration is needed.
[{{ech}}](https://cloud.elastic.co/) simplifies safe, secure communication between {{ls}} and {{es}}.
When you configure the Elasticsearch output plugin to use [`cloud_id`](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md#plugins-outputs-elasticsearch-cloud_id) with either the [`cloud_auth` option](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md#plugins-outputs-elasticsearch-cloud_auth) or the [`api_key` option](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md#plugins-outputs-elasticsearch-api_key), no additional SSL configuration is needed.

Examples:



* `output {elasticsearch { cloud_id => "<cloud id>" cloud_auth => "<cloud auth>" } }`
* `output {elasticsearch { cloud_id => "<cloud id>" api_key => "<api key>" } }`

Expand Down
2 changes: 1 addition & 1 deletion docs/reference/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Logstash accelerates your insights by harnessing a greater volume and variety of

::::{admonition} {{ls}} to {{serverless-full}}
You’ll use the {{ls}} [{{es}} output plugin](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md) to send data to {{serverless-full}}.
Note these differences between {{es-serverless}} and both {{ess}} and self-managed {{es}}:
Note these differences between {{es-serverless}} and both {{ech}} and self-managed {{es}}:

* Use **API keys** to access {{serverless-full}} from {{ls}}. Any user-based security settings in your [{{es}} output plugin](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md) configuration are ignored and may cause errors.
* {{serverless-full}} uses **data streams** and [{{dlm}} ({{dlm-init}})](docs-content://manage-data/lifecycle/data-stream.md) instead of {{ilm}} ({{ilm-init}}). Any {{ilm-init}} settings in your [{{es}} output plugin](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md) configuration are ignored and may cause errors.
Expand Down
Loading