github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-06-27 17:08:55 -04:00
Code Issues Projects Releases Packages Wiki Activity

Doc: Update cloud terminology (#17653)

Browse source
This commit is contained in:
Karen Metts 2025-06-24 17:32:32 -04:00 • committed by GitHub
parent 53e453180c
commit e76b7182ca
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 10 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/docset.yml
View file

@ -17,6 +17,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"
@ -47,5 +48,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
docs/reference/advanced-pipeline.md
View file

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

7
docs/reference/connecting-to-cloud.md
View file

@ -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>" } }`

2
docs/reference/index.md
View file

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