elastic · florent-leborgne · Feb 24, 2025 · Feb 24, 2025 · Feb 24, 2025 · Feb 24, 2025
@@ -24,7 +24,7 @@ Changes to the allowlist do not take effect immediately. After saving your chang
 
 ### Using the UI [using-the-ui]
 
-1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 2. Select a deployment.
 3. From your deployment menu, go to the **Edit** page.
 4. Select **Save**.

@@ -37,7 +37,7 @@ Open a new case to keep track of issues and share their details with colleagues.
 
 You can configure email notifications that occur when users are assigned to cases.
 
-For hosted {{kib}} on {{ess}}:
+For {{kib}} on {{ecloud}}:
 
 1. Add the email domains to the [notifications domain allowlist](../alerts.md).
 

@@ -24,11 +24,11 @@ To learn more about Kibana alerting and how to use it, check [Alerting and Actio
 
 ## Send alerts by email [watcher-allowlist]
 
-You can configure notifications similar to the [operational emails](../../../deploy-manage/cloud-organization/operational-emails.md) that Elasticsearch Service sends automatically to alert you about performance issues in your clusters.
+You can configure notifications similar to the [operational emails](../../../deploy-manage/cloud-organization/operational-emails.md) that {{ecloud}} sends automatically to alert you about performance issues in your clusters.
 
 Watcher in Elastic Cloud is preconfigured with an email service and can be used without any additional configuration. Alternatively, a custom mail server can be configured as described in [Configuring a custom mail server](#watcher-custom-mail-server)
 
-You can optionally add [HTML sanitization](../../../explore-analyze/alerts-cases/watcher/actions-email.md#email-html-sanitization) settings under [Elasticsearch User settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) so that HTML elements are sanitized in the email notification.
+You can optionally add [HTML sanitization](../../../explore-analyze/alerts-cases/watcher/actions-email.md#email-html-sanitization) settings under [Elasticsearch User settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) so that HTML elements are sanitized in the email notification.
 
 For more information on sending alerts by email, check [Email action](../../../explore-analyze/alerts-cases/watcher/actions-email.md).
 

@@ -108,7 +108,7 @@ If the estimated model memory limit for an {{anomaly-job}} is greater than the m
   * Add bigger {{ml}} nodes to the cluster, or
   * Accept that the job will hit its memory limit and will not necessarily find all the anomalies it could otherwise find.
 
-If you are using {{ece}} or the hosted Elasticsearch Service on Elastic Cloud, `xpack.ml.max_model_memory_limit` is set to prevent you from creating jobs that cannot be allocated to any {{ml}} nodes in the cluster. If you find that you cannot increase `model_memory_limit` for your {{ml}} jobs, the solution is to increase the size of the {{ml}} nodes in your cluster.
+If you are using {{ece}} or {{ech}}, `xpack.ml.max_model_memory_limit` is set to prevent you from creating jobs that cannot be allocated to any {{ml}} nodes in the cluster. If you find that you cannot increase `model_memory_limit` for your {{ml}} jobs, the solution is to increase the size of the {{ml}} nodes in your cluster.
 
 ### Dedicated indices [ml-ad-dedicated-indices]
 

@@ -23,7 +23,7 @@ Need more context? Check out the [{{es}} introduction](/get-started/index.md) to
 
 1. Before you can play with the {{ml-features}}, you must install {{es}} and {{kib}}. {{es}} stores the data and the analysis results. {{kib}} provides a helpful user interface for creating and viewing jobs.
    ::::{tip}
-   You can run {{es}} and {{kib}} on your own hardware, or use our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service) on {{ecloud}}. The {{ess}} is available on both AWS and GCP. [Try out the {{ess}} for free](https://www.elastic.co/cloud/elasticsearch-service/signup).
+   You can run {{es}} and {{kib}} on your own hardware or on [{{ecloud}}](https://www.elastic.co/cloud/). [Try out {{ecloud}} for free](https://cloud.elastic.co/registration?elektra=en-ess-sign-up-page).
    ::::
 
 2. Verify that your environment is set up properly to use the {{ml-features}}. If the {{es}} {{security-features}} are enabled, to complete this tutorial you need a user that has authority to manage {{anomaly-jobs}}. See [Setup and security](../setting-up-machine-learning.md).

@@ -30,7 +30,7 @@ This approach provides a more understandable search experience compared to vecto
 To use ELSER, you must have the [appropriate subscription](https://www.elastic.co/subscriptions) level for semantic search or the trial period activated.
 
 ::::{note}
-The minimum dedicated ML node size for deploying and using the ELSER model is 4 GB in Elasticsearch Service if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself.
+The minimum dedicated ML node size for deploying and using the ELSER model is 4 GB in {{ech}} if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself.
 ::::
 
 Enabling trained model autoscaling for your ELSER deployment is recommended. Refer to [*Trained model autoscaling*](ml-nlp-auto-scale.md) to learn more.

@@ -117,7 +117,7 @@ PUT ner-test
 ```
 
 ::::{tip}
-To use the `annotated_text` data type in this example, you must install the [mapper annotated text plugin](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/mapper-annotated-text.md). For more installation details, refer to [Add plugins provided with {{ess}}](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/cloud/ec-adding-elastic-plugins.md).
+To use the `annotated_text` data type in this example, you must install the [mapper annotated text plugin](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/mapper-annotated-text.md). For more installation details, refer to [Add plugins provided with {{ech}}](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/cloud/ec-adding-elastic-plugins.md).
 ::::
 
 You can then use the new pipeline to index some documents. For example, use a bulk indexing request with the `pipeline` query parameter for your NER pipeline:

@@ -10,7 +10,7 @@ mapped_pages:
 # Compatible third party models [ml-nlp-model-ref]
 
 ::::{note}
-The minimum dedicated ML node size for deploying and using the {{nlp}} models is 16 GB in Elasticsearch Service if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself.
+The minimum dedicated ML node size for deploying and using the {{nlp}} models is 16 GB in {{ech}} if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself.
 ::::
 
 The {{stack-ml-features}} support transformer models that conform to the standard BERT model interface and use the WordPiece tokenization algorithm.

@@ -23,7 +23,7 @@ To use the {{stack}} {{ml-features}}, you must have:
   * grant access to source and destination indices.
 
 ::::{tip}
-The fastest way to get started with {{ml-features}} is to [start a free 14-day trial of {{ess}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) in the cloud.
+The fastest way to get started with {{ml-features}} is to [start a free 14-day trial of {{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
 ::::
 
 ## Security privileges [setup-privileges]

@@ -22,7 +22,7 @@ With {{esql}}, you can execute a single query across multiple clusters.
 
 ## Prerequisites [esql-ccs-prerequisites]
 
-* {{ccs-cap}} requires remote clusters. To set up remote clusters on {{ess}}, see [configure remote clusters on {{ess}}](/deploy-manage/remote-clusters/ec-enable-ccs.md). If you run {{es}} on your own hardware, see [*Remote clusters*](../../../deploy-manage/remote-clusters.md).
+* {{ccs-cap}} requires remote clusters. To set up remote clusters, see [*Remote clusters*](../../../deploy-manage/remote-clusters.md).
 
     To ensure your remote cluster configuration supports {{ccs}}, see [Supported {{ccs}} configurations](../../../solutions/search/cross-cluster-search.md#ccs-supported-configurations).
 

@@ -108,7 +108,7 @@ This tab allows configuration for the following items:
 
 * Cloud ID
 
-  The *Cloud ID* is a string that simplifies the configuration when connecting to Elastic’s Cloud {{ess}}; it is obtained from within the Cloud console of each {{es}} cluster and encodes the connection parameters to that cluster.
+  The *Cloud ID* is a string that simplifies the configuration when connecting to {{ecloud}}. It encodes the connection parameters to that cluster. You can obtain it from from your deployment's details in the {{ecloud}} Console.
 
   ::::{note}
   When this field is provisioned, the *Hostname*, *Port* and the security settings are provisioned as well and their respective inputs disabled.

@@ -13,7 +13,7 @@ New to Elastic? Refer to [get started](/get-started/the-stack.md) to understand
 Users reach for Elastic products, features, and tools for three main use cases: observability, security, and search.
 
 These use cases are supported by ready-to-use implementations that help you get started quickly:
-- As integrated solutions on [{{ecloud}} Hosted](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md) and [self-managed](/deploy-manage/deploy/self-managed.md) deployments
+- As integrated solutions on [{{ech}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md) and [self-managed](/deploy-manage/deploy/self-managed.md) deployments
 - As project types on [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md)
 
 While these solutions and project types provide pre-built components for common use cases, you can also build custom implementations using Elastic's features, APIs, and tools. This documentation guides you through:

@@ -815,7 +815,7 @@ docker run -d \
 ```
 
 1. Substitute your {{es}} hosts and ports.
-2. If you are using the hosted {{ess}} in {{ecloud}}, replace the `-E output.elasticsearch.hosts` line with the Cloud ID and elastic password using the syntax shown earlier.
+2. If you are using {{ech}}, replace the `-E output.elasticsearch.hosts` line with the Cloud ID and elastic password using the syntax shown earlier.
 
 
 

@@ -52,8 +52,8 @@ User settings are appended to the `apm-server.yml` configuration file for your i
 
 To add user settings:
 
-1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. Find your deployment on the home page in the Elasticsearch Service card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
 
     On the deployments page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
 
@@ -63,14 +63,14 @@ To add user settings:
 6. Select **Save changes**.
 
 ::::{note}
-If a setting is not supported by Elasticsearch Service, you will get an error message when you try to save.
+If a setting is not supported on {{ecloud}}, you will get an error message when you try to save.
 ::::
 
 
 
 ## Supported standalone APM settings (legacy) [ec-apm-settings]
 
-Elasticsearch Service supports the following setting when running APM in standalone mode (legacy).
+{{ech}} supports the following setting when running APM in standalone mode (legacy).
 
 ::::{tip}
 Some settings that could break your cluster if set incorrectly are blocklisted. The following settings are generally safe in cloud environments. For detailed information about APM settings, check the [APM documentation](/solutions/observability/apps/configure-apm-server.md).

@@ -1,12 +1,12 @@
 ---
-navigation_title: "{{ess}}"
+navigation_title: "{{ech}}"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-configure-cloud-id.html
 ---
 
 
 
-# Configure the output for Elasticsearch Service on Elastic Cloud [apm-configure-cloud-id]
+# Configure the output for {{ech}} [apm-configure-cloud-id]
 
 
 ::::{admonition}
@@ -18,11 +18,11 @@ This documentation only applies to APM Server binary users.
 
 
 ::::{note}
-This page refers to using a separate instance of APM Server with an existing [{{ess}} deployment](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body). If you want to use APM on {{ess}}, see: [Create your deployment](../../../deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md) and [Add APM user settings](configure-apm-server.md).
+This page refers to using a separate instance of APM Server with an existing [{{ech}} deployment](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body). If you want to use APM on {{ech}}, see: [Create your deployment](../../../deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md) and [Add APM user settings](configure-apm-server.md).
 ::::
 
 
-APM Server comes with two settings that simplify the output configuration when used together with [{{ess}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body). When defined, these setting overwrite settings from other parts in the configuration.
+APM Server comes with two settings that simplify the output configuration when used together with [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body). When defined, these setting overwrite settings from other parts in the configuration.
 
 Example:
 
@@ -40,7 +40,7 @@ apm-server -e -E cloud.id="<cloud-id>" -E cloud.auth="<cloud.auth>"
 
 ## `cloud.id` [_cloud_id]
 
-The Cloud ID, which can be found in the {{ess}} web console, is used by APM Server to resolve the {{es}} and {{kib}} URLs. This setting overwrites the `output.elasticsearch.hosts` and `setup.kibana.host` settings.
+The Cloud ID, which can be found in the {{ecloud}} Console, is used by APM Server to resolve the {{es}} and {{kib}} URLs. This setting overwrites the `output.elasticsearch.hosts` and `setup.kibana.host` settings.
 
 
 ## `cloud.auth` [_cloud_auth]

@@ -11,7 +11,7 @@ mapped_pages:
 
 Output configuration options.
 
-* [{{ess}}](configure-output-for-elasticsearch-service-on-elastic-cloud.md)
+* [{{ech}}](configure-output-for-elasticsearch-service-on-elastic-cloud.md)
 * [{{es}}](configure-elasticsearch-output.md)
 * [{{ls}}](configure-logstash-output.md)
 * [Kafka](configure-kafka-output.md)

@@ -144,7 +144,7 @@ Looking for privileges and roles needed to use central configuration from the Ap
 ### Publish monitoring data [apm-privileges-to-publish-monitoring-write]
 
 ::::{important}
-**{{ecloud}} users:** This section does not apply to our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service). Monitoring on {{ecloud}} is enabled by clicking the **Enable** button in the **Monitoring** panel.
+**{{ecloud}} users:** This section does not apply to [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service). Monitoring on {{ecloud}} is enabled by clicking the **Enable** button in the **Monitoring** panel.
 
 ::::
 

@@ -16,7 +16,7 @@ Elastic APM utilizes {{es}}'s cross-cluster search functionality. Cross-cluster
 
 **Step 1. Set up remote clusters.**
 
-If you’re using the Hosted {{ess}}, see [Enable cross-cluster search](../../../deploy-manage/remote-clusters/ec-enable-ccs.md).
+If you’re using the {{ech}}, see [Enable cross-cluster search](../../../deploy-manage/remote-clusters/ec-enable-ccs.md).
 
 To add remote clusters directly in {{kib}}, find `Remote Clusters` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). All you need is a name for the remote cluster and the seed node(s). Remember the names of your remote clusters, you’ll need them in step two. See [managing remote clusters](/deploy-manage/tools/cross-cluster-replication/set-up-cross-cluster-replication.md) for detailed information on the setup process.
 

@@ -36,7 +36,7 @@ Fleet is a web-based UI in {{kib}} that is used to centrally manage {{agent}}s.
 **Supported outputs**:
 
 * {{es}}
-* {{ess}}
+* {{ech}}
 
 ::::{note}
 Fleet-managed APM Server does *not* support all the outputs that are supported by the APM Server binary method of running Elastic APM.
@@ -68,7 +68,7 @@ Install, configure, and run the APM Server binary wherever you need it.
 **Supported outputs**:
 
 * {{es}}
-* {{ess}}
+* {{ech}}
 * {{ls}}
 * Kafka
 * Redis

@@ -48,7 +48,7 @@ The APM integration serves Jaeger gRPC over the same host and port as the Elasti
 
 :::::::{tab-set}
 
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ecloud}}
 1. Log into [{{ecloud}}](https://cloud.elastic.co?page=docs&placement=docs-body) and select your deployment.
 2. In {{kib}}, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 3. Select **Elastic APM**. If the integration is already installed, under the polices tab, select **Actions*** > ***Edit integration**. If the integration has not been installed, select **Add Elastic APM**. Copy the URL. If you’re using Agent authorization, copy the Secret token as well.

@@ -18,5 +18,5 @@ Select your deployment method to get started:
 
 {{ecloud}} manages the installation and configuration of a monitoring agent for you — so all you have to do is flip a switch and watch the data pour in.
 
-* **{{ess}}** user? See [ESS: Enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md).
-* **{{ece}}** user? See [ECE: Enable logging and monitoring](/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md).
+* **{{ech}}** user? See [Stack Monitoring on {{ecloud}} deployments](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md).
+* **{{ece}}** user? See [Enable stack monitoring on ECE deployments](/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md).
-Original file line number
+Diff line change
@@ Expand Up / @@ -815,7 +815,7 @@ docker run -d \ @@
     ```
 . Substitute your {{es}} hosts and ports.
-. If you are using the hosted {{ess}} in {{ecloud}}, replace the `-E output.elasticsearch.hosts` line with the Cloud ID and elastic password using the syntax shown earlier.
+. If you are using {{ech}}, replace the `-E output.elasticsearch.hosts` line with the Cloud ID and elastic password using the syntax shown earlier.
@@ Expand Down @@