diff --git a/cloud-account/change-your-password.md b/cloud-account/change-your-password.md
index c3bba9d66..b18310dd7 100644
--- a/cloud-account/change-your-password.md
+++ b/cloud-account/change-your-password.md
@@ -8,7 +8,7 @@ applies:
# Change your password [ec-change-password]
-If you created a password when you signed up for a {{ecloud}} account, or you added the password-based login method to your account, then you can change your password if needed.
+If you created a password when you signed up for an {{ecloud}} account, or you added the password-based login method to your account, then you can change your password if needed.
If you know your current password:
diff --git a/deploy-manage/autoscaling/ec-autoscaling-api-example.md b/deploy-manage/autoscaling/ec-autoscaling-api-example.md
index d059ca6c8..92e391558 100644
--- a/deploy-manage/autoscaling/ec-autoscaling-api-example.md
+++ b/deploy-manage/autoscaling/ec-autoscaling-api-example.md
@@ -5,9 +5,9 @@ mapped_pages:
# Autoscaling through the API [ec-autoscaling-api-example]
-This example demonstrates how to use the Elasticsearch Service RESTful API to create a deployment with autoscaling enabled.
+This example demonstrates how to use the {{ecloud}} RESTful API to create a deployment with autoscaling enabled.
-The example deployment has a hot data and content tier, warm data tier, cold data tier, and a machine learning node, all of which will scale within the defined parameters. To learn about the autoscaling settings, check [Deployment autoscaling](../autoscaling.md) and [Autoscaling example](ec-autoscaling-example.md). For more information about using the Elasticsearch Service API in general, check [RESTful API](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-restful.md).
+The example deployment has a hot data and content tier, warm data tier, cold data tier, and a machine learning node, all of which will scale within the defined parameters. To learn about the autoscaling settings, check [Deployment autoscaling](../autoscaling.md) and [Autoscaling example](ec-autoscaling-example.md). For more information about using the {{ecloud}} API in general, check [RESTful API](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-restful.md).
## Requirements [ec_requirements]
@@ -46,7 +46,7 @@ $$$ec-autoscaling-api-example-requirements-table$$$
+ ✕ = Do not include the property.
-+ These rules match the behavior of the Elasticsearch Service user console.
++ These rules match the behavior of the {{ecloud}} Console.
+ * The `elasticsearch` object must contain the property `"autoscaling_enabled": true`.
diff --git a/deploy-manage/autoscaling/ec-autoscaling-example.md b/deploy-manage/autoscaling/ec-autoscaling-example.md
index 80d7787ba..7ca8f25a5 100644
--- a/deploy-manage/autoscaling/ec-autoscaling-example.md
+++ b/deploy-manage/autoscaling/ec-autoscaling-example.md
@@ -5,7 +5,7 @@ mapped_pages:
# Autoscaling example [ec-autoscaling-example]
-To help you better understand the available autoscaling settings, this example describes a typical autoscaling workflow on sample Elasticsearch Service deployment.
+To help you better understand the available autoscaling settings, this example describes a typical autoscaling workflow on sample {{ech}} deployment.
1. Enable autoscaling:
diff --git a/deploy-manage/autoscaling/ec-autoscaling.md b/deploy-manage/autoscaling/ec-autoscaling.md
index 999e7bd6b..ace565330 100644
--- a/deploy-manage/autoscaling/ec-autoscaling.md
+++ b/deploy-manage/autoscaling/ec-autoscaling.md
@@ -45,7 +45,7 @@ Currently, autoscaling behavior is as follows:
::::{note}
-For any Elasticsearch Service Elasticsearch component the number of availability zones is not affected by autoscaling. You can always set the number of availability zones manually and the autoscaling mechanism will add or remove capacity per availability zone.
+The number of availability zones for each component of your {{ech}} deployments is not affected by autoscaling. You can always set the number of availability zones manually and the autoscaling mechanism will add or remove capacity per availability zone.
::::
@@ -85,10 +85,10 @@ The following are known limitations and restrictions with autoscaling:
To enable or disable autoscaling on a deployment:
-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. On the **Deployments** page, select your deployment.
- 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.
+ 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.
3. In your deployment menu, select **Edit**.
4. Select desired autoscaling configuration for this deployment using **Enable Autoscaling for:** dropdown menu.
@@ -103,10 +103,10 @@ When autoscaling has been disabled, you need to adjust the size of data tiers an
Each autoscaling setting is configured with a default value. You can adjust these if necessary, as follows:
-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. On the **Deployments** page, select your deployment.
- 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.
+ 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.
3. In your deployment menu, select **Edit**.
4. To update a data tier:
diff --git a/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md b/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md
index 0afd6711d..4e426bafb 100644
--- a/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md
+++ b/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md
@@ -90,7 +90,7 @@ As is common with Cloud providers, we meter and bill snapshot storage using two
### How can I control the storage cost? [ec_how_can_i_control_the_storage_cost]
-Snapshots in Elasticsearch Service save data incrementally at each snapshot event. This means that the effective snapshot size may be larger than the size of the current indices. The snapshot size increases as data is added or updated in the cluster, and deletions do not reduce the snapshot size until the snapshot containing that data is removed.
+Snapshots in {{ech}} save data incrementally at each snapshot event. This means that the effective snapshot size may be larger than the size of the current indices. The snapshot size increases as data is added or updated in the cluster, and deletions do not reduce the snapshot size until the snapshot containing that data is removed.
API requests are executed every time a snapshot is taken or restored, affecting usage costs. In the event that you have any automated processes that use the Elasticsearch API to create or restore snapshots, these should be set so as to avoid unexpected charges.
diff --git a/deploy-manage/cloud-organization/operational-emails.md b/deploy-manage/cloud-organization/operational-emails.md
index bedecc35d..33c40d46e 100644
--- a/deploy-manage/cloud-organization/operational-emails.md
+++ b/deploy-manage/cloud-organization/operational-emails.md
@@ -19,4 +19,4 @@ We also send an email alert if one of the nodes in your cluster is restarted due
These alerts are sent to all users within an {{ecloud}} organization, as well as to the email addresses listed as operational email contacts. This means that an external distribution list or automated service can receive notifications without the need to be added to the organization directly.
-To configure recipients external to an {{ecloud}} organization for these notifications Elasticsearch Service, update the list of [operational email contacts](/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md).
+To configure recipients external to an {{ecloud}} organization for these notifications, update the list of [operational email contacts](/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md).
diff --git a/deploy-manage/cloud-organization/tools-and-apis.md b/deploy-manage/cloud-organization/tools-and-apis.md
index 794bcb3dc..e1a502ebf 100644
--- a/deploy-manage/cloud-organization/tools-and-apis.md
+++ b/deploy-manage/cloud-organization/tools-and-apis.md
@@ -5,30 +5,30 @@ mapped_pages:
# Tools and APIs [ec-work-with-apis]
-Most Elastic resources can be accessed and managed through RESTful APIs. While the Elasticsearch Service API is used to manage your deployments and their components, the Elasticsearch and Kibana APIs provide direct access to your data and your visualizations, respectively.
+Most Elastic resources can be accessed and managed through RESTful APIs. While the {{ecloud}} API is used to manage your deployments and their components, the Elasticsearch and Kibana APIs provide direct access to your data and your visualizations, respectively.
-Elasticsearch Service API
-: You can use the Elasticsearch Service API to manage your deployments and all of the resources associated with them. This includes performing deployment CRUD operations, scaling or autoscaling resources, and managing traffic filters, deployment extensions, remote clusters, and Elastic Stack versions. You can also access cost data by deployment and by organization.
+{{ecloud}} API
+: You can use the {{ecloud}} API to manage your deployments and all of the resources associated with them. This includes performing deployment CRUD operations, scaling or autoscaling resources, and managing traffic filters, deployment extensions, remote clusters, and Elastic Stack versions. You can also access cost data by deployment and by organization.
- To learn more about the Elasticsearch Service API, read through the [API overview](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-restful.md), try out some [getting started examples](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-examples.md), and check our [API reference documentation](https://www.elastic.co/docs/api/doc/cloud).
+ To learn more about the {{ecloud}} API, read through the [API overview](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-restful.md), try out some [getting started examples](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-examples.md), and check our [API reference documentation](https://www.elastic.co/docs/api/doc/cloud).
- Calls to the Elasticsearch Service API are subject to [Rate limiting](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-rate-limiting.md).
+ Calls to the {{ecloud}} API are subject to [Rate limiting](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-rate-limiting.md).
Elasticsearch APIs
: This set of APIs allows you to interact directly with the Elasticsearch nodes in your deployment. You can ingest data, run search queries, check the health of your clusters, manage snapshots, and more.
- To use these APIs in Elasticsearch Service read our topic [Access the Elasticsearch API console](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-console.md), and to learn about all of the available endpoints check the [Elasticsearch API reference documentation](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/rest-apis/index.md).
+ To use these APIs on {{ecloud}} read our topic [Access the API console](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-console.md), and to learn about all of the available endpoints check the [Elasticsearch API reference documentation](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/rest-apis/index.md).
- Some [restrictions](../deploy/elastic-cloud/restrictions-known-problems.md#ec-restrictions-apis-elasticsearch) apply when using the Elasticsearch APIs in Elasticsearch Service.
+ Some [restrictions](../deploy/elastic-cloud/restrictions-known-problems.md#ec-restrictions-apis-elasticsearch) apply when using the Elasticsearch APIs on {{ecloud}}.
Kibana APIs
: Many Kibana features can be accessed through these APIs, including Kibana objects, patterns, and dashboards, as well as user roles and user sessions. You can use these APIs to configure alerts and actions, and to access health details for the Kibana Task Manager.
- The Kibana APIs cannot be accessed directly from the Elasticsearch Service console; you need to use `curl` or another HTTP tool to connect. Check the [Kibana API reference documentation](https://www.elastic.co/guide/en/kibana/current/api.html) to learn about using the APIs and for details about all available endpoints.
+ The Kibana APIs cannot be accessed directly from the {{ecloud}} Console; you need to use `curl` or another HTTP tool to connect. Check the [Kibana API reference documentation](https://www.elastic.co/guide/en/kibana/current/api.html) to learn about using the APIs and for details about all available endpoints.
- Some [restrictions](../deploy/elastic-cloud/restrictions-known-problems.md#ec-restrictions-apis-kibana) apply when using these APIs with an Elasticsearch Service Kibana instance as compared to an on-prem installation.
+ Some [restrictions](../deploy/elastic-cloud/restrictions-known-problems.md#ec-restrictions-apis-kibana) apply when using these APIs with Kibana on {{ecloud}} as compared to an on-prem installation.
Other Products
diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md
index 0ce8fc9a6..5e44fd9a2 100644
--- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md
+++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md
@@ -39,7 +39,7 @@ $$$allocator-sample-tags$$$Tags are simple key-value pairs. A small sampling of
: Indicates allocators that can run CPU-intensive workloads faster than others.
`instanceFamily: i3`, `instanceFamily: m5`
-: Indicates the host type, used extensively on our hosted Elasticsearch Service to identify hosts with specific hardware characteristics. If you run your own hardware on-premise and have standardized on several specific host configurations, you could use similar tags. If you are deploying ECE on another cloud platform, you could use the instance type or machine type names from your provider.
+: Indicates the host type, used extensively on {{ech}} to identify hosts with specific hardware characteristics. If you run your own hardware on-premise and have standardized on several specific host configurations, you could use similar tags. If you are deploying ECE on another cloud platform, you could use the instance type or machine type names from your provider.
Avoid tags that describe a particular use case or an Elastic Stack component you plan to run on these allocators. Examples of tags to avoid include `elasticsearch: false` or `kibana: true`. You should define the intended use at the level of instance configurations instead and tag your allocators only to describe hardware characteristics.
diff --git a/deploy-manage/deploy/elastic-cloud/access-kibana.md b/deploy-manage/deploy/elastic-cloud/access-kibana.md
index e7617bbe4..cd9ec6d9d 100644
--- a/deploy-manage/deploy/elastic-cloud/access-kibana.md
+++ b/deploy-manage/deploy/elastic-cloud/access-kibana.md
@@ -33,7 +33,7 @@ To access Kibana:
1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
2. On the **Deployments** page, select your deployment.
- 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.
+ 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.
3. Under **Applications**, select the Kibana **Launch** link and wait for Kibana to open.
diff --git a/deploy-manage/deploy/elastic-cloud/configure.md b/deploy-manage/deploy/elastic-cloud/configure.md
index 94fc582f6..5cfef00d5 100644
--- a/deploy-manage/deploy/elastic-cloud/configure.md
+++ b/deploy-manage/deploy/elastic-cloud/configure.md
@@ -38,9 +38,9 @@ If you use a Platform-as-a-Service provider like Heroku, the administration cons
To change your deployment:
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.
+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.
+ 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.
3. From the deployment menu, select **Edit**.
4. Let the user interface guide you through the cluster configuration for your cluster.
diff --git a/deploy-manage/deploy/elastic-cloud/ech-api-console.md b/deploy-manage/deploy/elastic-cloud/ech-api-console.md
index 55cffbc51..c0aae3183 100644
--- a/deploy-manage/deploy/elastic-cloud/ech-api-console.md
+++ b/deploy-manage/deploy/elastic-cloud/ech-api-console.md
@@ -15,7 +15,7 @@ API console is intended for admin purposes. Avoid running normal workload like i
You are unable to make Elasticsearch Add-On for Heroku platform changes from the Elasticsearch API.
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
diff --git a/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md b/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md
index d004ba6a2..408788433 100644
--- a/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md
+++ b/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md
@@ -69,9 +69,9 @@ You can also update [dynamic cluster settings](../../../deploy-manage/deploy/sel
To add or edit user settings:
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.
+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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. In the **Elasticsearch** section, select **Manage user settings and extensions**.
@@ -93,9 +93,9 @@ For a list of supported settings, check [Kibana settings](asciidocalypse://docs/
To change Kibana settings:
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.
+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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. In the **Kibana** section, select **Edit user settings**. For deployments with existing user settings, you may have to expand the **Edit kibana.yml** caret instead.
diff --git a/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md b/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md
index 08adf046f..683739130 100644
--- a/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md
+++ b/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md
@@ -25,7 +25,7 @@ To view the activity for a deployment:
1. Log in to the [{{ech}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
2. On the **Deployments** page, select your deployment.
- 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.
+ 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.
3. In your deployment menu, select **Activity**.
4. You can:
diff --git a/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md b/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md
index 5810ddfd7..0b38fef93 100644
--- a/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md
+++ b/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md
@@ -105,7 +105,7 @@ Bundles
You must upload your files before you can apply them to your cluster configuration:
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.
+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.
3. Under **Features**, select **Extensions**.
4. Select **Upload extension**.
5. Complete the extension fields, including the {{es}} version.
@@ -133,9 +133,9 @@ Refer to [Managing plugins and extensions through the API](../../../deploy-manag
After uploading your files, you can select to enable them when creating a new {{es}} deployment. For existing deployments, you must update your deployment configuration to use the new files:
1. Log in to the [{{ech}} 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.
+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.
+ 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.
3. From the **Actions** dropdown, select **Edit deployment**.
4. Select **Manage user settings and extensions**.
@@ -164,9 +164,9 @@ To update an extension with a new file version,
1. Prepare a new plugin or bundle.
2. On the **Extensions** page, [upload a new extension](../../../deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md#ec-add-your-plugin).
3. Make your new files available by uploading them.
-4. 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.
+4. 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.
+ 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.
5. From the **Actions** dropdown, select **Edit deployment**.
6. Select **Manage user settings and extensions**.
diff --git a/deploy-manage/deploy/self-managed/access.md b/deploy-manage/deploy/self-managed/access.md
index adceacdd0..efaed030d 100644
--- a/deploy-manage/deploy/self-managed/access.md
+++ b/deploy-manage/deploy/self-managed/access.md
@@ -10,7 +10,7 @@ The fastest way to access {{kib}} is to use our hosted {{es}} Service. If you [i
## Set up on cloud [_set_up_on_cloud]
-There’s no faster way to get started than with our hosted {{ess}} on Elastic Cloud:
+There’s no faster way to get started than with {{ecloud}}:
1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
diff --git a/deploy-manage/deploy/self-managed/configure-elasticsearch.md b/deploy-manage/deploy/self-managed/configure-elasticsearch.md
index b3b9c3a6a..c6b267cb5 100644
--- a/deploy-manage/deploy/self-managed/configure-elasticsearch.md
+++ b/deploy-manage/deploy/self-managed/configure-elasticsearch.md
@@ -101,7 +101,7 @@ If you configure the same setting using multiple methods, {{es}} applies the set
For example, you can apply a transient setting to override a persistent setting or `elasticsearch.yml` setting. However, a change to an `elasticsearch.yml` setting will not override a defined transient or persistent setting.
::::{tip}
-If you use {{ess}}, use the [user settings](../elastic-cloud/edit-stack-settings.md) feature to configure all cluster settings. This method lets {{ess}} automatically reject unsafe settings that could break your cluster.
+If you use {{ech}}, use the [user settings](../elastic-cloud/edit-stack-settings.md) feature to configure all cluster settings. This method lets {{ech}} automatically reject unsafe settings that could break your cluster.
If you run {{es}} on your own hardware, use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings) to configure dynamic cluster settings. Only use `elasticsearch.yml` for static cluster settings and node settings. The API doesn’t require a restart and ensures a setting’s value is the same on all nodes.
diff --git a/deploy-manage/deploy/self-managed/configure.md b/deploy-manage/deploy/self-managed/configure.md
index a1a04e84b..4f4a5b4cb 100644
--- a/deploy-manage/deploy/self-managed/configure.md
+++ b/deploy-manage/deploy/self-managed/configure.md
@@ -178,10 +178,10 @@ $$$elasticsearch-user-passwd$$$ `elasticsearch.username` and `elasticsearch.pass
$$$elasticsearch-service-account-token$$$ `elasticsearch.serviceAccountToken`
: If your {{es}} is protected with basic authentication, this token provides the credentials that the {{kib}} server uses to perform maintenance on the {{kib}} index at startup. This setting is an alternative to `elasticsearch.username` and `elasticsearch.password`.
-`unifiedSearch.autocomplete.valueSuggestions.timeout` 
+`unifiedSearch.autocomplete.valueSuggestions.timeout` 
: Time in milliseconds to wait for autocomplete suggestions from {{es}}. This value must be a whole number greater than zero. **Default: `"1000"`**
-`unifiedSearch.autocomplete.valueSuggestions.terminateAfter` 
+`unifiedSearch.autocomplete.valueSuggestions.terminateAfter` 
: Maximum number of documents loaded by each shard to generate autocomplete suggestions. This value must be a whole number greater than zero. **Default: `"100000"`**
::::{note}
@@ -195,7 +195,7 @@ $$$logging-root$$$ `logging.root`
$$$logging-root-appenders$$$ `logging.root.appenders`
: A list of logging appenders to forward the root level logger instance to. By default `root` is configured with the `default` appender that logs to stdout with a `pattern` layout. This is the configuration that all custom loggers will use unless they’re re-configured explicitly. You can override the default behavior by configuring a different [appender](../../monitor/logging-configuration/kibana-logging.md#logging-appenders) to apply to `root`.
-$$$logging-root-level$$$ `logging.root.level` 
+$$$logging-root-level$$$ `logging.root.level` 
: Level at which a log record should be logged. Supported levels are: *all*, *fatal*, *error*, *warn*, *info*, *debug*, *trace*, *off*. Levels are ordered from *all* (highest) to *off* and a log record will be logged it its level is higher than or equal to the level of its logger, otherwise the log record is ignored. Use this value to [change the overall log level](../../monitor/logging-configuration/kibana-log-settings-examples.md#change-overall-log-level). **Default: `info`**.
::::{tip}
@@ -225,25 +225,25 @@ $$$logging-loggers$$$ `logging.loggers[]`
`logging.appenders[]`
: [Appenders](../../monitor/logging-configuration/kibana-logging.md#logging-appenders) define how and where log messages are displayed (eg. **stdout** or console) and stored (eg. file on the disk).
-`map.includeElasticMapsService` 
+`map.includeElasticMapsService` 
: Set to `false` to disable connections to Elastic Maps Service. When `includeElasticMapsService` is turned off, only tile layer configured by [`map.tilemap.url`](#tilemap-url) is available in [Maps](../../../explore-analyze/visualize/maps.md). **Default: `true`**
`map.emsUrl`
: Specifies the URL of a self hosted [{{hosted-ems}}](../../../explore-analyze/visualize/maps/maps-connect-to-ems.md#elastic-maps-server)
-$$$tilemap-settings$$$ `map.tilemap.options.attribution` 
+$$$tilemap-settings$$$ `map.tilemap.options.attribution` 
: The map attribution string. Provide attributions in markdown and use `\|` to delimit attributions, for example: `"[attribution 1](https://www.attribution1)\|[attribution 2](https://www.attribution2)"`. **Default: `"© [Elastic Maps Service](https://www.elastic.co/elastic-maps-service)"`**
-$$$tilemap-max-zoom$$$ `map.tilemap.options.maxZoom` 
+$$$tilemap-max-zoom$$$ `map.tilemap.options.maxZoom` 
: The maximum zoom level. **Default: `10`**
-$$$tilemap-min-zoom$$$ `map.tilemap.options.minZoom` 
+$$$tilemap-min-zoom$$$ `map.tilemap.options.minZoom` 
: The minimum zoom level. **Default: `1`**
-$$$tilemap-subdomains$$$ `map.tilemap.options.subdomains` 
+$$$tilemap-subdomains$$$ `map.tilemap.options.subdomains` 
: An array of subdomains used by the tile service. Specify the position of the subdomain the URL with the token `{s}`.
-$$$tilemap-url$$$ `map.tilemap.url` 
+$$$tilemap-url$$$ `map.tilemap.url` 
: The URL to the service that {{kib}} uses as the default basemap in [maps](../../../explore-analyze/visualize/maps.md) and [vega maps](../../../explore-analyze/visualize/custom-visualizations-with-vega.md#vega-with-a-map). By default, {{kib}} sets a basemap from the [Elastic Maps Service](../../../explore-analyze/visualize/maps/maps-connect-to-ems.md), but users can point to their own Tile Map Service. For example: `"https://tiles.elastic.co/v2/default/{{z}}/{x}/{{y}}.png?elastic_tile_service_tos=agree&my_app_name=kibana"`
`migrations.batchSize`
@@ -330,7 +330,7 @@ $$$server-securityResponseHeaders-disableEmbedding$$$`server.securityResponseHea
$$$server-securityResponseHeaders-crossOriginOpenerPolicy$$$ `server.securityResponseHeaders.crossOriginOpenerPolicy`
: Controls whether the [`Cross-Origin-Opener-Policy`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy) header is used in all responses to the client from the {{kib}} server, and specifies what value is used. Allowed values are `unsafe-none`, `same-origin-allow-popups`, `same-origin`, or `null`. To disable, set to `null`. **Default:** `"same-origin"`
-`server.customResponseHeaders` 
+`server.customResponseHeaders` 
: Header names and values to send on all responses to the client from the {{kib}} server. **Default: `{}`**
$$$server-shutdownTimeout$$$ `server.shutdownTimeout`
@@ -480,7 +480,7 @@ $$$settings-telemetry-optIn$$$ `telemetry.optIn`
This setting can be changed at any time in [Advanced Settings](asciidocalypse://docs/kibana/docs/reference/advanced-settings.md). To prevent users from changing it, set [`telemetry.allowChangingOptInStatus`](#telemetry-allowChangingOptInStatus) to `false`. **Default: `true`**
-`vis_type_vega.enableExternalUrls` 
+`vis_type_vega.enableExternalUrls` 
: Set this value to true to allow Vega to use any URL to access external data sources and images. When false, Vega can only get data from {{es}}. **Default: `false`**
`xpack.ccr.ui.enabled`
@@ -523,5 +523,5 @@ $$$settings-explore-data-in-chart$$$ `xpack.discoverEnhanced.actions.exploreData
`xpack.upgrade_assistant.ui.enabled`
: Set this value to false to disable the Upgrade Assistant UI. **Default: true**
-`i18n.locale` 
+`i18n.locale` 
: Set this value to change the {{kib}} interface language. Valid locales are: `en`, `zh-CN`, `ja-JP`, `fr-FR`. **Default: `en`**
\ No newline at end of file
diff --git a/deploy-manage/license/manage-your-license-in-ece.md b/deploy-manage/license/manage-your-license-in-ece.md
index c15f33770..e222bc733 100644
--- a/deploy-manage/license/manage-your-license-in-ece.md
+++ b/deploy-manage/license/manage-your-license-in-ece.md
@@ -27,7 +27,7 @@ If you have a license from 2018 or earlier, you might receive a warning that you
Elastic Cloud Enterprise Licenses contains two types of licenses - the actual license for Elastic Cloud Enterprise that is validated to enable Elastic Cloud Enterprise features and the *cluster licenses*, which Elastic Cloud Enterprise installs into the individual clusters.
-Elastic Cloud Enterprise installs those cluster licenses with an approximately 3 month window, and updates the cluster licenses automatically as they get within a month of expiration. This is the same system that we use for our Elasticsearch Service on Cloud.
+Elastic Cloud Enterprise installs those cluster licenses with an approximately 3 month window, and updates the cluster licenses automatically as they get within a month of expiration.
When the Elastic Cloud Enterprise license expires, and consequently the cluster license that’s currently installed for all managed clusters since it has the same expiration date, the following takes place:
diff --git a/deploy-manage/maintenance/start-stop-services/restart-cloud-hosted-deployment.md b/deploy-manage/maintenance/start-stop-services/restart-cloud-hosted-deployment.md
index 33ded47d5..a7e11e6cb 100644
--- a/deploy-manage/maintenance/start-stop-services/restart-cloud-hosted-deployment.md
+++ b/deploy-manage/maintenance/start-stop-services/restart-cloud-hosted-deployment.md
@@ -7,9 +7,9 @@ applies_to:
ess:
---
-# Restart a Cloud Hosted deployment
+# Restart an {{ech}} deployment
-You can restart your {{es}} deployment through the deployment overview UI or by using an API.
+You can restart your deployment through the deployment overview UI or by using an API.
## Restart your deployment through the deployment overview [ec-restart-deployment]
@@ -19,7 +19,7 @@ On the deployment overview, from the **Action** drop-down menu select **Restart
You can choose to restart without downtime or you can restart all nodes simultaneously.
-Note that if you are looking to restart {{es}} to clear out [deployment activity](../../../deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) plan failures, you may instead run a [no-op plan](../../../troubleshoot/monitoring/deployment-health-warnings.md) to re-synchronize the last successful configuration settings between Elasticsearch Service and {{es}}.
+Note that if you are looking to restart {{es}} to clear out [deployment activity](../../../deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) plan failures, you may instead run a [no-op plan](../../../troubleshoot/monitoring/deployment-health-warnings.md) to re-synchronize the last successful configuration settings between {{ech}} and {{es}}.
## Restart an {{es}} resource by using an API [ec_restart_an_elasticsearch_resource]
@@ -37,9 +37,9 @@ curl -XPOST \
`REF_ID` Name given to each resource type in the attribute `ref_id`. `main-elasticsearch` in the preceding example
-## Shut down a Elasticsearch Service deployment [ec_shut_down_a_elasticsearch_service_deployment]
+## Shut down an {{ech}} deployment [ec_shut_down_a_elasticsearch_service_deployment]
-Shut down a Elasticsearch Service deployment by calling the following API request:
+Shut down an {{ech}} deployment by calling the following API request:
```sh
curl -XPOST \
diff --git a/deploy-manage/monitor/logging-configuration/enabling-audit-logs.md b/deploy-manage/monitor/logging-configuration/enabling-audit-logs.md
index 51c948e32..31e889c6e 100644
--- a/deploy-manage/monitor/logging-configuration/enabling-audit-logs.md
+++ b/deploy-manage/monitor/logging-configuration/enabling-audit-logs.md
@@ -62,7 +62,7 @@ To enable audit logging in an {{ech}} deployment:
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.
+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.
3. From your deployment menu, go to the **Edit** page.
diff --git a/deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md b/deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md
index 6628fcd3e..a1aa885e4 100644
--- a/deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md
+++ b/deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md
@@ -14,7 +14,7 @@ applies_to:
Monitoring data is stored in data streams or indices in {{es}}. The default data stream or index settings may not work for your situation. For example, you might want to change index lifecycle management (ILM) settings, add custom mappings, or change the number of shards and replicas. The steps to change these settings depend on the monitoring method:
* [Configuring data streams created by {{agent}}](config-monitoring-data-streams-elastic-agent.md)
-* [Configuring data streams created by {{metricbeat}} 8](config-monitoring-data-streams-metricbeat-8.md) (the default for version 8 {{ess}} deployments on {{ecloud}})
+* [Configuring data streams created by {{metricbeat}} 8](config-monitoring-data-streams-metricbeat-8.md) (the default for version 8 {{ech}} deployments on {{ecloud}})
* [Configuring indices created by {{metricbeat}} 7 or internal collection](config-monitoring-indices-metricbeat-7-internal-collection.md)
::::{important}
diff --git a/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md b/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md
index 235a932ea..41fd8ae84 100644
--- a/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md
+++ b/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md
@@ -10,7 +10,7 @@ applies_to:
# JVM memory pressure indicator [ec-memory-pressure]
-In addition to the more detailed [cluster performance metrics](../stack-monitoring.md), the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) also includes a JVM memory pressure indicator for each node in your cluster. This indicator can help you to determine when you need to upgrade to a larger cluster.
+In addition to the more detailed [cluster performance metrics](../stack-monitoring.md), the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) also includes a JVM memory pressure indicator for each node in your cluster. This indicator can help you to determine when you need to upgrade to a larger cluster.
The percentage number used in the JVM memory pressure indicator is actually the fill rate of the old generation pool. For a detailed explanation of why this metric is used, check [Understanding Memory Pressure](https://www.elastic.co/blog/found-understanding-memory-pressure-indicator/).
diff --git a/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md b/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md
index ee856c031..373f45c53 100644
--- a/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md
+++ b/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md
@@ -9,16 +9,16 @@ applies_to:
# Access performance metrics [ec-saas-metrics-accessing]
-Cluster performance metrics are available directly in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of Elasticsearch Service-specific performance metrics.
+Cluster performance metrics are available directly in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of {{ech}}-specific performance metrics.
For advanced views or production monitoring, [enable logging and monitoring](../stack-monitoring/elastic-cloud-stack-monitoring.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period.
To access cluster performance metrics:
-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. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention.
+ 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. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention.
3. From your deployment menu, go to the **Performance** page.
@@ -31,7 +31,7 @@ The following metrics are available:
:alt: Graph showing CPU usage
:::
-Shows the maximum usage of the CPU resources assigned to your Elasticsearch cluster, as a percentage. CPU resources are relative to the size of your cluster, so that a cluster with 32GB of RAM gets assigned twice as many CPU resources as a cluster with 16GB of RAM. All clusters are guaranteed their share of CPU resources, as Elasticsearch Service infrastructure does not overcommit any resources. CPU credits permit boosting the performance of smaller clusters temporarily, so that CPU usage can exceed 100%.
+Shows the maximum usage of the CPU resources assigned to your Elasticsearch cluster, as a percentage. CPU resources are relative to the size of your cluster, so that a cluster with 32GB of RAM gets assigned twice as many CPU resources as a cluster with 16GB of RAM. All clusters are guaranteed their share of CPU resources, as {{ech}} infrastructure does not overcommit any resources. CPU credits permit boosting the performance of smaller clusters temporarily, so that CPU usage can exceed 100%.
::::{tip}
This chart reports the maximum CPU values over the sampling period. [Logs and Metrics](../stack-monitoring/elastic-cloud-stack-monitoring.md) ingested into [Stack Monitoring](visualizing-monitoring-data.md)'s "CPU Usage" instead reflects the average CPU over the sampling period. Therefore, you should not expect the two graphs to look exactly the same. When investigating [CPU-related performance issues](../../../troubleshoot/monitoring/performance.md), you should default to [Stack Monitoring](visualizing-monitoring-data.md).
@@ -97,7 +97,7 @@ Indicates the overhead involved in JVM garbage collection to reclaim memory.
Performance correlates directly with resources assigned to your cluster, and many of these metrics will show some sort of correlation with each other when you are trying to determine the cause of a performance issue. Take a look at some of the scenarios included in this section to learn how you can determine the cause of performance issues.
-It is not uncommon for performance issues on Elasticsearch Service to be caused by an undersized cluster that cannot cope with the workload it is being asked to handle. If your cluster performance metrics often shows high CPU usage or excessive memory pressure, consider increasing the size of your cluster soon to improve performance. This is especially true for clusters that regularly reach 100% of CPU usage or that suffer out-of-memory failures; it is better to resize your cluster early when it is not yet maxed out than to have to resize a cluster that is already overwhelmed. [Changing the configuration of your cluster](../../deploy/elastic-cloud/configure.md) may add some overhead if data needs to be migrated to the new nodes, which can increase the load on a cluster further and delay configuration changes.
+It is not uncommon for performance issues on {{ech}} to be caused by an undersized cluster that cannot cope with the workload it is being asked to handle. If your cluster performance metrics often shows high CPU usage or excessive memory pressure, consider increasing the size of your cluster soon to improve performance. This is especially true for clusters that regularly reach 100% of CPU usage or that suffer out-of-memory failures; it is better to resize your cluster early when it is not yet maxed out than to have to resize a cluster that is already overwhelmed. [Changing the configuration of your cluster](../../deploy/elastic-cloud/configure.md) may add some overhead if data needs to be migrated to the new nodes, which can increase the load on a cluster further and delay configuration changes.
To help diagnose high CPU usage you can also use the Elasticsearch [nodes hot threads API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-hot-threads), which identifies the threads on each node that have the highest CPU usage or that have been executing for a longer than normal period of time.
@@ -128,7 +128,7 @@ Cluster performance metrics are shown per node and are color-coded to indicate w
## Cluster restarts after out-of-memory failures [ec_cluster_restarts_after_out_of_memory_failures]
-For clusters that suffer out-of-memory failures, it can be difficult to determine whether the clusters are in a completely healthy state afterwards. For this reason, Elasticsearch Service automatically reboots clusters that suffer out-of-memory failures.
+For clusters that suffer out-of-memory failures, it can be difficult to determine whether the clusters are in a completely healthy state afterwards. For this reason, {{ech}} automatically reboots clusters that suffer out-of-memory failures.
You will receive an email notification to let you know that a restart occurred. For repeated alerts, the emails are aggregated so that you do not receive an excessive number of notifications. Either [resizing your cluster to reduce memory pressure](../../deploy/elastic-cloud/ec-customize-deployment-components.md#ec-cluster-size) or reducing the workload that a cluster is being asked to handle can help avoid these cluster restarts.
diff --git a/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md b/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md
index 074166ea0..aa41afaed 100644
--- a/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md
+++ b/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md
@@ -35,12 +35,12 @@ For example: An instance with 4 GB of RAM, can at most accumulate four hours wor
If you observe declining performance on a smaller instance over time, you might have depleted your vCPU credits. In this case, increase the size of your cluster to handle the workload with consistent performance.
-For more information, check [Elasticsearch Service default provider instance configurations](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/hardware.md#ec-getting-started-configurations).
+For more information, check [{{ech}} default provider instance configurations](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/hardware.md#ec-getting-started-configurations).
## Where to check vCPU credits status? [ec_where_to_check_vcpu_credits_status]
-You can check the **Monitoring > Performance > CPU Credits** section of the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), and find the related metrics:
+You can check the **Monitoring > Performance > CPU Credits** section of the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), and find the related metrics:
:::{image} ../../../images/cloud-metrics-credits.png
:alt: CPU usage versus CPU credits over time
diff --git a/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md
index a00f5886d..964a0bf76 100644
--- a/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md
+++ b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md
@@ -124,7 +124,7 @@ Elastic Cloud Enterprise manages the installation and configuration of the monit
To enable monitoring on your deployment:
1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
@@ -155,7 +155,7 @@ Enabling logs and monitoring requires some extra resource on a deployment. For p
With monitoring enabled for your deployment, you can access the [logs](https://www.elastic.co/guide/en/kibana/current/observability.html) and [stack monitoring](../monitoring-data/visualizing-monitoring-data.md) through Kibana.
1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
@@ -223,7 +223,7 @@ With logging and monitoring enabled for a deployment, metrics are collected for
Audit logs are useful for tracking security events on your {{es}} and/or {{kib}} clusters. To enable {{es}} audit logs on your deployment:
1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/deploy-manage/production-guidance.md b/deploy-manage/production-guidance.md
index 435f6ed3b..322e3f7d9 100644
--- a/deploy-manage/production-guidance.md
+++ b/deploy-manage/production-guidance.md
@@ -10,7 +10,7 @@ This section provides some best practices for managing your data to help you set
## Plan your data structure, availability, and formatting [ec_plan_your_data_structure_availability_and_formatting]
-* Build a [data architecture](/manage-data/lifecycle/data-tiers.md) that best fits your needs. Your Elasticsearch Service deployment comes with default hot tier {{es}} nodes that store your most frequently accessed data. Based on your own access and retention policies, you can add warm, cold, frozen data tiers, and automated deletion of old data.
+* Build a [data architecture](/manage-data/lifecycle/data-tiers.md) that best fits your needs. Your {{ech}} deployment comes with default hot tier {{es}} nodes that store your most frequently accessed data. Based on your own access and retention policies, you can add warm, cold, frozen data tiers, and automated deletion of old data.
* Make your data [highly available](/deploy-manage/tools.md) for production environments or otherwise critical data stores, and take regular [backup snapshots](tools/snapshot-and-restore.md).
* Normalize event data to better analyze, visualize, and correlate your events by adopting the [Elastic Common Schema](asciidocalypse://docs/ecs/docs/reference/ecs-getting-started.md) (ECS). Elastic integrations use ECS out-of-the-box. If you are writing your own integrations, ECS is recommended.
diff --git a/deploy-manage/reference-architectures/hotfrozen-high-availability.md b/deploy-manage/reference-architectures/hotfrozen-high-availability.md
index b97eab141..e4883a2cd 100644
--- a/deploy-manage/reference-architectures/hotfrozen-high-availability.md
+++ b/deploy-manage/reference-architectures/hotfrozen-high-availability.md
@@ -49,7 +49,7 @@ We use an Availability Zone (AZ) concept in the architecture above. When running
The diagram illustrates an {{es}} cluster deployed across 3 availability zones (AZ). For production we recommend a minimum of 2 availability zones and 3 availability zones for mission critical applications. See [Plan for production](/deploy-manage/production-guidance/plan-for-production-elastic-cloud.md) for more details. A cluster that is running in {{ecloud}} that has data nodes in only two AZs will create a third master-eligible node in a third AZ. High availability cannot be achieved without three zones for any distributed computing technology.
-The number of data nodes shown for each tier (hot and frozen) is illustrative and would be scaled up depending on ingest volume and retention period. Hot nodes contain both primary and replica shards. By default, primary and replica shards are always guaranteed to be in different availability zones in {{ess}}, but when self-deploying [shard allocation awareness](../distributed-architecture/shard-allocation-relocation-recovery/shard-allocation-awareness.md) would need to be configured. Frozen nodes act as a large high-speed cache and retrieve data from the snapshot store as needed.
+The number of data nodes shown for each tier (hot and frozen) is illustrative and would be scaled up depending on ingest volume and retention period. Hot nodes contain both primary and replica shards. By default, primary and replica shards are always guaranteed to be in different availability zones in {{ech}}, but when self-deploying [shard allocation awareness](../distributed-architecture/shard-allocation-relocation-recovery/shard-allocation-awareness.md) would need to be configured. Frozen nodes act as a large high-speed cache and retrieve data from the snapshot store as needed.
Machine learning nodes are optional but highly recommended for large scale time series use cases since the amount of data quickly becomes too difficult to analyze. Applying techniques such as machine learning based anomaly detection or Search AI with large language models helps to dramatically speed up problem identification and resolution.
@@ -93,7 +93,7 @@ This table shows our specific recommendations for nodes in a Hot/Frozen architec
**Kibana:**
-* If self-deploying outside of {{ess}}, ensure that {{kib}} is configured for [high availability](/deploy-manage/production-guidance/kibana-in-production-environments.md#high-availability).
+* If self-deploying outside of {{ech}}, ensure that {{kib}} is configured for [high availability](/deploy-manage/production-guidance/kibana-in-production-environments.md#high-availability).
## How many nodes of each do you need? [hot-frozen-estimate]
@@ -111,5 +111,5 @@ You can [contact us](https://www.elastic.co/contact) for an estimate and recomme
## Resources and references [hot-frozen-resources]
* [{{es}} - Get ready for production](/deploy-manage/production-guidance/getting-ready-for-production-elasticsearch.md)
-* [{{ess}} - Preparing a deployment for production](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md)
+* [{{ech}} - Preparing a deployment for production](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md)
* [Size your shards](/deploy-manage/production-guidance/optimize-performance/size-shards.md)
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
index 19ad49c5f..05def9ed7 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md
@@ -55,9 +55,9 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo
::::{dropdown} The CA is public
1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
+2. On the home page, find your hosted deployment 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.
+ 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.
3. From the deployment menu, select **Security**.
4. Locate **Remote connections** and select **Add an API key**.
@@ -83,9 +83,9 @@ If you later need to update the remote connection with different permissions, yo
::::{dropdown} The CA is private
1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
+2. On the home page, find your hosted deployment 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.
+ 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.
3. Access the **Security** page of the deployment.
4. Select **Remote Connections > Add trusted environment** and choose **{{ece}}**. Then click **Next**.
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md
index 9604bf2ae..de596ba48 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md
@@ -51,9 +51,9 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear
The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
+2. On the home page, find your hosted deployment 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.
+ 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.
3. From the deployment menu, select **Security**.
4. Locate **Remote connections** and select **Add an API key**.
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
index 8f34234a0..cf08bc919 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
@@ -51,9 +51,9 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear
The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
+2. On the home page, find your hosted deployment 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.
+ 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.
3. From the deployment menu, select **Security**.
4. Locate **Remote connections** and select **Add an API key**.
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md
index 2f90496dc..0e1f93873 100644
--- a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md
+++ b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md
@@ -55,9 +55,9 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo
::::{dropdown} The CA is public
1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
+2. On the home page, find your hosted deployment 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.
+ 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.
3. From the deployment menu, select **Security**.
4. Locate **Remote connections** and select **Add an API key**.
@@ -83,9 +83,9 @@ If you later need to update the remote connection with different permissions, yo
::::{dropdown} The CA is private
1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
+2. On the home page, find your hosted deployment 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.
+ 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.
3. Access the **Security** page of the deployment.
4. Select **Remote Connections > Add trusted environment** and choose **Self-managed**. Then click **Next**.
diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md
index 149e21b28..c400226c0 100644
--- a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md
+++ b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md
@@ -51,7 +51,7 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear
The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md
index b96658fcb..9cfdc15a7 100644
--- a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md
+++ b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md
@@ -52,7 +52,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo
::::{dropdown} The CA is public
1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
@@ -80,7 +80,7 @@ If you later need to update the remote connection with different permissions, yo
::::{dropdown} The CA is private
1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md
index e68977211..fab812ee3 100644
--- a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md
+++ b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md
@@ -50,7 +50,7 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear
The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md
index 7cbedacc1..88b107c9e 100644
--- a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md
+++ b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md
@@ -54,7 +54,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo
::::{dropdown} The CA is public
1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
@@ -82,7 +82,7 @@ If you later need to update the remote connection with different permissions, yo
::::{dropdown} The CA is private
1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md b/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md
index 5f3618a82..d34543c75 100644
--- a/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md
+++ b/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md
@@ -5,7 +5,7 @@ mapped_pages:
# Claim traffic filter link ID ownership through the API [ec-claim-traffic-filter-link-id-through-the-api]
-This example demonstrates how to use the Elasticsearch Service RESTful API to claim different types of private link ID (AWS PrivateLink, Azure Private Link, and GCP Private Service Connect). We cover the following examples:
+This example demonstrates how to use the {{ecloud}} RESTful API to claim different types of private link ID (AWS PrivateLink, Azure Private Link, and GCP Private Service Connect). We cover the following examples:
* [Claim a traffic filter link id](#ec-claim-a-traffic-filter-link-id)
diff --git a/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md b/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md
index cdb96584c..b7030b9be 100644
--- a/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md
+++ b/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md
@@ -158,11 +158,11 @@ Provide your key identifier without the key version identifier so Elastic Cloud
:::::::{tab-set}
::::::{tab-item} AWS
-1. Create a new deployment. You can do it from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), or from the API:
+1. Create a new deployment. You can do it from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), or from the API:
- * from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body):
+ * from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body):
- * Select **Create deployment** from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
+ * Select **Create deployment** from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
* In the **Settings**, set the **Cloud provider** to **Amazon Web Services** and select a region.
* Expand the **Advanced settings** and turn on **Use a customer-managed encryption key**. An additional field appears to let you specify the ARN of the AWS KMS key or key alias you will use to encrypt your new deployment.
* Configure the rest of your deployment to your convenience, and select **Create deployment**.
@@ -207,7 +207,7 @@ To create a new deployment with a customer-managed key in Azure, you need to per
1. In Elastic Cloud, retrieve the Azure application ID:
- * Select **Create deployment** from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
+ * Select **Create deployment** from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
* In the **Settings**, set the **Cloud provider** to **Azure** and select a region.
* Expand the **Advanced settings** and turn on **Use a customer-managed encryption key**.
* Copy the **Azure application ID**.
@@ -231,11 +231,11 @@ To create a new deployment with a customer-managed key in Azure, you need to per
**Step 2: Create your deployment**
-After you have created the service principal and granted it the necessary permissions, you can finish creating your deployment. You can do so from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), or from the API.
+After you have created the service principal and granted it the necessary permissions, you can finish creating your deployment. You can do so from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), or from the API.
-* Using the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body):
+* Using the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body):
- * Select **Create deployment** from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
+ * Select **Create deployment** from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
* In the **Settings**, set the **Cloud provider** to **Azure** and select a region.
* Expand the **Advanced settings** and turn on **Use a customer-managed encryption key**.
* Enter the Azure key identifier for the RSA key that you created.
@@ -284,7 +284,7 @@ Elastic Cloud uses two service principals to encrypt and decrypt data using your
1. In Elastic Cloud, retrieve the email addresses for the service principals that will be used by Elastic:
- * Select **Create deployment** from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
+ * Select **Create deployment** from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
* In the **Settings**, set the **Cloud provider** to **Google Cloud** and select a region.
* Expand the **Advanced settings** and turn on **Use a customer-managed encryption key**.
* Note the **Elastic service account** and **Google Cloud Platform storage service agent** email addresses.
@@ -310,11 +310,11 @@ The user performing this action needs to belong to the **Owner** or **Cloud KMS
**Step 2: Create your deployment**
-After you have granted the Elastic principals the necessary roles, you can finish creating your deployment. You can do so from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), or from the API.
+After you have granted the Elastic principals the necessary roles, you can finish creating your deployment. You can do so from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), or from the API.
-* Using the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body):
+* Using the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body):
- * Select **Create deployment** from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
+ * Select **Create deployment** from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) home page.
* In the **Settings**, set the **Cloud provider** to **Google Cloud** and select a region.
* Expand the **Advanced settings** and turn on **Use a customer-managed encryption key**.
* Enter the resource ID for the key that you created.
diff --git a/deploy-manage/tools/cross-cluster-replication/set-up-cross-cluster-replication.md b/deploy-manage/tools/cross-cluster-replication/set-up-cross-cluster-replication.md
index ff6a08544..90df231cf 100644
--- a/deploy-manage/tools/cross-cluster-replication/set-up-cross-cluster-replication.md
+++ b/deploy-manage/tools/cross-cluster-replication/set-up-cross-cluster-replication.md
@@ -30,7 +30,7 @@ In this guide, you’ll learn how to:
You can manually create follower indices to replicate specific indices on a remote cluster, or configure auto-follow patterns to replicate rolling time series indices.
::::{tip}
-If you want to replicate data across clusters in the cloud, you can [configure remote clusters on {{ess}}](/deploy-manage/remote-clusters/ec-enable-ccs.md). Then, you can [search across clusters](../../../solutions/search/cross-cluster-search.md) and set up {{ccr}}.
+If you want to replicate data across clusters in the cloud, you can [configure remote clusters on {{{ecloud}}](/deploy-manage/remote-clusters/ec-enable-ccs.md). Then, you can [search across clusters](../../../solutions/search/cross-cluster-search.md) and set up {{ccr}}.
::::
diff --git a/deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md b/deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md
index cd55d8eee..aba169d80 100644
--- a/deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md
+++ b/deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md
@@ -46,9 +46,9 @@ For a full list of settings that are supported for your S3 bucket, refer to [S3
## Store your secrets in the keystore [ec-snapshot-secrets-keystore]
-You can use the Elasticsearch Service Keystore to store the credentials to access your AWS account.
+You can use the {{es}} keystore to store the credentials to access your AWS account.
-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. Navigate to the **Security** page of the deployment you wish to configure.
3. Locate **Elasticsearch keystore** and select **Add settings**.
4. With **Type** set to **Single string**, add the following keys and their values:
diff --git a/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md b/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md
index d8ceb630e..628151004 100644
--- a/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md
+++ b/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md
@@ -21,7 +21,7 @@ For deployments with **Elastic Stack version 7.17 and earlier**, you’ll need t
1. Refer to [Azure Repository Plugin](https://www.elastic.co/guide/en/elasticsearch/plugins/7.17/repository-azure.html) to download the version of the plugin that matches your Elastic Stack version.
2. Upload the plugin to your deployment:
- 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. Open the **Features > Extensions** page and select **Upload extension**.
3. Specify the plugin name (`repository-azure`) and the version.
4. Select **An installable plugin (Compiled, no source code)**.
@@ -36,7 +36,7 @@ For deployments with **Elastic Stack version 7.17 and earlier**, you’ll need t
Create an entry for the Azure client in the Elasticsearch keystore:
-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. Navigate to the **Security** page of the deployment you wish to configure.
3. Locate **Elasticsearch keystore** and select **Add settings**.
4. With **Type** set to **Single string**, add the following keys and their values:
diff --git a/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md b/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md
index 6bb8dc372..d459631d0 100644
--- a/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md
+++ b/deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md
@@ -34,7 +34,7 @@ For deployments with **Elastic Stack version 7.17 and earlier**, you’ll need t
1. Refer to [Google Cloud Storage Repository Plugin](https://www.elastic.co/guide/en/elasticsearch/plugins/7.17/repository-gcs.html) to download the version of the plugin that matches your Elastic Stack version.
2. Upload the plugin to your deployment:
- 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. Open the **Features > Extensions** page and select **Upload extension**.
3. Specify the plugin name (`repository-gcs`) and the version.
4. Select **An installable plugin (Compiled, no source code)**.
@@ -49,7 +49,7 @@ For deployments with **Elastic Stack version 7.17 and earlier**, you’ll need t
Create an entry for the GCS client in the Elasticsearch keystore:
-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. Navigate to the **Security** page of the deployment you wish to configure.
3. Locate **Elasticsearch keystore** and select **Add settings**.
4. Enter the **Setting name** `gcs.client.secondary.credentials_file`.
diff --git a/deploy-manage/upgrade/prepare-to-upgrade/index-compatibility.md b/deploy-manage/upgrade/prepare-to-upgrade/index-compatibility.md
index 610dd15a6..cdeba0875 100644
--- a/deploy-manage/upgrade/prepare-to-upgrade/index-compatibility.md
+++ b/deploy-manage/upgrade/prepare-to-upgrade/index-compatibility.md
@@ -36,4 +36,4 @@ To upgrade to 9.0.0-beta1 from 7.16 or an earlier version, **you must first upgr
{{es}} 8.0+ requires Java 17 or later. {{es}} 8.13+ has been tested with [Bouncy Castle](https://www.bouncycastle.org/java.md)'s Java 17 [certified](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4616) FIPS implementation and is the recommended Java security provider when running {{es}} in FIPS 140-2 mode. Note - {{es}} does not ship with a FIPS certified security provider and requires explicit installation and configuration.
-Alternatively, consider using {{ess}} in the [FedRAMP-certified GovCloud region](https://www.elastic.co/industries/public-sector/fedramp).
+Alternatively, consider using {{ech}} in the [FedRAMP-certified GovCloud region](https://www.elastic.co/industries/public-sector/fedramp).
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md b/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md
index 3d5db2930..84ce3f85c 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md
@@ -29,9 +29,9 @@ The `elastic` user should be not be used unless you have no other way to access
To reset the password:
1. Log in to the Elastic Cloud Console.
-2. Find your deployment on the home page and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments.
+2. Find your deployment on the home page 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.
+ 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.
3. From your deployment menu, go to **Security**.
4. Select **Reset password**.
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md b/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md
index 70b0a8491..0bf9ef297 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md
@@ -330,7 +330,7 @@ For more information about OpenID connect in Okta, refer to [Okta OAuth 2.0 docu
Where:
* `YOUR_CLIENT_ID` is the Client ID that you set up in the previous steps.
- * `KIBANA_ENDPOINT_URL` is your Kibana endpoint, available from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+ * `KIBANA_ENDPOINT_URL` is your Kibana endpoint, available from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
* `YOUR_OKTA_DOMAIN` is the URL of your Okta domain shown on your Okta dashboard.
* `YOUR_DOMAIN` and `TLD` in the `claim_patterns.principal` regular expression are your organization email domain and top level domain.
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/operator-privileges-for-snapshot-restore.md b/deploy-manage/users-roles/cluster-or-deployment-auth/operator-privileges-for-snapshot-restore.md
index e10cba9fa..3378ca70d 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/operator-privileges-for-snapshot-restore.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/operator-privileges-for-snapshot-restore.md
@@ -15,7 +15,7 @@ This feature is designed for indirect use by {{ech}}, {{ece}}, and {{eck}}. Dire
::::
-Invoking [operator-only APIs](operator-only-functionality.md#operator-only-apis) or updating [operator-only dynamic cluster settings](operator-only-functionality.md#operator-only-dynamic-cluster-settings) typically results in changes in the cluster state. The cluster state can be included in a cluster [snapshot](../../tools/snapshot-and-restore.md). Snapshots are a great way to preserve the data of a cluster, which can later be restored to bootstrap a new cluster, perform migration, or disaster recovery, for example. In a traditional self-managed environment, the intention is for the restore process to copy the entire cluster state over when requested. However, in a more managed environment, such as [{{ess}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body), data that is associated with [operator-only functionality](operator-only-functionality.md) is explicitly managed by the infrastructure code.
+Invoking [operator-only APIs](operator-only-functionality.md#operator-only-apis) or updating [operator-only dynamic cluster settings](operator-only-functionality.md#operator-only-dynamic-cluster-settings) typically results in changes in the cluster state. The cluster state can be included in a cluster [snapshot](../../tools/snapshot-and-restore.md). Snapshots are a great way to preserve the data of a cluster, which can later be restored to bootstrap a new cluster, perform migration, or disaster recovery, for example. In a traditional self-managed environment, the intention is for the restore process to copy the entire cluster state over when requested. However, in a more managed environment, such as [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body), data that is associated with [operator-only functionality](operator-only-functionality.md) is explicitly managed by the infrastructure code.
Restoring snapshot data associated with operator-only functionality could be problematic because:
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/operator-privileges.md b/deploy-manage/users-roles/cluster-or-deployment-auth/operator-privileges.md
index c6c3b411e..1ea88cddb 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/operator-privileges.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/operator-privileges.md
@@ -14,7 +14,7 @@ applies_to:
This feature is designed for indirect use by {{ech}}, {{ece}}, and {{eck}}. Direct use is not supported.
::::
-With a typical {{es}} deployment, people who administer the cluster also operate the cluster at the infrastructure level. User authorization based on [role-based access control (RBAC)](user-roles.md) is effective and reliable for this environment. However, in more managed environments, such as [{{ess}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body), there is a distinction between the operator of the cluster infrastructure and the administrator of the cluster.
+With a typical {{es}} deployment, people who administer the cluster also operate the cluster at the infrastructure level. User authorization based on [role-based access control (RBAC)](user-roles.md) is effective and reliable for this environment. However, in more managed environments, such as [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body), there is a distinction between the operator of the cluster infrastructure and the administrator of the cluster.
Operator privileges limit some functionality to operator users *only*. Operator users are just regular {{es}} users with access to specific [operator-only functionality](operator-only-functionality.md). These privileges are not available to cluster administrators, even if they log in as a highly privileged user such as the `elastic` user or another user with the `superuser` role. By limiting system access, operator privileges enhance the {{es}} security model while safeguarding user capabilities.
diff --git a/docset.yml b/docset.yml
index 0f3befd59..bd70147d2 100644
--- a/docset.yml
+++ b/docset.yml
@@ -194,7 +194,6 @@ subs:
ess-trial: "https://cloud.elastic.co/registration?page=docs&placement=docs-body"
ess-product: "https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body"
ess-console: "https://cloud.elastic.co?page=docs&placement=docs-body"
- ess-console-name: "Elasticsearch Service Console"
ess-deployments: "https://cloud.elastic.co/deployments?page=docs&placement=docs-body"
ece-ref: "https://www.elastic.co/guide/en/cloud-enterprise/current"
eck-ref: "https://www.elastic.co/guide/en/cloud-on-k8s/current"
diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md b/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md
index 4e9f55def..b1c2d3305 100644
--- a/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md
+++ b/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md
@@ -43,7 +43,7 @@ docker run -it --rm docker.elastic.co/eland/eland \
--start
```
-You need to provide an administrator username and its password and replace the `$CLOUD_ID` with the ID of your Cloud deployment. This Cloud ID can be copied from the deployments page on your Cloud website.
+You need to provide an administrator username and its password and replace the `$CLOUD_ID` with the ID of your Cloud deployment. This Cloud ID can be copied from the **Deployments** page on your Cloud website.
Since the `--start` option is used at the end of the Eland import command, {{es}} deploys the model ready to use. If you have multiple models and want to select which model to deploy, you can use the **{{ml-app}} > Model Management** user interface in {{kib}} to manage the starting and stopping of models.
diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-text-emb-vector-search-example.md b/explore-analyze/machine-learning/nlp/ml-nlp-text-emb-vector-search-example.md
index 0fb5a4f1f..ca3609c6c 100644
--- a/explore-analyze/machine-learning/nlp/ml-nlp-text-emb-vector-search-example.md
+++ b/explore-analyze/machine-learning/nlp/ml-nlp-text-emb-vector-search-example.md
@@ -47,7 +47,7 @@ docker run -it --rm docker.elastic.co/eland/eland \
--start
```
-You need to provide an administrator username and password and replace the `$CLOUD_ID` with the ID of your Cloud deployment. This Cloud ID can be copied from the deployments page on your Cloud website.
+You need to provide an administrator username and password and replace the `$CLOUD_ID` with the ID of your Cloud deployment. This Cloud ID can be copied from the **Deployments** page on your Cloud website.
Since the `--start` option is used at the end of the Eland import command, {{es}} deploys the model ready to use. If you have multiple models and want to select which model to deploy, you can use the **{{ml-app}} > Model Management** user interface in {{kib}} to manage the starting and stopping of models.
diff --git a/get-started/introduction.md b/get-started/introduction.md
index 8fb48ab1e..e0241383b 100644
--- a/get-started/introduction.md
+++ b/get-started/introduction.md
@@ -55,10 +55,10 @@ The {{stack}} is used for a wide and growing range of use cases. Here are a few
- **Semantic search**: Understand the intent and contextual meaning behind search queries using tools like synonyms, dense vector embeddings, and learned sparse query-document expansion.
- **Hybrid search**: Combine full-text search with vector search using state-of-the-art ranking algorithms.
- **Build search experiences**: Add hybrid search capabilities to apps or websites, or build enterprise search engines over your organization’s internal data sources.
-- **Retrieval augmented generation (RAG)**: Use {{ess}} as a retrieval engine to supplement generative AI models with more relevant, up-to-date, or proprietary data for a range of use cases.
+- **Retrieval augmented generation (RAG)**: Use {{ecloud}} as a retrieval engine to supplement generative AI models with more relevant, up-to-date, or proprietary data for a range of use cases.
- **Geospatial search**: Search for locations and calculate spatial relationships using geospatial queries.
-This is just a sample of search, observability, and security use cases enabled by {{ess}}. Refer to Elastic [customer success stories](https://www.elastic.co/customers/success-stories) for concrete examples across a range of industries.
+This is just a sample of search, observability, and security use cases enabled by {{ecloud}}. Refer to Elastic [customer success stories](https://www.elastic.co/customers/success-stories) for concrete examples across a range of industries.
% TODO: cleanup these links, consolidate with Explore and analyze
diff --git a/manage-data/ingest/ingest-reference-architectures/ls-networkbridge.md b/manage-data/ingest/ingest-reference-architectures/ls-networkbridge.md
index ea898d854..0f7bc72ea 100644
--- a/manage-data/ingest/ingest-reference-architectures/ls-networkbridge.md
+++ b/manage-data/ingest/ingest-reference-architectures/ls-networkbridge.md
@@ -16,7 +16,7 @@ Use when
: Agents have network restrictions for connecting to {{es}} on {{stack}} deployed outside of the agent network
Example
-: You can send data from multiple {{agent}}s through your demilitarized zone (DMZ) to {{ls}}, and then use {{ls}} as a proxy through your firewall to {{ess}}. This approach helps reduce the number of firewall exceptions needed to forward data from large numbers of {{agent}}s.
+: You can send data from multiple {{agent}}s through your demilitarized zone (DMZ) to {{ls}}, and then use {{ls}} as a proxy through your firewall to {{ecloud}}. This approach helps reduce the number of firewall exceptions needed to forward data from large numbers of {{agent}}s.
## Resources [ls-networkbridge-resources]
diff --git a/manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md b/manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md
index 359c7e363..081af2985 100644
--- a/manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md
+++ b/manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md
@@ -40,7 +40,7 @@ $$$ece-db-logstash-pipeline$$$
$$$ece-db-logstash-prerequisites$$$
-This guide explains how to ingest data from a relational database into {{ess}} through [{{ls}}](asciidocalypse://docs/logstash/docs/reference/index.md), using the Logstash [JDBC input plugin](asciidocalypse://docs/logstash/docs/reference/plugins-inputs-jdbc.md). It demonstrates how Logstash can be used to efficiently copy records and to receive updates from a relational database, and then send them into {{es}} in an {{ech}} or {{ece}} deployment.
+This guide explains how to ingest data from a relational database into {{ecloud}} through [{{ls}}](asciidocalypse://docs/logstash/docs/reference/index.md), using the Logstash [JDBC input plugin](asciidocalypse://docs/logstash/docs/reference/plugins-inputs-jdbc.md). It demonstrates how Logstash can be used to efficiently copy records and to receive updates from a relational database, and then send them into {{es}} in an {{ech}} or {{ece}} deployment.
The code and methods presented here have been tested with MySQL. They should work with other relational databases.
@@ -98,7 +98,7 @@ The Logstash JDBC input plugin does not include any database connection drivers.
## Prepare a source MySQL database [ec-db-logstash-database]
-Let’s look at a simple database from which you’ll import data and send it to a {{ech}} or {{ece}} deployment. This example uses a MySQL database with timestamped records. The timestamps enable you to determine easily what’s changed in the database since the most recent data transfer.
+Let’s look at a simple database from which you’ll import data and send it to an {{ech}} or {{ece}} deployment. This example uses a MySQL database with timestamped records. The timestamps enable you to determine easily what’s changed in the database since the most recent data transfer.
### Consider the database structure and design [ec-db-logstash-database-structure]
diff --git a/manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-python-application-using-filebeat.md b/manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-python-application-using-filebeat.md
index 56e810dae..8f622c092 100644
--- a/manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-python-application-using-filebeat.md
+++ b/manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-python-application-using-filebeat.md
@@ -33,7 +33,7 @@ $$$ece-python-logs-send-ess$$$
$$$ece-python-logs-view-kibana$$$
-This guide demonstrates how to ingest logs from a Python application and deliver them securely into an Elasticsearch Service deployment. You’ll set up Filebeat to monitor a JSON-structured log file that has standard Elastic Common Schema (ECS) formatted fields, and you’ll then view real-time visualizations of the log events in {{kib}} as they occur. While Python is used for this example, this approach to monitoring log output is applicable across many client types. Check the list of [available ECS logging plugins](asciidocalypse://docs/ecs-logging/docs/reference/intro.md).
+This guide demonstrates how to ingest logs from a Python application and deliver them securely into an {{ech}} deployment. You’ll set up Filebeat to monitor a JSON-structured log file that has standard Elastic Common Schema (ECS) formatted fields, and you’ll then view real-time visualizations of the log events in {{kib}} as they occur. While Python is used for this example, this approach to monitoring log output is applicable across many client types. Check the list of [available ECS logging plugins](asciidocalypse://docs/ecs-logging/docs/reference/intro.md).
*Time required: 1 hour*
diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md
index 2db13a5fe..43e78eda4 100644
--- a/manage-data/lifecycle/data-tiers.md
+++ b/manage-data/lifecycle/data-tiers.md
@@ -137,10 +137,10 @@ To make sure that all data can be migrated from the data tier you want to disabl
::::{tab-item} {{ech}}
- 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. From the **Deployments** page, select your deployment.
- 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.
+ 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.
3. Filter the list of instances by the Data tier you want to disable.
diff --git a/manage-data/lifecycle/index-lifecycle-management/migrate-index-allocation-filters-to-node-roles.md b/manage-data/lifecycle/index-lifecycle-management/migrate-index-allocation-filters-to-node-roles.md
index 71be7632e..8fd0b551a 100644
--- a/manage-data/lifecycle/index-lifecycle-management/migrate-index-allocation-filters-to-node-roles.md
+++ b/manage-data/lifecycle/index-lifecycle-management/migrate-index-allocation-filters-to-node-roles.md
@@ -15,12 +15,12 @@ While we recommend relying on automatic data tier allocation to manage your data
::::
-{{ess}} and {{ece}} can perform the migration automatically. For self-managed deployments, you need to manually update your configuration, ILM policies, and indices to switch to node roles.
+{{ech}} and {{ece}} can perform the migration automatically. For self-managed deployments, you need to manually update your configuration, ILM policies, and indices to switch to node roles.
-## Automatically migrate to node roles on {{ess}} or {{ece}} [cloud-migrate-to-node-roles]
+## Automatically migrate to node roles on {{ech}} or {{ece}} [cloud-migrate-to-node-roles]
-If you are using node attributes from the default deployment template in {{ess}} or {{ece}}, you will be prompted to switch to node roles when you:
+If you are using node attributes from the default deployment template in {{ech}} or {{ece}}, you will be prompted to switch to node roles when you:
* Upgrade to {{es}} 7.10 or higher
* Deploy a warm, cold, or frozen data tier
@@ -50,7 +50,7 @@ To switch to using node roles:
Configure the appropriate roles for each data node to assign it to one or more data tiers: `data_hot`, `data_content`, `data_warm`, `data_cold`, or `data_frozen`. A node can also have other [roles](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/node-settings.md). By default, new nodes are configured with all roles.
-When you add a data tier to an {{ess}} deployment, one or more nodes are automatically configured with the corresponding role. To explicitly change the role of a node in an {{ess}} deployment, use the [Update deployment API](../../../deploy-manage/deploy/elastic-cloud/manage-deployments-using-elastic-cloud-api.md#ec_update_a_deployment). Replace the node’s `node_type` configuration with the appropriate `node_roles`. For example, the following configuration adds the node to the hot and content tiers, and enables it to act as an ingest node, remote, and transform node.
+When you add a data tier to an {{ech}} deployment, one or more nodes are automatically configured with the corresponding role. To explicitly change the role of a node in an {{ech}} deployment, use the [Update deployment API](../../../deploy-manage/deploy/elastic-cloud/manage-deployments-using-elastic-cloud-api.md#ec_update_a_deployment). Replace the node’s `node_type` configuration with the appropriate `node_roles`. For example, the following configuration adds the node to the hot and content tiers, and enables it to act as an ingest node, remote, and transform node.
```yaml
"node_roles": [
@@ -85,7 +85,7 @@ The policy must specify the corresponding phase for each data tier in your archi
When you create a data stream, its first backing index is now automatically assigned to `data_hot` nodes. Similarly, when you directly create an index, it is automatically assigned to `data_content` nodes.
-On {{ess}} deployments, remove the `cloud-hot-warm-allocation-0` index template that set the hot shard allocation attribute on all indices.
+On {{ech}} deployments, remove the `cloud-hot-warm-allocation-0` index template that set the hot shard allocation attribute on all indices.
```console
DELETE _template/.cloud-hot-warm-allocation-0
diff --git a/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md b/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md
index 4c6cd1027..4f923f1d5 100644
--- a/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md
+++ b/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md
@@ -26,10 +26,10 @@ To configure ILM Migration in the console:
::::{tab-set}
:::{tab-item} {{ech}}
-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. From the **Deployments** page, select your deployment.
- 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.
+ 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.
3. Near the top of the deployment overview, you should get a message to migrate from index curation to index lifecycle management (ILM) along with a **Start migration** button.
4. Select which index curation pattern you wish to migrate.
@@ -40,7 +40,7 @@ To configure ILM Migration in the console:
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
2. From the **Deployments** page, select your deployment.
- 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.
+ 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.
3. Near the top of the deployment overview, you should get a message to migrate from index curation to index lifecycle management (ILM) along with a **Start migration** button.
4. Select which index curation pattern you wish to migrate.
diff --git a/manage-data/lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md b/manage-data/lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md
index d728c5a3a..47db1c63f 100644
--- a/manage-data/lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md
+++ b/manage-data/lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md
@@ -38,7 +38,7 @@ To complete this tutorial, you’ll need:
* An {{es}} cluster with hot and warm data tiers.
- * {{ess}}: Elastic Stack deployments on {{ess}} include a hot tier by default. To add a warm tier, edit your deployment and click **Add capacity** for the warm data tier.
+ * {{ech}}: Elastic Stack deployments on {{ecloud}} include a hot tier by default. To add a warm tier, edit your deployment and click **Add capacity** for the warm data tier.
:::{image} ../../../images/elasticsearch-reference-tutorial-ilm-ess-add-warm-data-tier.png
:alt: Add a warm data tier to your deployment
diff --git a/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md b/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md
index 5190be210..9854e0fa0 100644
--- a/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md
+++ b/manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md
@@ -10,9 +10,9 @@ navigation_title: Reindex from a self-managed cluster
# Migrate from a self-managed cluster with a self-signed certificate using remote reindex [ec-remote-reindex]
-The following instructions show you how to configure remote reindex on Elasticsearch Service from a cluster that uses a self-signed CA.
+The following instructions show you how to configure remote reindex on {{ech}} from a cluster that uses a self-signed CA.
-Let’s assume that the self-managed cluster that uses a self-signed certificate is called `Source`, and you want to migrate data from `Source` to `Destination` on Elasticsearch Service.
+Let’s assume that the self-managed cluster that uses a self-signed certificate is called `Source`, and you want to migrate data from `Source` to `Destination` on {{ech}}.
## Step 1: Create the `Source` certificate in a bundle [ec-remote-reindex-step1]
@@ -37,14 +37,14 @@ Both the folder and file names must correspond to the settings configured in [St
-## Step 2: Upload the zip bundle to your Elasticsearch Service account [ec-remote-reindex-step2]
+## Step 2: Upload the zip bundle to your {{ecloud}} account [ec-remote-reindex-step2]
To upload your file, follow the steps in the section [Add your extension](../../deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md#ec-add-your-plugin). Enter wildcard `*` for **Version** in order to be compatible for all future upgrades, and select `A bundle containing dictionary or script` as **Type**.
-## Step 3: Create a new deployment on Elasticsearch Service [ec-remote-reindex-step3]
+## Step 3: Create a new {{ech}} deployment [ec-remote-reindex-step3]
-From the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) create a new deployment. This will be the `Destination` cluster.
+From the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) create a new deployment. This will be the `Destination` cluster.
::::{note}
The `Destination` cluster should be the same or newer version as the `Source` cluster. If you already have a cluster available, you can skip this step.
@@ -71,7 +71,7 @@ The `Destination` cluster should be the same or newer version as the `Source` cl
## Step 5: Reindex from remote `Source` cluster. [ec-remote-reindex-step5]
-You can now run `reindex` on the Elasticsearch Service `Destination` cluster from `Source` cluster:
+You can now run `reindex` on the {{ech}} `Destination` cluster from `Source` cluster:
```text
POST _reindex
diff --git a/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md b/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md
index fbf019506..04836910a 100644
--- a/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md
+++ b/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md
@@ -22,15 +22,15 @@ The steps for setting up data tiers vary based on your deployment type:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
-1. Log in to the [{{ess}} Console](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
-2. Add or select your deployment from the {{ess}} home page or the deployments page.
+::::::{tab-item} {{ech}}
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
+2. Add or select your deployment from the {{ecloud}} home page or the **Deployments** page.
3. From your deployment menu, select **Edit deployment**.
4. To enable a data tier, click **Add capacity**.
**Enable autoscaling**
-[Autoscaling](../deploy-manage/autoscaling.md) automatically adjusts your deployment’s capacity to meet your storage needs. To enable autoscaling, select **Autoscale this deployment** on the **Edit deployment** page. Autoscaling is only available for {{ess}}.
+[Autoscaling](../deploy-manage/autoscaling.md) automatically adjusts your deployment’s capacity to meet your storage needs. To enable autoscaling, select **Autoscale this deployment** on the **Edit deployment** page. Autoscaling is only available for {{ech}}.
::::::
::::::{tab-item} Self-managed
@@ -76,8 +76,8 @@ To use {{search-snaps}}, you must register a supported snapshot repository. The
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
-When you create a cluster, {{ess}} automatically registers a default [`found-snapshots`](../deploy-manage/tools/snapshot-and-restore.md) repository. This repository supports {{search-snaps}}.
+::::::{tab-item} {{ech}}
+When you create a cluster, {{ech}} automatically registers a default [`found-snapshots`](../deploy-manage/tools/snapshot-and-restore.md) repository. This repository supports {{search-snaps}}.
The `found-snapshots` repository is specific to your cluster. To use another cluster’s default repository, refer to the Cloud [Snapshot and restore](../deploy-manage/tools/snapshot-and-restore.md) documentation.
diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-api-console.md b/raw-migrated-files/cloud/cloud-enterprise/ece-api-console.md
index 7c09d6614..c0d20fa1c 100644
--- a/raw-migrated-files/cloud/cloud-enterprise/ece-api-console.md
+++ b/raw-migrated-files/cloud/cloud-enterprise/ece-api-console.md
@@ -10,7 +10,7 @@ API console is intended for admin purposes. Avoid running normal workload like i
You are unable to make Elastic Cloud Enterprise platform changes from the Elasticsearch API. If you want to work with the platform, check the [Elastic Cloud Enterprise RESTful API](asciidocalypse://docs/cloud/docs/reference/cloud-enterprise/restful-api.md).
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-configuring-keystore.md b/raw-migrated-files/cloud/cloud-enterprise/ece-configuring-keystore.md
index b21397ec0..1297b1ebf 100644
--- a/raw-migrated-files/cloud/cloud-enterprise/ece-configuring-keystore.md
+++ b/raw-migrated-files/cloud/cloud-enterprise/ece-configuring-keystore.md
@@ -14,7 +14,7 @@ There are three types of secrets that you can use:
Add keys and secret values to the keystore.
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
@@ -35,7 +35,7 @@ Only some settings are designed to be read from the keystore. However, the keyst
When your keys and secret values are no longer needed, delete them from the keystore.
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-manage-enterprise-search-settings.md b/raw-migrated-files/cloud/cloud-enterprise/ece-manage-enterprise-search-settings.md
index e8245f20f..461f2a4a6 100644
--- a/raw-migrated-files/cloud/cloud-enterprise/ece-manage-enterprise-search-settings.md
+++ b/raw-migrated-files/cloud/cloud-enterprise/ece-manage-enterprise-search-settings.md
@@ -11,7 +11,7 @@ Refer to the [Configuration settings reference](https://www.elastic.co/guide/en/
To add user settings:
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-traffic-filtering-deployment-configuration.md b/raw-migrated-files/cloud/cloud-enterprise/ece-traffic-filtering-deployment-configuration.md
index 20f9584ef..0f5cb7449 100644
--- a/raw-migrated-files/cloud/cloud-enterprise/ece-traffic-filtering-deployment-configuration.md
+++ b/raw-migrated-files/cloud/cloud-enterprise/ece-traffic-filtering-deployment-configuration.md
@@ -107,7 +107,7 @@ This section offers suggestions on how to troubleshoot your traffic filters. Bef
### Review the rule sets associated with a deployment [ece-review-rule-sets]
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-upgrade-deployment.md b/raw-migrated-files/cloud/cloud-enterprise/ece-upgrade-deployment.md
index 79bd80666..4d57619e6 100644
--- a/raw-migrated-files/cloud/cloud-enterprise/ece-upgrade-deployment.md
+++ b/raw-migrated-files/cloud/cloud-enterprise/ece-upgrade-deployment.md
@@ -35,7 +35,7 @@ When upgrading from one recent major Elasticsearch version to the next, we recom
To upgrade a cluster in Elastic Cloud Enterprise:
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-add-user-settings.md b/raw-migrated-files/cloud/cloud-heroku/ech-add-user-settings.md
index 20aa2ba01..11c447e1b 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-add-user-settings.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-add-user-settings.md
@@ -12,7 +12,7 @@ You can also update [dynamic cluster settings](../../../deploy-manage/deploy/sel
To add or edit user settings:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-configuring-keystore.md b/raw-migrated-files/cloud/cloud-heroku/ech-configuring-keystore.md
index 9499f91c0..d1c979f76 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-configuring-keystore.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-configuring-keystore.md
@@ -14,7 +14,7 @@ There are three types of secrets that you can use:
Add keys and secret values to the keystore.
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
@@ -35,7 +35,7 @@ Only some settings are designed to be read from the keystore. However, the keyst
When your keys and secret values are no longer needed, delete them from the keystore.
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-enable-kibana2.md b/raw-migrated-files/cloud/cloud-heroku/ech-enable-kibana2.md
index 2ee7b3f1b..c199b85b1 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-enable-kibana2.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-enable-kibana2.md
@@ -5,7 +5,7 @@ If your deployment didn’t include a Kibana instance initially, use these instr
To enable Kibana on your deployment:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-enable-logging-and-monitoring.md b/raw-migrated-files/cloud/cloud-heroku/ech-enable-logging-and-monitoring.md
index 34dc5ff16..50c6b171d 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-enable-logging-and-monitoring.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-enable-logging-and-monitoring.md
@@ -115,7 +115,7 @@ Elasticsearch Add-On for Heroku manages the installation and configuration of th
To enable monitoring on your deployment:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
@@ -146,7 +146,7 @@ Enabling logs and monitoring requires some extra resource on a deployment. For p
With monitoring enabled for your deployment, you can access the [logs](https://www.elastic.co/guide/en/kibana/current/observability.html) and [stack monitoring](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md) through Kibana.
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
@@ -214,7 +214,7 @@ With logging and monitoring enabled for a deployment, metrics are collected for
Audit logs are useful for tracking security events on your {{es}} and/or {{kib}} clusters. To enable {{es}} audit logs on your deployment:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-getting-started.md b/raw-migrated-files/cloud/cloud-heroku/ech-getting-started.md
index 17e9ef97f..b17a27b6d 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-getting-started.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-getting-started.md
@@ -2,7 +2,7 @@
This documentation applies to Heroku users who want to make use of the Elasticsearch Add-On for Heroku that is available from the [Heroku Dashboard](https://dashboard.heroku.com/) or that can be installed from the CLI.
-The add-on runs on the Elasticsearch Service and provides access to [Elasticsearch](https://www.elastic.co/products/elasticsearch), the open source, distributed, RESTful search engine. Many other features of the Elastic Stack are also readily available to Heroku users through the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) after you install the add-on. For example, you can use Kibana to visualize your Elasticsearch data.
+The add-on runs on {{ecloud}} and provides access to [Elasticsearch](https://www.elastic.co/products/elasticsearch), the open source, distributed, RESTful search engine. Many other features of the Elastic Stack are also readily available to Heroku users through the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) after you install the add-on. For example, you can use Kibana to visualize your Elasticsearch data.
[Elasticsearch Machine Learning](/explore-analyze/machine-learning.md), [Elastic Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/index.html), [Elastic APM](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Elastic Fleet Server](asciidocalypse://docs/docs-content/docs/reference/ingestion-tools/fleet/index.md) are not supported by the Elasticsearch Add-On for Heroku.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md b/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md
index ac3621048..e9ba2386e 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md
@@ -23,7 +23,7 @@ User settings are appended to the `apm-server.yml` configuration file for your i
To add user settings:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-manage-kibana-settings.md b/raw-migrated-files/cloud/cloud-heroku/ech-manage-kibana-settings.md
index 392693807..4a944696f 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-manage-kibana-settings.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-manage-kibana-settings.md
@@ -10,7 +10,7 @@ Be aware that some settings that could break your cluster if set incorrectly and
To change Kibana settings:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md b/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md
index 78a47d1e0..73a5e27d7 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md
@@ -7,7 +7,7 @@ For advanced views or production monitoring, [enable logging and monitoring](../
To access cluster performance metrics:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-deployment-configuration.md b/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-deployment-configuration.md
index f805d72b8..399b710d8 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-deployment-configuration.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-deployment-configuration.md
@@ -120,7 +120,7 @@ This section offers suggestions on how to troubleshoot your traffic filters. Bef
### Review the rule sets associated with a deployment [ech-review-rule-sets]
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
@@ -135,7 +135,7 @@ On this screen you can view and remove existing filters and attach new filters.
To identify which rule sets are automatically applied to new deployments in your account:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
3. Under the **Features** tab, open the **Traffic filters** page.
4. You can find the list of traffic filter rule sets.
5. Select each of the rule sets — **Include by default** is checked when this rule set is automatically applied to all new deployments in its region.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-ip.md b/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-ip.md
index 09fa4a66e..0da1f519e 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-ip.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-ip.md
@@ -14,7 +14,7 @@ You can combine any rules into a set, so we recommend that you group rules accor
To create a rule set:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
3. Under the **Features** tab, open the **Traffic filters** page.
4. Select **Create filter**.
5. Select **IP filtering rule set**.
@@ -58,7 +58,7 @@ If you want to remove any traffic restrictions from a deployment or delete a rul
You can edit a rule set name or change the allowed traffic sources using IPv4, or a range of addresses with CIDR.
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
3. Under the **Features** tab, open the **Traffic filters** page.
4. Find the rule set you want to edit.
5. Select the **Edit** icon.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-vpc.md b/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-vpc.md
index a10f8d8e1..eb6f03094 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-vpc.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-traffic-filtering-vpc.md
@@ -188,7 +188,7 @@ Having trouble finding your VPC endpoint ID? You can find it in the AWS console.
Once you know your VPC endpoint ID you can create a private link traffic filter rule set.
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
3. Under the **Features** tab, open the **Traffic filters** page.
4. Select **Create filter**.
5. Select **Private link endpoint**.
@@ -248,7 +248,7 @@ The settings `xpack.fleet.agents.fleet_server.hosts` and `xpack.fleet.outputs` t
You can edit a rule set name or to change the VPC endpoint ID.
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
3. Under the **Features** tab, open the **Traffic filters** page.
4. Find the rule set you want to edit.
5. Select the **Edit** icon.
diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-upgrade-deployment.md b/raw-migrated-files/cloud/cloud-heroku/ech-upgrade-deployment.md
index 9858ecdc3..d2c939215 100644
--- a/raw-migrated-files/cloud/cloud-heroku/ech-upgrade-deployment.md
+++ b/raw-migrated-files/cloud/cloud-heroku/ech-upgrade-deployment.md
@@ -42,7 +42,7 @@ To successfully replace and override a plugin which is being upgraded, the `name
To upgrade a cluster in Elasticsearch Add-On for Heroku:
1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
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.
@@ -56,7 +56,7 @@ To upgrade a cluster in Elasticsearch Add-On for Heroku:
7. If you are upgrading to version 6.6 and earlier, major upgrades require a full cluster restart to complete the upgrade process.
8. If you had Kibana enabled, the UI will prompt you to also upgrade Kibana. The Kibana upgrade takes place separately from the Elasticsearch version upgrade and needs to be triggered manually:
- 1. On the deployments page, select your deployment.
+ 1. On the **Deployments** page, select your deployment.
2. From your deployment menu, select **Kibana**.
3. If the button is available, select **Upgrade Kibana**. If the button is not available, Kibana does not need to be upgraded further.
4. Confirm the upgrade.
diff --git a/raw-migrated-files/cloud/cloud/ec-about.md b/raw-migrated-files/cloud/cloud/ec-about.md
index 01f967e74..3833dbad4 100644
--- a/raw-migrated-files/cloud/cloud/ec-about.md
+++ b/raw-migrated-files/cloud/cloud/ec-about.md
@@ -1,11 +1,11 @@
-# About Elasticsearch Service [ec-about]
+# About {{ech}} [ec-about]
The information in this section covers:
* [Subscription Levels](../../../deploy-manage/license.md)
* [Version Policy](../../../deploy-manage/deploy/elastic-cloud/available-stack-versions.md)
-* [Elasticsearch Service Hardware](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/hardware.md)
-* [Elasticsearch Service Regions](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/regions.md)
+* [{{ech}} Hardware](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/hardware.md)
+* [{{ech}} Regions](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/regions.md)
* [Service Status](../../../deploy-manage/cloud-organization/service-status.md)
* [Getting help](../../../troubleshoot/index.md)
* [Restrictions and known problems](../../../deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md)
diff --git a/raw-migrated-files/cloud/cloud/ec-access-kibana.md b/raw-migrated-files/cloud/cloud/ec-access-kibana.md
index 7454c4871..682c66292 100644
--- a/raw-migrated-files/cloud/cloud/ec-access-kibana.md
+++ b/raw-migrated-files/cloud/cloud/ec-access-kibana.md
@@ -6,10 +6,10 @@ For new Elasticsearch clusters, we automatically create a Kibana instance for yo
To access Kibana:
-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. On the **Deployments** page, select your deployment.
- 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.
+ 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.
3. Under **Applications**, select the Kibana **Launch** link and wait for Kibana to open.
@@ -37,10 +37,10 @@ If your deployment didn’t include a Kibana instance initially, use these instr
To enable Kibana on your deployment:
-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.
+ 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.
3. From your deployment menu, go to the **Kibana** page.
4. Select **Enable**.
diff --git a/raw-migrated-files/cloud/cloud/ec-activity-page.md b/raw-migrated-files/cloud/cloud/ec-activity-page.md
index adf4e6f65..caec9c856 100644
--- a/raw-migrated-files/cloud/cloud/ec-activity-page.md
+++ b/raw-migrated-files/cloud/cloud/ec-activity-page.md
@@ -4,10 +4,10 @@ The deployment **Activity** page gives you a convenient way to follow all config
To view the activity for a deployment:
-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. On the **Deployments** page, select your deployment.
- 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.
+ 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.
3. In your deployment menu, select **Activity**.
4. You can:
@@ -30,7 +30,7 @@ Summary
: A summary of what change was applied, when the change was performed, and how long it took.
Applied by
-: The user who submitted the configuration change. `System` indicates configuration changes initiated automatically by the Elasticsearch Service platform.
+: The user who submitted the configuration change. `System` indicates configuration changes initiated automatically by the {{ecloud}} platform.
Actions
: Select **Details** for an expanded view of each step in the configuration change, including the start time, end time, and duration. You can select **Reapply** to re-run the configuration change.
diff --git a/raw-migrated-files/cloud/cloud/ec-add-user-settings.md b/raw-migrated-files/cloud/cloud/ec-add-user-settings.md
index 4952b0577..9c8dcb5eb 100644
--- a/raw-migrated-files/cloud/cloud/ec-add-user-settings.md
+++ b/raw-migrated-files/cloud/cloud/ec-add-user-settings.md
@@ -1,20 +1,20 @@
# Edit {{es}} user settings [ec-add-user-settings]
-Change how {{es}} runs by providing your own user settings. Elasticsearch Service appends these settings to each node’s `elasticsearch.yml` configuration file.
+Change how {{es}} runs by providing your own user settings. {{ech}} appends these settings to each node’s `elasticsearch.yml` configuration file.
-Elasticsearch Service automatically rejects `elasticsearch.yml` settings that could break your cluster. For a list of supported settings, check [Supported {{es}} settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#ec-es-elasticsearch-settings).
+{{ech}} automatically rejects `elasticsearch.yml` settings that could break your cluster. For a list of supported settings, check [Supported {{es}} settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#ec-es-elasticsearch-settings).
::::{warning}
-You can also update [dynamic cluster settings](../../../deploy-manage/deploy/self-managed/configure-elasticsearch.md#dynamic-cluster-setting) using {{es}}'s [update cluster settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). However, Elasticsearch Service doesn’t reject unsafe setting changes made using this API. Use with caution.
+You can also update [dynamic cluster settings](../../../deploy-manage/deploy/self-managed/configure-elasticsearch.md#dynamic-cluster-setting) using {{es}}'s [update cluster settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). However, {{ech}} doesn’t reject unsafe setting changes made using this API. Use with caution.
::::
To add or edit 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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. In the **Elasticsearch** section, select **Manage user settings and extensions**.
@@ -28,7 +28,7 @@ In some cases, you may get a warning saying "User settings are different across
## Supported {{es}} settings [ec-es-elasticsearch-settings]
-Elasticsearch Service supports the following `elasticsearch.yml` settings.
+{{ech}} supports the following `elasticsearch.yml` settings.
### General settings [ec_general_settings]
diff --git a/raw-migrated-files/cloud/cloud/ec-autoscaling.md b/raw-migrated-files/cloud/cloud/ec-autoscaling.md
index 98d8c2612..a1399649a 100644
--- a/raw-migrated-files/cloud/cloud/ec-autoscaling.md
+++ b/raw-migrated-files/cloud/cloud/ec-autoscaling.md
@@ -40,7 +40,7 @@ Currently, autoscaling behavior is as follows:
::::{note}
-For any Elasticsearch Service Elasticsearch component the number of availability zones is not affected by autoscaling. You can always set the number of availability zones manually and the autoscaling mechanism will add or remove capacity per availability zone.
+The number of availability zones for each component of your {{ech}} deployments is not affected by autoscaling. You can always set the number of availability zones manually and the autoscaling mechanism will add or remove capacity per availability zone.
::::
@@ -80,10 +80,10 @@ The following are known limitations and restrictions with autoscaling:
To enable or disable autoscaling on a deployment:
-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. On the **Deployments** page, select your deployment.
- 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.
+ 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.
3. In your deployment menu, select **Edit**.
4. Select desired autoscaling configuration for this deployment using **Enable Autoscaling for:** dropdown menu.
@@ -98,10 +98,10 @@ When autoscaling has been disabled, you need to adjust the size of data tiers an
Each autoscaling setting is configured with a default value. You can adjust these if necessary, as follows:
-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. On the **Deployments** page, select your deployment.
- 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.
+ 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.
3. In your deployment menu, select **Edit**.
4. To update a data tier:
diff --git a/raw-migrated-files/cloud/cloud/ec-billing-stop.md b/raw-migrated-files/cloud/cloud/ec-billing-stop.md
index 9e932f7d3..10609f59d 100644
--- a/raw-migrated-files/cloud/cloud/ec-billing-stop.md
+++ b/raw-migrated-files/cloud/cloud/ec-billing-stop.md
@@ -9,10 +9,10 @@ Got a deployment you no longer need and don’t want to be charged for any longe
To stop being charged for a deployment:
-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.
+ 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.
3. Select **Delete deployment** and confirm the deletion.
diff --git a/raw-migrated-files/cloud/cloud/ec-configuring-keystore.md b/raw-migrated-files/cloud/cloud/ec-configuring-keystore.md
index bf99ff565..7c267874d 100644
--- a/raw-migrated-files/cloud/cloud/ec-configuring-keystore.md
+++ b/raw-migrated-files/cloud/cloud/ec-configuring-keystore.md
@@ -1,6 +1,6 @@
# Secure your settings [ec-configuring-keystore]
-Some of the settings that you configure in Elasticsearch Service are sensitive, such as passwords, and relying on file system permissions to protect these settings is insufficient. To protect your sensitive settings, use the Elasticsearch keystore. With the Elasticsearch keystore, you can add a key and its secret value, then use the key in place of the secret value when you configure your sensitive settings.
+Some of the settings that you configure in {{ech}} are sensitive, such as passwords, and relying on file system permissions to protect these settings is insufficient. To protect your sensitive settings, use the Elasticsearch keystore. With the Elasticsearch keystore, you can add a key and its secret value, then use the key in place of the secret value when you configure your sensitive settings.
There are three types of secrets that you can use:
@@ -13,10 +13,10 @@ There are three types of secrets that you can use:
Add keys and secret values to the keystore.
-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.
+ 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.
3. From your deployment menu, select **Security**.
4. Locate **Elasticsearch keystore** and select **Add settings**.
@@ -34,10 +34,10 @@ Only some settings are designed to be read from the keystore. However, the keyst
When your keys and secret values are no longer needed, delete them from the keystore.
-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.
+ 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.
3. From your deployment menu, select **Security**.
4. From the **Existing keystores** list, use the delete icon next to the **Setting Name** that you want to delete.
diff --git a/raw-migrated-files/cloud/cloud/ec-custom-bundles.md b/raw-migrated-files/cloud/cloud/ec-custom-bundles.md
index de5c18b93..61e50495b 100644
--- a/raw-migrated-files/cloud/cloud/ec-custom-bundles.md
+++ b/raw-migrated-files/cloud/cloud/ec-custom-bundles.md
@@ -87,7 +87,7 @@ Bundles
└── MyGeoLite2-City.mmdb
```
- Note that the extension must be `-(City|Country|ASN).mmdb`, and it must be a different name than the original file name `GeoLite2-City.mmdb` which already exists in Elasticsearch Service. To use this bundle, you can refer it in the GeoIP ingest pipeline as `MyGeoLite2-City.mmdb` under `database_file`.
+ Note that the extension must be `-(City|Country|ASN).mmdb`, and it must be a different name than the original file name `GeoLite2-City.mmdb` which already exists in {{ech}}. To use this bundle, you can refer it in the GeoIP ingest pipeline as `MyGeoLite2-City.mmdb` under `database_file`.
@@ -95,8 +95,8 @@ Bundles
You must upload your files before you can apply them to your cluster configuration:
-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.
3. Under **Features**, select **Extensions**.
4. Select **Upload extension**.
5. Complete the extension fields, including the {{es}} version.
@@ -123,10 +123,10 @@ Refer to [Managing plugins and extensions through the API](../../../deploy-manag
After uploading your files, you can select to enable them when creating a new {{es}} deployment. For existing deployments, you must update your deployment configuration to use the new files:
-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.
+ 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.
3. From the **Actions** dropdown, select **Edit deployment**.
4. Select **Manage user settings and extensions**.
@@ -155,9 +155,9 @@ To update an extension with a new file version,
1. Prepare a new plugin or bundle.
2. On the **Extensions** page, [upload a new extension](../../../deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md#ec-add-your-plugin).
3. Make your new files available by uploading them.
-4. 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.
+4. 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.
+ 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.
5. From the **Actions** dropdown, select **Edit deployment**.
6. Select **Manage user settings and extensions**.
diff --git a/raw-migrated-files/cloud/cloud/ec-custom-repository.md b/raw-migrated-files/cloud/cloud/ec-custom-repository.md
index 6d63d5504..cf790ff52 100644
--- a/raw-migrated-files/cloud/cloud/ec-custom-repository.md
+++ b/raw-migrated-files/cloud/cloud/ec-custom-repository.md
@@ -2,7 +2,7 @@
Specify your own repositories to snapshot to and restore from. This can be useful, for example, to do long-term archiving of old indexes, restore snapshots across Elastic Cloud accounts, or to be certain you have an exit strategy, should you need to move away from our service.
-Elasticsearch Service supports these repositories:
+{{ech}} supports these repositories:
* [Amazon Web Services (AWS)](../../../deploy-manage/tools/snapshot-and-restore/ec-aws-custom-repository.md)
* [Google Cloud Storage (GCS)](../../../deploy-manage/tools/snapshot-and-restore/ec-gcs-snapshotting.md)
diff --git a/raw-migrated-files/cloud/cloud/ec-editing-user-settings.md b/raw-migrated-files/cloud/cloud/ec-editing-user-settings.md
index 478ea8a25..cada29207 100644
--- a/raw-migrated-files/cloud/cloud/ec-editing-user-settings.md
+++ b/raw-migrated-files/cloud/cloud/ec-editing-user-settings.md
@@ -1,6 +1,6 @@
# Edit your user settings [ec-editing-user-settings]
-From the Elasticsearch Service console you can customize Elasticsearch, Kibana, and related products to suit your needs. These editors append your changes to the appropriate YAML configuration file and they affect all users of that cluster. In each editor you can:
+From the {{ecloud}} Console you can customize Elasticsearch, Kibana, and related products to suit your needs. These editors append your changes to the appropriate YAML configuration file and they affect all users of that cluster. In each editor you can:
* [Dictate the behavior of Elasticsearch and its security features](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md).
* [Manage Kibana’s settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md).
diff --git a/raw-migrated-files/cloud/cloud/ec-enable-logging-and-monitoring.md b/raw-migrated-files/cloud/cloud/ec-enable-logging-and-monitoring.md
index aae765e7a..27c12b67b 100644
--- a/raw-migrated-files/cloud/cloud/ec-enable-logging-and-monitoring.md
+++ b/raw-migrated-files/cloud/cloud/ec-enable-logging-and-monitoring.md
@@ -7,15 +7,15 @@ The deployment logging and monitoring feature lets you monitor your deployment i
Monitoring consists of two components:
-* A monitoring and logging agent that is installed on each node in your deployment. The agents collect and index metrics to {{es}}, either on the same deployment or by sending logs and metrics to an external monitoring deployment. Elasticsearch Service manages the installation and configuration of the monitoring agent for you, and you should not modify any of the settings.
+* A monitoring and logging agent that is installed on each node in your deployment. The agents collect and index metrics to {{es}}, either on the same deployment or by sending logs and metrics to an external monitoring deployment. {{ech}} manages the installation and configuration of the monitoring agent for you, and you should not modify any of the settings.
* The stack monitoring application in Kibana that visualizes the monitoring metrics through a dashboard and the logs application that allows you to search and analyze deployment logs.
-The steps in this section cover only the enablement of the monitoring and logging features in Elasticsearch Service. For more information on how to use the monitoring features, refer to [Monitor a cluster](../../../deploy-manage/monitor.md).
+The steps in this section cover only the enablement of the monitoring and logging features in {{ech}}. For more information on how to use the monitoring features, refer to [Monitor a cluster](../../../deploy-manage/monitor.md).
### Before you begin [ec-logging-and-monitoring-limitations]
-Some limitations apply when you use monitoring on Elasticsearch Service. To learn more, check the monitoring [restrictions and limitations](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-restrictions-monitoring).
+Some limitations apply when you use monitoring on {{ech}}. To learn more, check the monitoring [restrictions and limitations](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-restrictions-monitoring).
### Monitoring for production use [ec-logging-and-monitoring-production]
@@ -40,13 +40,13 @@ Logs and metrics that get sent to a dedicated monitoring {{es}} deployment [may
#### Stack versions 8.0 and above [ec-logging-and-monitoring-retention-8]
-When you enable monitoring in Elasticsearch Service, your monitoring indices are retained for a certain period by default. After the retention period has passed, the monitoring indices are deleted automatically. The retention period is configured in the `.monitoring-8-ilm-policy` index lifecycle policy. To view or edit the policy open {{kib}} **Stack management > Data > Index Lifecycle Policies**.
+When you enable monitoring in {{ech}}, your monitoring indices are retained for a certain period by default. After the retention period has passed, the monitoring indices are deleted automatically. The retention period is configured in the `.monitoring-8-ilm-policy` index lifecycle policy. To view or edit the policy open {{kib}} **Stack management > Data > Index Lifecycle Policies**.
### Sending monitoring data to itself (self monitoring) [ec-logging-and-monitoring-retention-self-monitoring]
$$$ec-logging-and-monitoring-retention-7$$$
-When you enable self-monitoring in Elasticsearch Service, your monitoring indices are retained for a certain period by default. After the retention period has passed, the monitoring indices are deleted automatically. Monitoring data is retained for three days by default or as specified by the [`xpack.monitoring.history.duration` user setting](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#xpack-monitoring-history-duration).
+When you enable self-monitoring in {{ech}}, your monitoring indices are retained for a certain period by default. After the retention period has passed, the monitoring indices are deleted automatically. Monitoring data is retained for three days by default or as specified by the [`xpack.monitoring.history.duration` user setting](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#xpack-monitoring-history-duration).
To retain monitoring indices as is without deleting them automatically, you must disable the [cleaner service](../../../deploy-manage/monitor/stack-monitoring/es-local-exporter.md#local-exporter-cleaner) by adding a disabled local exporter in your cluster settings.
@@ -69,7 +69,7 @@ PUT /_cluster/settings
When [monitoring for production use](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-logging-and-monitoring-production), where you configure your deployments **to send monitoring data to a dedicated monitoring deployment** for indexing, this retention period does not apply. Monitoring indices on a dedicated monitoring deployment are retained until you remove them. There are three options open to you:
-* To enable the automatic deletion of monitoring indices from dedicated monitoring deployments, [enable monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-enable-logging-and-monitoring-steps) on your dedicated monitoring deployment in Elasticsearch Service to send monitoring data to itself. When an {{es}} deployment sends monitoring data to itself, all monitoring indices are deleted automatically after the retention period, regardless of the origin of the monitoring data.
+* To enable the automatic deletion of monitoring indices from dedicated monitoring deployments, [enable monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-enable-logging-and-monitoring-steps) on your dedicated monitoring deployment in {{ech}} to send monitoring data to itself. When an {{es}} deployment sends monitoring data to itself, all monitoring indices are deleted automatically after the retention period, regardless of the origin of the monitoring data.
* Alternatively, you can enable the cleaner service on the monitoring deployment by creating a local exporter. You can define the retention period at the same time.
For example
@@ -110,14 +110,14 @@ When sending monitoring data to a deployment, you can configure [Index Lifecycle
### Enable logging and monitoring [ec-enable-logging-and-monitoring-steps]
-Elasticsearch Service manages the installation and configuration of the monitoring agent for you. When you enable monitoring on a deployment, you are configuring where the monitoring agent for your current deployment should send its logs and metrics.
+{{ech}} manages the installation and configuration of the monitoring agent for you. When you enable monitoring on a deployment, you are configuring where the monitoring agent for your current deployment should send its logs and metrics.
To enable monitoring on your deployment:
-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.
+ 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.
3. From your deployment menu, go to the **Logs and metrics** page.
4. Select **Enable**.
@@ -145,10 +145,10 @@ Enabling logs and monitoring requires some extra resource on a deployment. For p
With monitoring enabled for your deployment, you can access the [logs](https://www.elastic.co/guide/en/kibana/current/observability.html) and [stack monitoring](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md) through Kibana.
-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.
+ 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.
3. From your deployment menu, go to the **Logs and Metrics** page.
4. Select the corresponding **View** button to check the logs or metrics data.
@@ -214,10 +214,10 @@ With logging and monitoring enabled for a deployment, metrics are collected for
Audit logs are useful for tracking security events on your {{es}} and/or {{kib}} clusters. To enable {{es}} audit logs on your deployment:
-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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. To enable audit logs in {{es}}, in the **Elasticsearch** section select **Manage user settings and extensions**. For deployments with existing user settings, you may have to expand the **Edit elasticsearch.yml** caret for each node instead.
diff --git a/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md b/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md
index 85c357a6a..ce7f62be1 100644
--- a/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md
+++ b/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md
@@ -1,30 +1,30 @@
-# Elasticsearch Service FAQ [ec-faq-getting-started]
+# {{ech}} FAQ [ec-faq-getting-started]
-This frequently-asked-questions list helps you with common questions while you get Elasticsearch Service up and running for the first time. For questions about Elasticsearch Service configuration options or billing, check the [Technical FAQ](../../../deploy-manage/index.md) and the [Billing FAQ](../../../deploy-manage/cloud-organization/billing/billing-faq.md).
+This frequently-asked-questions list helps you with common questions while you get {{ech}} up and running for the first time. For questions about {{ech}} configuration options or billing, check the [Technical FAQ](../../../deploy-manage/index.md) and the [Billing FAQ](../../../deploy-manage/cloud-organization/billing/billing-faq.md).
-* [What is Elasticsearch Service?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-what)
-* [Is Elasticsearch Service the same as Amazon’s {{es}} Service?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-aws-difference)
-* [Can I run the full Elastic Stack in Elasticsearch Service?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-full-stack)
-* [Can I try Elasticsearch Service for free?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-trial)
+* [What is {{ech}}?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-what)
+* [Is {{ech}} the same as Amazon’s {{es}} Service?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-aws-difference)
+* [Can I run the full Elastic Stack in {{ech}}?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-full-stack)
+* [Can I try {{ech}} for free?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-trial)
* [What if I need to change the size of my {{es}} cluster at a later time?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-config)
* [Do you offer support subscriptions?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-subscriptions)
-* [Where is Elasticsearch Service hosted?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-where)
-* [What is the difference between Elasticsearch Service and the Amazon {{es}} Service?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-vs-aws)
-* [Can I use Elasticsearch Service on platforms other than AWS?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-aws)
+* [Where is {{ech}} hosted?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-where)
+* [What is the difference between {{ech}} and the Amazon {{es}} Service?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-vs-aws)
+* [Can I use {{ech}} on platforms other than AWS?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-aws)
* [Do you offer Elastic’s commercial products?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-elastic)
* [Is my {{es}} cluster protected by X-Pack?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-x-pack)
* [Is there a limit on the number of documents or indexes I can have in my cluster?](../../../deploy-manage/deploy/elastic-cloud/cloud-hosted.md#faq-limit)
- $$$faq-what$$$What is Elasticsearch Service?
- : Elasticsearch Service is hosted and managed {{es}} and {{kib}} brought to you by the creators of {{es}}. Elasticsearch Service is part of Elastic Cloud and ships with features that you can only get from the company behind {{es}}, {{kib}}, {{beats}}, and {{ls}}. {{es}} is a full text search engine that suits a range of uses, from search on websites to big data analytics and more.
+ $$$faq-what$$$What is {{ech}}?
+ : {{ech}} is hosted and managed {{es}} and {{kib}} brought to you by the creators of {{es}}. {{ech}} is part of Elastic Cloud and ships with features that you can only get from the company behind {{es}}, {{kib}}, {{beats}}, and {{ls}}. {{es}} is a full text search engine that suits a range of uses, from search on websites to big data analytics and more.
- $$$faq-aws-difference$$$Is Elasticsearch Service the same as Amazon’s {{es}} Service?
- : Elasticsearch Service is not the same as the Amazon {{es}} service. To learn more about the differences, check our [AWS {{es}} Service](https://www.elastic.co/aws-elasticsearch-service) comparison.
+ $$$faq-aws-difference$$$Is {{ech}} the same as Amazon’s {{es}} Service?
+ : {{ech}} is not the same as the Amazon {{es}} service. To learn more about the differences, check our [AWS {{es}} Service](https://www.elastic.co/aws-elasticsearch-service) comparison.
- $$$faq-full-stack$$$Can I run the full Elastic Stack in Elasticsearch Service?
- : Many of the products that are part of the Elastic Stack are readily available in Elasticsearch Service, including {{es}}, {{kib}}, plugins, and features such as monitoring and security. Use other Elastic Stack products directly with Elasticsearch Service. For example, both Logstash and Beats can send their data to Elasticsearch Service. What is run is determined by the [subscription level](https://www.elastic.co/cloud/as-a-service/subscriptions).
+ $$$faq-full-stack$$$Can I run the full Elastic Stack in {{ech}}?
+ : Many of the products that are part of the Elastic Stack are readily available in {{ech}}, including {{es}}, {{kib}}, plugins, and features such as monitoring and security. Use other Elastic Stack products directly with {{ech}}. For example, both Logstash and Beats can send their data to {{ech}}. What is run is determined by the [subscription level](https://www.elastic.co/cloud/as-a-service/subscriptions).
- $$$faq-trial$$$Can I try Elasticsearch Service for free?
+ $$$faq-trial$$$Can I try {{ech}} for free?
: Yes, sign up for a 14-day free trial. The trial starts the moment a cluster is created.
During the free trial period get access to a deployment to explore Elastic solutions for Search, Observability, Security, or the latest version of the Elastic Stack.
@@ -34,24 +34,24 @@ This frequently-asked-questions list helps you with common questions while you g
: Scale your clusters both up and down from the user console, whenever you like. The resizing of the cluster is transparently done in the background, and highly available clusters are resized without any downtime. If you scale your cluster down, make sure that the downsized cluster can handle your {{es}} memory requirements. Read more about sizing and memory in [Sizing {{es}}](https://www.elastic.co/blog/found-sizing-elasticsearch).
$$$faq-subscriptions$$$Do you offer support?
- : Yes, all subscription levels for Elasticsearch Service include support, handled by email or through the Elastic Support Portal. Different subscription levels include different levels of support. For the Standard subscription level, there is no service-level agreement (SLA) on support response times. Gold and Platinum subscription levels include an SLA on response times to tickets and dedicated resources. To learn more, check [Getting Help](../../../troubleshoot/index.md).
+ : Yes, all subscription levels for {{ech}} include support, handled by email or through the Elastic Support Portal. Different subscription levels include different levels of support. For the Standard subscription level, there is no service-level agreement (SLA) on support response times. Gold and Platinum subscription levels include an SLA on response times to tickets and dedicated resources. To learn more, check [Getting Help](../../../troubleshoot/index.md).
- $$$faq-where$$$Where is Elasticsearch Service hosted?
+ $$$faq-where$$$Where is {{ech}} hosted?
: We host our {{es}} clusters on Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. Check out which [regions we support](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/regions.md) and what [hardware we use](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/hardware.md). New data centers are added all the time.
- $$$faq-vs-aws$$$What is the difference between Elasticsearch Service and the Amazon {{es}} Service?
- : Elasticsearch Service is the only hosted and managed {{es}} service built, managed, and supported by the company behind {{es}}, {{kib}}, {{beats}}, and {{ls}}. With Elasticsearch Service, you always get the latest versions of the software. Our service is built on best practices and years of experience hosting and managing thousands of {{es}} clusters in the Cloud and on premise. For more information, check the following Amazon and Elastic {{es}} Service [comparison page](https://www.elastic.co/aws-elasticsearch-service).
+ $$$faq-vs-aws$$$What is the difference between {{ech}} and the Amazon {{es}} Service?
+ : {{ech}} is the only hosted and managed {{es}} service built, managed, and supported by the company behind {{es}}, {{kib}}, {{beats}}, and {{ls}}. With {{ech}}, you always get the latest versions of the software. Our service is built on best practices and years of experience hosting and managing thousands of {{es}} clusters in the Cloud and on premise. For more information, check the following Amazon and Elastic {{es}} Service [comparison page](https://www.elastic.co/aws-elasticsearch-service).
Please note that there is no formal partnership between Elastic and Amazon Web Services (AWS), and Elastic does not provide any support on the AWS {{es}} Service.
- $$$faq-aws$$$Can I use Elasticsearch Service on platforms other than AWS?
+ $$$faq-aws$$$Can I use {{ech}} on platforms other than AWS?
: Yes, create deployments on the Google Cloud Platform and Microsoft Azure.
$$$faq-elastic$$$Do you offer Elastic’s commercial products?
- : Yes, all Elasticsearch Service customers have access to basic authentication, role-based access control, and monitoring.
+ : Yes, all {{ech}} customers have access to basic authentication, role-based access control, and monitoring.
- Elasticsearch Service Gold, Platinum and Enterprise customers get complete access to all the capabilities in X-Pack:
+ {{ech}} Gold, Platinum and Enterprise customers get complete access to all the capabilities in X-Pack:
* Security
* Alerting
@@ -63,7 +63,7 @@ This frequently-asked-questions list helps you with common questions while you g
$$$faq-x-pack$$$Is my Elasticsearch cluster protected by X-Pack?
- : Yes, X-Pack security features offer the full power to protect your Elasticsearch Service deployment with basic authentication and role-based access control.
+ : Yes, X-Pack security features offer the full power to protect your {{ech}} deployment with basic authentication and role-based access control.
$$$faq-limit$$$Is there a limit on the number of documents or indexes I can have in my cluster?
: No. We do not enforce any artificial limit on the number of indexes or documents you can store in your cluster.
diff --git a/raw-migrated-files/cloud/cloud/ec-faq-technical.md b/raw-migrated-files/cloud/cloud/ec-faq-technical.md
index 7aa63686b..6685499dc 100644
--- a/raw-migrated-files/cloud/cloud/ec-faq-technical.md
+++ b/raw-migrated-files/cloud/cloud/ec-faq-technical.md
@@ -1,38 +1,38 @@
# Technical FAQ [ec-faq-technical]
-This frequently-asked-questions list answers some of your more common questions about configuring Elasticsearch Service.
+This frequently-asked-questions list answers some of your more common questions about configuring {{ech}}.
* [Can I implement a Hot-Warm architecture?](../../../deploy-manage/index.md#faq-hw-architecture)
* [What about dedicated master nodes?](../../../deploy-manage/index.md#faq-master-nodes)
* [Can I use a Custom SSL certificate?](../../../deploy-manage/index.md#faq-ssl)
-* [Can Elasticsearch Service autoscale?](../../../deploy-manage/index.md#faq-autoscale)
+* [Can {{ech}} autoscale?](../../../deploy-manage/index.md#faq-autoscale)
* [Do you support IP sniffing?](../../../deploy-manage/index.md#faq-ip-sniffing)
-* [Does Elasticsearch Service support encryption at rest?](../../../deploy-manage/index.md#faq-encryption-at-rest)
-* [Can I find the static IP addresses for my endpoints on Elasticsearch Service?](../../../deploy-manage/index.md#faq-static-ip-elastic-cloud)
+* [Does {{ech}} support encryption at rest?](../../../deploy-manage/index.md#faq-encryption-at-rest)
+* [Can I find the static IP addresses for my endpoints on {{ech}}?](../../../deploy-manage/index.md#faq-static-ip-elastic-cloud)
$$$faq-hw-architecture$$$Can I implement a hot-warm architecture?
- : [*hot-warm architecture*](https://www.elastic.co/blog/hot-warm-architecture) refers to an Elasticsearch setup for larger time-data analytics use cases with two different types of nodes, hot and warm. Elasticsearch Service supports hot-warm architectures in all of the solutions provided by allowing you to add warm nodes to any of your deployments.
+ : [*hot-warm architecture*](https://www.elastic.co/blog/hot-warm-architecture) refers to an Elasticsearch setup for larger time-data analytics use cases with two different types of nodes, hot and warm. {{ech}} supports hot-warm architectures in all of the solutions provided by allowing you to add warm nodes to any of your deployments.
$$$faq-master-nodes$$$What about dedicated master nodes?
: [Master nodes](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/modules-node.html#master-node) are responsible for cluster-wide actions, such as creating or deleting an index, tracking which nodes are part of the cluster, and deciding which shards to allocate to which nodes. For clusters that have six or more Elasticsearch nodes, dedicated master-eligible nodes are introduced. When your cluster grows, consider separating dedicated master-eligible nodes from dedicated data nodes. We recommend using at least 4GB RAM for dedicated master nodes.
$$$faq-ssl$$$Can I use a Custom SSL certificate?
- : We don’t support custom SSL certificates, which means that a custom CNAME for an Elasticsearch Service endpoint such as *mycluster.mycompanyname.com* also is not supported.
+ : We don’t support custom SSL certificates, which means that a custom CNAME for an {{ech}} endpoint such as *mycluster.mycompanyname.com* also is not supported.
- $$$faq-autoscale$$$Can Elasticsearch Service autoscale?
- : Elasticsearch Service now supports autoscaling. To learn how to enable it through the console or the API, check [Deployment autoscaling](../../../deploy-manage/autoscaling.md).
+ $$$faq-autoscale$$$Can {{ech}} autoscale?
+ : {{ech}} now supports autoscaling. To learn how to enable it through the console or the API, check [Deployment autoscaling](../../../deploy-manage/autoscaling.md).
$$$faq-ip-sniffing$$$Do you support IP sniffing?
- : IP sniffing is not supported by design and will not return the expected results. We prevent IP sniffing from returning the expected results to improve the security of our underlying Elasticsearch Service infrastructure.
+ : IP sniffing is not supported by design and will not return the expected results. We prevent IP sniffing from returning the expected results to improve the security of our underlying {{ech}} infrastructure.
- $$$faq-encryption-at-rest$$$Does Elasticsearch Service support encryption at rest?
- : Yes, encryption at rest (EAR) is enabled in Elasticsearch Service by default. We support EAR for both the data stored in your clusters and the snapshots we take for backup, on all cloud platforms and across all regions.
+ $$$faq-encryption-at-rest$$$Does {{ech}} support encryption at rest?
+ : Yes, encryption at rest (EAR) is enabled in {{ech}} by default. We support EAR for both the data stored in your clusters and the snapshots we take for backup, on all cloud platforms and across all regions.
You can also bring your own key (BYOK) to encrypt your Elastic Cloud deployment data and snapshots. For more information, check [Encrypt your deployment with a customer-managed encryption key](../../../deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md).
Note that the encryption happens at the file system level.
-$$$faq-static-ip-elastic-cloud$$$We have requirements around restricting access by adding firewall rules to only allow access to certain IP addresses from our Infosec team. Do you provide static IP addresses for the endpoints on Elasticsearch Service?
-: We do provide [static IP ranges](../../../deploy-manage/security/elastic-cloud-static-ips.md), but they should be used with caution as noted in the documentation. IP addresses assigned to cloud resources can change without notice. This could be initiated by cloud providers with no knowledge to us. For this reason, we generally do not recommend that you use firewall rules to allow or restrict certain IP ranges. If you do wish to secure communication for deployment endpoints on Elasticsearch Service, please use [Private Link](../../../deploy-manage/security/traffic-filtering.md). However, in situations where using Private Link services do not meet requirements (for example, secure traffic **from** Elastic Cloud), static IP ranges can be used.
+$$$faq-static-ip-elastic-cloud$$$We have requirements around restricting access by adding firewall rules to only allow access to certain IP addresses from our Infosec team. Do you provide static IP addresses for the endpoints on {{ech}}?
+: We do provide [static IP ranges](../../../deploy-manage/security/elastic-cloud-static-ips.md), but they should be used with caution as noted in the documentation. IP addresses assigned to cloud resources can change without notice. This could be initiated by cloud providers with no knowledge to us. For this reason, we generally do not recommend that you use firewall rules to allow or restrict certain IP ranges. If you do wish to secure communication for deployment endpoints on {{ech}}, please use [Private Link](../../../deploy-manage/security/traffic-filtering.md). However, in situations where using Private Link services do not meet requirements (for example, secure traffic **from** Elastic Cloud), static IP ranges can be used.
diff --git a/raw-migrated-files/cloud/cloud/ec-get-help.md b/raw-migrated-files/cloud/cloud/ec-get-help.md
index c47aab112..a1065d46d 100644
--- a/raw-migrated-files/cloud/cloud/ec-get-help.md
+++ b/raw-migrated-files/cloud/cloud/ec-get-help.md
@@ -1,13 +1,13 @@
# Getting help [ec-get-help]
-With your Elasticsearch Service subscription, you get access to support from the creators of Elasticsearch, Kibana, Beats, Logstash, and much more. We’re here to help!
+With your {{ecloud}} subscription, you get access to support from the creators of Elasticsearch, Kibana, Beats, Logstash, and much more. We’re here to help!
## How do I open a support case? [ec_how_do_i_open_a_support_case]
All roads lead to the Elastic Support Portal, where you can access to all your cases, subscriptions, and licenses.
-As an Elasticsearch Service customer, you will receive an email with instructions how to log in to the Support Portal, where you can track both current and archived cases. If you are a new customer who just signed up for Elasticsearch Service, it can take a few hours for your Support Portal access to be set up. If you have questions, reach out to us at `support@elastic.co`.
+As an {{ecloud}} customer, you will receive an email with instructions how to log in to the Support Portal, where you can track both current and archived cases. If you are a new customer who just signed up for E{{ecloud}}, it can take a few hours for your Support Portal access to be set up. If you have questions, reach out to us at `support@elastic.co`.
::::{note}
With the release of the new Support Portal, even if you have an existing account, you might be prompted to update your password.
@@ -17,7 +17,7 @@ With the release of the new Support Portal, even if you have an existing account
There are three ways you can get to the portal:
* Go directly to the Support Portal: [http://support.elastic.co](http://support.elastic.co)
-* From the Elasticsearch Service Console: Go to the [Support page](https://cloud.elastic.co/support?page=docs&placement=docs-body) or select the support icon, that looks like a life preserver, on any page in the console.
+* From the {{ecloud}} Console: Go to the [Support page](https://cloud.elastic.co/support?page=docs&placement=docs-body) or select the support icon, that looks like a life preserver, on any page in the console.
* Contact us by email: `support@elastic.co`
If you contact us by email, please use the email address that you registered with, so that we can help you more quickly. If you are using a distribution list as your registered email, you can also register a second email address with us. Just open a case to let us know the name and email address you would like to be added.
@@ -25,35 +25,35 @@ There are three ways you can get to the portal:
When opening a case, there are a few things you can do to get help faster:
-* Include the deployment ID that you want help with, especially if you have several deployments. The deployment ID can be found on the overview page for your cluster in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+* Include the deployment ID that you want help with, especially if you have several deployments. The deployment ID can be found on the overview page for your cluster in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
* Describe the problem. Include any relevant details, including error messages you encountered, dates and times when the problem occurred, or anything else you think might be helpful.
* Upload any pertinent files.
## What level of support can I expect? [ec_what_level_of_support_can_i_expect]
-Support is governed by the [Elasticsearch Service Standard Terms of Service](https://www.elastic.co/legal/terms-of-service/cloud). The level of support you can expect to receive applies to your Elasticsearch Service environment only and depends on your subscription level:
+Support is governed by the [{{ecloud}} Standard Terms of Service](https://www.elastic.co/legal/terms-of-service/cloud). The level of support you can expect to receive applies to your {{ecloud}} environment only and depends on your subscription level:
-Elasticsearch Service Standard subscriptions
-: Support is provided by email or through the Elastic Support Portal. The main focus of support is to ensure your Elasticsearch Service deployment shows a green status and is available. There is no guaranteed initial or ongoing response time, but we do strive to engage on every issue within three business days. We do not offer weekend coverage, so we respond Monday through Friday only. To learn more, check [Working with Elastic Support Elasticsearch Service Standard](https://www.elastic.co/support/welcome/cloud).
+{{ecloud}} Standard subscriptions
+: Support is provided by email or through the Elastic Support Portal. The main focus of support is to ensure your {{ech}} deployment shows a green status and is available. There is no guaranteed initial or ongoing response time, but we do strive to engage on every issue within three business days. We do not offer weekend coverage, so we respond Monday through Friday only. To learn more, check [Working with Elastic Support {{ecloud}} Standard](https://www.elastic.co/support/welcome/cloud).
-Elasticsearch Service Gold and Platinum subscriptions
-: Support is handled by email or through the Elastic Support Portal. Provides guaranteed response times for support issues, better support coverage hours, and support contacts at Elastic. Also includes support for how-to and development questions. The exact support coverage depends on whether you are a Gold or Platinum customer. To learn more, check [Elasticsearch Service Premium Support Services Policy](https://www.elastic.co/legal/support_policy/cloud_premium).
+{{ecloud}} Gold and Platinum subscriptions
+: Support is handled by email or through the Elastic Support Portal. Provides guaranteed response times for support issues, better support coverage hours, and support contacts at Elastic. Also includes support for how-to and development questions. The exact support coverage depends on whether you are a Gold or Platinum customer. To learn more, check [{{ecloud}} Premium Support Services Policy](https://www.elastic.co/legal/support_policy/cloud_premium).
::::{note}
-If you are in free trial, you are also eligible to get the Elasticsearch Service Standard level support for as long as the trial is active.
+If you are in free trial, you are also eligible to get the {{ecloud}} Standard level support for as long as the trial is active.
::::
-If you are on an Elasticsearch Service Standard subscription and you are interested in moving to Gold or Platinum support, please [contact us](https://www.elastic.co/cloud/contact). We also recommend that you read our best practices guide for getting the most out of your support experience: [https://www.elastic.co/support/welcome](https://www.elastic.co/support/welcome).
+If you are on an {{ecloud}} Standard subscription and you are interested in moving to Gold or Platinum support, please [contact us](https://www.elastic.co/cloud/contact). We also recommend that you read our best practices guide for getting the most out of your support experience: [https://www.elastic.co/support/welcome](https://www.elastic.co/support/welcome).
## Join the community forums [ec_join_the_community_forums]
-Elasticsearch, Logstash, and Kibana enjoy the benefit of having vibrant and helpful communities. You have our assurance of high-quality support and single source of truth as an Elasticsearch Service customer, but the Elastic community can also be a useful resource for you whenever you need it.
+Elasticsearch, Logstash, and Kibana enjoy the benefit of having vibrant and helpful communities. You have our assurance of high-quality support and single source of truth as an {{ecloud}} customer, but the Elastic community can also be a useful resource for you whenever you need it.
::::{tip}
-As of May 1, 2017, support for Elasticsearch Service **Standard** customers has moved from the Discuss forum to our link: [Elastic Support Portal](https://support.elastic.co). You should receive login instructions by email. We will also monitor the forum and help you get into the Support Portal, in case you’re unsure where to go.
+As of May 1, 2017, support for {{ecloud}} **Standard** customers has moved from the Discuss forum to our link: [Elastic Support Portal](https://support.elastic.co). You should receive login instructions by email. We will also monitor the forum and help you get into the Support Portal, in case you’re unsure where to go.
::::
diff --git a/raw-migrated-files/cloud/cloud/ec-getting-started-node-js.md b/raw-migrated-files/cloud/cloud/ec-getting-started-node-js.md
index 9abdfa537..4e9b0fb23 100644
--- a/raw-migrated-files/cloud/cloud/ec-getting-started-node-js.md
+++ b/raw-migrated-files/cloud/cloud/ec-getting-started-node-js.md
@@ -1,17 +1,17 @@
-# Ingest data with Node.js on Elasticsearch Service [ec-getting-started-node-js]
+# Ingest data with Node.js on {{ech}} [ec-getting-started-node-js]
This guide tells you how to get started with:
-* Securely connecting to Elasticsearch Service with Node.js
+* Securely connecting to {{ech}} with Node.js
* Ingesting data into your deployment from your application
-* Searching and modifying your data on Elasticsearch Service
+* Searching and modifying your data on {{ech}}
If you are an Node.js application programmer who is new to the Elastic Stack, this content helps you get started more easily.
*Time required: 45 minutes*
-## Get Elasticsearch Service [ec_get_elasticsearch_service]
+## Get {{ech}} [ec_get_elasticsearch_service]
1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
@@ -20,7 +20,7 @@ If you are an Node.js application programmer who is new to the Elastic Stack, th
5. Select **Create deployment** and save your Elastic deployment credentials. You need these credentials later on.
6. When the deployment is ready, click **Continue** and a page of **Setup guides** is displayed. To continue to the deployment homepage click **I’d like to do something else**.
-Prefer not to subscribe to yet another service? You can also get Elasticsearch Service through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
+Prefer not to subscribe to yet another service? You can also get {{ech}} through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
## Set up your application [ec_set_up_your_application]
@@ -73,9 +73,9 @@ The example here shows what the `config` package expects. You need to update `co
## About connecting securely [ec_about_connecting_securely]
-When connecting to Elasticsearch Service use a Cloud ID to specify the connection details. You must pass the Cloud ID that is found in {{kib}} or the cloud console.
+When connecting to {{ech}} use a Cloud ID to specify the connection details. You must pass the Cloud ID that is found in {{kib}} or the cloud console.
-To connect to, stream data to, and issue queries with Elasticsearch Service, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
+To connect to, stream data to, and issue queries with {{ech}}, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
### Basic authentication [ec_basic_authentication]
@@ -278,13 +278,13 @@ Check [Create API key API](https://www.elastic.co/docs/api/doc/elasticsearch/ope
### Best practices [ec_best_practices]
Security
-: When connecting to Elasticsearch Service, the client automatically enables both request and response compression by default, since it yields significant throughput improvements. Moreover, the client also sets the SSL option `secureProtocol` to `TLSv1_2_method` unless specified otherwise. You can still override this option by configuring it.
+: When connecting to {{ech}}, the client automatically enables both request and response compression by default, since it yields significant throughput improvements. Moreover, the client also sets the SSL option `secureProtocol` to `TLSv1_2_method` unless specified otherwise. You can still override this option by configuring it.
- Do not enable sniffing when using Elasticsearch Service, since the nodes are behind a load balancer. Elasticsearch Service takes care of everything for you. Take a look at [Elasticsearch sniffing best practices: What, when, why, how](https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how) if you want to know more.
+ Do not enable sniffing when using {{ech}}, since the nodes are behind a load balancer. {{ech}} takes care of everything for you. Take a look at [Elasticsearch sniffing best practices: What, when, why, how](https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how) if you want to know more.
Connections
-: If your application connecting to Elasticsearch Service runs under the Java security manager, you should at least disable the caching of positive hostname resolutions. To learn more, check the [Java API Client documentation](asciidocalypse://docs/elasticsearch-java/docs/reference/_others.md).
+: If your application connecting to {{ech}} runs under the Java security manager, you should at least disable the caching of positive hostname resolutions. To learn more, check the [Java API Client documentation](asciidocalypse://docs/elasticsearch-java/docs/reference/_others.md).
Schema
: When the example code was run an index mapping was created automatically. The field types were selected by {{es}} based on the content seen when the first record was ingested, and updated as new fields appeared in the data. It would be more efficient to specify the fields and field types in advance to optimize performance. Refer to the Elastic Common Schema documentation and Field Type documentation when you are designing the schema for your production use cases.
diff --git a/raw-migrated-files/cloud/cloud/ec-getting-started-python.md b/raw-migrated-files/cloud/cloud/ec-getting-started-python.md
index cb6011b85..5068b510d 100644
--- a/raw-migrated-files/cloud/cloud/ec-getting-started-python.md
+++ b/raw-migrated-files/cloud/cloud/ec-getting-started-python.md
@@ -1,10 +1,10 @@
-# Ingest data with Python on Elasticsearch Service [ec-getting-started-python]
+# Ingest data with Python on {{ech}} [ec-getting-started-python]
This guide tells you how to get started with:
-* Securely connecting to Elasticsearch Service with Python
+* Securely connecting to {{ech}} with Python
* Ingesting data into your deployment from your application
-* Searching and modifying your data on Elasticsearch Service
+* Searching and modifying your data on {{ech}}
If you are an Python application programmer who is new to the Elastic Stack, this content can help you get started more easily.
@@ -32,7 +32,7 @@ elasticsearch>=7.0.0,<8.0.0
```
-## Get Elasticsearch Service [ec_get_elasticsearch_service_2]
+## Get {{ech}} [ec_get_elasticsearch_service_2]
1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
@@ -41,14 +41,14 @@ elasticsearch>=7.0.0,<8.0.0
5. Select **Create deployment** and save your Elastic deployment credentials. You need these credentials later on.
6. When the deployment is ready, click **Continue** and a page of **Setup guides** is displayed. To continue to the deployment homepage click **I’d like to do something else**.
-Prefer not to subscribe to yet another service? You can also get Elasticsearch Service through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
+Prefer not to subscribe to yet another service? You can also get {{ech}} through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
## Connect securely [ec_connect_securely]
-When connecting to Elasticsearch Service you need to use your Cloud ID to specify the connection details. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+When connecting to {{ech}} you need to use your Cloud ID to specify the connection details. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
-To connect to, stream data to, and issue queries with Elasticsearch Service, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
+To connect to, stream data to, and issue queries with {{ech}}, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
### Basic authentication [ec_basic_authentication_2]
@@ -315,7 +315,7 @@ POST /_security/api_key
}
```
-Edit the `example.ini` file you created earlier and add the `id` and `api_key` you just created. You should also remove the lines for `user` and `password` you added earlier after you have tested the `api_key`, and consider changing the `elastic` password using the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+Edit the `example.ini` file you created earlier and add the `id` and `api_key` you just created. You should also remove the lines for `user` and `password` you added earlier after you have tested the `api_key`, and consider changing the `elastic` password using the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
```sh
[DEFAULT]
@@ -333,7 +333,7 @@ es = Elasticsearch(
)
```
-Check [Create API key API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-api-key) to learn more about API Keys and [Security privileges](../../../deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md) to understand which privileges are needed. If you are not sure what the right combination of privileges for your custom application is, you can enable [audit logging](../../../deploy-manage/monitor/logging-configuration/enabling-audit-logs.md) on {{es}} to find out what privileges are being used. To learn more about how logging works on Elasticsearch Service, check [Monitoring Elastic Cloud deployment logs and metrics](https://www.elastic.co/blog/monitoring-elastic-cloud-deployment-logs-and-metrics).
+Check [Create API key API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-api-key) to learn more about API Keys and [Security privileges](../../../deploy-manage/users-roles/cluster-or-deployment-auth/elasticsearch-privileges.md) to understand which privileges are needed. If you are not sure what the right combination of privileges for your custom application is, you can enable [audit logging](../../../deploy-manage/monitor/logging-configuration/enabling-audit-logs.md) on {{es}} to find out what privileges are being used. To learn more about how logging works on {{ech}}, check [Monitoring Elastic Cloud deployment logs and metrics](https://www.elastic.co/blog/monitoring-elastic-cloud-deployment-logs-and-metrics).
For more information on refreshing an index, searching, updating, and deleting, check the [elasticsearch-py examples](asciidocalypse://docs/elasticsearch-py/docs/reference/examples.md).
@@ -341,9 +341,9 @@ For more information on refreshing an index, searching, updating, and deleting,
### Best practices [ec_best_practices_2]
Security
-: When connecting to Elasticsearch Service, the client automatically enables both request and response compression by default, since it yields significant throughput improvements. Moreover, the client also sets the SSL option `secureProtocol` to `TLSv1_2_method` unless specified otherwise. You can still override this option by configuring it.
+: When connecting to {{ech}}, the client automatically enables both request and response compression by default, since it yields significant throughput improvements. Moreover, the client also sets the SSL option `secureProtocol` to `TLSv1_2_method` unless specified otherwise. You can still override this option by configuring it.
- Do not enable sniffing when using Elasticsearch Service, since the nodes are behind a load balancer. Elasticsearch Service takes care of everything for you. Take a look at [Elasticsearch sniffing best practices: What, when, why, how](https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how) if you want to know more.
+ Do not enable sniffing when using {{ech}}, since the nodes are behind a load balancer. {{ech}} takes care of everything for you. Take a look at [Elasticsearch sniffing best practices: What, when, why, how](https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how) if you want to know more.
Schema
diff --git a/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-beats-logstash.md b/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-beats-logstash.md
index dd8a2bf45..64e663a34 100644
--- a/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-beats-logstash.md
+++ b/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-beats-logstash.md
@@ -1,19 +1,19 @@
-# Ingest data from Beats to Elasticsearch Service with {{ls}} as a proxy [ec-getting-started-search-use-cases-beats-logstash]
+# Ingest data from Beats to {{ech}} with {{ls}} as a proxy [ec-getting-started-search-use-cases-beats-logstash]
-This guide explains how to ingest data from Filebeat and Metricbeat to {{ls}} as an intermediary, and then send that data to Elasticsearch Service. Using {{ls}} as a proxy limits your Elastic stack traffic through a single, external-facing firewall exception or rule. Consider the following features of this type of setup:
+This guide explains how to ingest data from Filebeat and Metricbeat to {{ls}} as an intermediary, and then send that data to {{ech}}. Using {{ls}} as a proxy limits your Elastic stack traffic through a single, external-facing firewall exception or rule. Consider the following features of this type of setup:
-* You can send multiple instances of Beats data through your local network’s demilitarized zone (DMZ) to {{ls}}. {{ls}} then acts as a proxy through your firewall to send the Beats data to Elasticsearch Service, as shown in the following diagram:
+* You can send multiple instances of Beats data through your local network’s demilitarized zone (DMZ) to {{ls}}. {{ls}} then acts as a proxy through your firewall to send the Beats data to {{ech}}, as shown in the following diagram:
-* This proxying reduces the firewall exceptions or rules necessary for Beats to communicate with Elasticsearch Service. It’s common to have many Beats dispersed across a network, each installed close to the data that it monitors, and each Beat individually communicating with an Elasticsearch Service deployment. Multiple Beats support multiple servers. Rather than configure each Beat to send its data directly to Elasticsearch Service, you can use {{ls}} to proxy this traffic through one firewall exception or rule.
+* This proxying reduces the firewall exceptions or rules necessary for Beats to communicate with {{ech}}. It’s common to have many Beats dispersed across a network, each installed close to the data that it monitors, and each Beat individually communicating with an {{ech}} deployment. Multiple Beats support multiple servers. Rather than configure each Beat to send its data directly to {{ech}}, you can use {{ls}} to proxy this traffic through one firewall exception or rule.
* This setup is not suitable in simple scenarios when there is only one or a couple of Beats in use. {{ls}} makes the most sense for proxying when there are many Beats.
The configuration in this example makes use of the System module, available for both Filebeat and Metricbeat. Filebeat’s System sends server system log details (that is, login success/failures, sudo *superuser do* command usage, and other key usage details). Metricbeat’s System module sends memory, CPU, disk, and other server usage metrics.
In the following sections you are going to learn how to:
-1. [Get Elasticsearch Service](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md#ec-beats-logstash-trial)
+1. [Get {{ech}}](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md#ec-beats-logstash-trial)
2. [Connect securely](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md#ec-beats-logstash-connect-securely)
3. [Set up {{ls}}](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md#ec-beats-logstash-logstash)
4. [Set up Metricbeat](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md#ec-beats-logstash-metricbeat)
@@ -27,7 +27,7 @@ In the following sections you are going to learn how to:
*Time required: 1 hour*
-## Get Elasticsearch Service [ec-beats-logstash-trial]
+## Get {{ech}} [ec-beats-logstash-trial]
1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
@@ -36,14 +36,14 @@ In the following sections you are going to learn how to:
5. Select **Create deployment** and save your Elastic deployment credentials. You need these credentials later on.
6. When the deployment is ready, click **Continue** and a page of **Setup guides** is displayed. To continue to the deployment homepage click **I’d like to do something else**.
-Prefer not to subscribe to yet another service? You can also get Elasticsearch Service through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
+Prefer not to subscribe to yet another service? You can also get {{ech}} through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
## Connect securely [ec-beats-logstash-connect-securely]
-When connecting to Elasticsearch Service you can use a Cloud ID to specify the connection details. You must pass the Cloud ID that you can find in the cloud console. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+When connecting to {{ech}} you can use a Cloud ID to specify the connection details. You must pass the Cloud ID that you can find in the cloud console. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
-To connect to, stream data to, and issue queries with Elasticsearch Service, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
+To connect to, stream data to, and issue queries with {{ech}}, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
## Set up {{ls}} [ec-beats-logstash-logstash]
@@ -53,7 +53,7 @@ To connect to, stream data to, and issue queries with Elasticsearch Service, you
## Set up Metricbeat [ec-beats-logstash-metricbeat]
-Now that {{ls}} is downloaded and your Elasticsearch Service deployment is set up, you can configure Metricbeat to send operational data to {{ls}}.
+Now that {{ls}} is downloaded and your {{ech}} deployment is set up, you can configure Metricbeat to send operational data to {{ls}}.
Install Metricbeat as close as possible to the service that you want to monitor. For example, if you have four servers with MySQL running, we recommend that you run Metricbeat on each server. This allows Metricbeat to access your service from *localhost*. This setup does not cause any additional network traffic and enables Metricbeat to collect metrics even in the event of network problems. Metrics from multiple Metricbeat instances are combined on the {{ls}} server.
@@ -69,7 +69,7 @@ Metricbeat has [many modules](asciidocalypse://docs/beats/docs/reference/metricb
**Load the Metricbeat Kibana dashboards**
-Metricbeat comes packaged with example dashboards, visualizations, and searches for visualizing Metricbeat data in Kibana. Before you can use the dashboards, you need to create the data view (formerly *index pattern*) *metricbeat-**, and load the dashboards into Kibana. This needs to be done from a local Beats machine that has access to the Elasticsearch Service deployment.
+Metricbeat comes packaged with example dashboards, visualizations, and searches for visualizing Metricbeat data in Kibana. Before you can use the dashboards, you need to create the data view (formerly *index pattern*) *metricbeat-**, and load the dashboards into Kibana. This needs to be done from a local Beats machine that has access to the {{ech}} deployment.
::::{note}
Beginning with Elastic Stack version 8.0, Kibana *index patterns* have been renamed to *data views*. To learn more, check the Kibana [What’s new in 8.0](https://www.elastic.co/guide/en/kibana/8.0/whats-new.html#index-pattern-rename) page.
@@ -85,7 +85,7 @@ sudo ./metricbeat setup \
-E cloud.auth=: <2>
```
-1. Specify the Cloud ID of your Elasticsearch Service deployment. You can include or omit the `:` prefix at the beginning of the Cloud ID. Both versions work fine. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+1. Specify the Cloud ID of your {{ech}} deployment. You can include or omit the `:` prefix at the beginning of the Cloud ID. Both versions work fine. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
2. Specify the username and password provided to you when creating the deployment. Make sure to keep the colon between ** and **.::::{important}
Depending on variables including the installation location, environment and local permissions, you might need to [change the ownership](asciidocalypse://docs/beats/docs/reference/libbeat/config-file-permissions.md) of the metricbeat.yml.
@@ -173,7 +173,7 @@ sudo ./filebeat setup \
-E cloud.auth=: <2>
```
-1. Specify the Cloud ID of your Elasticsearch Service deployment. You can include or omit the `:` prefix at the beginning of the Cloud ID. Both versions work fine. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+1. Specify the Cloud ID of your {{ech}} deployment. You can include or omit the `:` prefix at the beginning of the Cloud ID. Both versions work fine. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
2. Specify the username and password provided to you when creating the deployment. Make sure to keep the colon between ** and **.::::{important}
Depending on variables including the installation location, environment, and local permissions, you might need to [change the ownership](asciidocalypse://docs/beats/docs/reference/libbeat/config-file-permissions.md) of the filebeat.yml.
::::
@@ -361,7 +361,7 @@ Now, let’s try out the {{ls}} pipeline with the Metricbeats and Filebeats conf
## Output {{ls}} data to {{es}} [ec-beats-logstash-elasticsearch]
-In this section, you configure {{ls}} to send the Metricbeat and Filebeat data to {{es}}. You modify the *beats.conf* created earlier, and specify the output credentials needed for our Elasticsearch Service deployment. Then, you start {{ls}} to send the Beats data into {{es}}.
+In this section, you configure {{ls}} to send the Metricbeat and Filebeat data to {{es}}. You modify the *beats.conf* created earlier, and specify the output credentials needed for our {{ech}} deployment. Then, you start {{ls}} to send the Beats data into {{es}}.
1. In your */logstash-/* folder, open *beats.conf* for editing.
2. Replace the *output {}* section of the JSON with the following code:
@@ -379,7 +379,7 @@ In this section, you configure {{ls}} to send the Metricbeat and Filebeat data t
}
```
- 1. Use the Cloud ID of your Elasticsearch Service deployment. You can include or omit the `:` prefix at the beginning of the Cloud ID. Both versions work fine. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+ 1. Use the Cloud ID of your {{ech}} deployment. You can include or omit the `:` prefix at the beginning of the Cloud ID. Both versions work fine. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
2. the default usename is `elastic`. It is not recommended to use the `elastic` account for ingesting data as this is a superuser. We recommend using a user with reduced permissions, or an API Key with permissions specific to the indices or data streams that will be written to. Check the [Grant access to secured resources](asciidocalypse://docs/beats/docs/reference/filebeat/feature-roles.md) for information on the writer role and API Keys. Use the password provided when you created the deployment if using the `elastic` user, or the password used when creating a new ingest user with the roles specified in the [Grant access to secured resources](asciidocalypse://docs/beats/docs/reference/filebeat/feature-roles.md) documentation.
@@ -392,14 +392,14 @@ In this section, you configure {{ls}} to send the Metricbeat and Filebeat data t
If you use Metricbeat version 8.13.1, the index created in {{es}} is named *metricbeat-8.13.1*. Similarly, using the 8.13.1 version of Filebeat, the {{es}} index is named *filebeat-8.13.1*.
- * *cloud_id*: This is the ID that uniquely identifies your Elasticsearch Service deployment.
- * *ssl*: This should be set to `true` so that Secure Socket Layer (SSL) certificates are used for secure communication between {{ls}} and your Elasticsearch Service deployment.
- * *ilm_enabled*: Enables and disables Elasticsearch Service [index lifecycle management](../../../manage-data/lifecycle/index-lifecycle-management.md).
+ * *cloud_id*: This is the ID that uniquely identifies your {{ech}} deployment.
+ * *ssl*: This should be set to `true` so that Secure Socket Layer (SSL) certificates are used for secure communication between {{ls}} and your {{ech}} deployment.
+ * *ilm_enabled*: Enables and disables {{ech}} [index lifecycle management](../../../manage-data/lifecycle/index-lifecycle-management.md).
* *api_key*: If you choose to use an API key to authenticate (as discussed in the next step), you can provide it here.
-3. **Optional**: For additional security, you can generate an {{es}} API key through the Elasticsearch Service console and configure {{ls}} to use the new key to connect securely to the Elasticsearch Service.
+3. **Optional**: For additional security, you can generate an {{es}} API key through the {{ecloud}} Console and configure {{ls}} to use the new key to connect securely to {{ecloud}}.
- 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 the deployment and go to **☰** > **Management** > **Dev Tools**.
3. Enter the following:
@@ -467,7 +467,7 @@ In this section, you configure {{ls}} to send the Metricbeat and Filebeat data t
./filebeat -c filebeat.yml
```
-7. {{ls}} now outputs the Filebeat and Metricbeat data to your Elasticsearch Service instance.
+7. {{ls}} now outputs the Filebeat and Metricbeat data to your {{ech}} instance.
::::{note}
In this guide, you manually launch each of the Elastic stack applications through the command line interface. In production, you may prefer to configure {{ls}}, Metricbeat, and Filebeat to run as System Services. Check the following pages for the steps to configure each application to run as a service:
@@ -482,7 +482,7 @@ In this guide, you manually launch each of the Elastic stack applications throug
## View data in Kibana [ec-beats-logstash-view-kibana]
-In this section, you log into Elasticsearch Service, open Kibana, and view the Kibana dashboards populated with our Metricbeat and Filebeat data.
+In this section, you log into {{ech}}, open Kibana, and view the Kibana dashboards populated with our Metricbeat and Filebeat data.
**View the Metricbeat dashboard**
diff --git a/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-db-logstash.md b/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-db-logstash.md
index 3b4f7a611..b50fba317 100644
--- a/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-db-logstash.md
+++ b/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-db-logstash.md
@@ -1,6 +1,6 @@
-# Ingest data from a relational database into Elasticsearch Service [ec-getting-started-search-use-cases-db-logstash]
+# Ingest data from a relational database into {{ech}} [ec-getting-started-search-use-cases-db-logstash]
-This guide explains how to ingest data from a relational database into Elasticsearch Service through [Logstash](asciidocalypse://docs/logstash/docs/reference/index.md), using the Logstash [JDBC input plugin](asciidocalypse://docs/logstash/docs/reference/plugins-inputs-jdbc.md). It demonstrates how Logstash can be used to efficiently copy records and to receive updates from a relational database, and then send them into {{es}} in an Elasticsearch Service deployment.
+This guide explains how to ingest data from a relational database into {{ech}} through [Logstash](asciidocalypse://docs/logstash/docs/reference/index.md), using the Logstash [JDBC input plugin](asciidocalypse://docs/logstash/docs/reference/plugins-inputs-jdbc.md). It demonstrates how Logstash can be used to efficiently copy records and to receive updates from a relational database, and then send them into {{es}} in an {{ech}} deployment.
The code and methods presented here have been tested with MySQL. They should work with other relational databases.
@@ -9,7 +9,7 @@ The Logstash Java Database Connectivity (JDBC) input plugin enables you to pull
This document presents:
1. [Prerequisites](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md#ec-db-logstash-prerequisites)
-2. [Get Elasticsearch Service](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md#ec-db-logstash-trial)
+2. [Get {{ech}}](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md#ec-db-logstash-trial)
3. [Connect securely](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md#ec-db-logstash-connect-securely)
4. [Get the MySQL JDBC driver](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md#ec-db-logstash-driver)
5. [Prepare a source MySQL database](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md#ec-db-logstash-database)
@@ -25,7 +25,7 @@ This document presents:
For this tutorial you need a source MySQL instance for Logstash to read from. A free version of MySQL is available from the [MySQL Community Server section](https://dev.mysql.com/downloads/mysql/) of the MySQL Community Downloads site.
-## Get Elasticsearch Service [ec-db-logstash-trial]
+## Get {{ech}} [ec-db-logstash-trial]
1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
@@ -34,14 +34,14 @@ For this tutorial you need a source MySQL instance for Logstash to read from. A
5. Select **Create deployment** and save your Elastic deployment credentials. You need these credentials later on.
6. When the deployment is ready, click **Continue** and a page of **Setup guides** is displayed. To continue to the deployment homepage click **I’d like to do something else**.
-Prefer not to subscribe to yet another service? You can also get Elasticsearch Service through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
+Prefer not to subscribe to yet another service? You can also get {{ech}} through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
## Connect securely [ec-db-logstash-connect-securely]
-When connecting to Elasticsearch Service you can use a Cloud ID to specify the connection details. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+When connecting to {{ech}} you can use a Cloud ID to specify the connection details. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
-To connect to, stream data to, and issue queries with Elasticsearch Service, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
+To connect to, stream data to, and issue queries with {{ech}}, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
1. [Download](https://www.elastic.co/downloads/logstash) and unpack Logstash on the local machine that hosts MySQL or another machine granted access to the MySQL machine.
@@ -56,7 +56,7 @@ The Logstash JDBC input plugin does not include any database connection drivers.
## Prepare a source MySQL database [ec-db-logstash-database]
-Let’s look at a simple database from which you’ll import data and send it to Elasticsearch Service. This example uses a MySQL database with timestamped records. The timestamps enable you to determine easily what’s changed in the database since the most recent data transfer to Elasticsearch Service.
+Let’s look at a simple database from which you’ll import data and send it to {{ech}}. This example uses a MySQL database with timestamped records. The timestamps enable you to determine easily what’s changed in the database since the most recent data transfer to {{ech}}.
### Consider the database structure and design [ec-db-logstash-database-structure]
@@ -269,7 +269,7 @@ Let’s set up a sample Logstash input pipeline to ingest data from your new JDB
## Output to Elasticsearch [ec-db-logstash-output]
-In this section, we configure Logstash to send the MySQL data to Elasticsearch. We modify the configuration file created in the section [Configure a Logstash pipeline with the JDBC input plugin](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md#ec-db-logstash-pipeline) so that data is output directly to Elasticsearch. We start Logstash to send the data, and then log into Elasticsearch Service to verify the data in Kibana.
+In this section, we configure Logstash to send the MySQL data to Elasticsearch. We modify the configuration file created in the section [Configure a Logstash pipeline with the JDBC input plugin](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md#ec-db-logstash-pipeline) so that data is output directly to Elasticsearch. We start Logstash to send the data, and then log into {{ech}} to verify the data in Kibana.
1. Open the `jdbc.conf` file in the Logstash folder for editing.
2. Update the output section with the one that follows:
@@ -287,7 +287,7 @@ In this section, we configure Logstash to send the MySQL data to Elasticsearch.
}
```
- 1. Use the Cloud ID of your Elasticsearch Service deployment. You can include or omit the `:` prefix at the beginning of the Cloud ID. Both versions work fine. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+ 1. Use the Cloud ID of your {{ech}} deployment. You can include or omit the `:` prefix at the beginning of the Cloud ID. Both versions work fine. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
2. the default username is `elastic`. It is not recommended to use the `elastic` account for ingesting data as this is a superuser. We recommend using a user with reduced permissions, or an API Key with permissions specific to the indices or data streams that will be written to. Check [Configuring security in Logstash](asciidocalypse://docs/logstash/docs/reference/secure-connection.md) for information on roles and API Keys. Use the password provided when you created the deployment if using the `elastic` user, or the password used when creating a new ingest user with the roles specified in the [Configuring security in Logstash](asciidocalypse://docs/logstash/docs/reference/secure-connection.md) documentation.
@@ -299,9 +299,9 @@ In this section, we configure Logstash to send the MySQL data to Elasticsearch.
api_key
: If you choose to use an API key to authenticate (as discussed in the next step), you can provide it here.
-3. **Optional**: For additional security, you can generate an Elasticsearch API key through the Elasticsearch Service console and configure Logstash to use the new key to connect securely to Elasticsearch Service.
+3. **Optional**: For additional security, you can generate an Elasticsearch API key through the {{ecloud}} Console and configure Logstash to use the new key to connect securely to {{ech}}.
- 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 the deployment name and go to **☰** > **Management** > **Dev Tools**.
3. Enter the following:
@@ -375,9 +375,9 @@ In this section, we configure Logstash to send the MySQL data to Elasticsearch.
bin/logstash -f jdbc.conf
```
-6. Logstash outputs the MySQL data to your Elasticsearch Service deployment. Let’s take a look in Kibana and verify that data:
+6. Logstash outputs the MySQL data to your {{ech}} deployment. Let’s take a look in Kibana and verify that data:
- 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 the deployment and go to **☰** > **Management** > **Dev Tools**
3. Copy and paste the following API GET request into the Console pane, and then click **▶**. This queries all records in the new `rdbms_idx` index.
diff --git a/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-node-logs.md b/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-node-logs.md
index 8d74c9113..c1263dec1 100644
--- a/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-node-logs.md
+++ b/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-node-logs.md
@@ -1,11 +1,11 @@
# Ingest logs from a Node.js web application using Filebeat [ec-getting-started-search-use-cases-node-logs]
-This guide demonstrates how to ingest logs from a Node.js web application and deliver them securely into an Elasticsearch Service deployment. You’ll set up Filebeat to monitor a JSON-structured log file that has standard Elastic Common Schema (ECS) formatted fields, and you’ll then view real-time visualizations of the log events in Kibana as requests are made to the Node.js server. While Node.js is used for this example, this approach to monitoring log output is applicable across many client types. Check the list of [available ECS logging plugins](asciidocalypse://docs/ecs-logging/docs/reference/intro.md#_get_started).
+This guide demonstrates how to ingest logs from a Node.js web application and deliver them securely into an {{ech}} deployment. You’ll set up Filebeat to monitor a JSON-structured log file that has standard Elastic Common Schema (ECS) formatted fields, and you’ll then view real-time visualizations of the log events in Kibana as requests are made to the Node.js server. While Node.js is used for this example, this approach to monitoring log output is applicable across many client types. Check the list of [available ECS logging plugins](asciidocalypse://docs/ecs-logging/docs/reference/intro.md#_get_started).
This guide presents:
1. [Prerequisites](../../../manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-nodejs-web-application-using-filebeat.md#ec-node-logs-prerequisites)
-2. [Get Elasticsearch Service](../../../manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-nodejs-web-application-using-filebeat.md#ec-node-logs-trial)
+2. [Get {{ech}}](../../../manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-nodejs-web-application-using-filebeat.md#ec-node-logs-trial)
3. [Connect securely](../../../manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-nodejs-web-application-using-filebeat.md#ec-node-logs-connect-securely)
4. [Create a Node.js web application with logging](../../../manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-nodejs-web-application-using-filebeat.md#ec-node-logs-create-server-script)
5. [Create a Node.js HTTP request application](../../../manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-nodejs-web-application-using-filebeat.md#ec-node-logs-create-request-script)
@@ -47,7 +47,7 @@ For the three following packages, you can create a working directory to install
-## Get Elasticsearch Service [ec-node-logs-trial]
+## Get {{ech}} [ec-node-logs-trial]
1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
@@ -56,14 +56,14 @@ For the three following packages, you can create a working directory to install
5. Select **Create deployment** and save your Elastic deployment credentials. You need these credentials later on.
6. When the deployment is ready, click **Continue** and a page of **Setup guides** is displayed. To continue to the deployment homepage click **I’d like to do something else**.
-Prefer not to subscribe to yet another service? You can also get Elasticsearch Service through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
+Prefer not to subscribe to yet another service? You can also get {{ech}} through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
## Connect securely [ec-node-logs-connect-securely]
-When connecting to Elasticsearch Service you can use a Cloud ID to specify the connection details. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+When connecting to {{ech}} you can use a Cloud ID to specify the connection details. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
-To connect to, stream data to, and issue queries with Elasticsearch Service, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
+To connect to, stream data to, and issue queries with {{ech}}, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
## Create a Node.js web application with logging [ec-node-logs-create-server-script]
@@ -227,13 +227,13 @@ In this step, you’ll create a Node.js application that sends HTTP requests to
## Set up Filebeat [ec-node-logs-filebeat]
-Filebeat offers a straightforward, easy to configure way to monitor your Node.js log files and port the log data into Elasticsearch Service.
+Filebeat offers a straightforward, easy to configure way to monitor your Node.js log files and port the log data into {{ech}}.
**Get Filebeat**
[Download Filebeat](https://www.elastic.co/downloads/beats/filebeat) and unpack it on the local server from which you want to collect data.
-**Configure Filebeat to access Elasticsearch Service**
+**Configure Filebeat to access {{ech}}**
In */filebeat-/* (where ** is the directory where Filebeat is installed and ** is the Filebeat version number), open the *filebeat.yml* configuration file for editing.
@@ -351,9 +351,9 @@ The Filebeat data view is now available in Elasticsearch. To verify:
**Optional: Use an API key to authenticate**
-For additional security, instead of using basic authentication you can generate an Elasticsearch API key through the Elasticsearch Service console, and then configure Filebeat to use the new key to connect securely to the Elasticsearch Service deployment.
+For additional security, instead of using basic authentication you can generate an Elasticsearch API key through the {{ecloud}} Console, and then configure Filebeat to use the new key to connect securely to the {{ech}} deployment.
-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 the deployment name and go to **☰** > **Management** > **Dev Tools**.
3. Enter the following request:
@@ -452,9 +452,9 @@ node webrequests.js
Let the script run for a few minutes and maybe brew up a quick coffee or tea ☕ . After that, make sure that the *log.json* file is generated as expected and is populated with several log entries.
-**Verify the log entries in Elasticsearch Service**
+**Verify the log entries in {{ech}}**
-The next step is to confirm that the log data has successfully found it’s way into Elasticsearch Service.
+The next step is to confirm that the log data has successfully found it’s way into {{ech}}.
1. [Login to Kibana](../../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
2. Open the {{kib}} main menu and select **Management** > **{{kib}}** > **Data views**.
@@ -517,5 +517,5 @@ You can add titles to the visualizations, resize and position them as you like,
2. As your final step, remember to stop Filebeat, the Node.js web server, and the client. Enter *CTRL + C* in the terminal window for each application to stop them.
-You now know how to monitor log files from a Node.js web application, deliver the log event data securely into an Elasticsearch Service deployment, and then visualize the results in Kibana in real time. Consult the [Filebeat documentation](asciidocalypse://docs/beats/docs/reference/filebeat/filebeat-overview.md) to learn more about the ingestion and processing options available for your data. You can also explore our [documentation](../../../manage-data/ingest.md) to learn all about working in Elasticsearch Service.
+You now know how to monitor log files from a Node.js web application, deliver the log event data securely into an {{ech}} deployment, and then visualize the results in Kibana in real time. Consult the [Filebeat documentation](asciidocalypse://docs/beats/docs/reference/filebeat/filebeat-overview.md) to learn more about the ingestion and processing options available for your data. You can also explore our [documentation](../../../manage-data/ingest.md) to learn all about working in {{ech}}.
diff --git a/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-python-logs.md b/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-python-logs.md
index bdeec54a6..5ee8ccf43 100644
--- a/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-python-logs.md
+++ b/raw-migrated-files/cloud/cloud/ec-getting-started-search-use-cases-python-logs.md
@@ -1,6 +1,6 @@
# Ingest logs from a Python application using Filebeat [ec-getting-started-search-use-cases-python-logs]
-This guide demonstrates how to ingest logs from a Python application and deliver them securely into an Elasticsearch Service deployment. You’ll set up Filebeat to monitor a JSON-structured log file that has standard Elastic Common Schema (ECS) formatted fields, and you’ll then view real-time visualizations of the log events in {{kib}} as they occur. While Python is used for this example, this approach to monitoring log output is applicable across many client types. Check the list of [available ECS logging plugins](asciidocalypse://docs/ecs-logging/docs/reference/intro.md).
+This guide demonstrates how to ingest logs from a Python application and deliver them securely into an {{ech}} deployment. You’ll set up Filebeat to monitor a JSON-structured log file that has standard Elastic Common Schema (ECS) formatted fields, and you’ll then view real-time visualizations of the log events in {{kib}} as they occur. While Python is used for this example, this approach to monitoring log output is applicable across many client types. Check the list of [available ECS logging plugins](asciidocalypse://docs/ecs-logging/docs/reference/intro.md).
You are going to learn how to:
@@ -23,7 +23,7 @@ python -m pip install ecs-logging
```
-## Get Elasticsearch Service [ec_get_elasticsearch_service_3]
+## Get {{ech}} [ec_get_elasticsearch_service_3]
1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
@@ -32,14 +32,14 @@ python -m pip install ecs-logging
5. Select **Create deployment** and save your Elastic deployment credentials. You need these credentials later on.
6. When the deployment is ready, click **Continue** and a page of **Setup guides** is displayed. To continue to the deployment homepage click **I’d like to do something else**.
-Prefer not to subscribe to yet another service? You can also get Elasticsearch Service through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
+Prefer not to subscribe to yet another service? You can also get {{ech}} through [AWS, Azure, and GCP marketplaces](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md).
## Connect securely [ec_connect_securely_2]
-When connecting to Elasticsearch Service you can use a Cloud ID to specify the connection details. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
+When connecting to {{ech}} you can use a Cloud ID to specify the connection details. Find your Cloud ID by going to the {{kib}} main menu and selecting Management > Integrations, and then selecting View deployment details.
-To connect to, stream data to, and issue queries with Elasticsearch Service, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
+To connect to, stream data to, and issue queries with {{ech}}, you need to think about authentication. Two authentication mechanisms are supported, *API key* and *basic authentication*. Here, to get you started quickly, we’ll show you how to use basic authentication, but you can also generate API keys as shown later on. API keys are safer and preferred for production environments.
## Create a Python script with logging [ec-python-logs-create-script]
@@ -121,13 +121,13 @@ In this step, you’ll create a Python script that generates logs in JSON format
## Set up Filebeat [ec-python-logs-filebeat]
-Filebeat offers a straightforward, easy to configure way to monitor your Python log files and port the log data into Elasticsearch Service.
+Filebeat offers a straightforward, easy to configure way to monitor your Python log files and port the log data into {{ech}}.
**Get Filebeat**
[Download Filebeat](https://www.elastic.co/downloads/beats/filebeat) and unpack it on the local server from which you want to collect data.
-**Configure Filebeat to access Elasticsearch Service**
+**Configure Filebeat to access {{ech}}**
In */filebeat-/* (where ** is the directory where Filebeat is installed and ** is the Filebeat version number), open the *filebeat.yml* configuration file for editing.
@@ -247,9 +247,9 @@ Beginning with Elastic Stack version 8.0, Kibana *index patterns* have been rena
**Optional: Use an API key to authenticate**
-For additional security, instead of using basic authentication you can generate an Elasticsearch API key through the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), and then configure Filebeat to use the new key to connect securely to the Elasticsearch Service deployment.
+For additional security, instead of using basic authentication you can generate an Elasticsearch API key through the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), and then configure Filebeat to use the new key to connect securely to the {{ech}} deployment.
-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 the deployment name and go to **☰** > **Management** > **Dev Tools**.
3. Enter the following request:
@@ -342,9 +342,9 @@ python elvis.py
Let the script run for a few minutes and maybe brew up a quick coffee or tea ☕ . After that, make sure that the *elvis.json* file is generated as expected and is populated with several log entries.
-**Verify the log entries in Elasticsearch Service**
+**Verify the log entries in {{ech}}**
-The next step is to confirm that the log data has successfully found it’s way into Elasticsearch Service.
+The next step is to confirm that the log data has successfully found it’s way into {{ech}}.
1. [Login to Kibana](../../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
2. Open the {{kib}} main menu and select **Management** > **{{kib}}** > **Data views**.
@@ -408,5 +408,5 @@ You can add titles to the visualizations, resize and position them as you like,
2. As your final step, remember to stop Filebeat and the Python script. Enter *CTRL + C* in both your Filebeat terminal and in your `elvis.py` terminal.
-You now know how to monitor log files from a Python application, deliver the log event data securely into an Elasticsearch Service deployment, and then visualize the results in Kibana in real time. Consult the [Filebeat documentation](asciidocalypse://docs/beats/docs/reference/filebeat/filebeat-overview.md) to learn more about the ingestion and processing options available for your data. You can also explore our [documentation](../../../manage-data/ingest.md) to learn all about working in Elasticsearch Service.
+You now know how to monitor log files from a Python application, deliver the log event data securely into an {{ech}} deployment, and then visualize the results in Kibana in real time. Consult the [Filebeat documentation](asciidocalypse://docs/beats/docs/reference/filebeat/filebeat-overview.md) to learn more about the ingestion and processing options available for your data. You can also explore our [documentation](../../../manage-data/ingest.md) to learn all about working in {{ech}}.
diff --git a/raw-migrated-files/cloud/cloud/ec-getting-started.md b/raw-migrated-files/cloud/cloud/ec-getting-started.md
index cb03a884f..bccf92ab6 100644
--- a/raw-migrated-files/cloud/cloud/ec-getting-started.md
+++ b/raw-migrated-files/cloud/cloud/ec-getting-started.md
@@ -1,4 +1,4 @@
-# Introducing Elasticsearch Service [ec-getting-started]
+# Introducing {{ech}} [ec-getting-started]
::::{note}
Are you just discovering Elastic or are unfamiliar with the core concepts of the Elastic Stack? Would you like to be guided through the very first steps and understand how Elastic can help you? Try one of our [getting started guides](https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/getting-started-guides.html) first.
@@ -6,11 +6,11 @@ Are you just discovering Elastic or are unfamiliar with the core concepts of the
-## What is Elasticsearch Service? [ec_what_is_elasticsearch_service]
+## What is {{ech}}? [ec_what_is_elasticsearch_service]
**The Elastic Stack, managed through {{ecloud}} deployments.**
-Elasticsearch Service allows you to manage one or more instances of the Elastic Stack through **deployments**. These deployments are hosted on {{ecloud}}, through the cloud provider and regions of your choice, and are tied to your organization account.
+{{ech}} allows you to manage one or more instances of the Elastic Stack through **deployments**. These deployments are hosted on {{ecloud}}, through the cloud provider and regions of your choice, and are tied to your organization account.
A *deployment* helps you manage an Elasticsearch cluster and instances of other Elastic products, like Kibana or APM instances, in one place. Spin up, scale, upgrade, and delete your Elastic Stack products without having to manage each one separately. In a deployment, everything works together.
@@ -44,7 +44,7 @@ These solutions help you accomplish your use cases: Ingest data into the deploym
Of course, you can choose to follow your own path and use Elastic components available in your deployment to ingest, visualize, and analyze your data independently from solutions.
-## How to operate Elasticsearch Service? [ec_how_to_operate_elasticsearch_service]
+## How to operate {{ech}}? [ec_how_to_operate_elasticsearch_service]
**Where to start?**
@@ -68,10 +68,10 @@ Control which users and services can access your deployments by [securing your e
**Monitor your deployments and keep them healthy**
-Elasticsearch Service provides several ways to monitor your deployments, anticipate and prevent issues, or fix them when they occur. Check [Monitoring your deployment](../../../deploy-manage/monitor/stack-monitoring.md) to get more details.
+{{ech}} provides several ways to monitor your deployments, anticipate and prevent issues, or fix them when they occur. Check [Monitoring your deployment](../../../deploy-manage/monitor/stack-monitoring.md) to get more details.
**And then?**
-Now is the time for you to work with your data. The content of the Elasticsearch Service section helps you get your environment up and ready to handle your data the way you need. You can always adjust your deployments and their configuration as your usage evolves over time.
+Now is the time for you to work with your data. The content of the {{ecloud}} section helps you get your environment up and ready to handle your data the way you need. You can always adjust your deployments and their configuration as your usage evolves over time.
To get the most out of the solutions that the Elastic Stack offers, [log in to {{ecloud}}](https://cloud.elastic.co) or [browse the documentation](https://www.elastic.co/docs).
diff --git a/raw-migrated-files/cloud/cloud/ec-ingest-guides.md b/raw-migrated-files/cloud/cloud/ec-ingest-guides.md
index 0b163f75c..43a87d82c 100644
--- a/raw-migrated-files/cloud/cloud/ec-ingest-guides.md
+++ b/raw-migrated-files/cloud/cloud/ec-ingest-guides.md
@@ -2,23 +2,23 @@
The following tutorials demonstrate how you can use the Elasticsearch language clients to ingest data from an application.
-[Ingest data with Node.js on Elasticsearch Service](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-with-nodejs-on-elasticsearch-service.md)
-: Get Node.js application data securely into Elasticsearch Service, where it can then be searched and modified.
+[Ingest data with Node.js on {{ech}}](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-with-nodejs-on-elasticsearch-service.md)
+: Get Node.js application data securely into {{ech}}, where it can then be searched and modified.
-[Ingest data with Python on Elasticsearch Service](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-with-python-on-elasticsearch-service.md)
-: Get Python application data securely into Elasticsearch Service, where it can then be searched and modified.
+[Ingest data with Python on {{ech}}](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-with-python-on-elasticsearch-service.md)
+: Get Python application data securely into {{ech}}, where it can then be searched and modified.
-[Ingest data from Beats to Elasticsearch Service with Logstash as a proxy](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md)
-: Get server metrics or other types of data from Filebeat and Metricbeat into Logstash as an intermediary, and then send that data to Elasticsearch Service. Using Logstash as a proxy limits your Elastic Stack traffic through a single, external-facing firewall exception or rule.
+[Ingest data from Beats to {{ech}} with Logstash as a proxy](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-beats-to-elasticsearch-service-with-logstash-as-proxy.md)
+: Get server metrics or other types of data from Filebeat and Metricbeat into Logstash as an intermediary, and then send that data to {{ech}}. Using Logstash as a proxy limits your Elastic Stack traffic through a single, external-facing firewall exception or rule.
-[Ingest data from a relational database into Elasticsearch Service](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md)
-: Get data from a relational database into Elasticsearch Service using the Logstash JDBC input plugin. Logstash can be used as an efficient way to copy records and to receive updates from a relational database as changes happen, and then send the new data to a deployment.
+[Ingest data from a relational database into {{ech}}](../../../manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md)
+: Get data from a relational database into {{ech}} using the Logstash JDBC input plugin. Logstash can be used as an efficient way to copy records and to receive updates from a relational database as changes happen, and then send the new data to a deployment.
[Ingest logs from a Python application using Filebeat](../../../manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-python-application-using-filebeat.md)
-: Get logs from a Python application and deliver them securely into an Elasticsearch Service deployment. You’ll set up Filebeat to monitor an ECS-formatted log file, and then view real-time visualizations of the log events in Kibana as they occur.
+: Get logs from a Python application and deliver them securely into an {{ech}} deployment. You’ll set up Filebeat to monitor an ECS-formatted log file, and then view real-time visualizations of the log events in Kibana as they occur.
[Ingest logs from a Node.js web application using Filebeat](../../../manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-nodejs-web-application-using-filebeat.md)
-: Get HTTP request logs from a Node.js web application and deliver them securely into an Elasticsearch Service deployment. You’ll set up Filebeat to monitor an ECS-formatted log file and then view real-time visualizations of the log events as HTTP requests occur on your Node.js web server.
+: Get HTTP request logs from a Node.js web application and deliver them securely into an {{ech}} deployment. You’ll set up Filebeat to monitor an ECS-formatted log file and then view real-time visualizations of the log events as HTTP requests occur on your Node.js web server.
::::{tip}
You can use [Elasticsearch ingest pipelines](../../../manage-data/ingest/transform-enrich/ingest-pipelines.md) to preprocess incoming data. This enables you to optimize how your data is indexed, and simplifies tasks such as extracting error codes from a log file and mapping geographic locations to IP addresses.
diff --git a/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md b/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md
index a102997d5..d9fa25299 100644
--- a/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md
+++ b/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md
@@ -22,10 +22,10 @@ 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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. In the **APM** section, select **Edit user settings**. (For existing deployments with user settings, you may have to expand the **Edit apm-server.yml** caret instead.)
@@ -33,14 +33,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 by {{ech}}, 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).
diff --git a/raw-migrated-files/cloud/cloud/ec-manage-appsearch-settings.md b/raw-migrated-files/cloud/cloud/ec-manage-appsearch-settings.md
index 6d95d5c85..f74c36e76 100644
--- a/raw-migrated-files/cloud/cloud/ec-manage-appsearch-settings.md
+++ b/raw-migrated-files/cloud/cloud/ec-manage-appsearch-settings.md
@@ -9,10 +9,10 @@ Some settings that could break your cluster if set incorrectly are blocked. Revi
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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. At the bottom of the **App Search** section, expand the **User settings overrides** caret.
@@ -20,14 +20,14 @@ To add user settings:
6. Select **Save changes**.
::::{note}
-If a setting is not supported by Elasticsearch Service, you get an error message when you try to save.
+If a setting is not supported by {{ech}}, you get an error message when you try to save.
::::
## Supported App Search settings [ec-appsearch-settings]
-Elasticsearch Service supports the following App Search settings.
+{{ech}} supports the following App Search settings.
`app_search.auth.source`
: The origin of authenticated App Search users. Options are `standard`, `elasticsearch-native`, and `elasticsearch-saml`.
diff --git a/raw-migrated-files/cloud/cloud/ec-manage-enterprise-search-settings.md b/raw-migrated-files/cloud/cloud/ec-manage-enterprise-search-settings.md
index b6b1c5a56..28c7c169a 100644
--- a/raw-migrated-files/cloud/cloud/ec-manage-enterprise-search-settings.md
+++ b/raw-migrated-files/cloud/cloud/ec-manage-enterprise-search-settings.md
@@ -6,14 +6,14 @@ Enterprise Search is not available in {{stack}} 9.0+.
Change how Enterprise Search runs by providing your own user settings. User settings are appended to the `ent-search.yml` configuration file for your instance and provide custom configuration options.
-Refer to the [Configuration settings reference](https://www.elastic.co/guide/en/enterprise-search/current/configuration.html#configuration-file) in the Enterprise Search documentation for a full list of configuration settings. Settings supported on Elasticsearch Service are indicated by an {{ecloud}} icon (). Be sure to refer to the documentation version that matches the Elastic Stack version used in your deployment.
+Refer to the [Configuration settings reference](https://www.elastic.co/guide/en/enterprise-search/current/configuration.html#configuration-file) in the Enterprise Search documentation for a full list of configuration settings. Settings supported on {{ech}} are indicated by an {{ecloud}} icon (). Be sure to refer to the documentation version that matches the Elastic Stack version used in your deployment.
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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. In the **Enterprise Search** section, select **Edit user settings**. For deployments with existing user settings, you may have to expand the **Edit enterprise-search.yml** caret instead.
@@ -21,7 +21,7 @@ To add user settings:
6. Select **Save changes**.
::::{note}
-If a setting is not supported by Elasticsearch Service, an error message displays when you try to save your settings.
+If a setting is not supported by {{ech}}, an error message displays when you try to save your settings.
::::
diff --git a/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md b/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md
index d6c76d585..059023584 100644
--- a/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md
+++ b/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md
@@ -1,6 +1,6 @@
# Edit Kibana user settings [ec-manage-kibana-settings]
-Elasticsearch Service supports most of the standard Kibana and X-Pack settings. Through a YAML editor in the console, you can append Kibana properties to the `kibana.yml` file. Your changes to the configuration file are read on startup.
+{{ech}} supports most of the standard Kibana and X-Pack settings. Through a YAML editor in the console, you can append Kibana properties to the `kibana.yml` file. Your changes to the configuration file are read on startup.
::::{important}
Be aware that some settings that could break your cluster if set incorrectly and that the syntax might change between major versions. Before upgrading, be sure to review the full list of the [latest Kibana settings and syntax](asciidocalypse://docs/kibana/docs/reference/configuration-reference/general-settings.md).
@@ -9,10 +9,10 @@ Be aware that some settings that could break your cluster if set incorrectly and
To change Kibana 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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. In the **Kibana** section, select **Edit user settings**. (For deployments with existing user settings, you may have to expand the **Edit kibana.yml** caret instead.)
@@ -22,7 +22,7 @@ To change Kibana settings:
Saving your changes initiates a configuration plan change that restarts Kibana automatically for you.
::::{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 by {{ech}}, you will get an error message when you try to save.
::::
@@ -222,7 +222,7 @@ If a setting is not supported by Elasticsearch Service, you will get an error me
### SAML settings [ec_saml_settings]
-If you are using SAML to secure your clusters, these settings are supported in Elasticsearch Service.
+If you are using SAML to secure your clusters, these settings are supported in {{ech}}.
To learn more, refer to [configuring Kibana to use SAML](/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md#saml-configure-kibana).
@@ -285,7 +285,7 @@ The following additional setting is supported:
### OpenID Connect [ec_openid_connect]
-If you are using OpenID Connect to secure your clusters, these settings are supported in Elasticsearch Service.
+If you are using OpenID Connect to secure your clusters, these settings are supported in {{ech}}.
`xpack.security.authc.providers.oidc..order`
: Specifies order of the OpenID Connect authentication provider in the authentication chain.
@@ -304,7 +304,7 @@ To learn more, check [configuring Kibana to use OpenID Connect](/deploy-manage/u
### Anonymous authentication [ec_anonymous_authentication]
-If you want to allow anonymous authentication in Kibana, these settings are supported in Elasticsearch Service. To learn more on how to enable anonymous access, check [Enabling anonymous access](/deploy-manage/users-roles/cluster-or-deployment-auth/anonymous-access.md) and [Configuring Kibana to use anonymous authentication](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md#anonymous-authentication).
+If you want to allow anonymous authentication in Kibana, these settings are supported in {{ech}}. To learn more on how to enable anonymous access, check [Enabling anonymous access](/deploy-manage/users-roles/cluster-or-deployment-auth/anonymous-access.md) and [Configuring Kibana to use anonymous authentication](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md#anonymous-authentication).
#### Supported versions before 8.0.0 [ec_supported_versions_before_8_0_0]
diff --git a/raw-migrated-files/cloud/cloud/ec-metrics-memory-pressure.md b/raw-migrated-files/cloud/cloud/ec-metrics-memory-pressure.md
index 38a3d326a..33a8d5182 100644
--- a/raw-migrated-files/cloud/cloud/ec-metrics-memory-pressure.md
+++ b/raw-migrated-files/cloud/cloud/ec-metrics-memory-pressure.md
@@ -25,7 +25,7 @@ If the performance impact from high memory pressure is not acceptable, you need
## Increase the deployment size [ec_increase_the_deployment_size]
-Scaling with Elasticsearch Service is easy: simply log in to the Elasticsearch Service console, select your deployment, select edit, and either increase the number of zones or the size per zone.
+Scaling with {{ech}} is easy: simply log in to the {{ecloud}} Console, select your deployment, select edit, and either increase the number of zones or the size per zone.
## Reduce the workload [ec_reduce_the_workload]
diff --git a/raw-migrated-files/cloud/cloud/ec-monitoring-setup.md b/raw-migrated-files/cloud/cloud/ec-monitoring-setup.md
index b7b73bdf4..13d58758a 100644
--- a/raw-migrated-files/cloud/cloud/ec-monitoring-setup.md
+++ b/raw-migrated-files/cloud/cloud/ec-monitoring-setup.md
@@ -9,7 +9,7 @@ These steps are helpful to set yourself up for success by making monitoring read
As you manage, monitor, and troubleshoot your deployment, make sure you have an understanding of the [shared responsibilities](https://www.elastic.co/cloud/shared-responsibility) between Elastic and yourself, so you know what you need to do to keep your deployments running smoothly.
-You may also consider subscribing to incident notices reported on the Elasticsearch Service [status page](https://status.elastic.co).
+You may also consider subscribing to incident notices reported on the {{ecloud}} [status page](https://status.elastic.co).
## Enable logs and metrics [ec_enable_logs_and_metrics]
@@ -59,7 +59,7 @@ To learn more about what [Elasticsearch monitoring metrics](/deploy-manage/monit
:alt: Node tab in Kibana under Stack Monitoring
:::
-Some [performance metrics](../../../deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md) are also available directly in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu:
+Some [performance metrics](../../../deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md) are also available directly in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu:
:::{image} ../../../images/cloud-ec-ce-monitoring-performance.png
:alt: Performance page of the Elastic Cloud console
diff --git a/raw-migrated-files/cloud/cloud/ec-monitoring.md b/raw-migrated-files/cloud/cloud/ec-monitoring.md
index 0d0ac69f2..2b01e9b48 100644
--- a/raw-migrated-files/cloud/cloud/ec-monitoring.md
+++ b/raw-migrated-files/cloud/cloud/ec-monitoring.md
@@ -32,7 +32,7 @@ For {{stack}} versions 8.4 and later, the deployment **Health** page provides de
To view the health for a deployment:
-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. On the **Deployments** page, select your deployment.
3. In your deployment menu, select **Health**.
@@ -67,12 +67,12 @@ The deployment **Health** page does not include information on cluster performan
## Health warnings [ec-es-health-warnings]
-In the normal course of using your Elasticsearch Service deployments, health warnings and errors might appear from time to time. Following are the most common scenarios and methods to resolve them.
+In the normal course of using your {{ech}} deployments, health warnings and errors might appear from time to time. Following are the most common scenarios and methods to resolve them.
Health warning messages
: Health warning messages will sometimes appear on the main page for one of your deployments, as well as on the **Logs and metrics** page.
- A single warning is rarely cause for concern, as often it just reflects ongoing, routine maintenance activity occurring on the Elasticsearch Service platform.
+ A single warning is rarely cause for concern, as often it just reflects ongoing, routine maintenance activity occurring on {{ecloud}}.
Configuration change failures
@@ -128,5 +128,5 @@ We’ve compiled some guidelines to help you ensure the health of your deploymen
: Learn about the common causes of increased query response times and decreased performance in your deployment.
[Why did my node move to a different host?](../../../troubleshoot/monitoring/node-moves-outages.md)
-: Learn about why we may, from time to time, relocate your Elasticsearch Service deployments across hosts.
+: Learn about why we may, from time to time, relocate your {{ech}} deployments across hosts.
diff --git a/raw-migrated-files/cloud/cloud/ec-password-reset.md b/raw-migrated-files/cloud/cloud/ec-password-reset.md
index d55fc629c..c054ef069 100644
--- a/raw-migrated-files/cloud/cloud/ec-password-reset.md
+++ b/raw-migrated-files/cloud/cloud/ec-password-reset.md
@@ -19,10 +19,10 @@ The `elastic` user should be not be used unless you have no other way to access
To reset the password:
-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.
+ 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.
3. From your deployment menu, go to **Security**.
4. Select **Reset password**.
diff --git a/raw-migrated-files/cloud/cloud/ec-planning.md b/raw-migrated-files/cloud/cloud/ec-planning.md
index 8a046ad51..97eb60a55 100644
--- a/raw-migrated-files/cloud/cloud/ec-planning.md
+++ b/raw-migrated-files/cloud/cloud/ec-planning.md
@@ -1,6 +1,6 @@
# Plan for production [ec-planning]
-Elasticsearch Service supports a wide range of configurations. With such flexibility comes great freedom, but also the first rule of deployment planning: Your deployment needs to be matched to the workloads that you plan to run on your {{es}} clusters and {{kib}} instances. Specifically, this means two things:
+{{ech}} supports a wide range of configurations. With such flexibility comes great freedom, but also the first rule of deployment planning: Your deployment needs to be matched to the workloads that you plan to run on your {{es}} clusters and {{kib}} instances. Specifically, this means two things:
* [Does your data need to be highly available?](../../../deploy-manage/production-guidance/plan-for-production-elastic-cloud.md#ec-ha)
* [Do you know when to scale?](../../../deploy-manage/production-guidance/plan-for-production-elastic-cloud.md#ec-workloads)
@@ -8,7 +8,7 @@ Elasticsearch Service supports a wide range of configurations. With such flexibi
## Does your data need to be highly available? [ec-ha]
-With Elasticsearch Service, your deployment can be spread across as many as three separate availability zones, each hosted in its own, separate data center. Why this matters:
+With {{ech}}, your deployment can be spread across as many as three separate availability zones, each hosted in its own, separate data center. Why this matters:
* Data centers can have issues with availability. Internet outages, earthquakes, floods, or other events could affect the availability of a single data center. With a single availability zone, you have a single point of failure that can bring down your deployment.
* Multiple availability zones help your deployment remain available. This includes your {{es}} cluster, provided that your cluster is sized so that it can sustain your workload on the remaining data centers and that your indices are configured to have at least one replica.
@@ -46,10 +46,10 @@ Clusters that only have one master node are not highly available and are at risk
Knowing how to scale your deployment is critical, especially when unexpected workloads hits. Don’t forget to [check your performance metrics](../../../deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md) to make sure your deployments are healthy and can cope with your workloads.
-Scaling with Elasticsearch Service is easy:
+Scaling with {{ech}} is easy:
-* Turn on [deployment autoscaling](../../../deploy-manage/autoscaling.md) to let Elasticsearch Service manage your deployments by adjusting their available resources automatically.
-* Or, if you prefer manual control, log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), select your deployment, select **Edit deployment** from the **Actions** dropdown, and either increase the number of zones or the size per zone.
+* Turn on [deployment autoscaling](../../../deploy-manage/autoscaling.md) to let {{ecloud}} manage your deployments by adjusting their available resources automatically.
+* Or, if you prefer manual control, log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), select your deployment, select **Edit deployment** from the **Actions** dropdown, and either increase the number of zones or the size per zone.
::::{warning}
Increasing the number of zones should not be used to add more resources. The concept of zones is meant for High Availability (2 zones) and Fault Tolerance (3 zones), but neither will work if the cluster relies on the resources from those zones to be operational. The recommendation is to scale up the resources within a single zone until the cluster can take the full load (add some buffer to be prepared for a peak of requests), then scale out by adding additional zones depending on your requirements: 2 zones for High Availability, 3 zones for Fault Tolerance.
diff --git a/raw-migrated-files/cloud/cloud/ec-regional-deployment-aliases.md b/raw-migrated-files/cloud/cloud/ec-regional-deployment-aliases.md
index a09e8bfd6..70405a3db 100644
--- a/raw-migrated-files/cloud/cloud/ec-regional-deployment-aliases.md
+++ b/raw-migrated-files/cloud/cloud/ec-regional-deployment-aliases.md
@@ -1,6 +1,6 @@
# Custom endpoint aliases [ec-regional-deployment-aliases]
-Custom aliases for your deployment endpoints on Elasticsearch Service allow you to have predictable, human-readable URLs that can be shared easily. An alias is unique to only one deployment within a region.
+Custom aliases for your deployment endpoints on {{ech}} allow you to have predictable, human-readable URLs that can be shared easily. An alias is unique to only one deployment within a region.
## Create a custom endpoint alias for a deployment [ec-create-regional-deployment-alias]
diff --git a/raw-migrated-files/cloud/cloud/ec-restoring-snapshots.md b/raw-migrated-files/cloud/cloud/ec-restoring-snapshots.md
index 8470e4bae..3f8594eb3 100644
--- a/raw-migrated-files/cloud/cloud/ec-restoring-snapshots.md
+++ b/raw-migrated-files/cloud/cloud/ec-restoring-snapshots.md
@@ -2,9 +2,9 @@
Snapshots provide a way to restore your Elasticsearch indices. They can be used to copy indices for testing, to recover from failures or accidental deletions, or to migrate data to other deployments.
-By default, Elasticsearch Service takes a snapshot of all the indices in your Elasticsearch cluster every 30 minutes. You can set a different snapshot interval, if needed for your environment. You can also take snapshots on demand, without having to wait for the next interval. Taking a snapshot on demand does not affect the retention schedule for existing snapshots, it just adds an additional snapshot to the repository. This might be helpful if you are about to make a deployment change and you don’t have a current snapshot.
+By default, {{ech}} takes a snapshot of all the indices in your Elasticsearch cluster every 30 minutes. You can set a different snapshot interval, if needed for your environment. You can also take snapshots on demand, without having to wait for the next interval. Taking a snapshot on demand does not affect the retention schedule for existing snapshots, it just adds an additional snapshot to the repository. This might be helpful if you are about to make a deployment change and you don’t have a current snapshot.
-Use Kibana to manage your snapshots. In Kibana, you can set up additional repositories where the snapshots are stored, other than the one currently managed by Elasticsearch Service. You can view and delete snapshots, and configure a snapshot lifecycle management (SLM) policy to automate when snapshots are created and deleted. To learn more, check the [Snapshot and Restore](../../../deploy-manage/tools/snapshot-and-restore/create-snapshots.md) documentation.
+Use Kibana to manage your snapshots. In Kibana, you can set up additional repositories where the snapshots are stored, other than the one currently managed by {{ech}}. You can view and delete snapshots, and configure a snapshot lifecycle management (SLM) policy to automate when snapshots are created and deleted. To learn more, check the [Snapshot and Restore](../../../deploy-manage/tools/snapshot-and-restore/create-snapshots.md) documentation.
::::{important}
Snapshots back up only open indices. If you close an index, it is not included in snapshots and you will not be able to restore the data.
@@ -16,5 +16,5 @@ A snapshot taken using the default `found-snapshots` repository can only be rest
::::
-From within Elasticsearch Service, you can [restore a snapshot](../../../deploy-manage/tools/snapshot-and-restore/restore-snapshot.md) from a different deployment in the same region.
+From within {{ech}}, you can [restore a snapshot](../../../deploy-manage/tools/snapshot-and-restore/restore-snapshot.md) from a different deployment in the same region.
diff --git a/raw-migrated-files/cloud/cloud/ec-saas-metrics-accessing.md b/raw-migrated-files/cloud/cloud/ec-saas-metrics-accessing.md
index cea49add2..dd1b72703 100644
--- a/raw-migrated-files/cloud/cloud/ec-saas-metrics-accessing.md
+++ b/raw-migrated-files/cloud/cloud/ec-saas-metrics-accessing.md
@@ -1,15 +1,15 @@
# Access performance metrics [ec-saas-metrics-accessing]
-Cluster performance metrics are available directly in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of Elasticsearch Service-specific performance metrics.
+Cluster performance metrics are available directly in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of {{ech}}-specific performance metrics.
For advanced views or production monitoring, [enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period.
To access cluster performance metrics:
-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. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention.
+ 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. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention.
3. From your deployment menu, go to the **Performance** page.
@@ -22,7 +22,7 @@ The following metrics are available:
:alt: Graph showing CPU usage
:::
-Shows the maximum usage of the CPU resources assigned to your Elasticsearch cluster, as a percentage. CPU resources are relative to the size of your cluster, so that a cluster with 32GB of RAM gets assigned twice as many CPU resources as a cluster with 16GB of RAM. All clusters are guaranteed their share of CPU resources, as Elasticsearch Service infrastructure does not overcommit any resources. CPU credits permit boosting the performance of smaller clusters temporarily, so that CPU usage can exceed 100%.
+Shows the maximum usage of the CPU resources assigned to your Elasticsearch cluster, as a percentage. CPU resources are relative to the size of your cluster, so that a cluster with 32GB of RAM gets assigned twice as many CPU resources as a cluster with 16GB of RAM. All clusters are guaranteed their share of CPU resources, as {{ech}} infrastructure does not overcommit any resources. CPU credits permit boosting the performance of smaller clusters temporarily, so that CPU usage can exceed 100%.
::::{tip}
This chart reports the maximum CPU values over the sampling period. [Logs and Metrics](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) ingested into [Stack Monitoring](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md)'s "CPU Usage" instead reflects the average CPU over the sampling period. Therefore, you should not expect the two graphs to look exactly the same. When investigating [CPU-related performance issues](../../../troubleshoot/monitoring/performance.md), you should default to [Stack Monitoring](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md).
@@ -88,7 +88,7 @@ Indicates the overhead involved in JVM garbage collection to reclaim memory.
Performance correlates directly with resources assigned to your cluster, and many of these metrics will show some sort of correlation with each other when you are trying to determine the cause of a performance issue. Take a look at some of the scenarios included in this section to learn how you can determine the cause of performance issues.
-It is not uncommon for performance issues on Elasticsearch Service to be caused by an undersized cluster that cannot cope with the workload it is being asked to handle. If your cluster performance metrics often shows high CPU usage or excessive memory pressure, consider increasing the size of your cluster soon to improve performance. This is especially true for clusters that regularly reach 100% of CPU usage or that suffer out-of-memory failures; it is better to resize your cluster early when it is not yet maxed out than to have to resize a cluster that is already overwhelmed. [Changing the configuration of your cluster](../../../deploy-manage/deploy/elastic-cloud/configure.md) may add some overhead if data needs to be migrated to the new nodes, which can increase the load on a cluster further and delay configuration changes.
+It is not uncommon for performance issues on {{ech}} to be caused by an undersized cluster that cannot cope with the workload it is being asked to handle. If your cluster performance metrics often shows high CPU usage or excessive memory pressure, consider increasing the size of your cluster soon to improve performance. This is especially true for clusters that regularly reach 100% of CPU usage or that suffer out-of-memory failures; it is better to resize your cluster early when it is not yet maxed out than to have to resize a cluster that is already overwhelmed. [Changing the configuration of your cluster](../../../deploy-manage/deploy/elastic-cloud/configure.md) may add some overhead if data needs to be migrated to the new nodes, which can increase the load on a cluster further and delay configuration changes.
To help diagnose high CPU usage you can also use the Elasticsearch [nodes hot threads API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-hot-threads), which identifies the threads on each node that have the highest CPU usage or that have been executing for a longer than normal period of time.
@@ -119,7 +119,7 @@ Cluster performance metrics are shown per node and are color-coded to indicate w
## Cluster restarts after out-of-memory failures [ec_cluster_restarts_after_out_of_memory_failures]
-For clusters that suffer out-of-memory failures, it can be difficult to determine whether the clusters are in a completely healthy state afterwards. For this reason, Elasticsearch Service automatically reboots clusters that suffer out-of-memory failures.
+For clusters that suffer out-of-memory failures, it can be difficult to determine whether the clusters are in a completely healthy state afterwards. For this reason, {{ech}} automatically reboots clusters that suffer out-of-memory failures.
You will receive an email notification to let you know that a restart occurred. For repeated alerts, the emails are aggregated so that you do not receive an excessive number of notifications. Either [resizing your cluster to reduce memory pressure](../../../deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md#ec-cluster-size) or reducing the workload that a cluster is being asked to handle can help avoid these cluster restarts.
diff --git a/raw-migrated-files/cloud/cloud/ec-security.md b/raw-migrated-files/cloud/cloud/ec-security.md
index 9bd38a559..1e2dbecb2 100644
--- a/raw-migrated-files/cloud/cloud/ec-security.md
+++ b/raw-migrated-files/cloud/cloud/ec-security.md
@@ -1,6 +1,6 @@
# Securing your deployment [ec-security]
-The security of Elasticsearch Service is described on the [{{ecloud}} security](https://www.elastic.co/cloud/security) page. In addition to the security provided by {{ecloud}}, you can take the following steps to secure your deployments:
+The security of {{ech}} is described on the [{{ecloud}} security](https://www.elastic.co/cloud/security) page. In addition to the security provided by {{ecloud}}, you can take the following steps to secure your deployments:
* Prevent unauthorized access with password protection and role-based access control:
@@ -14,7 +14,7 @@ The security of Elasticsearch Service is described on the [{{ecloud}} security](
* Block unwanted traffic with [traffic filter](../../../deploy-manage/security/traffic-filtering.md).
* Secure your settings with the Elasticsearch [keystore](../../../deploy-manage/security/secure-settings.md).
-In addition, we also enable encryption at rest (EAR) by default. Elasticsearch Service supports EAR for both the data stored in your clusters and the snapshots we take for backup, on all cloud platforms and across all regions.
+In addition, we also enable encryption at rest (EAR) by default. {{ech}} supports EAR for both the data stored in your clusters and the snapshots we take for backup, on all cloud platforms and across all regions.
## Should I use organization-level or deployment-level SSO? [ec_should_i_use_organization_level_or_deployment_level_sso]
diff --git a/raw-migrated-files/cloud/cloud/ec-select-subscription-level.md b/raw-migrated-files/cloud/cloud/ec-select-subscription-level.md
index 32a2591c4..78677c415 100644
--- a/raw-migrated-files/cloud/cloud/ec-select-subscription-level.md
+++ b/raw-migrated-files/cloud/cloud/ec-select-subscription-level.md
@@ -6,7 +6,7 @@ If, at any time during your monthly subscription with Elastic Cloud, you decide
To change your subscription level:
-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 the user icon on the header bar and select **Billing** from the menu.
3. On the **Overview** page, select **Update subscription**.
4. Choose a new subscription level.
diff --git a/raw-migrated-files/cloud/cloud/ec-service-status.md b/raw-migrated-files/cloud/cloud/ec-service-status.md
index c87b03694..2a769018f 100644
--- a/raw-migrated-files/cloud/cloud/ec-service-status.md
+++ b/raw-migrated-files/cloud/cloud/ec-service-status.md
@@ -1,6 +1,6 @@
# Service status [ec-service-status]
-Elasticsearch Service is a hosted service for the Elastic Stack that runs on different cloud platforms, such as Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. Like any service, it might undergo availability changes from time to time. When availability changes, Elastic makes sure to provide you with a current service status.
+{{ech}} is a hosted service for the Elastic Stack that runs on different cloud platforms, such as Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. Like any service, it might undergo availability changes from time to time. When availability changes, Elastic makes sure to provide you with a current service status.
To check current and past service availability, go to [Cloud Status](https://cloud-status.elastic.co/) page.
diff --git a/raw-migrated-files/cloud/cloud/ec-snapshot-restore.md b/raw-migrated-files/cloud/cloud/ec-snapshot-restore.md
index d7245ca76..ebc1664c0 100644
--- a/raw-migrated-files/cloud/cloud/ec-snapshot-restore.md
+++ b/raw-migrated-files/cloud/cloud/ec-snapshot-restore.md
@@ -2,9 +2,9 @@
Snapshots are an efficient way to ensure that your Elasticsearch indices can be recovered in the event of an accidental deletion, or to migrate data across deployments.
-The information here is specific to managing repositories and snapshots in Elasticsearch Service. We also support the Elasticsearch snapshot and restore API to back up your data. For details, consult the [Snapshot and Restore documentation](../../../deploy-manage/tools/snapshot-and-restore.md).
+The information here is specific to managing repositories and snapshots in {{ech}}. We also support the Elasticsearch snapshot and restore API to back up your data. For details, consult the [Snapshot and Restore documentation](../../../deploy-manage/tools/snapshot-and-restore.md).
-When you create a cluster in Elasticsearch Service, a default repository called `found-snapshots` is automatically added to the cluster. This repository is specific to that cluster: the deployment ID is part of the repository’s `base_path`, i.e., `/snapshots/[cluster-id]`.
+When you create a cluster in {{ech}}, a default repository called `found-snapshots` is automatically added to the cluster. This repository is specific to that cluster: the deployment ID is part of the repository’s `base_path`, i.e., `/snapshots/[cluster-id]`.
::::{important}
Do not disable or delete the default `cloud-snapshot-policy` SLM policy, and do not change the default `found-snapshots` repository defined in that policy. These actions are not supported.
diff --git a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-deployment-configuration.md b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-deployment-configuration.md
index d464d1bf1..94ad8ce3e 100644
--- a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-deployment-configuration.md
+++ b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-deployment-configuration.md
@@ -1,8 +1,8 @@
# Traffic Filtering [ec-traffic-filtering-deployment-configuration]
-Traffic filtering is one of the security layers available in Elasticsearch Service. It allows you to limit how your deployments can be accessed. Add another layer of security to your installation and deployments by restricting inbound traffic to *only* the sources that you trust.
+Traffic filtering is one of the security layers available in {{ecloud}}. It allows you to limit how your deployments can be accessed. Add another layer of security to your installation and deployments by restricting inbound traffic to *only* the sources that you trust.
-Elasticsearch Service supports the following traffic sources:
+{{ecloud}} supports the following traffic sources:
* [IP addresses and Classless Inter-Domain Routing (CIDR) masks](../../../deploy-manage/security/ip-traffic-filtering.md), e.g. `82.102.25.74` or `199.226.244.0/24`.
* [AWS Virtual Private Clouds (VPCs) over AWS PrivateLink](../../../deploy-manage/security/aws-privatelink-traffic-filters.md), supported only in AWS regions.
@@ -44,7 +44,7 @@ By default, all your deployments are accessible over the public internet. They a
Once you associate at least one traffic filter with a deployment, traffic that does not match any rules (for this deployment) is denied.
::::{note}
-This only applies to external traffic. Internal traffic is managed by Elasticsearch Service. For example, Kibana can connect to Elasticsearch, as well as internal services which manage the deployment. Other deployments can’t connect to deployments protected by traffic filters.
+This only applies to external traffic. Internal traffic is managed by {{ecloud}}. For example, Kibana can connect to Elasticsearch, as well as internal services which manage the deployment. Other deployments can’t connect to deployments protected by traffic filters.
::::
@@ -83,7 +83,7 @@ Jane creates a deployment. At this point the deployment is accessible over inter
Jane wants to restrict access to the deployment so that only the traffic originating from Jane’s VPC is allowed.
-* They create a Traffic Filter *Private Link Endpoint* rule set, thus registering their VPC with Elasticsearch Service.
+* They create a Traffic Filter *Private Link Endpoint* rule set, thus registering their VPC with {{ecloud}}.
* They associate this rule set with the deployment.
* At this point, their deployment is only accessible over PrivateLink from Jane’s VPC. This does not affect other security layers, so Jane’s users need to authenticate with username+password.
* The deployment is no longer accessible over the public internet endpoint.
@@ -120,10 +120,10 @@ This section offers suggestions on how to troubleshoot your traffic filters. Bef
### Review the rule sets associated with a deployment [ec-review-rule-sets]
-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.
+ 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.
3. Select the **Security** tab on the left-hand side menu bar.
4. Traffic filter rule sets are listed under **Traffic filters**.
@@ -135,8 +135,8 @@ On this screen you can view and remove existing filters and attach new filters.
To identify which rule sets are automatically applied to new deployments in your account:
-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.
3. Under the **Features** tab, open the **Traffic filters** page.
4. You can find the list of traffic filter rule sets.
5. Select each of the rule sets — **Include by default** is checked when this rule set is automatically applied to all new deployments in its region.
diff --git a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-ip.md b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-ip.md
index 5b79ad013..e6e40fab6 100644
--- a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-ip.md
+++ b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-ip.md
@@ -1,13 +1,13 @@
# IP traffic filters [ec-traffic-filtering-ip]
-Traffic filtering, by IP address or CIDR block, is one of the security layers available in Elasticsearch Service. It allows you to limit how your deployments can be accessed. We have two types of filters available for filtering by IP address or CIDR block: Ingress/Inbound and Egress/Outbound (Beta, API only).
+Traffic filtering, by IP address or CIDR block, is one of the security layers available in {{ecloud}}. It allows you to limit how your deployments can be accessed. We have two types of filters available for filtering by IP address or CIDR block: Ingress/Inbound and Egress/Outbound (Beta, API only).
-* **Ingress or inbound IP filters** - These restrict access to your deployments from a set of IP addresses or CIDR blocks. These filters are available through the Elasticsearch Service console.
+* **Ingress or inbound IP filters** - These restrict access to your deployments from a set of IP addresses or CIDR blocks. These filters are available through the {{ecloud}} Console.
* **Egress or outbound IP filters** - These restrict the set of IP addresses or CIDR blocks accessible from your deployment. These might be used to restrict access to a certain region or service. This feature is in beta and is currently only available through the [Traffic Filtering API](../../../deploy-manage/security/manage-traffic-filtering-through-api.md).
-Read more about [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) for the general concepts behind traffic filtering in Elasticsearch Service.
+Read more about [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) for the general concepts behind traffic filtering in {{ecloud}}.
-Follow the step described here to set up ingress or inbound IP filters through the Elasticsearch Service console.
+Follow the step described here to set up ingress or inbound IP filters through the {{ecloud}} Console.
## Create an IP filter rule set [ec-create-traffic-filter-ip-rule-set]
@@ -16,8 +16,8 @@ You can combine any rules into a set, so we recommend that you group rules accor
To create a rule set:
-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.
3. Under the **Features** tab, open the **Traffic filters** page.
4. Select **Create filter**.
5. Select **IP filtering rule set**.
@@ -60,8 +60,8 @@ If you want to remove any traffic restrictions from a deployment or delete a rul
You can edit a rule set name or change the allowed traffic sources using IPv4, or a range of addresses with CIDR.
-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.
3. Under the **Features** tab, open the **Traffic filters** page.
4. Find the rule set you want to edit.
5. Select the **Edit** icon.
diff --git a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-psc.md b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-psc.md
index 16eb03ba3..eb6d7e051 100644
--- a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-psc.md
+++ b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-psc.md
@@ -1,8 +1,8 @@
# GCP Private Service Connect traffic filters [ec-traffic-filtering-psc]
-Traffic filtering, to allow only Private Service Connect connections, is one of the security layers available in Elasticsearch Service. It allows you to limit how your deployments can be accessed.
+Traffic filtering, to allow only Private Service Connect connections, is one of the security layers available in {{ecloud}}. It allows you to limit how your deployments can be accessed.
-Read more about [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) for the general concepts behind traffic filtering in Elasticsearch Service.
+Read more about [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) for the general concepts behind traffic filtering in {{ecloud}}.
::::{note}
Private Service Connect filtering is supported only for Google Cloud regions.
diff --git a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-through-the-api.md b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-through-the-api.md
index 94776ed60..f1fd7effd 100644
--- a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-through-the-api.md
+++ b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-through-the-api.md
@@ -1,6 +1,6 @@
# Manage traffic filtering through the API [ec-traffic-filtering-through-the-api]
-This example demonstrates how to use the Elasticsearch Service RESTful API to manage different types of traffic filters. We cover the following examples:
+This example demonstrates how to use the {{ecloud}} RESTful API to manage different types of traffic filters. We cover the following examples:
* [Create a traffic filter rule set](../../../deploy-manage/security/manage-traffic-filtering-through-api.md#ec-create-a-traffic-filter-rule-set)
@@ -15,7 +15,7 @@ This example demonstrates how to use the Elasticsearch Service RESTful API to ma
* [Delete a rule set association with a deployment](../../../deploy-manage/security/manage-traffic-filtering-through-api.md#ec-delete-rule-set-association-with-a-deployment)
* [Delete a traffic filter rule set](../../../deploy-manage/security/manage-traffic-filtering-through-api.md#ec-delete-a-rule-set)
-Read through the main [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) page to learn about the general concepts behind filtering access to your Elasticsearch Service deployments.
+Read through the main [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) page to learn about the general concepts behind filtering access to your {{ech}} deployments.
## Create a traffic filter rule set [ec-create-a-traffic-filter-rule-set]
diff --git a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-vnet.md b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-vnet.md
index 055438aa9..b2c967468 100644
--- a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-vnet.md
+++ b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-vnet.md
@@ -1,8 +1,8 @@
# Azure Private Link traffic filters [ec-traffic-filtering-vnet]
-Traffic filtering, to allow only Azure Private Link connections, is one of the security layers available in Elasticsearch Service. It allows you to limit how your deployments can be accessed.
+Traffic filtering, to allow only Azure Private Link connections, is one of the security layers available in {{ecloud}}. It allows you to limit how your deployments can be accessed.
-Read more about [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) for the general concepts behind traffic filtering in Elasticsearch Service.
+Read more about [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) for the general concepts behind traffic filtering in {{ecloud}}.
::::{note}
Azure Private Link filtering is supported only for Azure regions.
@@ -282,5 +282,5 @@ This means your deployment on Elastic Cloud can be in a different region than th
1. Create your Private Endpoint using the service alias for region 2 in the region 1 VNET (let’s call this VNET1).
2. Create a Private Hosted Zone for region 2, and associate it with VNET1 similar to the step [Create a Private Link endpoint and DNS](../../../deploy-manage/security/azure-private-link-traffic-filters.md#ec-private-link-azure-dns). Note that you are creating these resources in region 1, VNET1.
-2. [Create a traffic filter rule set](../../../deploy-manage/security/azure-private-link-traffic-filters.md#ec-azure-create-traffic-filter-private-link-rule-set) and [Associate the rule set](../../../deploy-manage/security/aws-privatelink-traffic-filters.md#ec-associate-traffic-filter-private-link-rule-set) through the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), just as you would for any deployment.
+2. [Create a traffic filter rule set](../../../deploy-manage/security/azure-private-link-traffic-filters.md#ec-azure-create-traffic-filter-private-link-rule-set) and [Associate the rule set](../../../deploy-manage/security/aws-privatelink-traffic-filters.md#ec-associate-traffic-filter-private-link-rule-set) through the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), just as you would for any deployment.
3. [Test the connection](../../../deploy-manage/security/azure-private-link-traffic-filters.md#ec-azure-access-the-deployment-over-private-link) from a VM or client in region 1 to your Private Link endpoint, and it should be able to connect to your Elasticsearch cluster hosted in region 2.
diff --git a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-vpc.md b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-vpc.md
index b0a30fd7a..417eb32ca 100644
--- a/raw-migrated-files/cloud/cloud/ec-traffic-filtering-vpc.md
+++ b/raw-migrated-files/cloud/cloud/ec-traffic-filtering-vpc.md
@@ -1,8 +1,8 @@
# AWS PrivateLink traffic filters [ec-traffic-filtering-vpc]
-Traffic filtering, to only AWS PrivateLink connections, is one of the security layers available in Elasticsearch Service. It allows you to limit how your deployments can be accessed.
+Traffic filtering, to only AWS PrivateLink connections, is one of the security layers available in {{ecloud}}. It allows you to limit how your deployments can be accessed.
-Read more about [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) for the general concepts behind traffic filtering in Elasticsearch Service.
+Read more about [Traffic Filtering](../../../deploy-manage/security/traffic-filtering.md) for the general concepts behind traffic filtering in {{ecloud}}.
::::{note}
PrivateLink filtering is supported only for AWS regions. AWS does not support cross-region PrivateLink connections. Your PrivateLink endpoint needs to be in the same region as your target deployments. Additional details can be found in the [AWS VPCE Documentation](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.md#vpce-interface-limitations). AWS interface VPC endpoints get created in availability zones (AZ). In some regions, our VPC endpoint *service* is not present in all the possible AZs that a region offers. You can only choose AZs that are common on both sides. As the *names* of AZs (for example `us-east-1a`) differ between AWS accounts, the following list of AWS regions shows the *ID* (e.g. `use1-az4`) of each available AZ for the service. Check [interface endpoint availability zone considerations](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.md#vpce-interface-availability-zones) for more details.
@@ -187,8 +187,8 @@ Having trouble finding your VPC endpoint ID? You can find it in the AWS console.
Once you know your VPC endpoint ID you can create a private link traffic filter rule set.
-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.
3. Under the **Features** tab, open the **Traffic filters** page.
4. Select **Create filter**.
5. Select **Private link endpoint**.
@@ -248,8 +248,8 @@ The settings `xpack.fleet.agents.fleet_server.hosts` and `xpack.fleet.outputs` t
You can edit a rule set name or to change the VPC endpoint ID.
-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.
3. Under the **Features** tab, open the **Traffic filters** page.
4. Find the rule set you want to edit.
5. Select the **Edit** icon.
diff --git a/raw-migrated-files/cloud/cloud/ec-upgrade-deployment.md b/raw-migrated-files/cloud/cloud/ec-upgrade-deployment.md
index 926a360a6..7c6102fa0 100644
--- a/raw-migrated-files/cloud/cloud/ec-upgrade-deployment.md
+++ b/raw-migrated-files/cloud/cloud/ec-upgrade-deployment.md
@@ -1,7 +1,7 @@
# Upgrade versions [ec-upgrade-deployment]
::::{important}
-Beginning with Elastic Stack version 8.0, instructions for upgrading your Elasticsearch Service stack version can be found in [Upgrading on Elastic Cloud](../../../deploy-manage/upgrade/deployment-or-cluster.md). The following instructions apply for upgrading to Elastic Stack versions 7.x and previous.
+Beginning with Elastic Stack version 8.0, instructions for upgrading {{ech}} deployments can be found in [Upgrading on Elastic Cloud](../../../deploy-manage/upgrade/deployment-or-cluster.md). The following instructions apply for upgrading to Elastic Stack versions 7.x and previous.
::::
@@ -39,12 +39,12 @@ To successfully replace and override a plugin which is being upgraded, the `name
## Perform the upgrade [ec_perform_the_upgrade]
-To upgrade a cluster in Elasticsearch Service:
+To upgrade a cluster in {{ech}}:
-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.
+ 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.
3. In the **Deployment version** section, select **Upgrade**.
4. Select a new version.
@@ -56,7 +56,7 @@ To upgrade a cluster in Elasticsearch Service:
7. If you are upgrading to version 6.6 and earlier, major upgrades require a full cluster restart to complete the upgrade process.
8. If you had Kibana enabled, the UI will prompt you to also upgrade Kibana. The Kibana upgrade takes place separately from the Elasticsearch version upgrade and needs to be triggered manually:
- 1. 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. 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.
2. From your deployment menu, select **Kibana**.
3. If the button is available, select **Upgrade Kibana**. If the button is not available, Kibana does not need to be upgraded further.
4. Confirm the upgrade.
diff --git a/raw-migrated-files/docs-content/serverless/general-billing-stop-project.md b/raw-migrated-files/docs-content/serverless/general-billing-stop-project.md
index 69e79e7fa..f6a3ac6c1 100644
--- a/raw-migrated-files/docs-content/serverless/general-billing-stop-project.md
+++ b/raw-migrated-files/docs-content/serverless/general-billing-stop-project.md
@@ -9,6 +9,6 @@ All data is lost. Billing for usage is by the hour and any outstanding charges f
To stop being charged for a project:
-1. Log in to the [{{ess-console-name}}](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. Find your project on the home page in the **Serverless Projects** card and select **Manage** to access it directly. Or, select **Serverless Projects** to go to the projects page to view all of your projects.
3. Select **Actions**, then select **Delete project** and confirm the deletion.
diff --git a/raw-migrated-files/docs-content/serverless/general-sign-up-trial.md b/raw-migrated-files/docs-content/serverless/general-sign-up-trial.md
index be29442a6..f0dd973ee 100644
--- a/raw-migrated-files/docs-content/serverless/general-sign-up-trial.md
+++ b/raw-migrated-files/docs-content/serverless/general-sign-up-trial.md
@@ -1,6 +1,6 @@
# Sign up for Elastic Cloud [general-sign-up-trial]
-The following page provides information on how to sign up for an Elastic Cloud Serverless account, for information on how to sign up for hosted deployments, see [Elasticsearch Service - How do i sign up?](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md).
+The following page provides information on how to sign up for an Elastic Cloud Serverless account, for information on how to sign up for hosted deployments, see [{{ech}} - How do i sign up?](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md).
## Trial features [general-sign-up-trial-what-is-included-in-my-trial]
@@ -11,7 +11,7 @@ Your free 14-day trial includes:
A deployment lets you explore Elastic solutions for Search, Observability, and Security. Trial deployments run on the latest version of the Elastic Stack. They includes 8 GB of RAM spread out over two availability zones, and enough storage space to get you started. If you’re looking to evaluate a smaller workload, you can scale down your trial deployment. Each deployment includes Elastic features such as Maps, SIEM, machine learning, advanced security, and much more. You have some sample data sets to play with and tutorials that describe how to add your own data.
-To learn more about Elastic Cloud Hosted, check our [Elasticsearch Service documentation](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md).
+To learn more about Elastic Cloud Hosted, check our [{{ech}} documentation](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md).
**One serverless project**
@@ -41,7 +41,7 @@ During the free 14 day trial, Elastic provides access to one hosted deployment a
* Machine learning nodes are available up to 4GB RAM
* Custom {{es}} plugins are not enabled
-To learn more about Elastic Cloud Hosted, check our [Elasticsearch Service documentation](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md).
+To learn more about Elastic Cloud Hosted, check our [{{ech}} documentation](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md).
**Serverless projects**
diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/autoscaling-machine-learning-decider.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/autoscaling-machine-learning-decider.md
index e6338ccfe..106eacf3b 100644
--- a/raw-migrated-files/elasticsearch/elasticsearch-reference/autoscaling-machine-learning-decider.md
+++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/autoscaling-machine-learning-decider.md
@@ -5,7 +5,7 @@ The [autoscaling](../../../deploy-manage/autoscaling.md) {{ml}} decider (`ml`) c
The {{ml}} decider is enabled for policies governing `ml` nodes.
::::{note}
-For {{ml}} jobs to open when the cluster is not appropriately scaled, set `xpack.ml.max_lazy_ml_nodes` to the largest number of possible {{ml}} nodes (refer to [Advanced machine learning settings](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/machine-learning-settings.md#advanced-ml-settings) for more information). In {{ess}}, this is automatically set.
+For {{ml}} jobs to open when the cluster is not appropriately scaled, set `xpack.ml.max_lazy_ml_nodes` to the largest number of possible {{ml}} nodes (refer to [Advanced machine learning settings](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/machine-learning-settings.md#advanced-ml-settings) for more information). In {{ech}}, this is automatically set.
::::
diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/fips-140-compliance.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/fips-140-compliance.md
index 0d275419a..d2c882cc7 100644
--- a/raw-migrated-files/elasticsearch/elasticsearch-reference/fips-140-compliance.md
+++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/fips-140-compliance.md
@@ -133,7 +133,7 @@ To verify that the security provider is installed and in use, you can use any of
{{es}} 8.0+ requires Java 17 or later. {{es}} 8.13+ has been tested with [Bouncy Castle](https://www.bouncycastle.org/java.md)'s Java 17 [certified](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4616) FIPS implementation and is the recommended Java security provider when running {{es}} in FIPS 140-2 mode. Note - {{es}} does not ship with a FIPS certified security provider and requires explicit installation and configuration.
-Alternatively, consider using {{ess}} in the [FedRAMP-certified GovCloud region](https://www.elastic.co/industries/public-sector/fedramp).
+Alternatively, consider using {{ech}} in the [FedRAMP-certified GovCloud region](https://www.elastic.co/industries/public-sector/fedramp).
::::{important}
Some encryption algorithms may no longer be available by default in updated FIPS 140-2 security providers. Notably, Triple DES and PKCS1.5 RSA are now discouraged and [Bouncy Castle](https://www.bouncycastle.org/fips-java) now requires explicit configuration to continue using these algorithms.
diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/install-elasticsearch.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/install-elasticsearch.md
index 15b225ffb..138b35bf6 100644
--- a/raw-migrated-files/elasticsearch/elasticsearch-reference/install-elasticsearch.md
+++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/install-elasticsearch.md
@@ -1,7 +1,7 @@
# Installing Elasticsearch [install-elasticsearch]
-## Hosted Elasticsearch Service [hosted-elasticsearch-service]
+## {{ecloud}} [hosted-elasticsearch-service]
{{ecloud}} offers all of the features of {{es}}, {{kib}}, and Elastic’s {{observability}}, and {{elastic-sec}} solutions as a hosted service available on AWS, GCP, and Azure.
diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/search-with-synonyms.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/search-with-synonyms.md
index 576358cb4..cc0f08dc8 100644
--- a/raw-migrated-files/elasticsearch/elasticsearch-reference/search-with-synonyms.md
+++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/search-with-synonyms.md
@@ -32,7 +32,7 @@ Changes in your synonyms sets will automatically reload the associated analyzers
You can store your synonyms set in a file.
-A synonyms set file needs to be uploaded to all your cluster nodes, and be located in the configuration directory for your {{es}} distribution. If you’re using {{ess}}, you can upload synonyms files using [custom bundles](../../../deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md).
+A synonyms set file needs to be uploaded to all your cluster nodes, and be located in the configuration directory for your {{es}} distribution. If you’re using {{ecloud}}, you can upload synonyms files using [custom bundles](../../../deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md).
An example synonyms file:
diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/snapshots-restore-snapshot.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/snapshots-restore-snapshot.md
index 6c7dd593d..a33ad3f9e 100644
--- a/raw-migrated-files/elasticsearch/elasticsearch-reference/snapshots-restore-snapshot.md
+++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/snapshots-restore-snapshot.md
@@ -182,7 +182,7 @@ When you restore a feature state, {{es}} closes and overwrites the feature’s e
::::{warning}
-Restoring the `security` feature state overwrites system indices used for authentication. If you use {{ess}}, ensure you have access to the {{ess}} Console before restoring the `security` feature state. If you run {{es}} on your own hardware, [create a superuser in the file realm](../../../deploy-manage/tools/snapshot-and-restore/restore-snapshot.md#restore-create-file-realm-user) to ensure you’ll still be able to access your cluster.
+Restoring the `security` feature state overwrites system indices used for authentication. If you use {{ech}}, ensure you have access to the {{ecloud}} Console before restoring the `security` feature state. If you run {{es}} on your own hardware, [create a superuser in the file realm](../../../deploy-manage/tools/snapshot-and-restore/restore-snapshot.md#restore-create-file-realm-user) to ensure you’ll still be able to access your cluster.
::::
@@ -454,7 +454,7 @@ DELETE _data_stream/logs-my_app-default
## Restore to a different cluster [restore-different-cluster]
::::{tip}
-{{ess}} can help you restore snapshots from other deployments. See [Work with snapshots](../../../deploy-manage/tools/snapshot-and-restore.md).
+{{ech}} can help you restore snapshots from other deployments. See [Work with snapshots](../../../deploy-manage/tools/snapshot-and-restore.md).
::::
diff --git a/raw-migrated-files/ingest-docs/fleet/fleet-agent-serverless-restrictions.md b/raw-migrated-files/ingest-docs/fleet/fleet-agent-serverless-restrictions.md
index eaf94d4ce..529243f5f 100644
--- a/raw-migrated-files/ingest-docs/fleet/fleet-agent-serverless-restrictions.md
+++ b/raw-migrated-files/ingest-docs/fleet/fleet-agent-serverless-restrictions.md
@@ -8,7 +8,7 @@ navigation_title: "Restrictions for {{serverless-full}}"
## {{agent}} [elastic-agent-serverless-restrictions]
-If you are using {{agent}} with [{{serverless-full}}](https://docs.elastic.co/serverless), note these differences from use with {{ess}} and self-managed {{es}}:
+If you are using {{agent}} with [{{serverless-full}}](https://docs.elastic.co/serverless), note these differences from use with {{ech}} and self-managed {{es}}:
* The number of {{agents}} that may be connected to an {{serverless-full}} project is limited to 10 thousand.
* The minimum supported version of {{agent}} supported for use with {{serverless-full}} is 8.11.0.
@@ -23,7 +23,7 @@ $$$outputs-serverless-restrictions$$$
The path to get to the {{fleet}} application in {{kib}} differs across projects:
-* In {{ess}} deployments, navigate to **Management > Fleet**.
+* In {{ech}} deployments, navigate to **Management > Fleet**.
* In {{serverless-short}} {{observability}} projects, navigate to **Project settings > Fleet**.
* In {{serverless-short}} Security projects, navigate to **Assets > Fleet**.
diff --git a/raw-migrated-files/kibana/kibana/apm-settings-kb.md b/raw-migrated-files/kibana/kibana/apm-settings-kb.md
index 02b860555..328ee5da5 100644
--- a/raw-migrated-files/kibana/kibana/apm-settings-kb.md
+++ b/raw-migrated-files/kibana/kibana/apm-settings-kb.md
@@ -29,62 +29,62 @@ More settings are available in the [Observability advanced settings](asciidocaly
::::
-`xpack.apm.maxSuggestions` 
+`xpack.apm.maxSuggestions` 
: Maximum number of suggestions fetched in autocomplete selection boxes. Defaults to `100`.
-`xpack.apm.serviceMapFingerprintBucketSize` 
+`xpack.apm.serviceMapFingerprintBucketSize` 
: Maximum number of unique transaction combinations sampled for generating service map focused on a specific service. Defaults to `100`.
-`xpack.apm.serviceMapFingerprintGlobalBucketSize` 
+`xpack.apm.serviceMapFingerprintGlobalBucketSize` 
: Maximum number of unique transaction combinations sampled for generating the global service map. Defaults to `100`.
-`xpack.apm.serviceMapEnabled` 
+`xpack.apm.serviceMapEnabled` 
: Set to `false` to disable service maps. Defaults to `true`.
-`xpack.apm.serviceMapTraceIdBucketSize` 
+`xpack.apm.serviceMapTraceIdBucketSize` 
: Maximum number of trace IDs sampled for generating service map focused on a specific service. Defaults to `65`.
-`xpack.apm.serviceMapTraceIdGlobalBucketSize` 
+`xpack.apm.serviceMapTraceIdGlobalBucketSize` 
: Maximum number of trace IDs sampled for generating the global service map. Defaults to `6`.
-`xpack.apm.serviceMapMaxTracesPerRequest` 
+`xpack.apm.serviceMapMaxTracesPerRequest` 
: Maximum number of traces per request for generating the global service map. Defaults to `50`.
-`xpack.apm.ui.enabled` 
+`xpack.apm.ui.enabled` 
: Set to `false` to hide the APM app from the main menu. Defaults to `true`.
-`xpack.apm.ui.maxTraceItems` 
+`xpack.apm.ui.maxTraceItems` 
: Maximum number of child items displayed when viewing trace details. Defaults to `5000`.
-`xpack.observability.annotations.index` 
+`xpack.observability.annotations.index` 
: Index name where Observability annotations are stored. Defaults to `observability-annotations`.
-`xpack.apm.metricsInterval` 
+`xpack.apm.metricsInterval` 
: Sets a `fixed_interval` for date histograms in metrics aggregations. Defaults to `30`.
-`xpack.apm.agent.migrations.enabled` 
+`xpack.apm.agent.migrations.enabled` 
: Set to `false` to disable cloud APM migrations. Defaults to `true`.
-`xpack.apm.indices.error` 
+`xpack.apm.indices.error` 
: Matcher for all error indices. Defaults to `logs-apm*,apm-*,traces-*.otel-*`.
-`xpack.apm.indices.onboarding` 
+`xpack.apm.indices.onboarding` 
: Matcher for all onboarding indices. Defaults to `apm-*`.
-`xpack.apm.indices.span` 
+`xpack.apm.indices.span` 
: Matcher for all span indices. Defaults to `traces-apm*,apm-*,traces-*.otel-*`.
-`xpack.apm.indices.transaction` 
+`xpack.apm.indices.transaction` 
: Matcher for all transaction indices. Defaults to `traces-apm*,apm-*,traces-*.otel-*`.
-`xpack.apm.indices.metric` 
+`xpack.apm.indices.metric` 
: Matcher for all metrics indices. Defaults to `metrics-apm*,apm-*,metrics-*.otel-*`.
-`xpack.apm.indices.sourcemap` 
+`xpack.apm.indices.sourcemap` 
: Matcher for all source map indices. Defaults to `apm-*`.
-`xpack.apm.autoCreateApmDataView` 
+`xpack.apm.autoCreateApmDataView` 
: Set to `false` to disable the automatic creation of the APM data view when the APM app is opened. Defaults to `true`.
-`xpack.apm.latestAgentVersionsUrl` 
+`xpack.apm.latestAgentVersionsUrl` 
: Specifies the URL of a self hosted file that contains latest agent versions. Defaults to `https://apm-agent-versions.elastic.co/versions.json`. Set to `''` to disable requesting latest agent versions.
diff --git a/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md b/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md
index 9552a724d..c64b5884d 100644
--- a/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md
+++ b/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md
@@ -4,7 +4,7 @@ Once you are [prepared to upgrade](../../../deploy-manage/upgrade/deployment-or-
Minor version upgrades, upgrades from 8.17 to 9.0.0-beta1, and cluster configuration changes can be performed with no downtime. Elastic Cloud only supports upgrades to released versions. Preview releases and master snapshots are not supported.
-{{ess}} and {{ece}} do not support the ability to upgrade to or from release candidate builds, such as 8.0.0-rc1.
+{{ech}} and {{ece}} do not support the ability to upgrade to or from release candidate builds, such as 8.0.0-rc1.
If you use a separate [monitoring deployment](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md), you should upgrade the monitoring deployment before the production deployment. In general, the monitoring deployment and the deployments being monitored should be running the same version of the Elastic Stack. A monitoring deployment cannot monitor production deployments running newer versions of the stack. If necessary, the monitoring deployment can monitor production deployments running the latest release of the previous major version.
@@ -209,16 +209,16 @@ function changeTabs(e) {
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
-1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co/?page=docs&placement=docs-body).
-2. Select your deployment on the home page in the {{ess}} card or go to the deployments page.
+::::::{tab-item} {{ech}}
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co/?page=docs&placement=docs-body).
+2. Select your deployment on the home page in the **Hosted deployments** card or go to the **Deployments** page.
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.
::::::
::::::{tab-item} Elastic Cloud Enterprise
1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md)
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
::::::
@@ -231,7 +231,7 @@ To upgrade a deployment:
3. Click **Upgrade** and then **Confirm upgrade**. The new configuration takes a few minutes to create.
::::{note}
- If any incompatibilities are detected when you attempt to upgrade to 9.0.0-beta1, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. After resolving the issues, return to the deployments page and restart the upgrade.
+ If any incompatibilities are detected when you attempt to upgrade to 9.0.0-beta1, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. After resolving the issues, return to the **Deployments** page and restart the upgrade.
::::
diff --git a/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/get-elastic.md b/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/get-elastic.md
index 58d2838ea..abb814879 100644
--- a/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/get-elastic.md
+++ b/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/get-elastic.md
@@ -38,7 +38,7 @@ If you prefer to go the self-managed route, you can install the Elastic Stack on
no
-Elastic Cloud: Hosted Elasticsearch Service
+Elastic Cloud Hosted
Subscribe through the , , or marketplace for
unified billing
AWS
diff --git a/reference/glossary/index.md b/reference/glossary/index.md
index f0c145faf..b52bc6bf0 100644
--- a/reference/glossary/index.md
+++ b/reference/glossary/index.md
@@ -65,7 +65,7 @@ $$$glossary-auto-follow-pattern$$$ auto-follow pattern
: [Index pattern](/reference/glossary/index.md#glossary-index-pattern) that automatically configures new [indices](/reference/glossary/index.md#glossary-index) as [follower indices](/reference/glossary/index.md#glossary-follower-index) for [{{ccr}}](/reference/glossary/index.md#glossary-ccr). See [Manage auto-follow patterns](/deploy-manage/tools/cross-cluster-replication/manage-auto-follow-patterns.md).
$$$glossary-zone$$$ availability zone
-: Contains resources available to a {{ece}} installation that are isolated from other availability zones to safeguard against failure. Could be a rack, a server zone or some other logical constraint that creates a failure boundary. In a highly available cluster, the nodes of a cluster are spread across two or three availability zones to ensure that the cluster can survive the failure of an entire availability zone. Also see [Fault Tolerance (High Availability)](/deploy-manage/deploy/cloud-enterprise/ece-ha.md).
+: Contains resources available to an {{ece}} installation that are isolated from other availability zones to safeguard against failure. Could be a rack, a server zone or some other logical constraint that creates a failure boundary. In a highly available cluster, the nodes of a cluster are spread across two or three availability zones to ensure that the cluster can survive the failure of an entire availability zone. Also see [Fault Tolerance (High Availability)](/deploy-manage/deploy/cloud-enterprise/ece-ha.md).
## B [b-glos]
@@ -134,7 +134,7 @@ $$$glossary-connector$$$ connector
$$$glossary-console$$$ Console
: In {{kib}}, a tool for interacting with the {{es}} REST API. You can send requests to {{es}}, view responses, view API documentation, and get your request history. See [Console](/explore-analyze/query-filter/tools/console.md).
- In {{ess}}, provides web-based access to manage your {{ecloud}} deployments.
+ In {{ecloud}}, provides web-based access to manage your {{ecloud}} deployments.
$$$glossary-constructor$$$ constructor
@@ -257,8 +257,8 @@ $$$glossary-elastic-security-indices$$$ {{elastic-sec}} indices
$$$glossary-elastic-stack$$$ {{stack}}
: Also known as the *ELK Stack*, the {{stack}} is the combination of various Elastic products that integrate for a scalable and flexible way to manage your data.
-$$$glossary-elasticsearch-service$$$ {{ess}}
-: The official hosted {{stack}} offering, from the makers of {{es}}. Available as a software-as-a-service (SaaS) offering on different cloud platforms, such as AWS, GCP, and Microsoft Azure.
+$$$glossary-elasticsearch-service$$$ Elasticsearch Service
+: The former name of {{ech}}, which is the official hosted {{stack}} offering, from the makers of {{es}}. Available as a software-as-a-service (SaaS) offering on different cloud platforms, such as AWS, GCP, and Microsoft Azure.
$$$glossary-element$$$ element
: A [Canvas](/reference/glossary/index.md#glossary-canvas) workpad object that displays an image, text, or visualization.
diff --git a/reference/ingestion-tools/cloud/apm-settings.md b/reference/ingestion-tools/cloud/apm-settings.md
index 91c872df5..b2c30ac0c 100644
--- a/reference/ingestion-tools/cloud/apm-settings.md
+++ b/reference/ingestion-tools/cloud/apm-settings.md
@@ -27,10 +27,10 @@ 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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. In the **APM** section, select **Edit user settings**. (For existing deployments with user settings, you may have to expand the **Edit apm-server.yml** caret instead.)
@@ -38,14 +38,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 by {{ech}}, 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).
diff --git a/reference/ingestion-tools/fleet/add-fleet-server-mixed.md b/reference/ingestion-tools/fleet/add-fleet-server-mixed.md
index a8cd77d01..572a45324 100644
--- a/reference/ingestion-tools/fleet/add-fleet-server-mixed.md
+++ b/reference/ingestion-tools/fleet/add-fleet-server-mixed.md
@@ -17,7 +17,7 @@ This approach might *not* be right for you if you don’t want to manage the lif
:alt: {{fleet-server}} on-premise and {{es}} on Cloud deployment model
:::
-To deploy a self-managed {{fleet-server}} on-premises to work with a hosted {{ess}}, you need to:
+To deploy a self-managed {{fleet-server}} on-premises to work with an {{ech}} deployment, you need to:
* Satisfy all [compatibility requirements](#add-fleet-server-mixed-compatibility) and [prerequisites](#add-fleet-server-mixed-prereq)
* Create a [{{fleet-server}} policy](#fleet-server-create-policy)
diff --git a/reference/ingestion-tools/fleet/agent-policy.md b/reference/ingestion-tools/fleet/agent-policy.md
index 83693f796..7ec3e3dd3 100644
--- a/reference/ingestion-tools/fleet/agent-policy.md
+++ b/reference/ingestion-tools/fleet/agent-policy.md
@@ -30,13 +30,13 @@ For example, it might make sense to create a policy per operating system type: W
## Policy types [agent-policy-types]
-In most use cases, {{fleet}} provides complete central management of {{agent}}s. However some use cases, like running in Kubernetes or using our hosted {{ess}} on {{ecloud}}, require {{agent}} infrastructure management outside of {{fleet}}. With this in mind, there are two types of {{agent}} policies:
+In most use cases, {{fleet}} provides complete central management of {{agent}}s. However some use cases, like running in Kubernetes or using {{ecloud}}, require {{agent}} infrastructure management outside of {{fleet}}. With this in mind, there are two types of {{agent}} policies:
* **regular policy**: The default use case, where {{fleet}} provides full central management for {{agent}}s. Users can manage {{agent}} infrastructure by adding, removing, or upgrading {{agent}}s. Users can also manage {{agent}} configuration by updating the {{agent}} policy.
* **hosted policy**: A policy where *something else* provides central management for {{agent}}s. For example, in Kubernetes, adding, removing, and upgrading {{agent}}s should be configured directly in Kubernetes. Allowing {{fleet}} users to manage {{agent}}s would conflict with any Kubernetes configuration.
::::{tip}
- Hosted policies also apply when using our hosted {{ess}} on {{ecloud}}. {{ecloud}} is responsible for hosting {{agent}}s and assigning them to a policy. Platform operators, who create and manage Elastic deployments can add, upgrade, and remove {{agent}}s through the {{ecloud}} console.
+ Hosted policies also apply when using {{ech}}. {{ecloud}} is responsible for hosting {{agent}}s and assigning them to a policy. Platform operators, who create and manage Elastic deployments can add, upgrade, and remove {{agent}}s through the {{ecloud}} console.
::::
diff --git a/reference/ingestion-tools/fleet/deployment-models.md b/reference/ingestion-tools/fleet/deployment-models.md
index ec2b52228..77cd70c20 100644
--- a/reference/ingestion-tools/fleet/deployment-models.md
+++ b/reference/ingestion-tools/fleet/deployment-models.md
@@ -14,11 +14,11 @@ The requirements for setting up {{fleet-server}} differ, depending on your parti
{{serverless-full}}
: In a [{{serverless-short}}](/deploy-manage/deploy/elastic-cloud/serverless.md) environment, {{fleet-server}} is offered as a service, it is configured and scaled automatically without the need for any user intervention.
-{{ess}}
-: If you’re running {{es}} and {{kib}} hosted on [{{ess}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md), no extra setup is required unless you want to scale your deployment. {{ess}} runs a hosted version of {{integrations-server}} that includes {{fleet-server}}. For details about this deployment model, refer to [Deploy on {{ecloud}}](/reference/ingestion-tools/fleet/add-fleet-server-cloud.md).
+{{ech}}
+: If you’re running {{es}} and {{kib}} with [{{ech}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md), no extra setup is required unless you want to scale your deployment. {{ech}} runs a hosted version of {{integrations-server}} that includes {{fleet-server}}. For details about this deployment model, refer to [Deploy on {{ecloud}}](/reference/ingestion-tools/fleet/add-fleet-server-cloud.md).
-{{ess}} with {{fleet-server}} on-premise
-: When you use a hosted {{ess}} deployment you may still choose to run {{fleet-server}} on-premise. For details about this deployment model and set up instructions, refer to [Deploy {{fleet-server}} on-premises and {{es}} on Cloud](/reference/ingestion-tools/fleet/add-fleet-server-mixed.md).
+{{ech}} with {{fleet-server}} on-premise
+: When you use an {{ech}} deployment you may still choose to run {{fleet-server}} on-premise. For details about this deployment model and set up instructions, refer to [Deploy {{fleet-server}} on-premises and {{es}} on Cloud](/reference/ingestion-tools/fleet/add-fleet-server-mixed.md).
Docker and Kubernetes
: You can deploy {{fleet}}-managed {{agent}} in Docker or on Kubernetes. Refer to [Run {{agent}} in a container](/reference/ingestion-tools/fleet/elastic-agent-container.md) or [Run {{agent}} on Kubernetes managed by {{fleet}}](/reference/ingestion-tools/fleet/running-on-kubernetes-managed-by-fleet.md) for all of the configuration instructions. For a Kubernetes install we also have a [Helm chart](/reference/ingestion-tools/fleet/install-on-kubernetes-using-helm.md) available to simplify the installation. Details for configuring {{fleet-server}} are included with the {{agent}} install steps.
diff --git a/reference/ingestion-tools/fleet/elastic-agent-container.md b/reference/ingestion-tools/fleet/elastic-agent-container.md
index c9c22183e..4a01cbab9 100644
--- a/reference/ingestion-tools/fleet/elastic-agent-container.md
+++ b/reference/ingestion-tools/fleet/elastic-agent-container.md
@@ -22,8 +22,8 @@ Considerations:
::::{tab-set}
- :::{tab-item} Elasticsearch Service
- To get started quickly, spin up a deployment of our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service). The {{ess}} is available on AWS, GCP, and Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
+ :::{tab-item} {{ech}}
+ To get started quickly, spin up an [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service) deployment. {{ech}} is available on AWS, GCP, and Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
:::
:::{tab-item} Self-managed
@@ -184,7 +184,7 @@ You can also add `type=tmpfs` to the mount parameter (`--mount type=tmpfs,destin
::::{tab-set}
- :::{tab-item} Elasticsearch Service
+ :::{tab-item} {{ech}}
1. [Log in](https://cloud.elastic.co/) to your {{ecloud}} account.
2. Navigate to the {{kib}} endpoint in your deployment.
:::
diff --git a/reference/ingestion-tools/fleet/example-standalone-monitor-nginx.md b/reference/ingestion-tools/fleet/example-standalone-monitor-nginx.md
index 29cef1d53..75971edf5 100644
--- a/reference/ingestion-tools/fleet/example-standalone-monitor-nginx.md
+++ b/reference/ingestion-tools/fleet/example-standalone-monitor-nginx.md
@@ -3,9 +3,9 @@ mapped_pages:
- https://www.elastic.co/guide/en/fleet/current/example-standalone-monitor-nginx.html
---
-# Example: Use standalone Elastic Agent with Elasticsearch Service to monitor nginx [example-standalone-monitor-nginx]
+# Example: Use standalone Elastic Agent with {{ech}} to monitor nginx [example-standalone-monitor-nginx]
-This guide walks you through a simple monitoring scenario so you can learn the basics of setting up standalone {{agent}}, using it to work with {{ess}} and an Elastic integration.
+This guide walks you through a simple monitoring scenario so you can learn the basics of setting up standalone {{agent}}, using it to work with {{ech}} and an Elastic integration.
Following these steps, you’ll deploy the {{stack}}, install a standalone {{agent}} on a host to monitor an nginx web server instance, and access visualizations based on the collected logs.
@@ -54,7 +54,7 @@ If you’ve already signed up for a trial deployment you can skip this step.
::::
-Now that your web server is running, let’s get set up to monitor it in {{ecloud}}. An {{ecloud}} {{ess}} deployment offers you all of the features of the {{stack}} as a hosted service. To test drive your first deployment, sign up for a free {{ecloud}} trial:
+Now that your web server is running, let’s get set up to monitor it in {{ecloud}}. An {{ech}} deployment offers you all of the features of the {{stack}} as a hosted service. To test drive your first deployment, sign up for a free {{ecloud}} trial:
1. Go to our [{{ecloud}} Trial](https://cloud.elastic.co/registration?elektra=guide-welcome-cta) page.
2. Enter your email address and a password.
diff --git a/reference/ingestion-tools/fleet/fleet-agent-serverless-restrictions.md b/reference/ingestion-tools/fleet/fleet-agent-serverless-restrictions.md
index e2d805f06..c98b6c406 100644
--- a/reference/ingestion-tools/fleet/fleet-agent-serverless-restrictions.md
+++ b/reference/ingestion-tools/fleet/fleet-agent-serverless-restrictions.md
@@ -10,7 +10,7 @@ mapped_pages:
## {{agent}} [elastic-agent-serverless-restrictions]
-If you are using {{agent}} with [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md), note these differences from use with {{ess}} and self-managed {{es}}:
+If you are using {{agent}} with [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md), note these differences from use with {{ech}} and self-managed {{es}}:
* The number of {{agents}} that may be connected to an {{serverless-full}} project is limited to 10 thousand.
* The minimum supported version of {{agent}} supported for use with {{serverless-full}} is 8.11.0.
@@ -25,7 +25,7 @@ $$$outputs-serverless-restrictions$$$
The path to get to the {{fleet}} application in {{kib}} differs across projects:
-* In {{ess}} deployments, navigate to **Management > Fleet**.
+* In {{ech}} deployments, navigate to **Management > Fleet**.
* In {{serverless-short}} {{observability}} projects, navigate to **Project settings > Fleet**.
* In {{serverless-short}} Security projects, navigate to **Assets > Fleet**.
diff --git a/reference/ingestion-tools/fleet/grant-access-to-elasticsearch.md b/reference/ingestion-tools/fleet/grant-access-to-elasticsearch.md
index 26c06a543..051c16c63 100644
--- a/reference/ingestion-tools/fleet/grant-access-to-elasticsearch.md
+++ b/reference/ingestion-tools/fleet/grant-access-to-elasticsearch.md
@@ -18,7 +18,7 @@ If you’re using {{fleet}}, refer to [{{fleet}} enrollment tokens](/reference/i
## Create API keys for standalone agents [create-api-key-standalone-agent]
::::{note}
-API keys are sent as plain-text, so they only provide security when used in combination with Transport Layer Security (TLS). Our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body) on {{ecloud}} provides secure, encrypted connections out of the box! For self-managed {{es}} clusters, refer to [Public Key Infrastructure (PKI) certificates](/reference/ingestion-tools/fleet/elasticsearch-output.md#output-elasticsearch-pki-certs-authentication-settings).
+API keys are sent as plain-text, so they only provide security when used in combination with Transport Layer Security (TLS). [{{ecloud}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body) provides secure, encrypted connections out of the box! For self-managed {{es}} clusters, refer to [Public Key Infrastructure (PKI) certificates](/reference/ingestion-tools/fleet/elasticsearch-output.md#output-elasticsearch-pki-certs-authentication-settings).
::::
diff --git a/reference/ingestion-tools/fleet/install-elastic-agents.md b/reference/ingestion-tools/fleet/install-elastic-agents.md
index 5edd1732e..278cd3c82 100644
--- a/reference/ingestion-tools/fleet/install-elastic-agents.md
+++ b/reference/ingestion-tools/fleet/install-elastic-agents.md
@@ -57,7 +57,7 @@ You have a few options for installing and managing an {{agent}}:
::::{admonition} Restrictions in {{serverless-short}}
:class: important
-If you are using {{agent}} with [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md), note these differences from use with {{ess}} and self-managed {{es}}:
+If you are using {{agent}} with [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md), note these differences from use with {{ech}} and self-managed {{es}}:
* The number of {{agents}} that may be connected to an {{serverless-full}} project is limited to 10 thousand.
* The minimum supported version of {{agent}} supported for use with {{serverless-full}} is 8.11.0.
diff --git a/reference/ingestion-tools/fleet/install-fleet-managed-elastic-agent.md b/reference/ingestion-tools/fleet/install-fleet-managed-elastic-agent.md
index 170d957f9..b9a63e105 100644
--- a/reference/ingestion-tools/fleet/install-fleet-managed-elastic-agent.md
+++ b/reference/ingestion-tools/fleet/install-fleet-managed-elastic-agent.md
@@ -29,7 +29,7 @@ Just want to learn how to install {{agent}}? Continue reading this page.
You will always need:
* **A {{kib}} user with `All` privileges on {{fleet}} and {{integrations}}.** Since many Integrations assets are shared across spaces, users need the {{kib}} privileges in all spaces.
-* **[{{fleet-server}}](/reference/ingestion-tools/fleet/fleet-server.md) running in a location accessible to {{agent}}.** {{agent}} must have a direct network connection to {{fleet-server}} and {{es}}. If you’re using our hosted {{ess}} on {{ecloud}}, {{fleet-server}} is already available as part of the {{integrations-server}}. For self-managed deployments, refer to [Deploy on-premises and self-managed](/reference/ingestion-tools/fleet/add-fleet-server-on-prem.md).
+* **[{{fleet-server}}](/reference/ingestion-tools/fleet/fleet-server.md) running in a location accessible to {{agent}}.** {{agent}} must have a direct network connection to {{fleet-server}} and {{es}}. If you’re using {{ecloud}}, {{fleet-server}} is already available as part of the {{integrations-server}}. For self-managed deployments, refer to [Deploy on-premises and self-managed](/reference/ingestion-tools/fleet/add-fleet-server-on-prem.md).
* **Internet connection for {{kib}} to download integration packages from the {{package-registry}}.** Make sure the {{kib}} server can connect to `https://epr.elastic.co` on port `443`. If your environment has network traffic restrictions, there are ways to work around this requirement. See [Air-gapped environments](/reference/ingestion-tools/fleet/air-gapped.md) for more information.
If you are using a {{fleet-server}} that uses your organization’s certificate, you will also need:
diff --git a/reference/ingestion-tools/fleet/mutual-tls.md b/reference/ingestion-tools/fleet/mutual-tls.md
index 7b337f75d..414bd21be 100644
--- a/reference/ingestion-tools/fleet/mutual-tls.md
+++ b/reference/ingestion-tools/fleet/mutual-tls.md
@@ -13,7 +13,7 @@ For a summary of flow by which TLS is established between components using eithe
* [On-premise deployments](#mutual-tls-on-premise)
* [{{fleet-server}} on {{ecloud}}](#mutual-tls-cloud)
* [{{fleet-server}} on {{ecloud}} using a proxy](#mutual-tls-cloud-proxy)
-* [{{fleet-server}} on-premise and Hosted Elasticsearch Service](#mutual-tls-on-premise-hosted-es)
+* [{{fleet-server}} on-premise and {{ech}}](#mutual-tls-on-premise-hosted-es)
## Overview [mutual-tls-overview]
@@ -157,20 +157,20 @@ During {{agent}} installation on premise use the following options:
| `--elastic-agent-cert-key-passphrase` | The path to the file that contains the passphrase for the mutual TLS private key that {{agent}} will use to connect to {{fleet-server}} |
-## {{fleet-server}} on-premise and Hosted Elasticsearch Service [mutual-tls-on-premise-hosted-es]
+## {{fleet-server}} on-premise and {{ech}} [mutual-tls-on-premise-hosted-es]
In some scenarios you may want to deploy {{fleet-server}} on your own premises. In this case, you’re able to provide your own certificates and certificate authority to enable mTLS between {{fleet-server}} and {{agent}}.
However, as with the [{{fleet-server}} on {{ecloud}}](#mutual-tls-cloud) use case, the data plane TLS connections terminate at the {{ecloud}} boundary. {{ecloud}} is not a multi-tenanted service and therefore can’t provide per-user certificates.
:::{image} images/mutual-tls-fs-onprem.png
-:alt: Diagram of mutual TLS with Fleet Server on premise and hosted Elasticsearch Service deployment model
+:alt: Diagram of mutual TLS with Fleet Server on premise and {{ech}} deployment model
:::
Similar to the {{fleet-server}} on {{ecloud}} use case, a secure proxy can be placed in such an environment to terminate the TLS connections and satisfy the mTLS requirements.
:::{image} images/mutual-tls-fs-onprem-proxy.png
-:alt: Diagram of mutual TLS with Fleet Server on premise and hosted Elasticsearch Service deployment model with a proxy
+:alt: Diagram of mutual TLS with Fleet Server on premise and {{ech}} deployment model with a proxy
:::
diff --git a/reference/ingestion-tools/fleet/running-on-kubernetes-managed-by-fleet.md b/reference/ingestion-tools/fleet/running-on-kubernetes-managed-by-fleet.md
index d1325ca9f..d464cabd0 100644
--- a/reference/ingestion-tools/fleet/running-on-kubernetes-managed-by-fleet.md
+++ b/reference/ingestion-tools/fleet/running-on-kubernetes-managed-by-fleet.md
@@ -12,9 +12,9 @@ mapped_pages:
::::{tab-set}
- :::{tab-item} Elasticsearch Service
+ :::{tab-item} {{ech}}
- To get started quickly, spin up a deployment of our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service). The {{ess}} is available on AWS, GCP, and Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
+ To get started quickly, spin up an [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service) deployment. {{ech}} is available on AWS, GCP, and Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
:::
:::{tab-item} Self-managed
@@ -187,7 +187,7 @@ If you’d like to run {{agent}} on Kubernetes on a read-only file system, you c
::::{tab-set}
- :::{tab-item} Elasticsearch Service
+ :::{tab-item} {{ech}}
1. [Log in](https://cloud.elastic.co/) to your {{ecloud}} account.
2. Navigate to the {{kib}} endpoint in your deployment.
diff --git a/reference/ingestion-tools/fleet/running-on-kubernetes-standalone.md b/reference/ingestion-tools/fleet/running-on-kubernetes-standalone.md
index 2300d6632..e583a3b68 100644
--- a/reference/ingestion-tools/fleet/running-on-kubernetes-standalone.md
+++ b/reference/ingestion-tools/fleet/running-on-kubernetes-standalone.md
@@ -12,8 +12,8 @@ mapped_pages:
::::{tab-set}
- :::{tab-item} Elasticsearch Service
- To get started quickly, spin up a deployment of our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service). The {{ess}} is available on AWS, GCP, and Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
+ :::{tab-item} {{ech}}
+ To get started quickly, spin up an [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service) deployment. {{ech}} is available on AWS, GCP, and Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
:::
:::{tab-item} Self-managed
@@ -157,7 +157,7 @@ If you’d like to run {{agent}} on Kubernetes on a read-only file system, you c
::::{tab-set}
- :::{tab-item} Elasticsearch Service
+ :::{tab-item} {{ech}}
1. [Log in](https://cloud.elastic.co/) to your {{ecloud}} account.
2. Navigate to the {{kib}} endpoint in your deployment.
diff --git a/reference/ingestion-tools/fleet/secure-connections.md b/reference/ingestion-tools/fleet/secure-connections.md
index 38fcc75eb..1d4c17760 100644
--- a/reference/ingestion-tools/fleet/secure-connections.md
+++ b/reference/ingestion-tools/fleet/secure-connections.md
@@ -12,7 +12,7 @@ For the install settings specific to mutual TLS, as opposed to one-way TLS, refe
For a summary of flow by which TLS is established between components using either one-way or mutual TLS, refer to [One-way and mutual TLS certifications flow](/reference/ingestion-tools/fleet/tls-overview.md).
::::{tip}
-Our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body) on {{ecloud}} provides secure, encrypted connections out of the box!
+[{{ecloud}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body) provides secure, encrypted connections out of the box!
::::
diff --git a/reference/ingestion-tools/fleet/secure-logstash-connections.md b/reference/ingestion-tools/fleet/secure-logstash-connections.md
index f5ec4e709..c8af46e05 100644
--- a/reference/ingestion-tools/fleet/secure-logstash-connections.md
+++ b/reference/ingestion-tools/fleet/secure-logstash-connections.md
@@ -94,9 +94,9 @@ In your {{ls}} configuration directory, open the `pipelines.yml` file and add th
path.config: "/etc/path/to/elastic-agent-pipeline.conf"
```
-In the `elastic-agent-pipeline.conf` file, add the pipeline configuration. Note that the configuration needed for {{ess}} on {{ecloud}} is different from self-managed {{es}} clusters. If you copied the configuration shown in {{fleet}}, adjust it as needed.
+In the `elastic-agent-pipeline.conf` file, add the pipeline configuration. Note that the configuration needed for {{ech}} is different from self-managed {{es}} clusters. If you copied the configuration shown in {{fleet}}, adjust it as needed.
-{{ess}} example:
+{{ech}} example:
```text
input {
@@ -122,7 +122,7 @@ output {
1. Use the `cloud_id` shown on your deployment page in {{ecloud}}.
2. In {{fleet}}, you can generate this API key when you add a {{ls}} output.
-3. {{ess}} uses standard publicly trusted certificates, so there’s no need specify other SSL settings here.
+3. {{ech}} uses standard publicly trusted certificates, so there’s no need specify other SSL settings here.
Self-managed {{es}} cluster example:
diff --git a/reference/overview/index.md b/reference/overview/index.md
index ea561e412..b49f55117 100644
--- a/reference/overview/index.md
+++ b/reference/overview/index.md
@@ -13,5 +13,5 @@ Explore the reference documentation for Elastic APIs.
| {{kib}} | * [{{kib}}](https://www.elastic.co/docs/api/doc/kibana)
* [{{kib}} Serverless](https://www.elastic.co/docs/api/doc/serverless)
* [{{fleet}}](/reference/ingestion-tools/fleet/fleet-api-docs.md)
* [{{observability}} Serverless SLOs](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-slo)
* [{{elastic-sec}}](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-security-ai-assistant-api)
* [{{elastic-sec}} Serverless](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-security-ai-assistant-api)
|
| {{ls}} | * [Monitoring {{ls}}](https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html)
|
| APM | * [APM](/solutions/observability/apps/apm-server-api.md)
* [APM Serverless](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-apm-agent-configuration)
* [Observability intake Serverless](https://www.elastic.co/docs/api/doc/observability-serverless)
|
-| {{ecloud}} | * [{{ess}}](https://www.elastic.co/docs/api/doc/cloud)
* [{{ecloud}} Serverless](https://www.elastic.co/docs/api/doc/elastic-cloud-serverless)
* [{{ece}}](https://www.elastic.co/docs/api/doc/cloud-enterprise)
* [{{eck}}](cloud-on-k8s://docs/reference/k8s-api-reference.md)
|
+| {{ecloud}} | * [{{ech}}](https://www.elastic.co/docs/api/doc/cloud)
* [{{ecloud}} Serverless](https://www.elastic.co/docs/api/doc/elastic-cloud-serverless)
* [{{ece}}](https://www.elastic.co/docs/api/doc/cloud-enterprise)
* [{{eck}}](cloud-on-k8s://docs/reference/k8s-api-reference.md)
|
diff --git a/solutions/observability/apps/configure-apm-server.md b/solutions/observability/apps/configure-apm-server.md
index 9afa26ad0..7fb6d2bcb 100644
--- a/solutions/observability/apps/configure-apm-server.md
+++ b/solutions/observability/apps/configure-apm-server.md
@@ -53,9 +53,9 @@ User settings are appended to the `apm-server.yml` configuration file for your i
To add user settings:
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.
+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.
+ 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.
3. From your deployment menu, go to the **Edit** page.
4. In the **APM** section, select **Edit user settings**. (For existing deployments with user settings, you may have to expand the **Edit apm-server.yml** caret instead.)
diff --git a/solutions/observability/apps/use-synthetics-with-traffic-filters.md b/solutions/observability/apps/use-synthetics-with-traffic-filters.md
index aefcd6612..551c186db 100644
--- a/solutions/observability/apps/use-synthetics-with-traffic-filters.md
+++ b/solutions/observability/apps/use-synthetics-with-traffic-filters.md
@@ -51,7 +51,7 @@ Once you know the CIDR blocks for your testing sources, add them to your {{es}}
For example, if you had a {{private-location}} running with a public CIDR block of `1.2.3.4/32` and were running tests from the `Europe - United Kingdom` region, you would first create a traffic filter with the following:
:::{image} ../../../images/observability-synthetics-traffic-filters-create-filter.png
-:alt: Create a traffic filter in {{cloud}}
+:alt: Create a traffic filter in {{ecloud}}
:class: screenshot
:::
diff --git a/troubleshoot/deployments/cloud-enterprise/heap-dumps.md b/troubleshoot/deployments/cloud-enterprise/heap-dumps.md
index b0c913ea6..a3d7d8adf 100644
--- a/troubleshoot/deployments/cloud-enterprise/heap-dumps.md
+++ b/troubleshoot/deployments/cloud-enterprise/heap-dumps.md
@@ -13,7 +13,7 @@ From the Elastic Cloud Enterprise console you can capture JVM heap dumps from de
You can view and download captured heap dumps for a given deployment.
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
@@ -42,7 +42,7 @@ The JVM will be paused while the heap dump is being captured, so there may be a
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
@@ -51,7 +51,7 @@ The JVM will be paused while the heap dump is being captured, so there may be a
Alternatively, you can capture an on-demand heap dump directly from the **Heap dumps** page.
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/troubleshoot/deployments/cloud-enterprise/thread-dumps.md b/troubleshoot/deployments/cloud-enterprise/thread-dumps.md
index 1c5c36375..bad22486f 100644
--- a/troubleshoot/deployments/cloud-enterprise/thread-dumps.md
+++ b/troubleshoot/deployments/cloud-enterprise/thread-dumps.md
@@ -13,7 +13,7 @@ You can capture JVM thread dumps from deployment instances. This can help discov
You can capture a thread dump from the deployment overview page.
1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. On the deployments page, select your deployment.
+2. On the **Deployments** page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
diff --git a/troubleshoot/elasticsearch/add-tier.md b/troubleshoot/elasticsearch/add-tier.md
index 0078fd041..faa2e0c86 100644
--- a/troubleshoot/elasticsearch/add-tier.md
+++ b/troubleshoot/elasticsearch/add-tier.md
@@ -16,13 +16,13 @@ In order to allow indices to be allocated, follow these steps to add the [data t
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to get the shards assigned we need enable a new tier in the deployment.
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/allow-all-cluster-allocation.md b/troubleshoot/elasticsearch/allow-all-cluster-allocation.md
index 7b9e965b2..9f959ab3f 100644
--- a/troubleshoot/elasticsearch/allow-all-cluster-allocation.md
+++ b/troubleshoot/elasticsearch/allow-all-cluster-allocation.md
@@ -14,7 +14,7 @@ In order to (re)allow all data to be allocated follow these steps:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to get the shards assigned we’ll need to change the value of the [configuration](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings.md#cluster-routing-allocation-enable) that restricts the assignemnt of the shards to allow all shards to be allocated.
We’ll achieve this by inspecting the system-wide `cluster.routing.allocation.enable` [cluster setting](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) and changing the configured value to `all`.
@@ -22,7 +22,7 @@ We’ll achieve this by inspecting the system-wide `cluster.routing.allocation.e
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/allow-all-index-allocation.md b/troubleshoot/elasticsearch/allow-all-index-allocation.md
index 0da28da37..41a8d97c1 100644
--- a/troubleshoot/elasticsearch/allow-all-index-allocation.md
+++ b/troubleshoot/elasticsearch/allow-all-index-allocation.md
@@ -17,13 +17,13 @@ In order to (re)allow all data to be allocated follow these steps:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to get the shards assigned we’ll need to change the value of the [configuration](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/index-settings/index-modules.md#index-routing-allocation-enable-setting) that restricts the assignemnt of the shards to `all`.
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md b/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md
index 363966e5b..82cea7c2f 100644
--- a/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md
+++ b/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md
@@ -15,11 +15,11 @@ Reducing the replicas of an index can potentially reduce search throughput and d
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
index 9c2b0954a..ed3ed03d9 100644
--- a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
+++ b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
@@ -14,13 +14,13 @@ In order to diagnose the unassigned shards in your deployment use the following
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to diagnose the unassigned shards, follow the next steps:
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md b/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md
index c923d170e..5d71a0abc 100644
--- a/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md
+++ b/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md
@@ -10,7 +10,7 @@ Multiple {{es}} deployments are writing to the same snapshot repository. {{es}}
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
Fixing the corrupted repository will entail making changes in multiple deployments that write to the same snapshot repository. Only one deployment must be writing to a repository. The deployment that will keep writing to the repository will be called the "primary" deployment (the current cluster), and the other one(s) where we’ll mark the repository read-only as the "secondary" deployments.
First mark the repository as read-only on the secondary deployments:
@@ -18,7 +18,7 @@ First mark the repository as read-only on the secondary deployments:
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/elasticsearch.md b/troubleshoot/elasticsearch/elasticsearch.md
index 6a98f8771..4fbb85b06 100644
--- a/troubleshoot/elasticsearch/elasticsearch.md
+++ b/troubleshoot/elasticsearch/elasticsearch.md
@@ -74,7 +74,7 @@ If none of these guides relate to your issue, or you need further assistance, th
* If you have an active subscription, you have several options:
* Go directly to the [Support Portal](http://support.elastic.co)
- * From the {{ess}} Console, go to the [Support page](https://cloud.elastic.co/support?page=docs&placement=docs-body), or select the support icon that looks like a life preserver on any page.
+ * From the {{ecloud}} Console, go to the [Support page](https://cloud.elastic.co/support?page=docs&placement=docs-body), or select the support icon that looks like a life preserver on any page.
* Contact us by email: `support@elastic.co`
::::{tip}
diff --git a/troubleshoot/elasticsearch/fix-master-node-out-of-disk.md b/troubleshoot/elasticsearch/fix-master-node-out-of-disk.md
index cc8768b11..aeddcf168 100644
--- a/troubleshoot/elasticsearch/fix-master-node-out-of-disk.md
+++ b/troubleshoot/elasticsearch/fix-master-node-out-of-disk.md
@@ -12,9 +12,9 @@ mapped_pages:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the gear under the `Manage deployment` column that corresponds to the name of your deployment.
+2. On the **Hosted deployments** panel, click the gear under the `Manage deployment` column that corresponds to the name of your deployment.
3. Go to `Actions > Edit deployment` and then go to the `Master instances` section:
:::{image} ../../images/elasticsearch-reference-increase-disk-capacity-master-node.png
diff --git a/troubleshoot/elasticsearch/fix-other-node-out-of-disk.md b/troubleshoot/elasticsearch/fix-other-node-out-of-disk.md
index 09e4985ec..a4978042b 100644
--- a/troubleshoot/elasticsearch/fix-other-node-out-of-disk.md
+++ b/troubleshoot/elasticsearch/fix-other-node-out-of-disk.md
@@ -12,9 +12,9 @@ mapped_pages:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the gear under the `Manage deployment` column that corresponds to the name of your deployment.
+2. On the **Hosted deployments** panel, click the gear under the `Manage deployment` column that corresponds to the name of your deployment.
3. Go to `Actions > Edit deployment` and then go to the `Coordinating instances` or the `Machine Learning instances` section depending on the roles listed in the diagnosis:
:::{image} ../../images/elasticsearch-reference-increase-disk-capacity-other-node.png
diff --git a/troubleshoot/elasticsearch/fix-watermark-errors.md b/troubleshoot/elasticsearch/fix-watermark-errors.md
index 208ef357f..6730c66d6 100644
--- a/troubleshoot/elasticsearch/fix-watermark-errors.md
+++ b/troubleshoot/elasticsearch/fix-watermark-errors.md
@@ -97,7 +97,7 @@ To resolve watermark errors permanently, perform one of the following actions:
* update related [ILM policy](../../manage-data/lifecycle/index-lifecycle-management.md) to push indices through to later [data tiers](../../manage-data/lifecycle/data-tiers.md)
::::{tip}
-On {{ess}} and {{ece}}, indices may need to be temporarily deleted via its [Elasticsearch API Console](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-console.md) to later [snapshot restore](../../deploy-manage/tools/snapshot-and-restore/restore-snapshot.md) in order to resolve [cluster health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) `status:red` which will block [attempted changes](../../deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md). If you experience issues with this resolution flow on {{ess}}, kindly reach out to [Elastic Support](https://support.elastic.co) for assistance.
+On {{ech}} and {{ece}}, indices may need to be temporarily deleted via its [Elasticsearch API Console](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-api-console.md) to later [snapshot restore](../../deploy-manage/tools/snapshot-and-restore/restore-snapshot.md) in order to resolve [cluster health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) `status:red` which will block [attempted changes](../../deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md). If you experience issues with this resolution flow on {{ech}}, kindly reach out to [Elastic Support](https://support.elastic.co) for assistance.
::::
diff --git a/troubleshoot/elasticsearch/high-cpu-usage.md b/troubleshoot/elasticsearch/high-cpu-usage.md
index 8996f1a1e..7bd0240b1 100644
--- a/troubleshoot/elasticsearch/high-cpu-usage.md
+++ b/troubleshoot/elasticsearch/high-cpu-usage.md
@@ -35,7 +35,7 @@ To track CPU usage over time, we recommend enabling monitoring:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
* (Recommended) Enable [logs and metrics](../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). When logs and metrics are enabled, monitoring information is visible on {{kib}}'s [Stack Monitoring](../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md) page.
You can also enable the [CPU usage threshold alert](../../deploy-manage/monitor/monitoring-data/kibana-alerts.md) to be notified about potential issues through email.
@@ -46,7 +46,7 @@ To track CPU usage over time, we recommend enabling monitoring:
* **CPU credits**: Your remaining CPU credits, measured in seconds of CPU time.
-{{ess}} grants [CPU credits](../../deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md) per deployment to provide smaller clusters with performance boosts when needed. High CPU usage can deplete these credits, which might lead to [performance degradation](../monitoring/performance.md) and [increased cluster response times](../monitoring/cluster-response-time.md).
+{{ech}} grants [CPU credits](../../deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md) per deployment to provide smaller clusters with performance boosts when needed. High CPU usage can deplete these credits, which might lead to [performance degradation](../monitoring/performance.md) and [increased cluster response times](../monitoring/cluster-response-time.md).
::::::
::::::{tab-item} Self-managed
diff --git a/troubleshoot/elasticsearch/high-jvm-memory-pressure.md b/troubleshoot/elasticsearch/high-jvm-memory-pressure.md
index f9342b550..a4b886c12 100644
--- a/troubleshoot/elasticsearch/high-jvm-memory-pressure.md
+++ b/troubleshoot/elasticsearch/high-jvm-memory-pressure.md
@@ -20,7 +20,7 @@ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
From your deployment menu, click **Elasticsearch**. Under **Instances**, each instance displays a **JVM memory pressure** indicator. When the JVM memory pressure reaches 75%, the indicator turns red.
You can also use the [nodes stats API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) to calculate the current JVM memory pressure for each node.
diff --git a/troubleshoot/elasticsearch/increase-capacity-data-node.md b/troubleshoot/elasticsearch/increase-capacity-data-node.md
index 43b038a58..cc04ca4d1 100644
--- a/troubleshoot/elasticsearch/increase-capacity-data-node.md
+++ b/troubleshoot/elasticsearch/increase-capacity-data-node.md
@@ -8,11 +8,11 @@ mapped_pages:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to increase the disk capacity of the data nodes in your cluster:
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the gear under the `Manage deployment` column that corresponds to the name of your deployment.
+2. On the **Hosted deployments** panel, click the gear under the `Manage deployment` column that corresponds to the name of your deployment.
3. If autoscaling is available but not enabled, please enable it. You can do this by clicking the button `Enable autoscaling` on a banner like the one below:
:::{image} ../../images/elasticsearch-reference-autoscaling_banner.png
diff --git a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md
index 34ae40e02..ebae1c4fc 100644
--- a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md
+++ b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md
@@ -16,13 +16,13 @@ In order to fix this follow the next steps:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to get the shards assigned we’ll need to increase the number of shards that can be collocated on a node in the cluster. We’ll achieve this by inspecting the system-wide `cluster.routing.allocation.total_shards_per_node` [cluster setting](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) and increasing the configured value.
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/increase-shard-limit.md b/troubleshoot/elasticsearch/increase-shard-limit.md
index 1b2136857..576da94eb 100644
--- a/troubleshoot/elasticsearch/increase-shard-limit.md
+++ b/troubleshoot/elasticsearch/increase-shard-limit.md
@@ -16,13 +16,13 @@ In order to fix this follow the next steps:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to get the shards assigned we’ll need to increase the number of shards that can be collocated on a node. We’ll achieve this by inspecting the configuration for the `index.routing.allocation.total_shards_per_node` [index setting](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-settings) and increasing the configured value for the indices that have shards unassigned.
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/increase-tier-capacity.md b/troubleshoot/elasticsearch/increase-tier-capacity.md
index 92cae5336..94ab500ed 100644
--- a/troubleshoot/elasticsearch/increase-tier-capacity.md
+++ b/troubleshoot/elasticsearch/increase-tier-capacity.md
@@ -14,13 +14,13 @@ In order to fix this follow the next steps:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
One way to get the replica shards assigned is to add an availability zone. This will increase the number of data nodes in the {{es}} cluster so that the replica shards can be assigned. This can be done by editing your deployment. But first you need to discover which tier an index is targeting for assignment. Do this using {{kib}}.
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/repeated-snapshot-failures.md b/troubleshoot/elasticsearch/repeated-snapshot-failures.md
index 3586cdfc9..bcef7a5f9 100644
--- a/troubleshoot/elasticsearch/repeated-snapshot-failures.md
+++ b/troubleshoot/elasticsearch/repeated-snapshot-failures.md
@@ -14,13 +14,13 @@ In the event that an automated {{slm}} policy execution is experiencing repeated
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to check the status of failing {{slm}} policies we need to go to Kibana and retrieve the [Snapshot Lifecycle Policy information](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-get-lifecycle).
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/restore-from-snapshot.md b/troubleshoot/elasticsearch/restore-from-snapshot.md
index 6fc9db4d6..170f67afc 100644
--- a/troubleshoot/elasticsearch/restore-from-snapshot.md
+++ b/troubleshoot/elasticsearch/restore-from-snapshot.md
@@ -14,13 +14,13 @@ Restoring the missing data requires you to have a backup of the affected indices
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to restore the indices and data streams that are missing data:
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/start-ilm.md b/troubleshoot/elasticsearch/start-ilm.md
index 81645dfee..642dbac5d 100644
--- a/troubleshoot/elasticsearch/start-ilm.md
+++ b/troubleshoot/elasticsearch/start-ilm.md
@@ -25,13 +25,13 @@ In order to start the automatic {{ilm}} service, follow these steps:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to start {{ilm}} we need to go to Kibana and execute the [start command](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-start).
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
@@ -113,13 +113,13 @@ In order to start the snapshot lifecycle management service, follow these steps:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to start {{slm}} we need to go to Kibana and execute the [start command](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-start).
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md b/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md
index 4841f0fba..73b0fe00a 100644
--- a/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md
+++ b/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md
@@ -16,13 +16,13 @@ In order to fix this follow the next steps:
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
In order to get the shards assigned we need to call the [migrate to data tiers routing](../../manage-data/lifecycle/data-tiers.md) API which will resolve the conflicting routing configurations towards using the standardized [data tiers](../../manage-data/lifecycle/data-tiers.md). This will also future-proof the system by migrating the index templates and ILM policies if needed.
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
index db7250bd0..43fb3eb36 100644
--- a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
+++ b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
@@ -19,11 +19,11 @@ If you’re confident your changes won’t destabilize the cluster, you can temp
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
@@ -229,11 +229,11 @@ If you’re confident your changes won’t destabilize the cluster, you can temp
:::::::{tab-set}
-::::::{tab-item} Elasticsearch Service
+::::::{tab-item} {{ech}}
**Use {{kib}}**
1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Elasticsearch Service** panel, click the name of your deployment.
+2. On the **Hosted deployments** panel, click the name of your deployment.
::::{note}
If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
diff --git a/troubleshoot/ingest/fleet/frequently-asked-questions.md b/troubleshoot/ingest/fleet/frequently-asked-questions.md
index e84083f1d..18164b550 100644
--- a/troubleshoot/ingest/fleet/frequently-asked-questions.md
+++ b/troubleshoot/ingest/fleet/frequently-asked-questions.md
@@ -157,7 +157,7 @@ Credentials that you provide for an agent or integration policy are stored in {{
## Which {{es}} and {{kib}} ports need to be accessible? [which-es-kibana-ports-are-needed]
-The policy generated by {{fleet}} already contains the correct {{es}} address and port for your setup. If you run everything locally, the address is `127.0.0.1:9200`. If you use our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body) on {{ecloud}}, you can copy the {{es}} endpoint URL from the overview page of your deployment. If you’re not running in {{ecloud}}, make sure the {{kib}} and {{es}} HTTPS ports are both accessible; by default these are `5601` and `9200` respectively.
+The policy generated by {{fleet}} already contains the correct {{es}} address and port for your setup. If you run everything locally, the address is `127.0.0.1:9200`. If you use [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body), you can copy the {{es}} endpoint URL from the overview page of your deployment. If you’re not running in {{ecloud}}, make sure the {{kib}} and {{es}} HTTPS ports are both accessible; by default these are `5601` and `9200` respectively.
## If I delete an integration dashboard asset from {{kib}}, how do I get it back? [how-do-i-reinstall-a-missing-dashboard-asset]
diff --git a/troubleshoot/kibana/access.md b/troubleshoot/kibana/access.md
index 991b83f91..703a9b2fd 100644
--- a/troubleshoot/kibana/access.md
+++ b/troubleshoot/kibana/access.md
@@ -10,7 +10,7 @@ mapped_pages:
%
% ## Set up on cloud [_set_up_on_cloud]
%
-% There’s no faster way to get started than with our hosted {{ess}} on Elastic Cloud:
+% There’s no faster way to get started than with {{ecloud}}:
%
% 1. [Get a free trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body).
% 2. Log into [Elastic Cloud](https://cloud.elastic.co?page=docs&placement=docs-body).
diff --git a/troubleshoot/monitoring/cluster-response-time.md b/troubleshoot/monitoring/cluster-response-time.md
index 125093a6d..c442bb2dd 100644
--- a/troubleshoot/monitoring/cluster-response-time.md
+++ b/troubleshoot/monitoring/cluster-response-time.md
@@ -9,7 +9,7 @@ mapped_pages:
Your {{es}} cluster is humming along nicely with good performance until you suddenly notice that response times increase substantially, for both index response times and search response times. The cluster is slow to respond for about 10 minutes, after which performance returns to a normal level.
-Initially, you think that perhaps memory pressure is to blame, because you already know that [high memory pressure can cause performance issues](/troubleshoot/monitoring/high-memory-pressure.md). You look at the **Cluster Performance Metrics** section of the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) and, after some zooming in to the right time frame, you get these metrics:
+Initially, you think that perhaps memory pressure is to blame, because you already know that [high memory pressure can cause performance issues](/troubleshoot/monitoring/high-memory-pressure.md). You look at the **Cluster Performance Metrics** section of the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and, after some zooming in to the right time frame, you get these metrics:
:::{image} /images/cloud-metrics-response-times.png
:alt: Cluster performance metrics
diff --git a/troubleshoot/monitoring/deployment-health-warnings.md b/troubleshoot/monitoring/deployment-health-warnings.md
index 6eef3c420..8c6577be3 100644
--- a/troubleshoot/monitoring/deployment-health-warnings.md
+++ b/troubleshoot/monitoring/deployment-health-warnings.md
@@ -8,7 +8,7 @@ mapped_pages:
# Troubleshoot deployment health warnings [ec-deployment-no-op]
-The Elasticsearch Service [Deployments](https://cloud.elastic.co/deployments) page shows the current status of your active deployments. From time to time you may get one or more health warnings, such as the following:
+The {{ecloud}} [Deployments](https://cloud.elastic.co/deployments) page shows the current status of your active deployments. From time to time you may get one or more health warnings, such as the following:
:::{image} /images/cloud-ec-ce-deployment-health-warning.png
:alt: A screen capture of the deployment page showing a typical warning: Deployment health warning: Latest change to {{es}} configuration failed.
@@ -18,7 +18,7 @@ The Elasticsearch Service [Deployments](https://cloud.elastic.co/deployments) pa
To resolve a single health warning, we recommended first re-applying any pending changes: Select **Edit** in the deployment menu to open the Edit page and then click **Save** without making any changes. This will check all components for pending changes and will apply the changes as needed. This may impact the uptime of clusters which are not [highly available](/deploy-manage/production-guidance/plan-for-production-elastic-cloud.md#ec-ha).
-Re-saving the deployment configuration without making any changes is often all that’s needed to resolve a transient health warning on the UI. Saving will redirect you to the Elasticsearch Service deployment [Activity page](/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) where you can monitor plan completion. Repeat errors should be investigated; for more information refer to [resolving configuration change errors](/troubleshoot/monitoring/node-bootlooping.md).
+Re-saving the deployment configuration without making any changes is often all that’s needed to resolve a transient health warning on the UI. Saving will redirect you to the {{ech}} deployment [Activity page](/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) where you can monitor plan completion. Repeat errors should be investigated; for more information refer to [resolving configuration change errors](/troubleshoot/monitoring/node-bootlooping.md).
**Seeing multiple warnings?**
diff --git a/troubleshoot/monitoring/high-availability.md b/troubleshoot/monitoring/high-availability.md
index e6fb0600f..06c4efbc6 100644
--- a/troubleshoot/monitoring/high-availability.md
+++ b/troubleshoot/monitoring/high-availability.md
@@ -9,9 +9,9 @@ mapped_pages:
% TODO: Edit edit edit
-You created a new cluster in Elasticsearch Service that uses three availability zones and index replicas, because you want to use the [cluster for production](/deploy-manage/production-guidance/plan-for-production-elastic-cloud.md#ec-ha). It’s a mission-critical deployment and you need it to be able to handle user requests at all times. Your cluster has been up and running for some time and it seems to handle its workload well. But is this cluster really highly available, given its current workload?
+You created a new {{ech}} deployment that uses three availability zones and index replicas, because you want to use the [cluster for production](/deploy-manage/production-guidance/plan-for-production-elastic-cloud.md#ec-ha). It’s a mission-critical deployment and you need it to be able to handle user requests at all times. Your cluster has been up and running for some time and it seems to handle its workload well. But is this cluster really highly available, given its current workload?
-To answer this question, let’s take a look at CPU usage in the **Cluster Performance Metrics** section in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body):
+To answer this question, let’s take a look at CPU usage in the **Cluster Performance Metrics** section in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body):
:::{image} /images/cloud-metrics-cpu.png
:alt: CPU usage over time
diff --git a/troubleshoot/monitoring/high-memory-pressure.md b/troubleshoot/monitoring/high-memory-pressure.md
index 0d45735de..7c04dca65 100644
--- a/troubleshoot/monitoring/high-memory-pressure.md
+++ b/troubleshoot/monitoring/high-memory-pressure.md
@@ -32,7 +32,7 @@ If the performance impact from high memory pressure is not acceptable, you need
## Increase the deployment size [ec_increase_the_deployment_size]
-Scaling with Elasticsearch Service is easy: simply log in to the Elasticsearch Service console, select your deployment, select edit, and either increase the number of zones or the size per zone.
+Scaling with {{ech}} is easy: simply log in to the {{ecloud}} Console, select your deployment, select edit, and either increase the number of zones or the size per zone.
## Reduce the workload [ec_reduce_the_workload]
diff --git a/troubleshoot/monitoring/node-bootlooping.md b/troubleshoot/monitoring/node-bootlooping.md
index a62e61629..8cd9ea897 100644
--- a/troubleshoot/monitoring/node-bootlooping.md
+++ b/troubleshoot/monitoring/node-bootlooping.md
@@ -89,7 +89,7 @@ In some cases, settings may accidentally be added to the keystore that should ha
## Expired custom plugins or bundles [ec-config-change-errors-expired-bundle-extension]
-During the process of applying a configuration change, Elasticsearch Service checks to determine if any [uploaded custom plugins or bundles](/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md) are expired.
+During the process of applying a configuration change, {{ecloud}} checks to determine if any [uploaded custom plugins or bundles](/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md) are expired.
Problematic plugins produce oscillating {{es}} start-up logs like the following:
diff --git a/troubleshoot/monitoring/node-moves-outages.md b/troubleshoot/monitoring/node-moves-outages.md
index 7300b596f..65a79d2f3 100644
--- a/troubleshoot/monitoring/node-moves-outages.md
+++ b/troubleshoot/monitoring/node-moves-outages.md
@@ -10,7 +10,7 @@ To ensure that your nodes are located on healthy hosts, we vacate nodes to perfo
All major scheduled maintenance and incidents can be found on the Elastic [status page](https://status.elastic.co/). You can subscribe to that page to be notified about updates.
-If events on your deployment don’t correlate to any items listed on the status page, the events are due to minor routine maintenance performed on only a subset of Elasticsearch Service deployments.
+If events on your deployment don’t correlate to any items listed on the status page, the events are due to minor routine maintenance performed on only a subset of {{ech}} deployments.
**What is the impact?**
diff --git a/troubleshoot/monitoring/performance.md b/troubleshoot/monitoring/performance.md
index 776f2f7bf..6bb842f80 100644
--- a/troubleshoot/monitoring/performance.md
+++ b/troubleshoot/monitoring/performance.md
@@ -9,7 +9,7 @@ mapped_pages:
You have a smaller {{es}} cluster and you’ve noticed that performance seems to have declined recently. The response time during searches seems to have gone up, and overall the system just doesn’t seem to perform quite as well as it used to. You have already looked at the cluster performance metrics and have confirmed that both index and search response times have increased steadily and remained higher than before. So what explains the performance degradation?
-When you look in the **Cluster Performance Metrics** section of the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), you get the following metrics:
+When you look in the **Cluster Performance Metrics** section of the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), you get the following metrics:
:::{image} /images/cloud-metrics-credits.png
:alt: CPU usage versus CPU credits over time
diff --git a/troubleshoot/monitoring/unavailable-nodes.md b/troubleshoot/monitoring/unavailable-nodes.md
index e84519cb8..22c94598b 100644
--- a/troubleshoot/monitoring/unavailable-nodes.md
+++ b/troubleshoot/monitoring/unavailable-nodes.md
@@ -45,12 +45,8 @@ If your issue is not addressed here, then [contact Elastic support for help](/tr
**Health check**
-1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. From the Elasticsearch Service panel, click the **Quick link** icon corresponding to the deployment that you want to manage.
-
- :::{image} /images/cloud-ec-quick-link-to-deployment.png
- :alt: Quick link to the deployment page
- :::
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+2. Click the **Manage** link corresponding to the deployment that you want to manage.
3. On your deployment page, scroll down to **Instances** and check if the disk allocation for your {{es}} instance is over 90%.
@@ -92,7 +88,7 @@ If your {{es}} cluster is unhealthy and reports a status of red, then increasing
**Health check**
-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. From the {{es}} Service panel, click the **Quick link** icon corresponding to the deployment that you want to manage.
:::{image} /images/cloud-ec-quick-link-to-deployment.png
@@ -151,7 +147,7 @@ If your {{es}} cluster is unhealthy and reports a status of red, the scale up co
**Health check**
-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. From the {{es}} Service panel, click the **Quick link** icon corresponding to the deployment that you want to manage.
:::{image} /images/cloud-ec-quick-link-to-deployment.png
@@ -217,7 +213,7 @@ If your {{es}} cluster is unhealthy and reports a status of red, the scale up co
By default, the allowed CPU usage threshold is set at 85%.
-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. From the {{es}} Service panel, click the **Quick link** icon corresponding to the deployment that you want to manage.
:::{image} /images/cloud-ec-quick-link-to-deployment.png