elastic · leemthompo · Feb 18, 2025 · Feb 18, 2025 · Feb 18, 2025 · Feb 18, 2025
@@ -14,7 +14,6 @@ The [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application
 
 * Kibana
 * APM Server
-* Enterprise Search
 * Elastic Maps Server
 
 These resources expose the `scale` subresource which can be used by the Horizontal Pod Autoscaler controller to automatically adjust the number of replicas according to the CPU load or any other custom or external metric. This example shows how to create an `HorizontalPodAutoscaler` resource to adjust the replicas of a Kibana deployment according to the CPU load:

@@ -39,7 +39,6 @@ $$$ec-autoscaling-api-example-requirements-table$$$
 | coordinating and master nodes | ✓ | ✕ | ✕ |
 | Kibana | ✓ | ✕ | ✕ |
 | APM | ✓ | ✕ | ✕ |
-| Enterprise Search | ✓ | ✕ | ✕ |
 
 +
 

@@ -78,7 +78,6 @@ The following are known limitations and restrictions with autoscaling:
 
 * Autoscaling will not run if the cluster is unhealthy or if the last Elasticsearch plan failed.
 * Trial deployments cannot be configured to autoscale beyond the normal Trial deployment size limits. The maximum size per zone is increased automatically from the Trial limit when you convert to a paid subscription.
-* If Enterprise Search is left at the default size, and has no engines or sources configured for an extended period, it will be automatically disabled. This occurs whether autoscaling is enabled or not. Reactivate the service by editing the **Enterprise Search** settings for your deployment under **Cloud > Deployments > *your-deployment* > Edit**.
 * ELSER deployments do not scale automatically. For more information, refer to [ELSER](../../explore-analyze/machine-learning/nlp/ml-nlp-elser.md) and [Trained model autoscaling](../../explore-analyze/machine-learning/nlp/ml-nlp-auto-scale.md).
 
 

@@ -40,7 +40,6 @@ $$$ece-autoscaling-api-example-requirements-table$$$
 | coordinating and master nodes | ✓ | ✕ | ✕ |
 | Kibana | ✓ | ✕ | ✕ |
 | APM | ✓ | ✕ | ✕ |
-| Enterprise Search | ✓ | ✕ | ✕ |
 
 +
 

@@ -96,7 +96,6 @@ $$$faq-included$$$What is included in my paid {{ech}} deployment?
 
     * Free 1GB RAM Kibana instance
     * Free 1GB RAM Machine Learning node
-    * Free 2GB RAM Enterprise Search instance
     * Free 1GB RAM APM server
     * A free allowance for [data transfer and snapshot storage costs](#faq-dts)
 

@@ -37,7 +37,6 @@ Other Products
     * [APM event intake API Reference](/solutions/observability/apps/elastic-apm-events-intake-api.md)
     * [App Search API Reference](https://www.elastic.co/guide/en/app-search/current/api-reference.html)
     * [Elastic Security APIs](https://www.elastic.co/guide/en/security/current/security-apis.html)
-    * [Enterprise Search management APIs](https://www.elastic.co/guide/en/enterprise-search/current/management-apis.html)
     * [Fleet APIs](https://www.elastic.co/guide/en/fleet/current/fleet-api-docs.html)
     * [Logstash APIs](https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html)
     * [Workplace Search API Reference](https://www.elastic.co/guide/en/workplace-search/current/workplace-search-api-overview.html)

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Change the ECE API URL [ece-config-api-base-url]
 
-You can configure the HTTPS URL used to access the ECE API. You can specify either a DNS host name or an IP address. The primary use for this is to enable [single sign-on](../../users-roles/cloud-enterprise-orchestrator/configure-sso-for-deployments.md) on your deployments, so you can log into Kibana and Enterprise Search automatically once logged in to ECE.
+You can configure the HTTPS URL used to access the ECE API. You can specify either a DNS host name or an IP address. The primary use for this is to enable [single sign-on](../../users-roles/cloud-enterprise-orchestrator/configure-sso-for-deployments.md) on your deployments, so you can log into Kibana automatically once logged in to ECE.
 
 To change the ECE API URL in the Cloud UI:
 

@@ -13,7 +13,6 @@ The components of the Elastic Stack that we support as part of a deployment are
 * Machine Learning (ML) nodes
 * Kibana instances
 * APM and Fleet instances
-* Enterprise Search instances
 
 Elastic Cloud Enterprise comes with some deployment templates already built in, but you can [create new deployment templates](ece-configuring-ece-create-templates.md) to address a particular use case you might have. To make the most out of your hardware, we also recommend that you [configure deployment templates](configure-deployment-templates.md), so that ECE knows where to deploy components of the Elastic Stack.
 
@@ -39,10 +38,6 @@ The deployment templates available are:
 
     Use this template to prevent, collect, detect, and respond to threats for unified protection across your infrastructure. Check the [**Elastic Security**](../../../solutions/security.md) documentation for more information.
 
-* **Elastic Enterprise Search template**
-
-    Default deployment template for Elastic Enterprise Search. Check the [**Enterprise Search**](https://www.elastic.co/guide/en/enterprise-search/current/index.html) documentation for more information.
-
 * **Elastic Observability template**
 
     This template allows you to consolidate your logs, metrics, application traces, and system availability with purpose-built UIs. Check the [**Elastic Observability**](../../../solutions/observability/get-started/what-is-elastic-observability.md) documentation for more information.

@@ -399,7 +399,7 @@ Before you start creating your own deployment templates, you should have: [tagge
 
 
 ::::{note}
-When specifying `node_roles` in the Elasticsearch plan of the deployment template, the template must contain all resource types and all Elasticsearch tiers. The deployment template must contain exactly one entry for each resource type. It must have one Elasticsearch, one Kibana, one APM, and one Enterprise Search. On top of that, it must also include all supported Elasticsearch tiers in the Elasticsearch plan. The supported tiers are identified by the IDs `hot_content`, `warm`, `cold`, `frozen`, `master`, `coordinating` and `ml`.
+When specifying `node_roles` in the Elasticsearch plan of the deployment template, the template must contain all resource types and all Elasticsearch tiers. The deployment template must contain exactly one entry for each resource type. It must have one Elasticsearch, one Kibana, and one APM. On top of that, it must also include all supported Elasticsearch tiers in the Elasticsearch plan. The supported tiers are identified by the IDs `hot_content`, `warm`, `cold`, `frozen`, `master`, `coordinating` and `ml`.
 ::::
 
 

@@ -31,6 +31,10 @@ To learn more about adding the stack pack to ECE, check [Manage Elastic Stack Ve
 
 ## Most recent Elastic Stack packs and Docker images [ece-recent-download-list]
 
+:::{important}
+Enterprise Search is not available in versions 9.0+.
+:::
+
 | Required downloads | Minimum required ECE version |
 | --- | --- |
 | [Elasticsearch, Kibana, APM, and Enterprise Search stack pack: 8.17.1](https://download.elastic.co/cloud-enterprise/versions/8.17.1.zip) | ECE 3.0.0<br>(+ Docker 20.10.10+ required for 8.16+) |

@@ -24,7 +24,7 @@ To perform an offline installation without a private Docker registry, you have t
     For example, for Elastic Cloud Enterprise 3.8.1 and the Elastic Stack versions it shipped with, you need:
 
     * Elastic Cloud Enterprise 3.8.1
-    * Elasticsearch 8.17.1, Kibana 8.17.1, APM 8.17.1, and Enterprise Search 8.17.1
+    * Elasticsearch 8.17.1, Kibana 8.17.1, and APM 8.17.1
 
 2. Create .tar files of the images:
 

@@ -32,6 +32,10 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
     * Elastic Cloud Enterprise 3.8.1
     * Elasticsearch 8.17.1, Kibana 8.17.1, APM 8.17.1, and Enterprise Search 8.17.1
 
+    :::{important}
+       Enterprise Search is not available in versions 9.0+.
+    :::
+
 3. Tag the Docker images with your private registry, where `REGISTRY` is `my.private.repo:5000`, for example:
 
     ```sh

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Manage your installation capacity [ece-manage-capacity]
 
-In ECE, every host is a runner. Depending on the size of your platform, runners can have [one or more roles](ece-roles.md): Coordinator, director, proxy, and allocator. While planning the capacity of your ECE installation, you have to properly size the capacity for all roles. However, the allocator role deserves particular attention, as it hosts the Elasticsearch, Kibana, APM,  Enterprise Search nodes, and the relevant services.
+In ECE, every host is a runner. Depending on the size of your platform, runners can have [one or more roles](ece-roles.md): Coordinator, director, proxy, and allocator. While planning the capacity of your ECE installation, you have to properly size the capacity for all roles. However, the allocator role deserves particular attention, as it hosts the Elasticsearch, Kibana, and APM nodes, and the relevant services.
 
 This section focuses on the allocator role, and explains how to plan its capacity in terms of memory, CPU, `processors` setting, and storage.
 

@@ -25,7 +25,6 @@ After installing or upgrading to version 2.10 or later:
     * For Elasticsearch, the certificate needs to allow for ***.es.<your-domain>**
     * For Kibana, the certificate needs to allow for ***.kb.<your-domain>**
     * For APM, the certificate needs to allow for ***.apm.<your-domain>**
-    * For Enterprise Search or AppSearch, the certificate needs to allow for ***.ent.<your-domain>**
     * For Fleet, the certificate needs to allow for ***.fleet.<your-domain>**
 
 3. In the **Platform** menu, select **Settings**.

@@ -22,6 +22,10 @@ Elasticsearch 7.8 and later comes with Index Lifecycle Management (ILM) always e
 
 ## Most recent Elastic Stack packs [ece_most_recent_elastic_stack_packs]
 
+:::{important}
+Enterprise Search is not available in versions 9.0+.
+:::
+
 The following are the most recently released Elastic Stack packs for version 8.x, 7.x, and 6.x, respectively:
 
 $$$ece-elastic-stack-stackpacks-recent$$$

@@ -55,7 +55,7 @@ stringData:
     logging.level: debug
 ```
 
-Refer to [Set compute resources for Kibana, Enterprise Search, Elastic Maps Server, APM Server and Logstash](manage-compute-resources.md#k8s-compute-resources-kibana-and-apm) for adjusting compute resources for Elastic Maps Server.
+Refer to [Set compute resources for Kibana, Elastic Maps Server, APM Server and Logstash](manage-compute-resources.md#k8s-compute-resources-kibana-and-apm) for adjusting compute resources for Elastic Maps Server.
 
 
 ## Scale out an Elastic Maps Server deployment [k8s-maps-scaling]
-Original file line number
+Diff line change
@@ Expand Up @@
     ::::{note}
-    When specifying `node_roles` in the Elasticsearch plan of the deployment template, the template must contain all resource types and all Elasticsearch tiers. The deployment template must contain exactly one entry for each resource type. It must have one Elasticsearch, one Kibana, one APM, and one Enterprise Search. On top of that, it must also include all supported Elasticsearch tiers in the Elasticsearch plan. The supported tiers are identified by the IDs `hot_content`, `warm`, `cold`, `frozen`, `master`, `coordinating` and `ml`.
+    When specifying `node_roles` in the Elasticsearch plan of the deployment template, the template must contain all resource types and all Elasticsearch tiers. The deployment template must contain exactly one entry for each resource type. It must have one Elasticsearch, one Kibana, and one APM. On top of that, it must also include all supported Elasticsearch tiers in the Elasticsearch plan. The supported tiers are identified by the IDs `hot_content`, `warm`, `cold`, `frozen`, `master`, `coordinating` and `ml`.
     ::::
@@ Expand Down @@