diff --git a/explore-analyze/alerts-cases/alerts/notifications-domain-allowlist.md b/explore-analyze/alerts-cases/alerts/notifications-domain-allowlist.md index bf9068a6d4..c2fe82a786 100644 --- a/explore-analyze/alerts-cases/alerts/notifications-domain-allowlist.md +++ b/explore-analyze/alerts-cases/alerts/notifications-domain-allowlist.md @@ -24,7 +24,7 @@ Changes to the allowlist do not take effect immediately. After saving your chang ### Using the UI [using-the-ui] -1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). 2. Select a deployment. 3. From your deployment menu, go to the **Edit** page. 4. Select **Save**. diff --git a/explore-analyze/alerts-cases/cases/manage-cases.md b/explore-analyze/alerts-cases/cases/manage-cases.md index 72d5df19e5..198c1882c5 100644 --- a/explore-analyze/alerts-cases/cases/manage-cases.md +++ b/explore-analyze/alerts-cases/cases/manage-cases.md @@ -37,7 +37,7 @@ Open a new case to keep track of issues and share their details with colleagues. You can configure email notifications that occur when users are assigned to cases. -For hosted {{kib}} on {{ess}}: +For {{kib}} on {{ecloud}}: 1. Add the email domains to the [notifications domain allowlist](../alerts.md). diff --git a/explore-analyze/alerts-cases/watcher/enable-watcher.md b/explore-analyze/alerts-cases/watcher/enable-watcher.md index fea71d49f3..d2550a260f 100644 --- a/explore-analyze/alerts-cases/watcher/enable-watcher.md +++ b/explore-analyze/alerts-cases/watcher/enable-watcher.md @@ -24,11 +24,11 @@ To learn more about Kibana alerting and how to use it, check [Alerting and Actio ## Send alerts by email [watcher-allowlist] -You can configure notifications similar to the [operational emails](../../../deploy-manage/cloud-organization/operational-emails.md) that Elasticsearch Service sends automatically to alert you about performance issues in your clusters. +You can configure notifications similar to the [operational emails](../../../deploy-manage/cloud-organization/operational-emails.md) that {{ecloud}} sends automatically to alert you about performance issues in your clusters. Watcher in Elastic Cloud is preconfigured with an email service and can be used without any additional configuration. Alternatively, a custom mail server can be configured as described in [Configuring a custom mail server](#watcher-custom-mail-server) -You can optionally add [HTML sanitization](../../../explore-analyze/alerts-cases/watcher/actions-email.md#email-html-sanitization) settings under [Elasticsearch User settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) so that HTML elements are sanitized in the email notification. +You can optionally add [HTML sanitization](../../../explore-analyze/alerts-cases/watcher/actions-email.md#email-html-sanitization) settings under [Elasticsearch User settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) so that HTML elements are sanitized in the email notification. For more information on sending alerts by email, check [Email action](../../../explore-analyze/alerts-cases/watcher/actions-email.md). diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md b/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md index 021cd27f56..31588c65bf 100644 --- a/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md +++ b/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md @@ -108,7 +108,7 @@ If the estimated model memory limit for an {{anomaly-job}} is greater than the m * Add bigger {{ml}} nodes to the cluster, or * Accept that the job will hit its memory limit and will not necessarily find all the anomalies it could otherwise find. -If you are using {{ece}} or the hosted Elasticsearch Service on Elastic Cloud, `xpack.ml.max_model_memory_limit` is set to prevent you from creating jobs that cannot be allocated to any {{ml}} nodes in the cluster. If you find that you cannot increase `model_memory_limit` for your {{ml}} jobs, the solution is to increase the size of the {{ml}} nodes in your cluster. +If you are using {{ece}} or {{ech}}, `xpack.ml.max_model_memory_limit` is set to prevent you from creating jobs that cannot be allocated to any {{ml}} nodes in the cluster. If you find that you cannot increase `model_memory_limit` for your {{ml}} jobs, the solution is to increase the size of the {{ml}} nodes in your cluster. ### Dedicated indices [ml-ad-dedicated-indices] diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md b/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md index 489ac6c413..eb46af80bb 100644 --- a/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md +++ b/explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md @@ -23,7 +23,7 @@ Need more context? Check out the [{{es}} introduction](/get-started/index.md) to 1. Before you can play with the {{ml-features}}, you must install {{es}} and {{kib}}. {{es}} stores the data and the analysis results. {{kib}} provides a helpful user interface for creating and viewing jobs. ::::{tip} - You can run {{es}} and {{kib}} on your own hardware, or use our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service) on {{ecloud}}. The {{ess}} is available on both AWS and GCP. [Try out the {{ess}} for free](https://www.elastic.co/cloud/elasticsearch-service/signup). + You can run {{es}} and {{kib}} on your own hardware or on [{{ecloud}}](https://www.elastic.co/cloud/). [Try out {{ecloud}} for free](https://cloud.elastic.co/registration?elektra=en-ess-sign-up-page). :::: 2. Verify that your environment is set up properly to use the {{ml-features}}. If the {{es}} {{security-features}} are enabled, to complete this tutorial you need a user that has authority to manage {{anomaly-jobs}}. See [Setup and security](../setting-up-machine-learning.md). diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-elser.md b/explore-analyze/machine-learning/nlp/ml-nlp-elser.md index 3d1de74a77..4d01564574 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-elser.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-elser.md @@ -30,7 +30,7 @@ This approach provides a more understandable search experience compared to vecto To use ELSER, you must have the [appropriate subscription](https://www.elastic.co/subscriptions) level for semantic search or the trial period activated. ::::{note} -The minimum dedicated ML node size for deploying and using the ELSER model is 4 GB in Elasticsearch Service if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself. +The minimum dedicated ML node size for deploying and using the ELSER model is 4 GB in {{ech}} if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself. :::: Enabling trained model autoscaling for your ELSER deployment is recommended. Refer to [*Trained model autoscaling*](ml-nlp-auto-scale.md) to learn more. diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-inference.md b/explore-analyze/machine-learning/nlp/ml-nlp-inference.md index bb3ea1992e..82539d37b6 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-inference.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-inference.md @@ -117,7 +117,7 @@ PUT ner-test ``` ::::{tip} -To use the `annotated_text` data type in this example, you must install the [mapper annotated text plugin](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/mapper-annotated-text.md). For more installation details, refer to [Add plugins provided with {{ess}}](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/cloud/ec-adding-elastic-plugins.md). +To use the `annotated_text` data type in this example, you must install the [mapper annotated text plugin](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/mapper-annotated-text.md). For more installation details, refer to [Add plugins provided with {{ech}}](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/cloud/ec-adding-elastic-plugins.md). :::: You can then use the new pipeline to index some documents. For example, use a bulk indexing request with the `pipeline` query parameter for your NER pipeline: diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-model-ref.md b/explore-analyze/machine-learning/nlp/ml-nlp-model-ref.md index f0aa88d80a..d30917239b 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-model-ref.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-model-ref.md @@ -10,7 +10,7 @@ mapped_pages: # Compatible third party models [ml-nlp-model-ref] ::::{note} -The minimum dedicated ML node size for deploying and using the {{nlp}} models is 16 GB in Elasticsearch Service if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself. +The minimum dedicated ML node size for deploying and using the {{nlp}} models is 16 GB in {{ech}} if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself. :::: The {{stack-ml-features}} support transformer models that conform to the standard BERT model interface and use the WordPiece tokenization algorithm. diff --git a/explore-analyze/machine-learning/setting-up-machine-learning.md b/explore-analyze/machine-learning/setting-up-machine-learning.md index d6960b3265..732a9708ff 100644 --- a/explore-analyze/machine-learning/setting-up-machine-learning.md +++ b/explore-analyze/machine-learning/setting-up-machine-learning.md @@ -23,7 +23,7 @@ To use the {{stack}} {{ml-features}}, you must have: * grant access to source and destination indices. ::::{tip} -The fastest way to get started with {{ml-features}} is to [start a free 14-day trial of {{ess}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) in the cloud. +The fastest way to get started with {{ml-features}} is to [start a free 14-day trial of {{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). :::: ## Security privileges [setup-privileges] diff --git a/explore-analyze/query-filter/languages/esql-cross-clusters.md b/explore-analyze/query-filter/languages/esql-cross-clusters.md index 39bf39c50e..af921965d8 100644 --- a/explore-analyze/query-filter/languages/esql-cross-clusters.md +++ b/explore-analyze/query-filter/languages/esql-cross-clusters.md @@ -22,7 +22,7 @@ With {{esql}}, you can execute a single query across multiple clusters. ## Prerequisites [esql-ccs-prerequisites] -* {{ccs-cap}} requires remote clusters. To set up remote clusters on {{ess}}, see [configure remote clusters on {{ess}}](/deploy-manage/remote-clusters/ec-enable-ccs.md). If you run {{es}} on your own hardware, see [*Remote clusters*](../../../deploy-manage/remote-clusters.md). +* {{ccs-cap}} requires remote clusters. To set up remote clusters, see [*Remote clusters*](../../../deploy-manage/remote-clusters.md). To ensure your remote cluster configuration supports {{ccs}}, see [Supported {{ccs}} configurations](../../../solutions/search/cross-cluster-search.md#ccs-supported-configurations). diff --git a/explore-analyze/query-filter/languages/sql-odbc-setup.md b/explore-analyze/query-filter/languages/sql-odbc-setup.md index a129ce284d..9ccd2d8377 100644 --- a/explore-analyze/query-filter/languages/sql-odbc-setup.md +++ b/explore-analyze/query-filter/languages/sql-odbc-setup.md @@ -108,7 +108,7 @@ This tab allows configuration for the following items: * Cloud ID - The *Cloud ID* is a string that simplifies the configuration when connecting to Elastic’s Cloud {{ess}}; it is obtained from within the Cloud console of each {{es}} cluster and encodes the connection parameters to that cluster. + The *Cloud ID* is a string that simplifies the configuration when connecting to {{ecloud}}. It encodes the connection parameters to that cluster. You can obtain it from from your deployment's details in the {{ecloud}} Console. ::::{note} When this field is provisioned, the *Hostname*, *Port* and the security settings are provisioned as well and their respective inputs disabled. diff --git a/solutions/index.md b/solutions/index.md index 2969325136..38108cc124 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -13,7 +13,7 @@ New to Elastic? Refer to [get started](/get-started/the-stack.md) to understand Users reach for Elastic products, features, and tools for three main use cases: observability, security, and search. These use cases are supported by ready-to-use implementations that help you get started quickly: -- As integrated solutions on [{{ecloud}} Hosted](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md) and [self-managed](/deploy-manage/deploy/self-managed.md) deployments +- As integrated solutions on [{{ech}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md) and [self-managed](/deploy-manage/deploy/self-managed.md) deployments - As project types on [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md) While these solutions and project types provide pre-built components for common use cases, you can also build custom implementations using Elastic's features, APIs, and tools. This documentation guides you through: diff --git a/solutions/observability/apps/apm-server-binary.md b/solutions/observability/apps/apm-server-binary.md index 41873fdf66..55769a95b4 100644 --- a/solutions/observability/apps/apm-server-binary.md +++ b/solutions/observability/apps/apm-server-binary.md @@ -815,7 +815,7 @@ docker run -d \ ``` 1. Substitute your {{es}} hosts and ports. -2. If you are using the hosted {{ess}} in {{ecloud}}, replace the `-E output.elasticsearch.hosts` line with the Cloud ID and elastic password using the syntax shown earlier. +2. If you are using {{ech}}, replace the `-E output.elasticsearch.hosts` line with the Cloud ID and elastic password using the syntax shown earlier. diff --git a/solutions/observability/apps/configure-apm-server.md b/solutions/observability/apps/configure-apm-server.md index b715a08e69..9afa26ad06 100644 --- a/solutions/observability/apps/configure-apm-server.md +++ b/solutions/observability/apps/configure-apm-server.md @@ -52,8 +52,8 @@ User settings are appended to the `apm-server.yml` configuration file for your i To add user settings: -1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the Elasticsearch Service card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments. +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the deployments page to view all of your deployments. On the deployments page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. @@ -63,14 +63,14 @@ To add user settings: 6. Select **Save changes**. ::::{note} -If a setting is not supported by Elasticsearch Service, you will get an error message when you try to save. +If a setting is not supported on {{ecloud}}, you will get an error message when you try to save. :::: ## Supported standalone APM settings (legacy) [ec-apm-settings] -Elasticsearch Service supports the following setting when running APM in standalone mode (legacy). +{{ech}} supports the following setting when running APM in standalone mode (legacy). ::::{tip} Some settings that could break your cluster if set incorrectly are blocklisted. The following settings are generally safe in cloud environments. For detailed information about APM settings, check the [APM documentation](/solutions/observability/apps/configure-apm-server.md). diff --git a/solutions/observability/apps/configure-output-for-elasticsearch-service-on-elastic-cloud.md b/solutions/observability/apps/configure-output-for-elasticsearch-service-on-elastic-cloud.md index 7e5e8fd9c0..e20a2c234a 100644 --- a/solutions/observability/apps/configure-output-for-elasticsearch-service-on-elastic-cloud.md +++ b/solutions/observability/apps/configure-output-for-elasticsearch-service-on-elastic-cloud.md @@ -1,12 +1,12 @@ --- -navigation_title: "{{ess}}" +navigation_title: "{{ech}}" mapped_pages: - https://www.elastic.co/guide/en/observability/current/apm-configure-cloud-id.html --- -# Configure the output for Elasticsearch Service on Elastic Cloud [apm-configure-cloud-id] +# Configure the output for {{ech}} [apm-configure-cloud-id] ::::{admonition} @@ -18,11 +18,11 @@ This documentation only applies to APM Server binary users. ::::{note} -This page refers to using a separate instance of APM Server with an existing [{{ess}} deployment](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body). If you want to use APM on {{ess}}, see: [Create your deployment](../../../deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md) and [Add APM user settings](configure-apm-server.md). +This page refers to using a separate instance of APM Server with an existing [{{ech}} deployment](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body). If you want to use APM on {{ech}}, see: [Create your deployment](../../../deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md) and [Add APM user settings](configure-apm-server.md). :::: -APM Server comes with two settings that simplify the output configuration when used together with [{{ess}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body). When defined, these setting overwrite settings from other parts in the configuration. +APM Server comes with two settings that simplify the output configuration when used together with [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service?page=docs&placement=docs-body). When defined, these setting overwrite settings from other parts in the configuration. Example: @@ -40,7 +40,7 @@ apm-server -e -E cloud.id="" -E cloud.auth="" ## `cloud.id` [_cloud_id] -The Cloud ID, which can be found in the {{ess}} web console, is used by APM Server to resolve the {{es}} and {{kib}} URLs. This setting overwrites the `output.elasticsearch.hosts` and `setup.kibana.host` settings. +The Cloud ID, which can be found in the {{ecloud}} Console, is used by APM Server to resolve the {{es}} and {{kib}} URLs. This setting overwrites the `output.elasticsearch.hosts` and `setup.kibana.host` settings. ## `cloud.auth` [_cloud_auth] diff --git a/solutions/observability/apps/configure-output.md b/solutions/observability/apps/configure-output.md index 3ad1e5932b..60e79e6715 100644 --- a/solutions/observability/apps/configure-output.md +++ b/solutions/observability/apps/configure-output.md @@ -11,7 +11,7 @@ mapped_pages: Output configuration options. -* [{{ess}}](configure-output-for-elasticsearch-service-on-elastic-cloud.md) +* [{{ech}}](configure-output-for-elasticsearch-service-on-elastic-cloud.md) * [{{es}}](configure-elasticsearch-output.md) * [{{ls}}](configure-logstash-output.md) * [Kafka](configure-kafka-output.md) diff --git a/solutions/observability/apps/create-assign-feature-roles-to-apm-server-users.md b/solutions/observability/apps/create-assign-feature-roles-to-apm-server-users.md index 4cba434095..9c9826b293 100644 --- a/solutions/observability/apps/create-assign-feature-roles-to-apm-server-users.md +++ b/solutions/observability/apps/create-assign-feature-roles-to-apm-server-users.md @@ -144,7 +144,7 @@ Looking for privileges and roles needed to use central configuration from the Ap ### Publish monitoring data [apm-privileges-to-publish-monitoring-write] ::::{important} -**{{ecloud}} users:** This section does not apply to our [hosted {{ess}}](https://www.elastic.co/cloud/elasticsearch-service). Monitoring on {{ecloud}} is enabled by clicking the **Enable** button in the **Monitoring** panel. +**{{ecloud}} users:** This section does not apply to [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service). Monitoring on {{ecloud}} is enabled by clicking the **Enable** button in the **Monitoring** panel. :::: diff --git a/solutions/observability/apps/cross-cluster-search-with-application-data.md b/solutions/observability/apps/cross-cluster-search-with-application-data.md index 15c05e76b9..6d7ef8d634 100644 --- a/solutions/observability/apps/cross-cluster-search-with-application-data.md +++ b/solutions/observability/apps/cross-cluster-search-with-application-data.md @@ -16,7 +16,7 @@ Elastic APM utilizes {{es}}'s cross-cluster search functionality. Cross-cluster **Step 1. Set up remote clusters.** -If you’re using the Hosted {{ess}}, see [Enable cross-cluster search](../../../deploy-manage/remote-clusters/ec-enable-ccs.md). +If you’re using the {{ech}}, see [Enable cross-cluster search](../../../deploy-manage/remote-clusters/ec-enable-ccs.md). To add remote clusters directly in {{kib}}, find `Remote Clusters` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). All you need is a name for the remote cluster and the seed node(s). Remember the names of your remote clusters, you’ll need them in step two. See [managing remote clusters](/deploy-manage/tools/cross-cluster-replication/set-up-cross-cluster-replication.md) for detailed information on the setup process. diff --git a/solutions/observability/apps/get-started-with-apm.md b/solutions/observability/apps/get-started-with-apm.md index a9ccfcb6a8..de0ae5ec71 100644 --- a/solutions/observability/apps/get-started-with-apm.md +++ b/solutions/observability/apps/get-started-with-apm.md @@ -36,7 +36,7 @@ Fleet is a web-based UI in {{kib}} that is used to centrally manage {{agent}}s. **Supported outputs**: * {{es}} -* {{ess}} +* {{ech}} ::::{note} Fleet-managed APM Server does *not* support all the outputs that are supported by the APM Server binary method of running Elastic APM. @@ -68,7 +68,7 @@ Install, configure, and run the APM Server binary wherever you need it. **Supported outputs**: * {{es}} -* {{ess}} +* {{ech}} * {{ls}} * Kafka * Redis diff --git a/solutions/observability/apps/integrate-with-jaeger-deprecated.md b/solutions/observability/apps/integrate-with-jaeger-deprecated.md index 2069a01f89..7669265bb1 100644 --- a/solutions/observability/apps/integrate-with-jaeger-deprecated.md +++ b/solutions/observability/apps/integrate-with-jaeger-deprecated.md @@ -48,7 +48,7 @@ The APM integration serves Jaeger gRPC over the same host and port as the Elasti :::::::{tab-set} -::::::{tab-item} Elasticsearch Service +::::::{tab-item} {{ecloud}} 1. Log into [{{ecloud}}](https://cloud.elastic.co?page=docs&placement=docs-body) and select your deployment. 2. In {{kib}}, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). 3. Select **Elastic APM**. If the integration is already installed, under the polices tab, select **Actions*** > ***Edit integration**. If the integration has not been installed, select **Add Elastic APM**. Copy the URL. If you’re using Agent authorization, copy the Secret token as well. diff --git a/solutions/observability/apps/monitor-apm-server.md b/solutions/observability/apps/monitor-apm-server.md index 1c822c9d82..acb28280b3 100644 --- a/solutions/observability/apps/monitor-apm-server.md +++ b/solutions/observability/apps/monitor-apm-server.md @@ -18,5 +18,5 @@ Select your deployment method to get started: {{ecloud}} manages the installation and configuration of a monitoring agent for you — so all you have to do is flip a switch and watch the data pour in. -* **{{ess}}** user? See [ESS: Enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). -* **{{ece}}** user? See [ECE: Enable logging and monitoring](/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md). +* **{{ech}}** user? See [Stack Monitoring on {{ecloud}} deployments](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). +* **{{ece}}** user? See [Enable stack monitoring on ECE deployments](/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md). diff --git a/solutions/observability/apps/secret-token.md b/solutions/observability/apps/secret-token.md index 244d3b9c44..f85f7b08f4 100644 --- a/solutions/observability/apps/secret-token.md +++ b/solutions/observability/apps/secret-token.md @@ -27,7 +27,7 @@ Secret tokens are not applicable for the RUM Agent, as there is no way to preven ## Create a secret token [apm-create-secret-token] ::::{note} -{{ess}} and {{ece}} deployments provision a secret token when the deployment is created. The secret token can be found and reset in the {{ecloud}} console under **Deployments** — **APM & Fleet**. +{{ech}} and {{ece}} deployments provision a secret token when the deployment is created. The secret token can be found and reset in the {{ecloud}} Console under **Deployments** — **APM & Fleet**. :::: diff --git a/solutions/observability/apps/switch-an-elastic-cloud-cluster-to-apm-integration.md b/solutions/observability/apps/switch-an-elastic-cloud-cluster-to-apm-integration.md index 4bbed5a5b3..da487aeebd 100644 --- a/solutions/observability/apps/switch-an-elastic-cloud-cluster-to-apm-integration.md +++ b/solutions/observability/apps/switch-an-elastic-cloud-cluster-to-apm-integration.md @@ -17,7 +17,7 @@ mapped_pages: ## Upgrade the {{stack}} [apm-integration-upgrade-ess-1] -Use the {{ecloud}} console to upgrade the {{stack}} to version 9.0.0-beta1. See the [{{ess}} upgrade guide](../../../deploy-manage/upgrade/deployment-or-cluster.md) for details. +Use the {{ecloud}} Console to upgrade the {{stack}} to version 9.0.0-beta1. See the [Upgrade guide](../../../deploy-manage/upgrade/deployment-or-cluster.md) for details. ## Switch to {{agent}} [apm-integration-upgrade-ess-2] @@ -53,7 +53,7 @@ In {{kib}}, navigate to **Management** > **Fleet***. Select the ***Elastic Cloud Certain {{es}} output configuration options are not available with the APM integration. To ensure data is not lost, you can scale APM and {{fleet}} up and out. APM’s capacity to process events increases with the instance memory size. -Go to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body), select your deployment and click **Edit**. Here you can edit the number and size of each availability zone. +Go to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), select your deployment and click **Edit**. Here you can edit the number and size of each availability zone. :::{image} ../../../images/observability-scale-apm.png :alt: scale APM diff --git a/solutions/observability/apps/tutorial-monitor-java-application.md b/solutions/observability/apps/tutorial-monitor-java-application.md index 53f12c1dfc..8080010878 100644 --- a/solutions/observability/apps/tutorial-monitor-java-application.md +++ b/solutions/observability/apps/tutorial-monitor-java-application.md @@ -21,7 +21,7 @@ You’ll learn how to: ## Before you begin [_before_you_begin] -Create a deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, {{kib}} for visualizing and managing your data, and an APM server. If you do not want to follow all those steps listed here and take a look at the final java code, check out the [observability-contrib GitHub repository](https://github.com/elastic/observability-contrib/tree/main/monitor-java-app) for the sample application. +Create an [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, {{kib}} for visualizing and managing your data, and an APM server. If you do not want to follow all those steps listed here and take a look at the final java code, check out the [observability-contrib GitHub repository](https://github.com/elastic/observability-contrib/tree/main/monitor-java-app) for the sample application. ## Step 1: Create a Java application [_step_1_create_a_java_application] @@ -323,7 +323,7 @@ Depending on the application traffic and whether it happens outside of the appli ### Create an ISO8601 timestamp [_create_an_iso8601_timestamp] -Before ingesting logs into {{ess}}, create an ISO8601 timestamp by editing the `log4j2.xml` file. +Before ingesting logs into {{ech}}, create an ISO8601 timestamp by editing the `log4j2.xml` file. ::::{note} Creating an ISO8601 timestamp removes the need to do any calculation for timestamps when ingesting logs, as this is a unique point in time, including the timezone. Having a timezone becomes more important once you are running across data centers while trying to follow data streams. @@ -410,7 +410,7 @@ Version 9.0.0-beta1 of Filebeat has not yet been released. echo -n "" | ./filebeat keystore add CLOUD_ID --stdin ``` - To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ess}}. + To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ecloud}}. 2. Log into {{kib}} user (you can do so from the Cloud Console without typing in any permissions) and select **Management** → **{{dev-tools-app}}**. Send the following request: diff --git a/solutions/observability/cloud/gcp-dataflow-templates.md b/solutions/observability/cloud/gcp-dataflow-templates.md index eab6ba5a2a..26238b5084 100644 --- a/solutions/observability/cloud/gcp-dataflow-templates.md +++ b/solutions/observability/cloud/gcp-dataflow-templates.md @@ -18,7 +18,7 @@ You’ll learn how to: ## Before you begin [_before_you_begin_3] -Create a deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. +Create an [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. ## Step 1: Install the GCP integration [_step_1_install_the_gcp_integration] diff --git a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md index 20f4927dff..4d3c9d7235 100644 --- a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md +++ b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md @@ -24,7 +24,7 @@ In this tutorial, you’ll learn how to: ## Before you begin [aws-elastic-firehose-before-you-begin] -Create a deployment in AWS regions (including gov cloud) using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. +Create an [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment in AWS regions (including gov cloud) using. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. ## Step 1: Install AWS integration in {{kib}} [firehose-step-one] @@ -50,8 +50,8 @@ For advanced use cases, source records can be transformed by invoking a custom L 1. From the **Destination settings** panel, specify the following settings: - * **Elastic endpoint URL**: Enter the Elastic endpoint URL of your Elasticsearch cluster. To find the Elasticsearch endpoint, go to the Elastic Cloud console and select **Connection details**. Here is an example of how it looks like: `https://my-deployment.es.us-east-1.aws.elastic-cloud.com`. - * **API key**: Enter the encoded Elastic API key. To create an API key, go to the Elastic Cloud console, select **Connection details** and click **Create and manage API keys**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least "auto_configure" & "write" permissions for the indices you will be using with this delivery stream. + * **Elastic endpoint URL**: Enter the Elastic endpoint URL of your Elasticsearch cluster. To find the Elasticsearch endpoint, go to the {{ecloud}} Console and select **Connection details**. Here is an example of how it looks like: `https://my-deployment.es.us-east-1.aws.elastic-cloud.com`. + * **API key**: Enter the encoded Elastic API key. To create an API key, go to the {{ecloud}} Console, select **Connection details** and click **Create and manage API keys**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least "auto_configure" & "write" permissions for the indices you will be using with this delivery stream. * **Content encoding**: For a better network efficiency, leave content encoding set to GZIP. * **Retry duration**: Determines how long Firehose continues retrying the request in the event of an error. A duration of 60-300s should be suitable for most use cases. * **Parameters**: diff --git a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md index 3883fefe43..466bb4776b 100644 --- a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md +++ b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-beats.md @@ -25,7 +25,7 @@ You’ll learn how to: ## Before you begin [aws-before-you-begin] -Create a deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. +Create an [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. With this tutorial, we assume that your logs and your infrastructure data are already shipped to CloudWatch. We are going to show you how you can stream your data from CloudWatch to {{es}}. If you don’t know how to put your AWS logs and infrastructure data in CloudWatch, Amazon provides a lot of documentation around this specific topic: @@ -165,7 +165,7 @@ Setting up {{filebeat}} is an admin-level task that requires extra privileges. A ### Configure {{filebeat}} output [_configure_filebeat_output] -Next, you are going to configure {{filebeat}} output to {{ess}}. +Next, you are going to configure {{filebeat}} output to {{ecloud}}. 1. Use the {{filebeat}} keystore to store [secure settings](asciidocalypse://docs/beats/docs/reference/ingestion-tools/beats-filebeat/keystore.md). Store the Cloud ID in the keystore. @@ -174,7 +174,7 @@ Next, you are going to configure {{filebeat}} output to {{ess}}. echo -n "" | ./filebeat keystore add CLOUD_ID --stdin ``` -2. To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Send the following request: +2. To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ecloud}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Send the following request: ```console POST /_security/api_key @@ -218,7 +218,7 @@ Next, you are going to configure {{filebeat}} output to {{ess}}. ./filebeat keystore list ``` -5. To configure {{filebeat}} to output to {{ess}}, edit the `filebeat.yml` configuration file. Add the following lines to the end of the file. +5. To configure {{filebeat}} to output to {{ecloud}}, edit the `filebeat.yml` configuration file. Add the following lines to the end of the file. ```yaml cloud.id: ${CLOUD_ID} @@ -433,7 +433,7 @@ Setting up {{metricbeat}} is an admin-level task that requires extra privileges. ### Configure {{metricbeat}} output [_configure_metricbeat_output] -Next, you are going to configure {{metricbeat}} output to {{ess}}. +Next, you are going to configure {{metricbeat}} output to {{ecloud}}. 1. Use the {{metricbeat}} keystore to store [secure settings](asciidocalypse://docs/beats/docs/reference/ingestion-tools/beats-metricbeat/keystore.md). Store the Cloud ID in the keystore. @@ -442,7 +442,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. echo -n "" | ./metricbeat keystore add CLOUD_ID --stdin ``` -2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: +2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ecloud}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: ```console POST /_security/api_key @@ -479,7 +479,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. ./metricbeat keystore list ``` -5. To configure {{metricbeat}} to output to {{ess}}, edit the `metricbeat.yml` configuration file. Add the following lines to the end of the file. +5. To configure {{metricbeat}} to output to {{ecloud}}, edit the `metricbeat.yml` configuration file. Add the following lines to the end of the file. ```yaml cloud.id: ${CLOUD_ID} diff --git a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md index bfd0e6fdaf..9545c0c6c0 100644 --- a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md +++ b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md @@ -31,7 +31,7 @@ First you’ll focus on monitoring logs, then you’ll add metrics after you’v ## Before you begin [aws-elastic-agent-before-you-begin] -Create a deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. +Create an [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. In this tutorial, we assume that: diff --git a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md index b75d008823..6f530c2b75 100644 --- a/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md +++ b/solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md @@ -24,7 +24,7 @@ In this tutorial, you’ll learn how to: ## Before you begin [aws-esf-prerequisites] -Create a deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. Elastic Serverless Forwarder works with Elastic Stack 7.17 and later. You also need an AWS account with permissions to pull the necessary data from AWS. +Create an [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. Elastic Serverless Forwarder works with Elastic Stack 7.17 and later. You also need an AWS account with permissions to pull the necessary data from AWS. ## Step 1: Create an S3 Bucket to store VPC flow logs [esf-step-one] diff --git a/solutions/observability/cloud/monitor-aws-network-firewall-logs.md b/solutions/observability/cloud/monitor-aws-network-firewall-logs.md index 604de92131..0118ac847b 100644 --- a/solutions/observability/cloud/monitor-aws-network-firewall-logs.md +++ b/solutions/observability/cloud/monitor-aws-network-firewall-logs.md @@ -24,7 +24,7 @@ You will go through the following steps: We assume that you already have: * An AWS account with permissions to pull the necessary data from AWS. -* A deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. +* An [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. ::::{important} AWS PrivateLink is not supported. Make sure the deployment is on AWS, because the Amazon Data Firehose delivery stream connects specifically to an endpoint that needs to be on AWS. diff --git a/solutions/observability/cloud/monitor-cloudtrail-logs.md b/solutions/observability/cloud/monitor-cloudtrail-logs.md index 2b248b6648..cb25818a51 100644 --- a/solutions/observability/cloud/monitor-cloudtrail-logs.md +++ b/solutions/observability/cloud/monitor-cloudtrail-logs.md @@ -23,7 +23,7 @@ In this section, you’ll learn how to monitor and analyze the CloudTrail logs y We assume that you already have: * An AWS account with permissions to pull the necessary data from AWS. -* A deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. +* An [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. ::::{important} Make sure the deployment is on AWS, because the Amazon Data Firehose delivery stream connects specifically to an endpoint that needs to be on AWS. diff --git a/solutions/observability/cloud/monitor-cloudwatch-logs.md b/solutions/observability/cloud/monitor-cloudwatch-logs.md index 18dc4adc8d..f1f948aa05 100644 --- a/solutions/observability/cloud/monitor-cloudwatch-logs.md +++ b/solutions/observability/cloud/monitor-cloudwatch-logs.md @@ -25,7 +25,7 @@ You’ll go through the following steps: We assume that you already have: * An AWS account with permissions to pull the necessary data from AWS. -* A deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. +* An [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. ::::{important} AWS PrivateLink is not supported. Make sure the deployment is on AWS, because the Amazon Data Firehose delivery stream connects specifically to an endpoint that needs to be on AWS. diff --git a/solutions/observability/cloud/monitor-google-cloud-platform-gcp.md b/solutions/observability/cloud/monitor-google-cloud-platform-gcp.md index e5067e3829..50d7fa0567 100644 --- a/solutions/observability/cloud/monitor-google-cloud-platform-gcp.md +++ b/solutions/observability/cloud/monitor-google-cloud-platform-gcp.md @@ -30,7 +30,7 @@ You’ll learn how to: ## Before you begin [_before_you_begin_2] -Create a deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. +Create an [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. ## Step 1: Setup a Service Account [_step_1_setup_a_service_account] @@ -159,7 +159,7 @@ Setting up {{metricbeat}} is an admin-level task that requires extra privileges. ### Configure {{metricbeat}} output [_configure_metricbeat_output_3] -Next, you are going to configure {{metricbeat}} output to {{ess}}. +Next, you are going to configure {{metricbeat}} output to {{ecloud}}. 1. Use the {{metricbeat}} keystore to store [secure settings](asciidocalypse://docs/beats/docs/reference/ingestion-tools/beats-metricbeat/keystore.md). Store the Cloud ID in the keystore. @@ -168,7 +168,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. echo -n "" | ./metricbeat keystore add CLOUD_ID --stdin ``` -2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: +2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ecloud}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: ```console POST /_security/api_key @@ -205,7 +205,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. ./metricbeat keystore list ``` -5. To configure {{metricbeat}} to output to {{ess}}, edit the `metricbeat.yml` configuration file. Add the following lines to the end of the file. +5. To configure {{metricbeat}} to output to {{ecloud}}, edit the `metricbeat.yml` configuration file. Add the following lines to the end of the file. ```yaml cloud.id: ${CLOUD_ID} @@ -330,7 +330,7 @@ Setting up {{filebeat}} is an admin-level task that requires extra privileges. A #### Configure {{filebeat}} output [_configure_filebeat_output_2] -Next, you are going to configure {{filebeat}} output to {{ess}}. +Next, you are going to configure {{filebeat}} output to {{ecloud}}. 1. Use the {{filebeat}} keystore to store [secure settings](asciidocalypse://docs/beats/docs/reference/ingestion-tools/beats-filebeat/keystore.md). Store the Cloud ID in the keystore. @@ -339,7 +339,7 @@ Next, you are going to configure {{filebeat}} output to {{ess}}. echo -n "" | ./filebeat keystore add CLOUD_ID --stdin ``` -2. To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Send the following request: +2. To store logs in {{es}} with minimal permissions, create an API key to send data from {{filebeat}} to {{ecloud}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Send the following request: ```console POST /_security/api_key @@ -383,7 +383,7 @@ Next, you are going to configure {{filebeat}} output to {{ess}}. ./filebeat keystore list ``` -5. To configure {{filebeat}} to output to {{ess}}, edit the `filebeat.yml` configuration file. Add the following lines to the end of the file. +5. To configure {{filebeat}} to output to {{ecloud}}, edit the `filebeat.yml` configuration file. Add the following lines to the end of the file. ```yaml cloud.id: ${CLOUD_ID} diff --git a/solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md b/solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md index 62f7efcf3c..f110b7b0c9 100644 --- a/solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md +++ b/solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md @@ -6,7 +6,7 @@ mapped_pages: # Monitor Microsoft Azure with the Azure Native ISV Service [monitor-azure-native] ::::{admonition} -The {{ecloud}} Azure Native ISV Service allows you to deploy managed instances of the {{stack}} directly in Azure, through the Azure integrated marketplace. The service includes native capabilities for consolidating Azure logs and metrics in Elastic. For more information, refer to [Azure Native ISV Service](../../../deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md) in the {{ess}} documentation. +The {{ecloud}} Azure Native ISV Service allows you to deploy managed instances of the {{stack}} directly in Azure, through the Azure integrated marketplace. The service includes native capabilities for consolidating Azure logs and metrics in Elastic. For more information, refer to [Azure Native ISV Service](../../../deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md). **Using {{agent}} to monitor Azure?** Refer to [Monitor Microsoft Azure with {{agent}}](monitor-microsoft-azure-with-elastic-agent.md). diff --git a/solutions/observability/cloud/monitor-microsoft-azure-with-beats.md b/solutions/observability/cloud/monitor-microsoft-azure-with-beats.md index 67b6740ae6..f5b19faee0 100644 --- a/solutions/observability/cloud/monitor-microsoft-azure-with-beats.md +++ b/solutions/observability/cloud/monitor-microsoft-azure-with-beats.md @@ -237,7 +237,7 @@ Setting up {{metricbeat}} is an admin-level task that requires extra privileges. ### Configure {{metricbeat}} output [_configure_metricbeat_output_2] -Next, you are going to configure {{metricbeat}} output to {{ess}}. +Next, you are going to configure {{metricbeat}} output to {{ecloud}}. 1. Use the {{metricbeat}} keystore to store [secure settings](asciidocalypse://docs/beats/docs/reference/ingestion-tools/beats-metricbeat/keystore.md). Store the Cloud ID in the keystore. @@ -246,7 +246,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. echo -n "" | ./metricbeat keystore add CLOUD_ID --stdin ``` -2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ess}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: +2. To store metrics in {{es}} with minimal permissions, create an API key to send data from {{metricbeat}} to {{ecloud}}. Log into {{kib}} (you can do so from the Cloud Console without typing in any permissions) and find `Dev Tools` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From the **Console**, send the following request: ```console POST /_security/api_key @@ -283,7 +283,7 @@ Next, you are going to configure {{metricbeat}} output to {{ess}}. ./metricbeat keystore list ``` -5. To configure {{metricbeat}} to output to {{ess}}, edit the `metricbeat.yml` configuration file. Add the following lines to the end of the file. +5. To configure {{metricbeat}} to output to {{ecloud}}, edit the `metricbeat.yml` configuration file. Add the following lines to the end of the file. ```yaml cloud.id: ${CLOUD_ID} diff --git a/solutions/observability/cloud/monitor-virtual-private-cloud-vpc-flow-logs.md b/solutions/observability/cloud/monitor-virtual-private-cloud-vpc-flow-logs.md index c935565023..8c5a402760 100644 --- a/solutions/observability/cloud/monitor-virtual-private-cloud-vpc-flow-logs.md +++ b/solutions/observability/cloud/monitor-virtual-private-cloud-vpc-flow-logs.md @@ -20,7 +20,7 @@ In this section, you’ll learn how to monitor and analyze the VPC flow logs you We assume that you already have: -* A deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Kinesis Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. +* An [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Kinesis Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. ::::{important} Make sure the deployment is on AWS, because the Firehose delivery stream connects specifically to an endpoint that needs to be on AWS. diff --git a/solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md b/solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md index b4ae8abb23..d9747bbe93 100644 --- a/solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md +++ b/solutions/observability/cloud/monitor-web-application-firewall-waf-logs.md @@ -25,7 +25,7 @@ You will go through the following steps: We assume that you already have: * An AWS account with permissions to pull the necessary data from AWS. -* A deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. +* An [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. AWS Data Firehose works with Elastic Stack version 7.17 or greater, running on Elastic Cloud only. ::::{important} Make sure the deployment is on AWS, because the Amazon Data Firehose delivery stream connects specifically to an endpoint that needs to be on AWS. diff --git a/solutions/observability/get-started.md b/solutions/observability/get-started.md index b98814113b..9f44c8877b 100644 --- a/solutions/observability/get-started.md +++ b/solutions/observability/get-started.md @@ -24,7 +24,7 @@ Learn about key features available to help you get value from your observability ## Get started with your use case [get-started-with-use-case] -Learn how to spin up a deployment of our hosted {{ess}} or create an Observability serverless project and use Elastic Observability to gain deeper insight into the behavior of your applications and systems. +Learn how to spin up a deployment on {{ech}} or create an Observability serverless project and use Elastic Observability to gain deeper insight into the behavior of your applications and systems. :::{image} ../../images/observability-get-started.svg :alt: get started diff --git a/solutions/observability/get-started/add-data-from-splunk.md b/solutions/observability/get-started/add-data-from-splunk.md index d06be67cce..a46856dd91 100644 --- a/solutions/observability/get-started/add-data-from-splunk.md +++ b/solutions/observability/get-started/add-data-from-splunk.md @@ -29,9 +29,9 @@ To follow the steps in this guide, you need an {{stack}} deployment that include * {{es}} for storing and searching data * {{kib}} for visualizing and managing data * Kibana user with `All` privileges on {{fleet}} and Integrations. Since many Integrations assets are shared across spaces, users need the Kibana privileges in all spaces. -* Integrations Server (included by default in every {{ess}} deployment) +* Integrations Server (included by default in every {{ech}} deployment) -To get started quickly, spin up a deployment of our hosted {{ess}}. 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, create an {{ech}} deployment and host it on AWS, GCP, or Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body). ## Step 1: Add integration [splunk-step-one] diff --git a/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md b/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md index 2517f70917..7decdd26de 100644 --- a/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md +++ b/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md @@ -59,7 +59,7 @@ Some AWS services need additional manual configuration to properly ingest logs a :::: -Data collection with AWS Firehose is supported on ESS deployments in AWS, Azure and GCP. +Data collection with AWS Firehose is supported on {{ech}} deployments in AWS, Azure and GCP. ## Prerequisites [_prerequisites_5] @@ -70,7 +70,7 @@ Data collection with AWS Firehose is supported on ESS deployments in AWS, Azure :::{tab-item} Elastic Stack :sync: stack -* A deployment using our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. +* An [{{ech}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body) deployment. The deployment includes an {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. * A user with the `superuser` [built-in role](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md) or the privileges required to onboard data. ::::{dropdown} Expand to view required privileges diff --git a/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md b/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md index db826b37fe..feb40482dd 100644 --- a/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md +++ b/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md @@ -21,7 +21,7 @@ The script also generates an {{agent}} configuration file that you can use with :::{tab-item} Elastic Stack :sync: stack -* An {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. This quickstart is available for all Elastic deployment models. To get started quickly, try out our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). +* An {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. This quickstart is available for all Elastic deployment models. To get started quickly, try out [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). * A user with the `superuser` [built-in role](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md) or the privileges required to onboard data. ::::{dropdown} Expand to view required privileges diff --git a/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md b/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md index c2c201edeb..0ad8f0abb0 100644 --- a/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md +++ b/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md @@ -21,7 +21,7 @@ The kubectl command installs the standalone Elastic Agent in your Kubernetes clu :::{tab-item} Elastic Stack :sync: stack -* An {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. This quickstart is available for all Elastic deployment models. To get started quickly, try out our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). +* An {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. This quickstart is available for all Elastic deployment models. To get started quickly, try out [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). * A user with the `superuser` [built-in role](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md) or the privileges required to onboard data. ::::{dropdown} Expand to view required privileges diff --git a/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md b/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md index 8868dd37af..1f62b87cd4 100644 --- a/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md +++ b/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md @@ -31,7 +31,7 @@ For a more detailed description of the components and advanced configuration, re :::{tab-item} Elastic Stack :sync: stack -* An {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. This quickstart is available for all Elastic deployment models. To get started quickly, try out our hosted {{ess}} on [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). +* An {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. This quickstart is available for all Elastic deployment models. To get started quickly, try out [{{ecloud}}](https://cloud.elastic.co/registration?page=docs&placement=docs-body). * A running Kubernetes cluster (v1.23 or newer). * [Kubectl](https://kubernetes.io/docs/reference/kubectl/). * [Helm](https://helm.sh/docs/intro/install/). diff --git a/solutions/observability/incident-management/create-an-slo.md b/solutions/observability/incident-management/create-an-slo.md index b69df795cd..81891901eb 100644 --- a/solutions/observability/incident-management/create-an-slo.md +++ b/solutions/observability/incident-management/create-an-slo.md @@ -28,7 +28,7 @@ From here, complete the following steps: 3. [Describe your SLO](../../../solutions/observability/incident-management/create-an-slo.md#slo-describe). ::::{note} -**For Elastic Stack**, the cluster must include one or more nodes with both `ingest` and `transform` [roles](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#node-roles). The roles can exist on the same node or be distributed across separate nodes. On ESS deployments (Elastic Cloud), this is handled by the hot nodes, which serve as both `ingest` and `transform` nodes. +**For Elastic Stack**, the cluster must include one or more nodes with both `ingest` and `transform` [roles](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#node-roles). The roles can exist on the same node or be distributed across separate nodes. On {{ech}} deployments, this is handled by the hot nodes, which serve as both `ingest` and `transform` nodes. :::: diff --git a/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md b/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md index fb893674bb..05638e1841 100644 --- a/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md +++ b/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md @@ -24,9 +24,9 @@ To follow the steps in this guide, you need an {{stack}} deployment that include * {{es}} for storing and searching data * {{kib}} for visualizing and managing data * Kibana user with `All` privileges on {{fleet}} and Integrations. Since many Integrations assets are shared across spaces, users need the Kibana privileges in all spaces. -* Integrations Server (included by default in every {{ess}} deployment) +* Integrations Server (included by default in every {{ech}} deployment) -To get started quickly, spin up a deployment of our hosted {{ess}}. 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, create an {{ech}} deployment and host it on AWS, GCP, or Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body). ::: diff --git a/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md b/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md index 79eb02c9d6..e0a12a6129 100644 --- a/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md +++ b/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md @@ -547,7 +547,7 @@ Think of a latency spike — APM can help you narrow the scope of your inves Application monitoring data is streamed from your applications running in Kubernetes to APM, where it is validated, processed, and transformed into {{es}} documents. -There are many ways to deploy APM when working with Kubernetes, but this guide assumes that you’re using our hosted {{ess}} on {{ecloud}}. If you haven’t done so already, enable APM in the [{{ess}} console](https://cloud.elastic.co?page=docs&placement=docs-body). +There are many ways to deploy APM when working with Kubernetes, but this guide assumes that you’re using an {{ech}} deployment. If you haven’t done so already, enable APM in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). If you want to manage APM yourself, there are a few alternative options: diff --git a/solutions/observability/infra-and-hosts/upgrade-universal-profiling.md b/solutions/observability/infra-and-hosts/upgrade-universal-profiling.md index 716ec98e1d..08b27f6b28 100644 --- a/solutions/observability/infra-and-hosts/upgrade-universal-profiling.md +++ b/solutions/observability/infra-and-hosts/upgrade-universal-profiling.md @@ -29,7 +29,7 @@ To upgrade from version 8.10 or later, you need to: 1. Perform a stack upgrade in {{ecloud}} -### Perform a stack upgrade in the {{ecloud}} console [profiling-upgrade-in-cloud] +### Perform a stack upgrade in the {{ecloud}} Console [profiling-upgrade-in-cloud] To perform a stack upgrade in {{ecloud}}: diff --git a/solutions/observability/logs/stream-any-log-file.md b/solutions/observability/logs/stream-any-log-file.md index d9fd2740ba..0e59890c02 100644 --- a/solutions/observability/logs/stream-any-log-file.md +++ b/solutions/observability/logs/stream-any-log-file.md @@ -26,9 +26,9 @@ To follow the steps in this guide, you need an {{stack}} deployment that include * {{es}} for storing and searching data * {{kib}} for visualizing and managing data * Kibana user with `All` privileges on {{fleet}} and Integrations. Since many Integrations assets are shared across spaces, users need the Kibana privileges in all spaces. -* Integrations Server (included by default in every {{ess}} deployment) +* Integrations Server (included by default in every {{ech}} deployment) -To get started quickly, spin up a deployment of our hosted {{ess}}. 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, create an {{ech}} deployment and host it on AWS, GCP, or Azure. [Try it out for free](https://cloud.elastic.co/registration?page=docs&placement=docs-body). ::: diff --git a/solutions/search/cross-cluster-search.md b/solutions/search/cross-cluster-search.md index 6770bd7d37..320bbc2c68 100644 --- a/solutions/search/cross-cluster-search.md +++ b/solutions/search/cross-cluster-search.md @@ -31,7 +31,7 @@ The following APIs support {{ccs}}: ## Prerequisites [_prerequisites] -* {{ccs-cap}} requires remote clusters. To set up remote clusters on {{ess}}, see [configure remote clusters on {{ess}}](/deploy-manage/remote-clusters/ec-enable-ccs.md). If you run {{es}} on your own hardware, see [*Remote clusters*](../../deploy-manage/remote-clusters.md). +* {{ccs-cap}} requires remote clusters. To set up remote clusters, see [*Remote clusters*](../../deploy-manage/remote-clusters.md). To ensure your remote cluster configuration supports {{ccs}}, see [Supported {{ccs}} configurations](#ccs-supported-configurations). diff --git a/solutions/search/full-text/search-with-synonyms.md b/solutions/search/full-text/search-with-synonyms.md index a77bf293b3..3d0833a086 100644 --- a/solutions/search/full-text/search-with-synonyms.md +++ b/solutions/search/full-text/search-with-synonyms.md @@ -11,7 +11,7 @@ applies_to: $$$ece-add-custom-bundle-example-synonyms$$$ ::::{note} -Learn about [adding custom synonym bundles](/solutions/search/full-text/search-with-synonyms.md#ece-add-custom-bundle-example-synonyms) to your Elastic Cloud Enterprise deployment. +Learn about [adding custom synonym bundles](/solutions/search/full-text/search-with-synonyms.md#ece-add-custom-bundle-example-synonyms) to your {{ece}} deployment. :::: @@ -59,7 +59,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 {{ech}}, 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/solutions/search/retrievers-examples.md b/solutions/search/retrievers-examples.md index 6f3719bb7d..6ba37f528d 100644 --- a/solutions/search/retrievers-examples.md +++ b/solutions/search/retrievers-examples.md @@ -88,7 +88,7 @@ POST /retrievers_example/_doc/4 POST /retrievers_example/_doc/5 { "vector": [0.11, 0.65, 0.47], - "text": "Learn how to spin up a deployment of our hosted Elasticsearch Service and use Elastic Observability to gain deeper insight into the behavior of your applications and systems.", + "text": "Learn how to spin up a deployment on Elastic Cloud and use Elastic Observability to gain deeper insight into the behavior of your applications and systems.", "year": 2024, "topic": ["documentation", "observability", "elastic"], "timestamp": "2025-01-01T12:10:30" diff --git a/solutions/search/semantic-search/semantic-search-elser-ingest-pipelines.md b/solutions/search/semantic-search/semantic-search-elser-ingest-pipelines.md index 5433456879..d7f1729fbe 100644 --- a/solutions/search/semantic-search/semantic-search-elser-ingest-pipelines.md +++ b/solutions/search/semantic-search/semantic-search-elser-ingest-pipelines.md @@ -32,7 +32,7 @@ Only the first 512 extracted tokens per field are considered during semantic sea To perform semantic search by using ELSER, you must have the NLP model deployed in your cluster. Refer to the [ELSER documentation](/explore-analyze/machine-learning/nlp/ml-nlp-elser.md) to learn how to download and deploy the model. ::::{note} -The minimum dedicated ML node size for deploying and using the ELSER model is 4 GB in Elasticsearch Service if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself. +The minimum dedicated ML node size for deploying and using the ELSER model is 4 GB in {{ech}} if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself. :::: ### Create the index mapping [elser-mappings] diff --git a/solutions/security/detect-and-alert/create-manage-shared-exception-lists.md b/solutions/security/detect-and-alert/create-manage-shared-exception-lists.md index b77c909c3a..2bf7daa403 100644 --- a/solutions/security/detect-and-alert/create-manage-shared-exception-lists.md +++ b/solutions/security/detect-and-alert/create-manage-shared-exception-lists.md @@ -8,7 +8,7 @@ mapped_urls: Shared exception lists allow you to group exceptions together and then apply them to multiple rules. Use the Shared Exception Lists page to set up shared exception lists. -% The following note is only applicable to ESS and is only relevant for users who are upgrading from 8.5 -> 8.6 or later. Might need to add this to the [8.6.x upgrade docs](https://www.elastic.co/guide/en/security/8.6/upgrade-intro.html) later. +% The following note is only applicable to {{ech}} and is only relevant for users who are upgrading from 8.5 -> 8.6 or later. Might need to add this to the [8.6.x upgrade docs](https://www.elastic.co/guide/en/security/8.6/upgrade-intro.html) later. % ::::{note} % Exception lists created in 8.5 and earlier become shared exception lists in 8.6 or later. You can access all shared exception % lists from the Shared Exception Lists page. @@ -142,7 +142,7 @@ If no attribute is selected, the app searches the list name by default. You can edit, export, import, duplicate, and delete shared exception lists from the Shared Exception Lists page. -% The following note is only applicable to ESS and is only relevant for users who are upgrading from 8.5 -> 8.6 or later. Might need to add this to the [8.6.x upgrade docs](https://www.elastic.co/guide/en/security/8.6/upgrade-intro.html) later. +% The following note is only applicable to {{ech}} and is only relevant for users who are upgrading from 8.5 -> 8.6 or later. Might need to add this to the [8.6.x upgrade docs](https://www.elastic.co/guide/en/security/8.6/upgrade-intro.html) later. % ::::{note} % Exception lists created in 8.5 and earlier become shared exception lists in 8.6 or later. You can access all shared exception lists from the Shared Exception Lists page. diff --git a/solutions/security/investigate/open-manage-cases.md b/solutions/security/investigate/open-manage-cases.md index 07c3b71f87..0882b47fa9 100644 --- a/solutions/security/investigate/open-manage-cases.md +++ b/solutions/security/investigate/open-manage-cases.md @@ -76,7 +76,7 @@ Open a new case to keep track of security issues and share their details with co You can configure email notifications that occur when users are assigned to cases. -For hosted {{kib}} on {{ess}}: +For {{kib}} on {{ecloud}}: 1. Add the email domains to the [notifications domain allowlist](/explore-analyze/alerts-cases/alerts.md).