diff --git a/deploy-manage/autoscaling/autoscaling-stateless-applications-on-eck.md b/deploy-manage/autoscaling/autoscaling-stateless-applications-on-eck.md index 6033ace9e3..1a618acb0f 100644 --- a/deploy-manage/autoscaling/autoscaling-stateless-applications-on-eck.md +++ b/deploy-manage/autoscaling/autoscaling-stateless-applications-on-eck.md @@ -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: diff --git a/deploy-manage/autoscaling/ec-autoscaling-api-example.md b/deploy-manage/autoscaling/ec-autoscaling-api-example.md index d7eb0d9a3e..8f509e6d5d 100644 --- a/deploy-manage/autoscaling/ec-autoscaling-api-example.md +++ b/deploy-manage/autoscaling/ec-autoscaling-api-example.md @@ -39,7 +39,6 @@ $$$ec-autoscaling-api-example-requirements-table$$$ | coordinating and master nodes | ✓ | ✕ | ✕ | | Kibana | ✓ | ✕ | ✕ | | APM | ✓ | ✕ | ✕ | -| Enterprise Search | ✓ | ✕ | ✕ | + diff --git a/deploy-manage/autoscaling/ec-autoscaling.md b/deploy-manage/autoscaling/ec-autoscaling.md index d89bdc716f..c7e94def41 100644 --- a/deploy-manage/autoscaling/ec-autoscaling.md +++ b/deploy-manage/autoscaling/ec-autoscaling.md @@ -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). diff --git a/deploy-manage/autoscaling/ece-autoscaling-api-example.md b/deploy-manage/autoscaling/ece-autoscaling-api-example.md index e2609e8b05..539cedcc87 100644 --- a/deploy-manage/autoscaling/ece-autoscaling-api-example.md +++ b/deploy-manage/autoscaling/ece-autoscaling-api-example.md @@ -40,7 +40,6 @@ $$$ece-autoscaling-api-example-requirements-table$$$ | coordinating and master nodes | ✓ | ✕ | ✕ | | Kibana | ✓ | ✕ | ✕ | | APM | ✓ | ✕ | ✕ | -| Enterprise Search | ✓ | ✕ | ✕ | + diff --git a/deploy-manage/cloud-organization/billing/billing-faq.md b/deploy-manage/cloud-organization/billing/billing-faq.md index a9b4c27d98..f0ee15c8ae 100644 --- a/deploy-manage/cloud-organization/billing/billing-faq.md +++ b/deploy-manage/cloud-organization/billing/billing-faq.md @@ -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) diff --git a/deploy-manage/cloud-organization/tools-and-apis.md b/deploy-manage/cloud-organization/tools-and-apis.md index c295caa97e..0cb89d8639 100644 --- a/deploy-manage/cloud-organization/tools-and-apis.md +++ b/deploy-manage/cloud-organization/tools-and-apis.md @@ -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) diff --git a/deploy-manage/deploy/cloud-enterprise/change-ece-api-url.md b/deploy-manage/deploy/cloud-enterprise/change-ece-api-url.md index 0d019e987f..2d3be29af5 100644 --- a/deploy-manage/deploy/cloud-enterprise/change-ece-api-url.md +++ b/deploy-manage/deploy/cloud-enterprise/change-ece-api-url.md @@ -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: diff --git a/deploy-manage/deploy/cloud-enterprise/deployment-templates.md b/deploy-manage/deploy/cloud-enterprise/deployment-templates.md index 741402d043..3e93f71a3e 100644 --- a/deploy-manage/deploy/cloud-enterprise/deployment-templates.md +++ b/deploy-manage/deploy/cloud-enterprise/deployment-templates.md @@ -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. diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md index dfa651cea1..20939bb793 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md @@ -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`. :::: diff --git a/deploy-manage/deploy/cloud-enterprise/ece-install-offline-images.md b/deploy-manage/deploy/cloud-enterprise/ece-install-offline-images.md index 9647ab7262..e728f6908d 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-install-offline-images.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-install-offline-images.md @@ -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
(+ Docker 20.10.10+ required for 8.16+) | diff --git a/deploy-manage/deploy/cloud-enterprise/ece-install-offline-no-registry.md b/deploy-manage/deploy/cloud-enterprise/ece-install-offline-no-registry.md index 74ef4134cc..5f0b2ded8e 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-install-offline-no-registry.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-install-offline-no-registry.md @@ -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: diff --git a/deploy-manage/deploy/cloud-enterprise/ece-install-offline-with-registry.md b/deploy-manage/deploy/cloud-enterprise/ece-install-offline-with-registry.md index c8ff0849e5..a2faa50ed7 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-install-offline-with-registry.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-install-offline-with-registry.md @@ -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 diff --git a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md index 3032f53686..5daf15cd36 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md @@ -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. diff --git a/deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases.md b/deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases.md index eba4241ce6..dbae739bd6 100644 --- a/deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases.md +++ b/deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases.md @@ -25,7 +25,6 @@ After installing or upgrading to version 2.10 or later: * For Elasticsearch, the certificate needs to allow for ***.es.** * For Kibana, the certificate needs to allow for ***.kb.** * For APM, the certificate needs to allow for ***.apm.** - * For Enterprise Search or AppSearch, the certificate needs to allow for ***.ent.** * For Fleet, the certificate needs to allow for ***.fleet.** 3. In the **Platform** menu, select **Settings**. diff --git a/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md b/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md index 7ae5459eea..a5943cfc0f 100644 --- a/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md +++ b/deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md @@ -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$$$ diff --git a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server.md b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server.md index 7293fb67b7..9478d3d322 100644 --- a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server.md +++ b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server.md @@ -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] diff --git a/deploy-manage/deploy/cloud-on-k8s/configuration-enterprise-search.md b/deploy-manage/deploy/cloud-on-k8s/configuration-enterprise-search.md deleted file mode 100644 index 9242a8a5a4..0000000000 --- a/deploy-manage/deploy/cloud-on-k8s/configuration-enterprise-search.md +++ /dev/null @@ -1,240 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-enterprise-search-configuration.html ---- - -# Configuration [k8s-enterprise-search-configuration] - -## Upgrade the Enterprise Search specification [k8s-enterprise-search-upgrade-specification] - -You can upgrade the Enterprise Search version or change settings by editing the YAML specification. ECK will apply the changes by performing a rolling restart of Enterprise Search pods. - - -## Customize Enterprise Search configuration [k8s-enterprise-search-custom-configuration] - -ECK sets up a default Enterprise Search [configuration](https://www.elastic.co/guide/en/enterprise-search/current/configuration.html#configuration). To customize it, use the `config` element in the specification. - -At a minimum, you must set both `ent_search.external_url` and `kibana.host` to the desired URLs. - -```yaml -apiVersion: enterprisesearch.k8s.elastic.co/v1 -kind: EnterpriseSearch -metadata: - name: enterprise-search-quickstart -spec: - version: 8.16.1 - count: 1 - elasticsearchRef: - name: quickstart - config: - # define the exposed URL at which users will reach Enterprise Search - ent_search.external_url: https://my-custom-domain:3002 - # define the exposed URL at which users will reach Kibana - kibana.host: https://kibana.my-custom-domain:5601 - # configure app search document size limit - app_search.engine.document_size.limit: 100kb -``` - - -## Reference Kubernetes Secrets for sensitive settings [k8s-enterprise-search-secret-configuration] - -Sensitive settings are best stored in Kubernetes Secrets, referenced in the Enterprise Search specification. - -This example sets up a Secret with SMTP credentials: - -```yaml -apiVersion: enterprisesearch.k8s.elastic.co/v1 -kind: EnterpriseSearch -metadata: - name: enterprise-search-quickstart -spec: - version: 8.16.1 - count: 1 - elasticsearchRef: - name: quickstart - config: - ent_search.external_url: https://my-custom-domain:3002 - kibana.host: https://kibana.my-custom-domain:5601 - configRef: - secretName: smtp-credentials ---- -kind: Secret -apiVersion: v1 -metadata: - name: smtp-credentials -stringData: - enterprise-search.yml: |- - email.account.enabled: true - email.account.smtp.auth: plain - email.account.smtp.starttls.enable: false - email.account.smtp.host: 127.0.0.1 - email.account.smtp.port: 25 - email.account.smtp.user: myuser - email.account.smtp.password: mypassword - email.account.email_defaults.from: my@email.com -``` - -ECK merges the content of `config` and `configRef` into a single internal Secret. In case of duplicate settings, the `configRef` secret has precedence. - - -## Customize the Pod template [k8s-enterprise-search-custom-pod-template] - -You can override the Enterprise Search Pod’s specification through the `podTemplate` element. - -This example overrides the default 4Gi deployment to use 8Gi instead, and makes the deployment highly-available with 3 Pods: - -```yaml -apiVersion: enterprisesearch.k8s.elastic.co/v1 -kind: EnterpriseSearch -metadata: - name: enterprise-search-quickstart -spec: - version: 8.16.1 - count: 3 - elasticsearchRef: - name: quickstart - podTemplate: - spec: - containers: - - name: enterprise-search - resources: - requests: - cpu: 3 - memory: 8Gi - limits: - memory: 8Gi - env: - - name: JAVA_OPTS - value: -Xms7500m -Xmx7500m -``` - -### Customize the Pod template security context [k8s-enterprise-search-custom-pod-template-security-context] - -The Enterprise Search Pod’s security context can be customized through the `podTemplate` element. However, if `readOnlyRootFilesystem` is set to `true` without additional configuration, the Pod will fail to start. This happens because Enterprise Search (a Ruby service) requires write access to certain directories within `/usr/share/enterprise-search`, which include WAR files and configurations. - -To work around this, use an init container to copy the necessary WAR files to a temporary writable location, before starting the Enterprise Search container with mounted writable volumes. Having the temporary directories (`/tmp`) in-memory also ensures Ruby has a temporary directory to work with during startup. - -This example demonstrates the workaround: - -```yaml -apiVersion: enterprisesearch.k8s.elastic.co/v1 -kind: EnterpriseSearch -metadata: - name: testing -spec: - version: 8.16.1 - image: docker.elastic.co/enterprise-search/enterprise-search:8.16.1 - count: 1 - elasticsearchRef: - name: testing - podTemplate: - spec: - containers: - - name: enterprise-search - image: docker.elastic.co/enterprise-search/enterprise-search:8.16.1 - securityContext: <1> - readOnlyRootFilesystem: true - runAsNonRoot: true - allowPrivilegeEscalation: false - runAsUser: 1000 <2> - volumeMounts: <3> - - name: search-tmp - mountPath: /usr/share/enterprise-search/tmp - - name: tmp - mountPath: /tmp - - name: filebeat-data - mountPath: /usr/share/enterprise-search/filebeat/data - - name: war-files - mountPath: /usr/share/enterprise-search/lib/war - resources: - requests: - cpu: 3 - memory: 8Gi - limits: - memory: 8Gi - env: <4> - - name: JAVA_OPTS - value: -Xms7500m -Xmx7500m - initContainers: <5> - - name: init-war-dir - image: docker.elastic.co/enterprise-search/enterprise-search:8.16.1 - command: ['sh', '-c', 'cp --verbose -r /usr/share/enterprise-search/lib/war/. /usr/share/enterprise-search-war-tmp'] - volumeMounts: - - name: war-files - mountPath: /usr/share/enterprise-search-war-tmp - volumes: <6> - - name: war-files - emptyDir: {} - - name: filebeat-data - emptyDir: {} - - name: search-tmp - emptyDir: - medium: Memory - - name: tmp - emptyDir: - medium: Memory -``` - -1. Adds a security context to define permissions and access control settings for the `enterprise-search` container. -2. Sets the user to random UID `1000` to run the container as a non-root user. -3. Adds volume mounts for `search-tmp`, `tmp`, `filebeat-data`, and `war-files` to the `enterprise-search` container. -4. Adds the variable `JAVA_OPTS` to pass options and configurations to the Java Virtual Machine (JVM). -5. Adds an init container to copy WAR files to a temporary location. -6. Adds volumes for WAR files and adds volumes with in-memory storage for `search-tmp` and `tmp`. - - - - -## Expose Enterprise Search [k8s-enterprise-search-expose] - -By default ECK manages self-signed TLS certificates to secure the connection to Enterprise Search. It also restricts the Kubernetes service to `ClusterIP` type that cannot be accessed publicly. - -Check [how to access Elastic Stack services](accessing-services.md) to customize TLS settings and expose the service. - -::::{note} -When exposed outside the scope of `localhost`, make sure to set both `ent_search.external_url`, and `kibana.host` accordingly in the Enterprise Search configuration. -:::: - - - -## Customize the connection to an Elasticsearch cluster [k8s-enterprise-search-connect-es] - -The `elasticsearchRef` element allows ECK to automatically configure Enterprise Search to establish a secured connection to a managed Elasticsearch cluster. By default it targets all nodes in your cluster. If you want to direct traffic to specific nodes of your Elasticsearch cluster, refer to [*Traffic Splitting*](requests-routing-to-elasticsearch-nodes.md) for more information and examples. - - -## Connect to an external Elasticsearch cluster [k8s-enterprise-search-connect-non-eck-es] - -### Automatically [k8s_automatically] - -Refer to [*Connect to external Elastic resources*](connect-to-external-elastic-resources.md) to automatically configure Enterprise Search using connection settings from a `Secret`. - - -### Manually [k8s_manually] - -If you do not want to use the `elasticsearchRef` mechanism you can manually configure Enterprise Search to access any available Elasticsearch cluster: - -```yaml -apiVersion: enterprisesearch.k8s.elastic.co/v1 -kind: EnterpriseSearch -metadata: - name: enterprise-search-quickstart -spec: - version: 8.16.1 - count: 1 - configRef: - secretName: elasticsearch-credentials ---- -kind: Secret -apiVersion: v1 -metadata: - name: elasticsearch-credentials -stringData: - enterprise-search.yml: |- - elasticsearch.host: [https://elasticsearch-url:9200](https://elasticsearch-url:9200) - elasticsearch.username: elastic - elasticsearch.password: my-password - elasticsearch.ssl.enabled: true -``` - - - diff --git a/deploy-manage/deploy/cloud-on-k8s/configure-deployments.md b/deploy-manage/deploy/cloud-on-k8s/configure-deployments.md index 7122ba6ada..857a783f20 100644 --- a/deploy-manage/deploy/cloud-on-k8s/configure-deployments.md +++ b/deploy-manage/deploy/cloud-on-k8s/configure-deployments.md @@ -11,7 +11,6 @@ mapped_pages: * [*Run standalone Elastic Agent on ECK*](standalone-elastic-agent.md) * [*Run {{fleet}}-managed {{agent}} on ECK*](fleet-managed-elastic-agent.md) * [*Run Elastic Maps Server on ECK*](elastic-maps-server.md) -* [*Run Enterprise Search on ECK*](enterprise-search.md) * [*Run Beats on ECK*](beats.md) * [*Run {{ls}} on ECK*](logstash.md) * [*Elastic Stack Helm Chart*](managing-deployments-using-helm-chart.md) diff --git a/deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook.md b/deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook.md index 4389a45d64..25f5523f56 100644 --- a/deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook.md +++ b/deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook.md @@ -5,7 +5,7 @@ mapped_pages: # Configure the validating webhook [k8s-webhook] -ECK can be configured to provide a [validating webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) that validates Elastic custom resources (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash) before they are created or updated. Validating webhooks provide immediate feedback if a submitted manifest contains invalid or illegal configuration — which can help you catch errors early and save time that would otherwise be spent on troubleshooting. +ECK can be configured to provide a [validating webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) that validates Elastic custom resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) before they are created or updated. Validating webhooks provide immediate feedback if a submitted manifest contains invalid or illegal configuration — which can help you catch errors early and save time that would otherwise be spent on troubleshooting. Validating webhooks are defined using a `ValidatingWebhookConfiguration` object that defines the following: diff --git a/deploy-manage/deploy/cloud-on-k8s/create-custom-images.md b/deploy-manage/deploy/cloud-on-k8s/create-custom-images.md index 3710c0afbb..d789ef3ef2 100644 --- a/deploy-manage/deploy/cloud-on-k8s/create-custom-images.md +++ b/deploy-manage/deploy/cloud-on-k8s/create-custom-images.md @@ -5,7 +5,7 @@ mapped_pages: # Create custom images [k8s-custom-images] -You can create your own custom application images (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash) instead of using the base images provided by Elastic. You might want to do this to have a canonical image with all the necessary plugins pre-loaded rather than [installing them through an init container](init-containers-for-plugin-downloads.md) each time a Pod starts. You must use the official image as the base for custom images. For example, if you want to create an Elasticsearch 8.16.1 image with the [ICU Analysis Plugin](https://www.elastic.co/guide/en/elasticsearch/plugins/current/analysis-icu.html), you can do the following: +You can create your own custom application images (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) instead of using the base images provided by Elastic. You might want to do this to have a canonical image with all the necessary plugins pre-loaded rather than [installing them through an init container](init-containers-for-plugin-downloads.md) each time a Pod starts. You must use the official image as the base for custom images. For example, if you want to create an Elasticsearch 8.16.1 image with the [ICU Analysis Plugin](https://www.elastic.co/guide/en/elasticsearch/plugins/current/analysis-icu.html), you can do the following: 1. Create a `Dockerfile` containing: diff --git a/deploy-manage/deploy/cloud-on-k8s/customize-pods.md b/deploy-manage/deploy/cloud-on-k8s/customize-pods.md index 83d489834d..c48aac2c3b 100644 --- a/deploy-manage/deploy/cloud-on-k8s/customize-pods.md +++ b/deploy-manage/deploy/cloud-on-k8s/customize-pods.md @@ -56,7 +56,7 @@ spec: ``` ::::{note} -Configuration for other Elastic stack applications, like APM Server, Enterprise Search or Beats, is identical to the Kibana configuration except for the `apiVersion` and `kind` fields. +Configuration for other Elastic stack applications, like APM Server, or Beats, is identical to the Kibana configuration except for the `apiVersion` and `kind` fields. :::: diff --git a/deploy-manage/deploy/cloud-on-k8s/enterprise-search.md b/deploy-manage/deploy/cloud-on-k8s/enterprise-search.md deleted file mode 100644 index dcdc004786..0000000000 --- a/deploy-manage/deploy/cloud-on-k8s/enterprise-search.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-enterprise-search.html ---- - -# Enterprise Search [k8s-enterprise-search] - -This section describes how to deploy, configure and access Enterprise Search with ECK. - -* [Quickstart](quickstart-enterprise-search.md) -* [Configuration](configuration-enterprise-search.md) -* [Troubleshooting](troubleshooting-enterprise-search.md) - - - - diff --git a/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md b/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md index 3aaa779fa5..5a4c068f2f 100644 --- a/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md +++ b/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md @@ -49,7 +49,7 @@ spec: The name of the container in the [Pod Template](https://kubernetes.io/docs/concepts/workloads/pods/#pod-templates) must be `kibana`. -Check [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 more information. +Check [Set compute resources for Kibana, Elastic Maps Server, APM Server and Logstash](manage-compute-resources.md#k8s-compute-resources-kibana-and-apm) for more information. ## {{kib}} configuration [k8s-kibana-configuration] diff --git a/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-anyuid-workaround.md b/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-anyuid-workaround.md index e53a7f6c30..39a4036746 100644 --- a/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-anyuid-workaround.md +++ b/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-anyuid-workaround.md @@ -70,3 +70,6 @@ Starting with version 7.9, it is possible to run the APM Server with the `restri ``` +:::{important} +Enterprise Search is not available in versions 9.0+. +::: \ No newline at end of file diff --git a/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-deploy-operator.md b/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-deploy-operator.md index 026c7fdb66..286fa0baf6 100644 --- a/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-deploy-operator.md +++ b/deploy-manage/deploy/cloud-on-k8s/k8s-openshift-deploy-operator.md @@ -18,7 +18,7 @@ mapped_pages: oc adm pod-network make-projects-global elastic-system ``` -3. Create a namespace to hold the Elastic resources (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash): +3. Create a namespace to hold the Elastic resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash): ::::{note} A namespace other than the default namespaces (default, kube-**, openshift-**, etc) is required such that default [Security Context Constraint](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.md) (SCC) permissions are applied automatically. Elastic resources will not work properly in any of the default namespaces. diff --git a/deploy-manage/deploy/cloud-on-k8s/k8s-service-mesh-istio.md b/deploy-manage/deploy/cloud-on-k8s/k8s-service-mesh-istio.md index 870171d4ae..ff13b3d009 100644 --- a/deploy-manage/deploy/cloud-on-k8s/k8s-service-mesh-istio.md +++ b/deploy-manage/deploy/cloud-on-k8s/k8s-service-mesh-istio.md @@ -61,7 +61,7 @@ spec: As the default `failurePolicy` of the webhook is `Ignore`, the operator continues to function even if the above annotations are not present. The downside is that you are still able to submit an invalid manifest using `kubectl` without receiving any immediate feedback. -ECK has a fallback validation mechanism that reports validation failures as events associated with the relevant resource (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash) that must be manually discovered by running `kubectl describe`. For example, to find the validation errors in an Elasticsearch resource named `quickstart`, you can run `kubectl describe elasticsearch quickstart`. +ECK has a fallback validation mechanism that reports validation failures as events associated with the relevant resource (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) that must be manually discovered by running `kubectl describe`. For example, to find the validation errors in an Elasticsearch resource named `quickstart`, you can run `kubectl describe elasticsearch quickstart`. ## Connect Elastic Stack applications to the Istio service mesh [k8s-service-mesh-istio-stack-connection] diff --git a/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md b/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md index 544cb4ac27..b818afa956 100644 --- a/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md +++ b/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md @@ -5,7 +5,7 @@ mapped_pages: # Manage compute resources [k8s-managing-compute-resources] -To help the Kubernetes scheduler correctly place Pods in available Kubernetes nodes and ensure quality of service (QoS), it is recommended to specify the CPU and memory requirements for objects managed by the operator (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash). In Kubernetes, `requests` defines the minimum amount of resources that must be available for a Pod to be scheduled; `limits` defines the maximum amount of resources that a Pod is allowed to consume. For more information about how Kubernetes uses these concepts, check [Managing Compute Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/). +To help the Kubernetes scheduler correctly place Pods in available Kubernetes nodes and ensure quality of service (QoS), it is recommended to specify the CPU and memory requirements for objects managed by the operator (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash). In Kubernetes, `requests` defines the minimum amount of resources that must be available for a Pod to be scheduled; `limits` defines the maximum amount of resources that a Pod is allowed to consume. For more information about how Kubernetes uses these concepts, check [Managing Compute Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/). ::::{note} The operator applies default requests and limits for memory and CPU. They may be suitable for experimenting with the Elastic Stack, however it is recommended to reevaluate these values for production use cases. diff --git a/deploy-manage/deploy/cloud-on-k8s/managing-deployments-using-helm-chart.md b/deploy-manage/deploy/cloud-on-k8s/managing-deployments-using-helm-chart.md index c7d7688997..2780ad8eac 100644 --- a/deploy-manage/deploy/cloud-on-k8s/managing-deployments-using-helm-chart.md +++ b/deploy-manage/deploy/cloud-on-k8s/managing-deployments-using-helm-chart.md @@ -74,18 +74,6 @@ helm install eck-stack-with-apm-server elastic/eck-stack \ --values https://raw.githubusercontent.com/elastic/cloud-on-k8s/2.16/deploy/eck-stack/examples/apm-server/basic.yaml -n elastic-stack ``` - -## Installing an Elastic Enterprise Search Server along with Elasticsearch and Kibana using the eck-stack Helm Chart [k8s-install-enterprise-search-elasticsearch-kibana-helm] - -The following section builds upon the previous sections, and allows installing an Elastic Enterprise Search Server along with Elasticsearch and Kibana. - -```sh -# Install an eck-managed Elasticsearch, Kibana, and Enterprise Search Server using custom values. -helm install eck-stack-with-enterprise-search elastic/eck-stack \ - --values https://raw.githubusercontent.com/elastic/cloud-on-k8s/2.16/deploy/eck-stack/examples/enterprise-search/basic.yaml -n elastic-stack -``` - - ### Installing individual components of the Elastic Stack using the Helm Charts [k8s-eck-stack-individual-components] You can install individual components in one of two ways using the provided Helm Charts. diff --git a/deploy-manage/deploy/cloud-on-k8s/quickstart-enterprise-search.md b/deploy-manage/deploy/cloud-on-k8s/quickstart-enterprise-search.md deleted file mode 100644 index f22d8ace53..0000000000 --- a/deploy-manage/deploy/cloud-on-k8s/quickstart-enterprise-search.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-enterprise-search-quickstart.html ---- - -# Quickstart [k8s-enterprise-search-quickstart] - -1. Apply the following specification to deploy Enterprise Search. ECK automatically configures the secured connection to an Elasticsearch cluster named `quickstart`, created in [Elasticsearch quickstart](deploy-an-orchestrator.md). - - ```yaml - cat < heap.hprof.gz - -# Remove the heap dump from the running container to free up space -kubectl exec $POD_NAME -- rm /usr/share/enterprise-search/tmp/heap.hprof -``` - - diff --git a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md index 887200e32d..d9a5d6f2bd 100644 --- a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md @@ -169,7 +169,7 @@ $$$azure-integration-existing-email$$$Can I subscribe using an email address fro $$$azure-integration-azure-user-management$$$Is the {{ecloud}} Azure Native ISV Service connected with Azure user management? : No. Elastic is not currently integrated with Azure user management. Azure users who deploy {{es}} on Azure view and manage their own cluster through the Cloud console. Other Azure users in the same tenant cannot access clusters through the Cloud console other than those that they themselves created. - When trying to access resources such as {{es}}, {{kib}}, {{ents}}, or APM in a deployment that was created by another Azure user, the following error is shown: + When trying to access resources such as {{es}}, {{kib}}, or APM in a deployment that was created by another Azure user, the following error is shown: :::{image} ../../../images/cloud-ec-marketplace-azure026.png :alt: Error message displayed in the {{ecloud}} console: To access the resource {resource-name} @@ -300,8 +300,6 @@ $$$azure-integration-whats-included$$$What is included in my {{ecloud}} deployme * An {{es}} cluster * A {{kib}} instance which provides data visualization and a front-end for the {{stack}} * An APM server that allows you to easily collect application traces - * An {{ents}} instance that allows you to easily build a search experience with an intuitive interface - $$$azure-integration-how-to-access$$$How can I access my {{ecloud}} deployment? : Navigate to the deployment overview page in Azure: @@ -320,7 +318,7 @@ $$$azure-integration-modify-deployment$$$How can I modify my {{ecloud}} deployme * [Re-size](ec-customize-deployment-components.md) to increase or decrease the amount of RAM, CPU, and storage available to your deployment, or to add additional availability zones. * [Upgrade](../../upgrade/deployment-or-cluster.md) your deployment to a new {{stack}} version. - * Enable or disable individual {{stack}} components such as APM, Machine Learning, and {{ents}}. + * Enable or disable individual {{stack}} components such as APM and Machine Learning. * [Update {{stack}} user settings](edit-stack-settings.md) in the component YML files. * [Add or remove custom plugins](add-plugins-extensions.md). * [Configure IP filtering](../../security/traffic-filtering.md). diff --git a/deploy-manage/deploy/elastic-cloud/change-hardware.md b/deploy-manage/deploy/elastic-cloud/change-hardware.md index 2e14ac4c9c..85ed6fb9ff 100644 --- a/deploy-manage/deploy/elastic-cloud/change-hardware.md +++ b/deploy-manage/deploy/elastic-cloud/change-hardware.md @@ -7,7 +7,7 @@ mapped_pages: The virtual hardware on which Elastic stack deployments run is defined by instance configurations. To learn more about what an instance configuration is, refer to [Instance configurations](https://www.elastic.co/guide/en/cloud/current/ec-reference-hardware.html#ec-getting-started-configurations). -When a deployment is created, each Elasticsearch tier and stateless resource (e.g., Kibana, Enterprise Search) gets an instance configuration assigned to it, based on the hardware profile used. The combination of instance configurations defined within each hardware profile is designed to provide the best possible outcome for each use case. Therefore, it is not advisable to use instance configurations that are not specified on the hardware profile, except in specific situations in which we may need to migrate an Elasticsearch tier or stateless resource to a different hardware type. An example of such a scenario is when a cloud provider stops supporting a hardware type in a specific region. +When a deployment is created, each Elasticsearch tier and stateless resource (e.g., Kibana) gets an instance configuration assigned to it, based on the hardware profile used. The combination of instance configurations defined within each hardware profile is designed to provide the best possible outcome for each use case. Therefore, it is not advisable to use instance configurations that are not specified on the hardware profile, except in specific situations in which we may need to migrate an Elasticsearch tier or stateless resource to a different hardware type. An example of such a scenario is when a cloud provider stops supporting a hardware type in a specific region. ## Migrate to a different instance configuration using the API [ec_migrate_to_a_different_instance_configuration_using_the_api] diff --git a/deploy-manage/deploy/elastic-cloud/ec-configure-deployment-settings.md b/deploy-manage/deploy/elastic-cloud/ec-configure-deployment-settings.md index d096be0d70..6675c4e493 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-configure-deployment-settings.md +++ b/deploy-manage/deploy/elastic-cloud/ec-configure-deployment-settings.md @@ -36,9 +36,8 @@ The components of the Elastic Stack that we support as part of a deployment are * Kibana instances * APM and Fleet instances * Integrations Server instances -* Enterprise Search instances -When you [create your deployment](create-an-elastic-cloud-hosted-deployment.md), you can choose the hardware profile that best fits your needs, and configure it with the **Advanced settings** option. Depending on the cloud provider that you select, you can adjust the size of Elasticsearch nodes, or configure your Kibana, APM & Fleet, and Enterprise Search instances. As your usage evolves, you can [change the hardware profile](ec-change-hardware-profile.md) of your deployment. +When you [create your deployment](create-an-elastic-cloud-hosted-deployment.md), you can choose the hardware profile that best fits your needs, and configure it with the **Advanced settings** option. Depending on the cloud provider that you select, you can adjust the size of Elasticsearch nodes, or configure your Kibana and APM & Fleet instances. As your usage evolves, you can [change the hardware profile](ec-change-hardware-profile.md) of your deployment. ::::{note} Elastic Agent, Beats, and Logstash are components of the Elastic Stack that are not included in the hardware profiles as they are installed outside of Elastic Cloud. diff --git a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md index dca388774b..74ef2a8102 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md @@ -121,14 +121,6 @@ In production systems, you might need to control what {{es}} data users can acce Refer to [Manage your Integrations Server](manage-integrations-server.md) to learn more. - -## {{ents}} [ec_ents] - -{{ents}} enables you to add modern search to your application or connect and unify content across your workplace. An {{ents}} instance is created automatically as part of every deployment. - -Refer to [Enable Enterprise Search](https://www.elastic.co/guide/en/cloud/current/ec-enable-enterprise-search.html) to learn more. - - ## Security [ec_security] Here, you can configure features that keep your deployment secure: reset the password for the `elastic` user, set up traffic filters, and add settings to the {{es}} keystore. You can also set up remote connections to other deployments. diff --git a/deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md b/deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md index 7022c679ed..b734038a9f 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md @@ -107,11 +107,6 @@ In production systems, you might need to control what {{es}} data users can acce {{integrations-server}} connects observability and security data from Elastic Agents and APM to Elasticsearch. An {{integrations-server}} instance is created automatically as part of every deployment. -### {{ents}} [echents] - -{{ents}} enables you to add modern search to your application or connect and unify content across your workplace. An {{ents}} instance is created automatically as part of every deployment. - - ### Security [echsecurity] Here, you can configure features that keep your deployment secure: reset the password for the `elastic` user, set up traffic filters, and add settings to the {{es}} keystore. You can also set up remote connections to other deployments. diff --git a/deploy-manage/deploy/elastic-cloud/ech-gcp-instance-configuration.md b/deploy-manage/deploy/elastic-cloud/ech-gcp-instance-configuration.md index b08d7055e0..732721ef58 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-gcp-instance-configuration.md +++ b/deploy-manage/deploy/elastic-cloud/ech-gcp-instance-configuration.md @@ -47,7 +47,7 @@ The benefits of the new configurations are multifold: 2. The existing family types have been extended in terms of disk capacity which translates to a more cost effective infrastructure which in some cases can save up to 80% when calculating cost by disk capacity. 3. There are now more instance types to choose from in the hot tier. Rather than the traditional “highio” and “highcpu”, there are now four options to cover the hot data tier which allows to optimize cost/performance further. -In addition to data nodes for storage and search, Elasticsearch nodes also have machine learning nodes, master nodes, and coordinating nodes. These auxiliary node types along with application nodes such as APM servers, Kibana, and Enterprise search have also been upgraded to the new N2 instance types. Both auxiliary node and application node configurations are based on Elasticsearch data node configuration types shown in the previous table. +In addition to data nodes for storage and search, Elasticsearch nodes also have machine learning nodes, master nodes, and coordinating nodes. These auxiliary node types along with application nodes such as APM servers and Kibana instances have also been upgraded to the new N2 instance types. Both auxiliary node and application node configurations are based on Elasticsearch data node configuration types shown in the previous table. | New config name | Notes | | --- | --- | @@ -58,8 +58,6 @@ In addition to data nodes for storage and search, Elasticsearch nodes also have | gcp.kibana.n2.68x32x45 | Kibana nodes have been upgraded two steps up as well, to use 4x the CPU as they had when based on “highmem”. This ensures a more performant Kibana and helps with some client side aggregation, as well as responsive UI. | | gcp.apm.n2.68x32x45 | Same upgrade for APM. Will now use 4x the CPU. | | gcp.integrationsserver.n2.68x32x45 | Same upgrade for Integrations Server. Will now use 4x the CPU. | -| gcp.enterprisesearch.n2.68x32x45 | Same upgrade for Enterprise Search application servers. Will now use 4x the CPU. | - ## Selecting the right configuration for you [ech-gcp-configuration-choose] diff --git a/deploy-manage/deploy/elastic-cloud/ech-getting-started.md b/deploy-manage/deploy/elastic-cloud/ech-getting-started.md index 5bd8b2081f..0ee816c333 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-getting-started.md +++ b/deploy-manage/deploy/elastic-cloud/ech-getting-started.md @@ -9,7 +9,7 @@ This documentation applies to Heroku users who want to make use of the Elasticse 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. -[Elasticsearch Machine Learning](https://www.elastic.co/guide/en/machine-learning/current/index.html), [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](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) are not supported by the Elasticsearch Add-On for Heroku. +[Elasticsearch Machine Learning](https://www.elastic.co/guide/en/machine-learning/current/index.html), [Elastic APM](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Elastic Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) are not supported by the Elasticsearch Add-On for Heroku. To learn more about what plans are available for Heroku users and their cost, check the [Elasticsearch add-on](https://elements.heroku.com/addons/foundelasticsearch) in the Elements Marketplace. diff --git a/deploy-manage/deploy/elastic-cloud/ech-restrictions.md b/deploy-manage/deploy/elastic-cloud/ech-restrictions.md index 2740a0cb2d..480b776d8e 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-restrictions.md +++ b/deploy-manage/deploy/elastic-cloud/ech-restrictions.md @@ -89,6 +89,10 @@ If you are using APM 7.9.0 or older: ## Enterprise Search in Kibana [ech-restrictions-enterprise-search-kibana-integration-traffic-filters] +:::{important} +Enterprise Search is not available in {{stack}} 9.0+. +::: + Enterprise Search’s management interface in Kibana does not work with traffic filters with 8.3.1 and older, it will return an `Insufficient permissions` (403 Forbidden) error. In Kibana 8.3.2, 8.4.0 and higher, the Enterprise Search management interface works with traffic filters. diff --git a/deploy-manage/deploy/elastic-cloud/ech-whats-new.md b/deploy-manage/deploy/elastic-cloud/ech-whats-new.md index 3012262e1f..1b10635f2e 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-whats-new.md +++ b/deploy-manage/deploy/elastic-cloud/ech-whats-new.md @@ -3,7 +3,7 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud-heroku/current/ech-whats-new.html --- -# What���s new with the Elastic Stack [ech-whats-new] +# What's new with the Elastic Stack [ech-whats-new] As soon as the latest Elastic Stack version is released, we make it available to you. @@ -33,5 +33,9 @@ APM Enterprise Search +:::{important} +Enterprise Search is not available in {{stack}} 9.0+. +::: + * [Enterprise Search Release Notes](https://www.elastic.co/guide/en/enterprise-search/current/changelog.html) diff --git a/deploy-manage/deploy/elastic-cloud/manage-deployments-using-elastic-cloud-api.md b/deploy-manage/deploy/elastic-cloud/manage-deployments-using-elastic-cloud-api.md index 7ec7690466..1de40f136f 100644 --- a/deploy-manage/deploy/elastic-cloud/manage-deployments-using-elastic-cloud-api.md +++ b/deploy-manage/deploy/elastic-cloud/manage-deployments-using-elastic-cloud-api.md @@ -68,7 +68,7 @@ This example creates a new deployment named "my-first-api-deployment" with the f * Version 8.17.1 of the Elastic Stack * Elasticsearch cluster in two zones with 4 GB of memory for each node -* 1 GB single zone Kibana instance, 1 GB Integrations Server instance, and 2GB Enterprise Search instance +* 1 GB single zone Kibana instance and 1 GB Integrations Server instance ```sh curl -XPOST \ @@ -252,33 +252,6 @@ curl -XPOST \ }, "ref_id": "main-integrations_server" } - ], - "enterprise_search": [ - { - "elasticsearch_cluster_ref_id": "main-elasticsearch", - "region": "gcp-us-central1", - "plan": { - "cluster_topology": [ - { - "node_type": { - "connector": true, - "appserver": true, - "worker": true - }, - "instance_configuration_id": "gcp.enterprisesearch.n2.68x32x45", - "zone_count": 1, <10> - "size": { - "resource": "memory", - "value": 2048 <11> - } - } - ], - "enterprise_search": { - "version": "8.17.1" - } - }, - "ref_id": "main-enterprise_search" - } ] }, "name": "my-first-api-deployment" @@ -295,8 +268,6 @@ curl -XPOST \ 7. Memory allocated for Kibana 8. Availability zones for Integrations Server 9. Memory allocated for Integrations Server -10. Availability zones for Enterprise Search -11. Memory allocated for Enterprise Search ::::{tip} diff --git a/deploy-manage/deploy/elastic-cloud/manage-deployments.md b/deploy-manage/deploy/elastic-cloud/manage-deployments.md index 4ef831c4cc..85e86038af 100644 --- a/deploy-manage/deploy/elastic-cloud/manage-deployments.md +++ b/deploy-manage/deploy/elastic-cloud/manage-deployments.md @@ -7,7 +7,7 @@ mapped_pages: Sometimes you might need to make changes to the entire deployment, a specific component, or just a single data tier. -* Make adjustments to specific deployment components, such as an [Integrations Server](manage-integrations-server.md), [APM & Fleet Server](switch-from-apm-to-integrations-server-payload.md#ec-manage-apm-and-fleet), [Enterprise Search](https://www.elastic.co/guide/en/cloud/current/ec-enable-enterprise-search.html), [Watcher](../../../explore-analyze/alerts-cases/watcher.md), or [Kibana](access-kibana.md#ec-enable-kibana2). +* Make adjustments to specific deployment components, such as an [Integrations Server](manage-integrations-server.md), [APM & Fleet Server](switch-from-apm-to-integrations-server-payload.md#ec-manage-apm-and-fleet), [Watcher](../../../explore-analyze/alerts-cases/watcher.md), or [Kibana](access-kibana.md#ec-enable-kibana2). * [Enable logging and monitoring](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) of the deployment performance. * [Disable a data tier](../../../manage-data/lifecycle/index-lifecycle-management.md). * [Restart](../../maintenance/start-stop-services/restart-cloud-hosted-deployment.md), [stop routing](../../maintenance/ece/start-stop-routing-requests.md), or [delete your deployment](../../uninstall/delete-a-cloud-deployment.md). diff --git a/deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md b/deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md index b39a617292..0547b1e9a9 100644 --- a/deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md +++ b/deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md @@ -15,7 +15,6 @@ When using Elasticsearch Service, there are some limitations you should be aware * [Kibana](#ec-restrictions-kibana) * [APM Agent central configuration with Private Link or traffic filters](#ec-restrictions-apm-traffic-filters) * [Fleet with Private Link or traffic filters](#ec-restrictions-fleet-traffic-filters) -* [Enterprise Search in Kibana](#ec-restrictions-enterprise-search-kibana-integration-traffic-filters) * [Restoring a snapshot across deployments](#ec-snapshot-restore-enterprise-search-kibana-across-deployments) * [Migrate Fleet-managed {{agents}} across deployments by restoring a snapshot](#ec-migrate-elastic-agent) * [Regions and Availability Zones](#ec-regions-and-availability-zone) @@ -110,20 +109,13 @@ If you are using APM 7.9.0 or older: * You cannot use Fleet 7.13.x if your deployment is secured by [traffic filters](../../security/traffic-filtering.md). Fleet 7.14.0 and later works with traffic filters (both Private Link and IP filters). * If you are using Fleet 8.12+, using a remote {{es}} output with a target cluster that has [traffic filters](../../security/traffic-filtering.md) enabled is not currently supported. - -## Enterprise Search in Kibana [ec-restrictions-enterprise-search-kibana-integration-traffic-filters] - -Enterprise Search’s management interface in Kibana does not work with traffic filters with 8.3.1 and older, it will return an `Insufficient permissions` (403 Forbidden) error. In Kibana 8.3.2, 8.4.0 and higher, the Enterprise Search management interface works with traffic filters. - - ## Restoring a snapshot across deployments [ec-snapshot-restore-enterprise-search-kibana-across-deployments] -Kibana and Enterprise Search do not currently support restoring a snapshot of their indices across Elastic Cloud deployments. +Kibana does not currently support restoring a snapshot of their indices across Elastic Cloud deployments. * [Kibana uses encryption keys](https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html#security-configure-settings) in various places, ranging from encrypting data in some areas of reporting, alerts, actions, connector tokens, ingest outputs used in Fleet and Synthetics monitoring to user sessions. -* [Enterprise Search uses encryption keys](https://www.elastic.co/guide/en/enterprise-search/current/encryption-keys.html) when storing content source synchronization credentials, API tokens and other sensitive information. -* Currently, there is not a way to retrieve the values of Kibana and Enterprise Search encryption keys, or set them in the target deployment before restoring a snapshot. As a result, once a snapshot is restored, Kibana and Enterprise Search will not be able to decrypt the data required for some Kibana and Enterprise Search features to function properly in the target deployment. -* If you have already restored a snapshot across deployments and now have broken Kibana saved objects or Enterprise Search features in the target deployment, you will have to recreate all broken configurations and objects, or create a new setup in the target deployment instead of using snapshot restore. +* Currently, there is not a way to retrieve the values of Kibana encryption keys, or set them in the target deployment before restoring a snapshot. As a result, once a snapshot is restored, Kibana will not be able to decrypt the data required for some features to function properly in the target deployment. +* If you have already restored a snapshot across deployments and now have broken Kibana saved objects in the target deployment, you will have to recreate all broken configurations and objects, or create a new setup in the target deployment instead of using snapshot restore. A snapshot taken using the default `found-snapshots` repository can only be restored to deployments in the same region. If you need to restore snapshots across regions, create the destination deployment, connect to the [custom repository](../../tools/snapshot-and-restore/elastic-cloud-hosted.md), and then [restore from a snapshot](../../tools/snapshot-and-restore/restore-snapshot.md). diff --git a/deploy-manage/license/manage-your-license-in-eck.md b/deploy-manage/license/manage-your-license-in-eck.md index e06631fcea..3cd98799a8 100644 --- a/deploy-manage/license/manage-your-license-in-eck.md +++ b/deploy-manage/license/manage-your-license-in-eck.md @@ -150,9 +150,6 @@ elastic_licensing_memory_gibibytes_apm{license_level="enterprise"} 0.5 # HELP elastic_licensing_memory_gibibytes_elasticsearch Memory used by Elasticsearch in GiB # TYPE elastic_licensing_memory_gibibytes_elasticsearch gauge elastic_licensing_memory_gibibytes_elasticsearch{license_level="enterprise"} 18 -# HELP elastic_licensing_memory_gibibytes_enterprise_search Memory used by Enterprise Search in GiB -# TYPE elastic_licensing_memory_gibibytes_enterprise_search gauge -elastic_licensing_memory_gibibytes_enterprise_search{license_level="enterprise"} 4 # HELP elastic_licensing_memory_gibibytes_kibana Memory used by Kibana in GiB # TYPE elastic_licensing_memory_gibibytes_kibana gauge elastic_licensing_memory_gibibytes_kibana{license_level="enterprise"} 1 diff --git a/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md b/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md index 72c8740869..4b45cbdf99 100644 --- a/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md +++ b/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md @@ -12,7 +12,7 @@ applies: The {{kib}} {{monitor-features}} serve two separate purposes: -1. To visualize monitoring data from across the {{stack}}. You can view health and performance data for {{es}}, {{ls}}, {{ents}}, APM, and Beats in real time, as well as analyze past performance. +1. To visualize monitoring data from across the {{stack}}. You can view health and performance data for {{es}}, {{ls}}, APM, and Beats in real time, as well as analyze past performance. 2. To monitor {{kib}} itself and route that data to the monitoring cluster. If you enable monitoring across the {{stack}}, each monitored component is considered unique based on its persistent UUID, which is written to the [`path.data`](../../deploy/self-managed/configure.md) directory when the node or instance starts. diff --git a/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md index 5aa4f0c630..9c5d7ce9ac 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md @@ -198,20 +198,6 @@ After you’ve enabled log delivery on your deployment, you can [add the Kibana Enabling log collection also supports collecting and indexing the following types of logs from other components in your deployments: -**Enterprise Search** - -* connectors.log* -* crawler.log* -* filebeat* -* app-server.log* -* system.log* -* worker.log* -* kibana.log* - -**App Search** - -* app-search*.log - **APM** * apm*.log* @@ -228,7 +214,7 @@ Check the respective product documentation for more information about the loggin ## Metrics features [ece-extra-metrics-features] -With logging and monitoring enabled for a deployment, metrics are collected for Elasticsearch, Kibana, Enterprise Search, and APM with Fleet Server. +With logging and monitoring enabled for a deployment, metrics are collected for Elasticsearch, Kibana, and APM with Fleet Server. #### Enabling Elasticsearch/Kibana audit logs on your deployment [ece-enable-audit-logs] diff --git a/deploy-manage/production-guidance/optimize-performance/size-shards.md b/deploy-manage/production-guidance/optimize-performance/size-shards.md index 4f05e10ab5..b89030422a 100644 --- a/deploy-manage/production-guidance/optimize-performance/size-shards.md +++ b/deploy-manage/production-guidance/optimize-performance/size-shards.md @@ -80,7 +80,7 @@ There is some overhead associated with each shard, both in terms of cluster mana There is no hard limit on the physical size of a shard, and each shard can in theory contain up to [just over two billion documents](#troubleshooting-max-docs-limit). However, experience shows that shards between 10GB and 50GB typically work well for many use cases, as long as the per-shard document count is kept below 200 million. -You may be able to use larger shards depending on your network and use case, and smaller shards may be appropriate for [Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/index.html) and similar use cases. +You may be able to use larger shards depending on your network and use case, and smaller shards may be appropriate for certain use cases. If you use {{ilm-init}}, set the [rollover action](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-rollover.html)'s `max_primary_shard_size` threshold to `50gb` to avoid shards larger than 50GB and `min_primary_shard_size` threshold to `10gb` to avoid shards smaller than 10GB. diff --git a/deploy-manage/remote-clusters/ec-enable-ccs.md b/deploy-manage/remote-clusters/ec-enable-ccs.md index 35f8e09351..f1ab4c063a 100644 --- a/deploy-manage/remote-clusters/ec-enable-ccs.md +++ b/deploy-manage/remote-clusters/ec-enable-ccs.md @@ -48,12 +48,6 @@ If your deployment was created before February 2021, CCR won’t be enabled by d To enable these features, go to the **Security** page of your deployment and under **Trust management** select **Enable CCR**. -::::{note} -CCR is not supported for indices used by Enterprise Search. -:::: - - - ## Remote clusters and traffic filtering [ec-ccs-ccr-traffic-filtering] ::::{note} diff --git a/deploy-manage/remote-clusters/ece-enable-ccs.md b/deploy-manage/remote-clusters/ece-enable-ccs.md index 8c64f523ae..d1a854edfd 100644 --- a/deploy-manage/remote-clusters/ece-enable-ccs.md +++ b/deploy-manage/remote-clusters/ece-enable-ccs.md @@ -53,11 +53,6 @@ If your deployment was created before ECE version `2.9.0`, CCR won’t be enable To enable these features, go to the **Security** page of your deployment and under **Trust management** select **Enable CCR**. -::::{note} -CCR is not supported for indices used by Enterprise Search. -:::: - - ## Remote clusters and traffic filtering [ece-ccs-ccr-traffic-filtering] diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index c6bd71ff42..3224f254fa 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -327,11 +327,6 @@ toc: - file: deploy/cloud-on-k8s/map-data.md - file: deploy/cloud-on-k8s/advanced-configuration-maps-server.md - file: deploy/cloud-on-k8s/http-configuration.md - - file: deploy/cloud-on-k8s/enterprise-search.md - children: - - file: deploy/cloud-on-k8s/quickstart-enterprise-search.md - - file: deploy/cloud-on-k8s/configuration-enterprise-search.md - - file: deploy/cloud-on-k8s/troubleshooting-enterprise-search.md - file: deploy/cloud-on-k8s/beats.md children: - file: deploy/cloud-on-k8s/quickstart-beats.md diff --git a/deploy-manage/users-roles/cloud-enterprise-orchestrator/configure-sso-for-deployments.md b/deploy-manage/users-roles/cloud-enterprise-orchestrator/configure-sso-for-deployments.md index d303b80320..d96cb32a87 100644 --- a/deploy-manage/users-roles/cloud-enterprise-orchestrator/configure-sso-for-deployments.md +++ b/deploy-manage/users-roles/cloud-enterprise-orchestrator/configure-sso-for-deployments.md @@ -5,7 +5,7 @@ mapped_pages: # Configure SSO for deployments [ece-deployment-sso] -The single sign-on (SSO) feature in ECE allows `platform admins` and `deployment managers` to log in to their Kibana and Enterprise Search instances automatically once they are logged in to ECE. +The single sign-on (SSO) feature in ECE allows `platform admins` and `deployment managers` to log in to their Kibana instances automatically once they are logged in to ECE. ::::{note} Single sign-on is not available for system deployments; you need to use credentials to log in to them. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/service-accounts.md b/deploy-manage/users-roles/cluster-or-deployment-auth/service-accounts.md index 12469eab55..5c8742aff2 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/service-accounts.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/service-accounts.md @@ -32,9 +32,6 @@ Service accounts are predefined in code. The following service accounts are avai `elastic/kibana` : The service account used by {{kib}} to communicate with {{es}}. -`elastic/enterprise-search-server` -: The service account used by Enterprise Search to communicate with {{es}}. - ::::{important} Do not attempt to use service accounts for authenticating individual users. Service accounts can only be authenticated with service tokens, which are not applicable to regular users. :::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/user-profiles.md b/deploy-manage/users-roles/cluster-or-deployment-auth/user-profiles.md index a39f4c7b6e..c9303a2cbc 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/user-profiles.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/user-profiles.md @@ -6,7 +6,7 @@ mapped_pages: # User profiles [user-profile] ::::{note} -The user profile feature is designed only for use by {{kib}} and Elastic’s {{observability}}, {{ents}}, and {{elastic-sec}} solutions. Individual users and external applications should not call this API directly. Elastic reserves the right to change or remove this feature in future releases without prior notice. +The user profile feature is designed only for use by {{kib}} and Elastic’s {{observability}}, and {{elastic-sec}} solutions. Individual users and external applications should not call this API directly. Elastic reserves the right to change or remove this feature in future releases without prior notice. :::: diff --git a/explore-analyze/machine-learning/nlp/nlp-end-to-end-tutorial.md b/explore-analyze/machine-learning/nlp/nlp-end-to-end-tutorial.md index 873d904b59..67a4d0699b 100644 --- a/explore-analyze/machine-learning/nlp/nlp-end-to-end-tutorial.md +++ b/explore-analyze/machine-learning/nlp/nlp-end-to-end-tutorial.md @@ -42,8 +42,6 @@ If your team does not have an Elastic Cloud deployment, start by signing up for Follow the steps to **Create** a new deployment. Make sure to add capacity to the **Machine Learning instances** under the **Advanced settings** before creating the deployment. To simplify scaling, turn on the **Autoscale this deployment** feature. If you use autoscaling, you should increase the minimum RAM for the machine learning instance. For this tutorial, we’ll need at least 2GB of RAM. For more details, refer to [Create a deployment^](../../../deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md) in the Elastic Cloud documentation. -Enriching documents using machine learning was introduced in Enterprise Search **8.5.0**, so be sure to use version **8.5.0 or later**. - ## Clone Eland [nlp-example-clone-eland] Elastic’s [Eland](https://github.com/elastic/eland) tool makes it easy to upload trained models to your deployment via Docker. diff --git a/get-started/installing-elastic-stack.md b/get-started/installing-elastic-stack.md index 32971c0d5a..13af4d83b5 100644 --- a/get-started/installing-elastic-stack.md +++ b/get-started/installing-elastic-stack.md @@ -13,7 +13,6 @@ To install the Elastic Stack on-premises, the following ports need to be open fo | Default port | Component | | --- | --- | -| 3002 | {{ents}} | | 5044 | {{agent}} → {{ls}}
{{beats}} → {{ls}} | | 5601 | {{kib}}
{{agent}} → {{fleet}}
{{fleet-server}} → {{fleet}} | | 8220 | {{agent}} → {{fleet-server}}
APM Server | diff --git a/get-started/introduction.md b/get-started/introduction.md index fbdf23ba4c..e0af00a993 100644 --- a/get-started/introduction.md +++ b/get-started/introduction.md @@ -26,7 +26,7 @@ navigation_title: "What is Kibana?" Being able to search, observe, and protect your data is a requirement for any analyst. {{kib}} provides solutions for each of these use cases. -* [**Enterprise Search**](https://www.elastic.co/guide/en/enterprise-search/current/index.html) enables you to implement premier search experiences for your apps, organizations, and websites. +* [**Elastic Search**](/solutions/search.md) enables you to implement premier search experiences for your apps, organizations, and websites. * [**Elastic Observability**](../solutions/observability/get-started/what-is-elastic-observability.md) enables you to monitor and apply analytics in real time to events happening across all your environments. You can analyze log events, monitor performance metrics for hosts and containers, trace transactions, and maintain service availability. * Designed for security analysts, [**Elastic Security**](../solutions/security.md) includes a multitude of prebuilt detection rules and data integrations to help you collect important information in one place, get an overview of events and alerts, and secure your environments from endpoints to the cloud. diff --git a/get-started/the-stack.md b/get-started/the-stack.md index ba18313dd9..923a8612b5 100644 --- a/get-started/the-stack.md +++ b/get-started/the-stack.md @@ -7,7 +7,7 @@ mapped_urls: # The stack -This section provides an overview of the {{stack}} and its components — including {{kib}}, the primary user interface for all of Elastic's solutions: Enterprise Search, Elastic Observability, and Elastic Security. It then describes how to install the {{stack}}. +This section provides an overview of the {{stack}} and its components — including {{kib}}, the primary user interface for all of Elastic's solutions: Elastic Search, Elastic Observability, and Elastic Security. It then describes how to install the {{stack}}. $$$kibana-navigation-search$$$ @@ -73,7 +73,7 @@ Use {{kib}} to query and visualize the data that’s stored in {{es}}. Or, use t $$$stack-components-kibana$$$ {{kib}} -: {{kib}} is the tool to harness your {{es}} data and to manage the {{stack}}. Use it to analyze and visualize the data that’s stored in {{es}}. {{kib}} is also the home for the Elastic Enterprise Search, Elastic Observability and Elastic Security solutions. [Learn more about {{kib}}](https://www.elastic.co/guide/en/kibana/current/introduction.html). +: {{kib}} is the tool to harness your {{es}} data and to manage the {{stack}}. Use it to analyze and visualize the data that’s stored in {{es}}. {{kib}} is also the home for the Search, Observability and Security solutions. [Learn more about {{kib}}](https://www.elastic.co/guide/en/kibana/current/introduction.html). $$$stack-components-elasticsearch-clients$$$ diff --git a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-air-gapped.md b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-air-gapped.md index 737723b4de..da626e0ff6 100644 --- a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-air-gapped.md +++ b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-air-gapped.md @@ -37,7 +37,7 @@ Once the ECK operator image is copied internally, replace the original image nam ## Override the default container registry [k8s-container-registry-override] -When creating custom resources (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash), the operator defaults to using container images pulled from the `docker.elastic.co` registry. If you are in an environment where external network access is restricted, you can configure the operator to use a different default container registry by starting the operator with the `--container-registry` command-line flag. Check [*Configure ECK*](../../../deploy-manage/deploy/cloud-on-k8s/configure-eck.md) for more information on how to configure the operator using command-line flags and environment variables. +When creating custom resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash), the operator defaults to using container images pulled from the `docker.elastic.co` registry. If you are in an environment where external network access is restricted, you can configure the operator to use a different default container registry by starting the operator with the `--container-registry` command-line flag. Check [*Configure ECK*](../../../deploy-manage/deploy/cloud-on-k8s/configure-eck.md) for more information on how to configure the operator using command-line flags and environment variables. The operator expects container images to be located at specific repositories in the default container registry. Make sure that your container images are stored in the right repositories and are tagged correctly with the Stack version number. For example, if your private registry is `my.registry` and you wish to deploy components from Stack version 8.16.1, the following image names should exist: diff --git a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-install-yaml-manifests.md b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-install-yaml-manifests.md index 5013d170de..89840c3781 100644 --- a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-install-yaml-manifests.md +++ b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-install-yaml-manifests.md @@ -2,7 +2,7 @@ This method is the quickest way to get started with ECK if you have full administrative access to the Kubernetes cluster. The [Quickstart](../../../deploy-manage/deploy/cloud-on-k8s/deploy-an-orchestrator.md) document describes how to proceed with this method. When you run the `kubectl` command listed in [*Deploy ECK in your Kubernetes cluster*](../../../deploy-manage/deploy/cloud-on-k8s/install-using-yaml-manifest-quickstart.md), the following components are installed or updated: -* `CustomResourceDefinition` objects for all supported resource types (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash). +* `CustomResourceDefinition` objects for all supported resource types (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash). * `Namespace` named `elastic-system` to hold all operator resources. * `ServiceAccount`, `ClusterRole` and `ClusterRoleBinding` to allow the operator to manage resources throughout the cluster. * `ValidatingWebhookConfiguration` to validate Elastic custom resources on admission. diff --git a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-installing-eck.md b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-installing-eck.md index 861e9d3e0e..3d8d73a968 100644 --- a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-installing-eck.md +++ b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-installing-eck.md @@ -1,9 +1,9 @@ # Install ECK [k8s-installing-eck] -Elastic Cloud on Kubernetes (ECK) is a [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) to orchestrate Elastic applications (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash) on Kubernetes. It relies on a set of [Custom Resource Definitions (CRD)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions) to declaratively define the way each application is deployed. CRDs are global resources shared by all users of the Kubernetes cluster, which requires [certain permissions](../../../deploy-manage/deploy/cloud-on-k8s/required-rbac-permissions.md#k8s-eck-permissions-installing-crds) to install them for initial use. The operator itself can be installed as a cluster-scoped application managing all namespaces or it can be restricted to a pre-defined set of namespaces. Multiple copies of the operator can be installed on a single Kubernetes cluster provided that the global CRDs are compatible with each instance and optional cluster-scoped extensions such as the [validating webhook](../../../deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook.md) are disabled. +Elastic Cloud on Kubernetes (ECK) is a [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) to orchestrate Elastic applications (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) on Kubernetes. It relies on a set of [Custom Resource Definitions (CRD)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions) to declaratively define the way each application is deployed. CRDs are global resources shared by all users of the Kubernetes cluster, which requires [certain permissions](../../../deploy-manage/deploy/cloud-on-k8s/required-rbac-permissions.md#k8s-eck-permissions-installing-crds) to install them for initial use. The operator itself can be installed as a cluster-scoped application managing all namespaces or it can be restricted to a pre-defined set of namespaces. Multiple copies of the operator can be installed on a single Kubernetes cluster provided that the global CRDs are compatible with each instance and optional cluster-scoped extensions such as the [validating webhook](../../../deploy-manage/deploy/cloud-on-k8s/configure-validating-webhook.md) are disabled. ::::{warning} -Deleting CRDs will trigger deletion of all custom resources (Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash) in all namespaces of the cluster, regardless of whether they are managed by a single operator or multiple operators. +Deleting CRDs will trigger deletion of all custom resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) in all namespaces of the cluster, regardless of whether they are managed by a single operator or multiple operators. :::: diff --git a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-overview.md b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-overview.md index 709fef78b3..69d1ad6b43 100644 --- a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-overview.md +++ b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-overview.md @@ -1,6 +1,6 @@ # Overview [k8s-overview] -Built on the Kubernetes Operator pattern, Elastic Cloud on Kubernetes (ECK) extends the basic Kubernetes orchestration capabilities to support the setup and management of Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash on Kubernetes. +Built on the Kubernetes Operator pattern, Elastic Cloud on Kubernetes (ECK) extends the basic Kubernetes orchestration capabilities to support the setup and management of Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash on Kubernetes. With Elastic Cloud on Kubernetes you can streamline critical operations, such as: diff --git a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-supported.md b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-supported.md index 1f4cde423f..58850c32e2 100644 --- a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-supported.md +++ b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-supported.md @@ -7,7 +7,8 @@ ECK is compatible with: * Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), and Amazon Elastic Kubernetes Service (EKS) * Helm: 3.2.0+ * Elasticsearch, Kibana, APM Server: 6.8+, 7.1+, 8+ -* Enterprise Search: 7.7+, 8+ +* Enterprise Search: 7.7+, 8.x (Enterprise Search is not available in {{stack}} 9.0+) + * Beats: 7.0+, 8+ * Elastic Agent: 7.10+ (standalone), 7.14+ (Fleet), 8+ * Elastic Maps Server: 7.11+, 8+ diff --git a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-tls-certificates.md b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-tls-certificates.md index 6008225960..871f230190 100644 --- a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-tls-certificates.md +++ b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-tls-certificates.md @@ -86,7 +86,7 @@ spec: ## Disable TLS [k8s-disable-tls] -You can explicitly disable TLS for Kibana, APM Server, Enterprise Search and the HTTP layer of Elasticsearch. +You can explicitly disable TLS for Kibana, APM Server, and the HTTP layer of Elasticsearch. ```yaml spec: diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-create-deployment.md b/raw-migrated-files/cloud/cloud-enterprise/ece-create-deployment.md index b5c805804b..6c527bd549 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/ece-create-deployment.md +++ b/raw-migrated-files/cloud/cloud-enterprise/ece-create-deployment.md @@ -22,7 +22,6 @@ To get up and running with your deployment quickly: * **Default**. A template to get you started and for backwards compatibility with existing deployments. The default template is suitable for search and general all-purpose workloads that don’t require more specialized resources. * **Cross-cluster Search**. A lightweight hub to manage remote connections for running Elasticsearch queries across multiple deployments and indices. * [**Elastic Security**](../../../solutions/security.md). Provides an overview of the events and alerts from your environment. Elastic Security helps you defend your organization from threats before damage and loss occur. - * [**Enterprise Search**](https://www.elastic.co/guide/en/enterprise-search/current/index.html). Default deployment template for Elastic Enterprise Search. * [**Elastic Observability**](../../../solutions/observability/get-started/what-is-elastic-observability.md). Enables you to monitor and apply analytics in real time to events happening across all your environments. You can analyze log events, monitor the performance metrics for the host or container that it ran in, trace the transaction, and check the overall service availability. 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 2c7115e27a..e8245f20fb 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 @@ -1,5 +1,9 @@ # Add Enterprise Search user settings [ece-manage-enterprise-search-settings] +:::{important} +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 Elastic Cloud Enterprise are indicated by an {{ecloud}} icon (![logo cloud](https://doc-icons.s3.us-east-2.amazonaws.com/logo_cloud.svg "Supported on {{ecloud}}")). Be sure to refer to the documentation version that matches the Elastic Stack version used in your deployment. diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-securing-clusters-JWT.md b/raw-migrated-files/cloud/cloud-enterprise/ece-securing-clusters-JWT.md index 1a5cac6cb3..e4e09b66a0 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/ece-securing-clusters-JWT.md +++ b/raw-migrated-files/cloud/cloud-enterprise/ece-securing-clusters-JWT.md @@ -1,6 +1,6 @@ # Secure your clusters with JWT [ece-securing-clusters-JWT] -These steps show how you can secure your Elasticsearch clusters, and Enterprise Search instances in a deployment by using a JSON Web Token (JWT) realm for authentication. +These steps show how you can secure your Elasticsearch clusters instances in a deployment by using a JSON Web Token (JWT) realm for authentication. ::::{note} The JWT credentials are valid against the deployment, not the ECE platform. You can configure [role-based access control](../../../deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md) for the platform separately. diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-securing-clusters-SAML.md b/raw-migrated-files/cloud/cloud-enterprise/ece-securing-clusters-SAML.md index d3c122cc46..42fb11a492 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/ece-securing-clusters-SAML.md +++ b/raw-migrated-files/cloud/cloud-enterprise/ece-securing-clusters-SAML.md @@ -1,6 +1,6 @@ # Secure your clusters with SAML [ece-securing-clusters-SAML] -These steps show how you can secure your Elasticsearch clusters, Kibana, and Enterprise Search instances in a deployment by using a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication. +These steps show how you can secure your Elasticsearch clusters and Kibana instances in a deployment by using a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication. ::::{note} The SAML credentials are valid against the deployment, not the ECE platform. You can configure [role-based access control](../../../deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md) for the platform separately. @@ -112,29 +112,7 @@ You must edit your cluster configuration, sometimes also referred to as the depl 1. This arbitrary string defines how SAML login is titled in the Login Selector UI that is shown when you enable multiple authentication providers in Kibana. You can also configure the optional `icon` and `hint` settings for any authentication provider. -7. Recommended: If you are using Enterprise Search, we recommend you set up SAML 2.0 single sign-on (SSO) for the solution. This allows you to manage access to App Search and Workplace Search for your existing SAML users. - - [Configure your Enterprise Search user settings](../../../deploy-manage/deploy/cloud-enterprise/edit-stack-settings.md) with the following parameters: - - * If you are using an Enterprise Search deployment of version 7.14.0 or later: - - Check [Set up Enterprise Search with SAML 2.0 single sign-on (SSO)](https://www.elastic.co/guide/en/enterprise-search/current/saml-idp.html) in the Enterprise Search documentation. This document covers the Elastic Cloud user settings for Elasticsearch, Kibana, and Enterprise Search. It also explains how to manage access to App Search and Workplace Search for your existing SAML users. - - * If you are using an Enterprise Search deployment of version 7.9.2 - 7.17: - - ```sh - ent_search.auth.saml1.source: elasticsearch-saml <1> - ent_search.auth.saml1.order: 1 <2> - ent_search.auth.saml1.description: "SAML login" <3> - ent_search.auth.saml1.icon: "https://my-company.org/company-logo.png" <4> - ``` - - 1. The name of the SAML realm that you have configured earlier, for instance `saml-realm-name`. The SAML realm name can only contain alphanumeric characters, underscores, and hyphens. To reference an `ent_search.auth..source`, you must create a separate application in your third-party SAML provider first and then set up a new SAML realm in Elasticsearch for Enterprise Search. To learn more, check [Elasticsearch SAML](https://www.elastic.co/guide/en/app-search/7.13/security-and-users.html#app-search-self-managed-security-and-user-management-elasticsearch-saml) in the App Search documentation. - 2. The order in which to display this provider on the login screen. - 3. The name to be displayed on the login screen associated with this provider. - 4. The URL to an icon to be displayed on the login screen associated with this provider. - -8. Optional: Generate SAML metadata for the Service Provider. +7. Optional: Generate SAML metadata for the Service Provider. The SAML 2.0 specification provides a mechanism for Service Providers to describe their capabilities and configuration using a metadata file. If your SAML Identity Provider requires or allows you to configure it to trust the Elastic Stack Service Provider through the use of a metadata file, you can generate the SAML metadata by issuing the following request to Elasticsearch: @@ -156,7 +134,7 @@ You must edit your cluster configuration, sometimes also referred to as the depl 1. The elasticsearch endpoint for the given deployment where the `saml1` realm is configured. -9. Optional: If your Identity Provider doesn’t publish its SAML metadata at an HTTP URL, or if your Elasticsearch cluster cannot reach that URL, you can upload the SAML metadata as a file. +8. Optional: If your Identity Provider doesn’t publish its SAML metadata at an HTTP URL, or if your Elasticsearch cluster cannot reach that URL, you can upload the SAML metadata as a file. 1. Prepare a ZIP file with a [custom bundle](../../../solutions/search/full-text/search-with-synonyms.md) that contains your Identity Provider’s metadata (`metadata.xml`) inside of a `saml` folder. @@ -206,7 +184,7 @@ You must edit your cluster configuration, sometimes also referred to as the depl 1. The path to the SAML metadata file that was uploaded. -10. Use the Kibana endpoint URL to log in. +9. Use the Kibana endpoint URL to log in. ## Configure your 7.x cluster to use SAML [ece-7x-saml] diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-stack-getting-started.md b/raw-migrated-files/cloud/cloud-enterprise/ece-stack-getting-started.md index c471ebbce0..cc5fbbfecb 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/ece-stack-getting-started.md +++ b/raw-migrated-files/cloud/cloud-enterprise/ece-stack-getting-started.md @@ -32,6 +32,10 @@ Building a rich search experience, gaining actionable insight into your environm :alt: Elastic Stack components and solutions with Enterprise Search ::: +:::{important} +Enterprise Search is not available in {{stack}} 9.0+. +::: + These solutions help you accomplish your use cases: Ingest data into the deployment and set up specific capabilities of the Elastic Stack. 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. diff --git a/raw-migrated-files/cloud/cloud-enterprise/editing-user-settings.md b/raw-migrated-files/cloud/cloud-enterprise/editing-user-settings.md index 92bddc9cb1..90c505924f 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/editing-user-settings.md +++ b/raw-migrated-files/cloud/cloud-enterprise/editing-user-settings.md @@ -6,8 +6,6 @@ From the Elastic Cloud Enterprise console you can customize Elasticsearch, Kiban * [Manage Kibana’s settings](../../../deploy-manage/deploy/cloud-enterprise/edit-stack-settings.md). * [Tune your APM Server](../../../deploy-manage/deploy/cloud-enterprise/edit-stack-settings.md). * [Configure App Search](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-appsearch-settings.html). -* [Configure Enterprise Search](../../../deploy-manage/deploy/cloud-enterprise/edit-stack-settings.md). - 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 6dc86b9606..df7ee6c623 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 @@ -190,20 +190,6 @@ After you’ve enabled log delivery on your deployment, you can [add the Kibana Enabling log collection also supports collecting and indexing the following types of logs from other components in your deployments: -**Enterprise Search** - -* connectors.log* -* crawler.log* -* filebeat* -* app-server.log* -* system.log* -* worker.log* -* kibana.log* - -**App Search** - -* app-search*.log - **APM** * apm*.log* @@ -220,7 +206,7 @@ Check the respective product documentation for more information about the loggin ## Metrics features [ech-extra-metrics-features] -With logging and monitoring enabled for a deployment, metrics are collected for Elasticsearch, Kibana, Enterprise Search, and APM with Fleet Server. +With logging and monitoring enabled for a deployment, metrics are collected for Elasticsearch, Kibana, and APM with Fleet Server. #### Enabling Elasticsearch/Kibana audit logs on your deployment [ech-enable-audit-logs] 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 859b22da12..910877a5a8 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 @@ -459,7 +459,7 @@ This setting is not available in versions 8.0.0 through 8.2.0. As such, this set ### All supported versions [echall_supported_versions_5] `xpack.alerting.defaultRuleTaskTimeout` -: Specifies the default timeout for the all rule types tasks. Defaults to `5m`. Deprecated in versions 8.2+ and removed in versions 9.0+. +: Specifies the default timeout for the all rule types tasks. Defaults to `5m`. Deprecated in versions 8.2+ and removed in {{stack}} 9.0+. `xpack.actions.microsoftGraphApiUrl` : Specifies the URL to the Microsoft Graph server when using the MS Exchange Server email service. Defaults to `https://graph.microsoft.com/v1.0`. diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md index 5672d0de23..fcc4587388 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md @@ -2,7 +2,7 @@ Keeping on top of the health of your deployments is a key part of the [shared responsibilities](https://www.elastic.co/cloud/shared-responsibility) between Elastic and yourself. Elastic Cloud provides out of the box tools for monitoring the health of your deployment and resolving health issues when they arise. If you are ready to set up a deployment for production use cases, make sure you check the recommendations and best practices for [production readiness](../../../deploy-manage/production-guidance/plan-for-production-elastic-cloud.md). -A deployment on Elastic Cloud is a combination of an Elasticsearch cluster, a Kibana instance and potentially an APM server instance, an Enterprise Search Server instance and an Integration Server instance. The health of an Elastic Cloud deployment comprises the health of the various components that are part of the deployment. +A deployment on Elastic Cloud is a combination of an Elasticsearch cluster, a Kibana instance and potentially an APM server instance, and an Integration Server instance. The health of an Elastic Cloud deployment comprises the health of the various components that are part of the deployment. The most important of these is the {{es}} cluster, because it is the heart of the system for searching and indexing data. @@ -32,7 +32,7 @@ To view the health for a deployment: The **Health** page provides the following information: -* Health issues for Kibana, Enterprise Search, APM and plan changes are reported in the health banner. +* Health issues for Kibana, APM and plan changes are reported in the health banner. * Health issues for {{es}} clusters are broken down into a table with more details on Severity, Description and Affected capabilities. :::{image} ../../../images/cloud-heroku-es-health-page.png diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-regional-deployment-aliases.md b/raw-migrated-files/cloud/cloud-heroku/ech-regional-deployment-aliases.md index e9966911b6..b32b2cef62 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-regional-deployment-aliases.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-regional-deployment-aliases.md @@ -141,7 +141,7 @@ server { This should work for all of your applications, not just {{es}}. To set it up for {{kib}}, for example, you can select `Copy cluster ID` next to {{kib}} on your deployment’s main page to get the correct UUID. ::::{note} -Doing this for {{kib}} or {{ents}} would not work with Cloud SSO. +Doing this for {{kib}} won't work with Cloud SSO. :::: diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-securing-clusters-JWT.md b/raw-migrated-files/cloud/cloud-heroku/ech-securing-clusters-JWT.md index 382772eb26..6800c922a2 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-securing-clusters-JWT.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-securing-clusters-JWT.md @@ -1,6 +1,6 @@ # Secure your clusters with JWT [ech-securing-clusters-JWT] -These steps show how you can secure your Elasticsearch clusters, and Enterprise Search instances in a deployment by using a JSON Web Token (JWT) realm for authentication. +These steps show how you can secure your Elasticsearch clusters in a deployment by using a JSON Web Token (JWT) realm for authentication. ## Before you begin [echbefore_you_begin_11] diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-securing-clusters-SAML.md b/raw-migrated-files/cloud/cloud-heroku/ech-securing-clusters-SAML.md index 94d6dd6dec..d66b27fb44 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-securing-clusters-SAML.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-securing-clusters-SAML.md @@ -1,6 +1,6 @@ # Secure your clusters with SAML [ech-securing-clusters-SAML] -These steps show how you can secure your Elasticsearch clusters, Kibana, and Enterprise Search instances in a deployment by using a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication. +These steps show how you can secure your Elasticsearch clusters and Kibana instances in a deployment by using a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication. ## Configure your 8.0 or above cluster to use SAML [echconfigure_your_8_0_or_above_cluster_to_use_saml] diff --git a/raw-migrated-files/cloud/cloud/ec-autoscaling.md b/raw-migrated-files/cloud/cloud/ec-autoscaling.md index 2a805359fc..36728fe26b 100644 --- a/raw-migrated-files/cloud/cloud/ec-autoscaling.md +++ b/raw-migrated-files/cloud/cloud/ec-autoscaling.md @@ -73,7 +73,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). diff --git a/raw-migrated-files/cloud/cloud/ec-cloud-ingest-data.md b/raw-migrated-files/cloud/cloud/ec-cloud-ingest-data.md index f2a4dd6f04..1ceecbe26f 100644 --- a/raw-migrated-files/cloud/cloud/ec-cloud-ingest-data.md +++ b/raw-migrated-files/cloud/cloud/ec-cloud-ingest-data.md @@ -1,11 +1,11 @@ # Adding data to Elasticsearch [ec-cloud-ingest-data] -You have a number of options for getting data into Elasticsearch, referred to as ingesting or indexing your data. Use Elastic Agent, Beats, Logstash, Elastic language clients, Elastic connectors, or the Enterprise Search web crawler. The option (or combination) selected depends on whether you are indexing general content or timestamped data. +You have a number of options for getting data into Elasticsearch, referred to as ingesting or indexing your data. Use Elastic Agent, Beats, Logstash, Elastic language clients, Elastic connectors, or the web crawler. The option (or combination) selected depends on whether you are indexing general content or timestamped data. $$$ec-ingest-methods$$$ General content -: Index content like HTML pages, catalogs and other files. Send data directly to Elasticseach from your application using an Elastic language client. Otherwise use Elastic content [connectors](https://www.elastic.co/guide/en/enterprise-search/current/connectors.html) or the Elastic [web crawler](https://www.elastic.co/guide/en/enterprise-search/current/crawler.html). +: Index content like HTML pages, catalogs and other files. Send data directly to Elasticseach from your application using an Elastic language client. Otherwise use Elastic content [connectors](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-connectors.html) or the Elastic [web crawler](https://github.com/elastic/crawler). Timestamped data : The preferred way to index timestamped data is to use Elastic Agent. Elastic Agent is a single, unified way to add monitoring for logs, metrics, and other types of data to a host. It can also protect hosts from security threats, query data from operating systems, and forward data from remote services or hardware. Each Elastic Agent based integration includes default ingestion rules, dashboards, and visualizations to start analyzing your data right away. Fleet Management enables you to centrally manage all of your deployed Elastic Agents from Kibana. @@ -188,7 +188,7 @@ For users who want to build their own solution, we can help you get started inge ### Ingest data with Elastic web crawler, connectors [ec-ingest-crawler-connectors] -[Add data with the web crawler](https://www.elastic.co/guide/en/enterprise-search/current/crawler.html) +[Add data with the web crawler](https://github.com/elastic/crawler) : Use the web crawler to programmatically discover, extract, and index searchable content from websites and knowledge bases. [Add data with connectors](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-connectors.html) @@ -200,9 +200,6 @@ For users who want to build their own solution, we can help you get started inge [Elasticsearch language clients](https://www.elastic.co/guide/en/elasticsearch/client/index.html) : Use the {{es}} language clients to ingest data from an application into {{es}}. -[Enterprise Search language clients](https://www.elastic.co/guide/en/enterprise-search/current/programming-language-clients.html) -: The {{ents}} programming language client libraries provide native APIs for those languages to ingest data into {{ents}}, App Search, and Workplace Search. - [Application ingest tutorials](../../../manage-data/ingest/ingesting-data-from-applications.md) : These hands-on guides demonstrate how to use the {{es}} language clients to ingest data from your applications. 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 39e0bf282d..478ea8a251 100644 --- a/raw-migrated-files/cloud/cloud/ec-editing-user-settings.md +++ b/raw-migrated-files/cloud/cloud/ec-editing-user-settings.md @@ -5,9 +5,6 @@ From the Elasticsearch Service console you can customize Elasticsearch, Kibana, * [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). * [Tune your APM Server](../../../solutions/observability/apps/configure-apm-server.md). -* [Configure App Search](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md). -* [Configure Enterprise Search](../../../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 f30761a883..1b8f272e5a 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 @@ -190,20 +190,6 @@ After you’ve enabled log delivery on your deployment, you can [add the Kibana Enabling log collection also supports collecting and indexing the following types of logs from other components in your deployments: -**Enterprise Search** - -* connectors.log* -* crawler.log* -* filebeat* -* app-server.log* -* system.log* -* worker.log* -* kibana.log* - -**App Search** - -* app-search*.log - **APM** * apm*.log* @@ -220,7 +206,7 @@ Check the respective product documentation for more information about the loggin ## Metrics features [ec-extra-metrics-features] -With logging and monitoring enabled for a deployment, metrics are collected for Elasticsearch, Kibana, Enterprise Search, and APM with Fleet Server. +With logging and monitoring enabled for a deployment, metrics are collected for Elasticsearch, Kibana, and APM with Fleet Server. #### Enabling Elasticsearch/Kibana audit logs on your deployment [ec-enable-audit-logs] 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 d10683131c..84cd31f781 100644 --- a/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md +++ b/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md @@ -27,7 +27,7 @@ This frequently-asked-questions list helps you with common questions while you g $$$faq-trial$$$Can I try Elasticsearch Service 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 Enterprise Search, Observability, Security, or the latest version of the Elastic Stack. + 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. $$$faq-config$$$What if I need to change the size of my {{es}} cluster at a later time? diff --git a/raw-migrated-files/cloud/cloud/ec-getting-started.md b/raw-migrated-files/cloud/cloud/ec-getting-started.md index c09387f830..cb03a884f5 100644 --- a/raw-migrated-files/cloud/cloud/ec-getting-started.md +++ b/raw-migrated-files/cloud/cloud/ec-getting-started.md @@ -35,6 +35,10 @@ Building a rich search experience, gaining actionable insight into your environm :alt: Elastic Stack components and solutions with Enterprise Search ::: +:::{important} +Enterprise Search is not available in {{stack}} 9.0+. +::: + These solutions help you accomplish your use cases: Ingest data into the deployment and set up specific capabilities of the Elastic Stack. 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. 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 3a7dce7f0c..b6b1c5a565 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 @@ -1,5 +1,9 @@ # Add Enterprise Search user settings [ec-manage-enterprise-search-settings] +:::{important} +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 (![logo cloud](https://doc-icons.s3.us-east-2.amazonaws.com/logo_cloud.svg "Supported on {{ecloud}}")). Be sure to refer to the documentation version that matches the Elastic Stack version used in your deployment. 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 4f69d28b9d..747973ad6f 100644 --- a/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md +++ b/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md @@ -459,7 +459,7 @@ This setting is not available in versions 8.0.0 through 8.2.0. As such, this set ### All supported versions [ec_all_supported_versions_5] `xpack.alerting.defaultRuleTaskTimeout` -: Specifies the default timeout for the all rule types tasks. Defaults to `5m`. Deprecated in versions 8.2+ and removed in versions 9.0+. +: Specifies the default timeout for the all rule types tasks. Defaults to `5m`. Deprecated in versions 8.2+ and removed in {{stack}} 9.0+. `xpack.actions.microsoftGraphApiUrl` : Specifies the URL to the Microsoft Graph server when using the MS Exchange Server email service. Defaults to `https://graph.microsoft.com/v1.0`. diff --git a/raw-migrated-files/cloud/cloud/ec-monitoring.md b/raw-migrated-files/cloud/cloud/ec-monitoring.md index cf9414fddb..12a9e06d3e 100644 --- a/raw-migrated-files/cloud/cloud/ec-monitoring.md +++ b/raw-migrated-files/cloud/cloud/ec-monitoring.md @@ -8,7 +8,7 @@ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your Keeping on top of the health of your deployments is a key part of the [shared responsibilities](https://www.elastic.co/cloud/shared-responsibility) between Elastic and yourself. Elastic Cloud provides out of the box tools for monitoring the health of your deployment and resolving health issues when they arise. If you are ready to set up a deployment for production use cases, make sure you check the recommendations and best practices for [production readiness](../../../deploy-manage/production-guidance/plan-for-production-elastic-cloud.md). -A deployment on Elastic Cloud is a combination of an Elasticsearch cluster, a Kibana instance and potentially an APM server instance, an Enterprise Search Server instance and an Integration Server instance. The health of an Elastic Cloud deployment comprises the health of the various components that are part of the deployment. +A deployment on Elastic Cloud is a combination of an Elasticsearch cluster, a Kibana instance and potentially an APM server instance, and an Integration Server instance. The health of an Elastic Cloud deployment comprises the health of the various components that are part of the deployment. The most important of these is the {{es}} cluster, because it is the heart of the system for searching and indexing data. 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 3c962d996d..a09e8bfd68 100644 --- a/raw-migrated-files/cloud/cloud/ec-regional-deployment-aliases.md +++ b/raw-migrated-files/cloud/cloud/ec-regional-deployment-aliases.md @@ -141,7 +141,7 @@ server { This should work for all of your applications, not just {{es}}. To set it up for {{kib}}, for example, you can select `Copy cluster ID` next to {{kib}} on your deployment’s main page to get the correct UUID. ::::{note} -Doing this for {{kib}} or {{ents}} would not work with Cloud SSO. +Doing this for {{kib}} or won't work with Cloud SSO. :::: diff --git a/raw-migrated-files/cloud/cloud/ec-securing-clusters-JWT.md b/raw-migrated-files/cloud/cloud/ec-securing-clusters-JWT.md index 4883ecec5e..5947abe84d 100644 --- a/raw-migrated-files/cloud/cloud/ec-securing-clusters-JWT.md +++ b/raw-migrated-files/cloud/cloud/ec-securing-clusters-JWT.md @@ -1,6 +1,6 @@ # Secure your clusters with JWT [ec-securing-clusters-JWT] -These steps show how you can secure your Elasticsearch clusters, and Enterprise Search instances in a deployment by using a JSON Web Token (JWT) realm for authentication. +These steps show how you can secure your Elasticsearch clusters in a deployment by using a JSON Web Token (JWT) realm for authentication. ## Before you begin [ec_before_you_begin_14] diff --git a/raw-migrated-files/cloud/cloud/ec-securing-clusters-SAML.md b/raw-migrated-files/cloud/cloud/ec-securing-clusters-SAML.md index 75d58694c3..fcdf52da16 100644 --- a/raw-migrated-files/cloud/cloud/ec-securing-clusters-SAML.md +++ b/raw-migrated-files/cloud/cloud/ec-securing-clusters-SAML.md @@ -1,8 +1,8 @@ # Secure your clusters with SAML [ec-securing-clusters-SAML] -These steps show how you can secure your Elasticsearch clusters, Kibana, and Enterprise Search instances in a deployment by using a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication. +These steps show how you can secure your Elasticsearch clusters and Kibana instances in a deployment by using a Security Assertion Markup Language (SAML) identity provider (IdP) for cross-domain, single sign-on authentication. -For a detailed walk-through of how to implement SAML authentication for Kibana and Enterprise Search with Azure AD as an identity provider, refer to our guide [Set up SAML with Microsoft Entra ID](../../../deploy-manage/users-roles/cluster-or-deployment-auth/saml.md). +For a detailed walk-through of how to implement SAML authentication for Kibana with Azure AD as an identity provider, refer to our guide [Set up SAML with Microsoft Entra ID](../../../deploy-manage/users-roles/cluster-or-deployment-auth/saml.md). ## Configure your 8.0 or above cluster to use SAML [ec_configure_your_8_0_or_above_cluster_to_use_saml] @@ -109,29 +109,7 @@ You must edit your cluster configuration, sometimes also referred to as the depl 1. This arbitrary string defines how SAML login is titled in the Login Selector UI that is shown when you enable multiple authentication providers in Kibana. You can also configure the optional `icon` and `hint` settings for any authentication provider. -7. Recommended: If you are using Enterprise Search, we recommend you set up SAML 2.0 single sign-on (SSO) for the solution. This allows you to manage access to App Search and Workplace Search for your existing SAML users. - - [Configure your Enterprise Search user settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) with the following parameters: - - * If you are using an Enterprise Search deployment of version 7.14.0 or later: - - Check [Set up Enterprise Search with SAML 2.0 single sign-on (SSO)](https://www.elastic.co/guide/en/enterprise-search/current/saml-idp.html) in the Enterprise Search documentation. This document covers the Elastic Cloud user settings for Elasticsearch, Kibana, and Enterprise Search. It also explains how to manage access to App Search and Workplace Search for your existing SAML users. - - * If you are using an Enterprise Search deployment of version 7.9.2 - 7.17: - - ```sh - ent_search.auth.saml1.source: elasticsearch-saml <1> - ent_search.auth.saml1.order: 1 <2> - ent_search.auth.saml1.description: "SAML login" <3> - ent_search.auth.saml1.icon: "https://my-company.org/company-logo.png" <4> - ``` - - 1. The name of the SAML realm that you have configured earlier, for instance `saml-realm-name`. The SAML realm name can only contain alphanumeric characters, underscores, and hyphens. To reference an `ent_search.auth..source`, you must create a separate application in your third-party SAML provider first and then set up a new SAML realm in Elasticsearch for Enterprise Search. To learn more, check [Elasticsearch SAML](https://www.elastic.co/guide/en/app-search/7.13/security-and-users.html#app-search-self-managed-security-and-user-management-elasticsearch-saml) in the App Search documentation. - 2. The order in which to display this provider on the login screen. - 3. The name to be displayed on the login screen associated with this provider. - 4. The URL to an icon to be displayed on the login screen associated with this provider. - -8. Optional: Generate SAML metadata for the Service Provider. +7. Optional: Generate SAML metadata for the Service Provider. The SAML 2.0 specification provides a mechanism for Service Providers to describe their capabilities and configuration using a metadata file. If your SAML Identity Provider requires or allows you to configure it to trust the Elastic Stack Service Provider through the use of a metadata file, you can generate the SAML metadata by issuing the following request to Elasticsearch: @@ -153,7 +131,7 @@ You must edit your cluster configuration, sometimes also referred to as the depl 1. The elasticsearch endpoint for the given deployment where the `saml1` realm is configured. -9. Optional: If your Identity Provider doesn’t publish its SAML metadata at an HTTP URL, or if your Elasticsearch cluster cannot reach that URL, you can upload the SAML metadata as a file. +8. Optional: If your Identity Provider doesn’t publish its SAML metadata at an HTTP URL, or if your Elasticsearch cluster cannot reach that URL, you can upload the SAML metadata as a file. 1. Prepare a ZIP file with a [custom bundle](../../../deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md) that contains your Identity Provider’s metadata (`metadata.xml`) inside of a `saml` folder. @@ -181,7 +159,7 @@ You must edit your cluster configuration, sometimes also referred to as the depl 1. The path to the SAML metadata file that was uploaded. -10. Use the Kibana endpoint URL to log in. +9. Use the Kibana endpoint URL to log in. ## Configure your 7.x cluster to use SAML [ec-7x-saml] diff --git a/raw-migrated-files/cloud/cloud/ec-securing-clusters-saml-azure.md b/raw-migrated-files/cloud/cloud/ec-securing-clusters-saml-azure.md index 627c690fe9..40bbf4eedc 100644 --- a/raw-migrated-files/cloud/cloud/ec-securing-clusters-saml-azure.md +++ b/raw-migrated-files/cloud/cloud/ec-securing-clusters-saml-azure.md @@ -1,11 +1,10 @@ # Set up SAML with Microsoft Entra ID [ec-securing-clusters-saml-azure] -This guide provides a walk-through of how to configure Microsoft Entra ID (formerly Azure Active Directory) as an identity provider for SAML single sign-on (SSO) authentication, used for accessing Kibana and Enterprise Search in Elasticsearch Service. +This guide provides a walk-through of how to configure Microsoft Entra ID (formerly Azure Active Directory) as an identity provider for SAML single sign-on (SSO) authentication, used for accessing Kibana in Elasticsearch Service. -Use the following steps to configure SAML access to Kibana and/or Enterprise Search: +Use the following steps to configure SAML access to Kibana: * [Configure SAML with Azure AD to access Kibana](../../../deploy-manage/users-roles/cluster-or-deployment-auth/saml.md#ec-securing-clusters-saml-azure-kibana) -* [Configure SAML with Azure AD to access Enterprise Search (Versions 7.x and earlier)](../../../deploy-manage/users-roles/cluster-or-deployment-auth/saml.md#ec-securing-clusters-saml-azure-enterprise-search) For more information about SAML configuration, you can also refer to: @@ -35,7 +34,7 @@ Follow these steps to configure SAML with Microsoft Entra ID as an identity prov 5. Navigate to **Single sign-on** and edit the basic SAML configuration, adding the following information: - 1. `Identifier (Entity ID)` - a string that uniquely identifies a SAML service provider. We recommend using your Kibana or Enterprise Search URL, but you can use any identifier. + 1. `Identifier (Entity ID)` - a string that uniquely identifies a SAML service provider. We recommend using your Kibana URL, but you can use any identifier. For example, `https://saml-azure.kb.northeurope.azure.elastic-cloud.com:443`. @@ -139,59 +138,4 @@ Follow these steps to configure SAML with Microsoft Entra ID as an identity prov For more information, refer to [Configure role mapping](../../../deploy-manage/users-roles/cluster-or-deployment-auth/saml.md#saml-role-mapping) in the Elasticsearch SAML documentation. - -## Configure SAML with Azure AD to access Enterprise Search (versions 7.x and earlier) [ec-securing-clusters-saml-azure-enterprise-search] - -::::{note} -The following instructions only apply to **Enterprise Search versions 7.x and earlier**, which used a standalone UI. Since 8.0 Enterprise Search uses {{kib}} as its user interface. - -:::: - - -1. The initial steps to configure SAML with Azure AD to access Enterprise Search are similar to the earlier steps for [the prior steps for Kibana](../../../deploy-manage/users-roles/cluster-or-deployment-auth/saml.md#ec-securing-clusters-saml-azure-kibana) except that the Enterprise Search URL is used instead of the Kibana URL in the Azure configuration. Follow those steps first to configure the Azure Identity Provider, using your Enterprise Search URL as shown. - - :::{image} ../../../images/cloud-ec-saml-azuread-es-config.png - :alt: The Azure SAML configuration page with Kibana settings - ::: - -2. After you have configured the Azure Identity Provider, proceed with the following steps to configure Elasticsearch and Enterprise Search for SAML: - - 1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). - 2. [Update your Elasticsearch user settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) with the following configuration: - - ```sh - xpack.security.authc.realms.saml.enterprise-search-realm: - order: 3 - attributes.principal: "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" - attributes.groups: "http://schemas.microsoft.com/ws/2008/06/identity/claims/groups" - idp.metadata.path: "https://login.microsoftonline.com//federationmetadata/2007-06/federationmetadata.xml?appid=" - idp.entity_id: "https://sts.windows.net//" - sp.entity_id: "https://" - sp.acs: "/api/security/v1/saml" - sp.logout: "/logout" - ``` - - Where: - - * ``` is your Application ID, available in the application details in Azure. - * ``` is your Tenant ID, available in the application details in Azure. - * `` is your Enterprise Search endpoint, available from the Elasticsearch Service console. Ensure this is the same value that you set for `Identifier (Entity ID)` in the earlier Azure AD configuration step. - - Remember to add this configuration for each node type in your [user settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) if you use several node types based on your deployment architecture (Dedicated Master, High IO, and/or High Storage). - - Note that for `idp.metadata.path` we’ve shown the format to construct the URL, but this should be identical to the `App Federation Metadata URL` setting that you made a note of in the previous step. - - 3. Next, configure Enterprise Search in order to enable SAML authentication: - - 1. Log in to the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). - 2. [Update your Enterprise Search user settings](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) with the following configuration: - - ```sh - ent_search.auth.ent-search-realm.source: elasticsearch-saml - ent_search.auth.ent-search-realm.order: 1 - ent_search.auth.ent-search-realm.description: "SAML login" - ent_search.auth.ent-search-realm.icon: "https://my-company.org/company-logo.png" - ``` - - -You should now have successfully configured SSO access to both Kibana and Enterprise Search with Azure AD as the identity provider. +You should now have successfully configured SSO access to Kibana with Azure AD as the identity provider. diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md index b17343d5c2..75bcaf8e0e 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md @@ -21,7 +21,6 @@ To learn how to collect monitoring data, refer to: * [Monitoring {{kib}}](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md) * [Monitoring {{ls}}](https://www.elastic.co/guide/en/logstash/current/configuring-logstash.html) -* [Monitoring {{ents}}](https://www.elastic.co/guide/en/enterprise-search/current/monitoring.html) * Monitoring {{beats}}: * [{{auditbeat}}](https://www.elastic.co/guide/en/beats/auditbeat/current/monitoring.html) diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/install-elasticsearch.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/install-elasticsearch.md index 8434610556..15b225ffb6 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/install-elasticsearch.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/install-elasticsearch.md @@ -3,7 +3,7 @@ ## Hosted Elasticsearch Service [hosted-elasticsearch-service] -{{ecloud}} offers all of the features of {{es}}, {{kib}}, and Elastic’s {{observability}}, {{ents}}, and {{elastic-sec}} solutions as a hosted service available on AWS, GCP, and Azure. +{{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. To set up Elasticsearch in {{ecloud}}, sign up for a [free {{ecloud}} trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body). diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-overview.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-overview.md index 4f47ae075a..7506692e22 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-overview.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-overview.md @@ -5,7 +5,7 @@ navigation_title: "Overview" # Monitoring overview [monitoring-overview] -When you monitor a cluster, you collect data from the {{es}} nodes, {{ls}} nodes, {{kib}} instances, {{ents}}, APM Server, and Beats in your cluster. You can also collect logs. +When you monitor a cluster, you collect data from the {{es}} nodes, {{ls}} nodes, {{kib}} instances, APM Server, and Beats in your cluster. You can also collect logs. All of the monitoring metrics are stored in {{es}}, which enables you to easily visualize the data in {{kib}}. By default, the monitoring metrics are stored in local indices. diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md index 0f81e7e020..cb7c18dbe4 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md @@ -69,8 +69,7 @@ To store monitoring data in a separate cluster: * [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md) 3. (Optional) [Configure {{ls}} to collect data and send it to the monitoring cluster](https://www.elastic.co/guide/en/logstash/current/configuring-logstash.html). -4. (Optional) [Configure {{ents}} monitoring](https://www.elastic.co/guide/en/enterprise-search/current/monitoring.html). -5. (Optional) Configure the {{beats}} to collect data and send it to the monitoring cluster. Skip this step for {{beats}} that are managed by {{agent}}. +4. (Optional) Configure the {{beats}} to collect data and send it to the monitoring cluster. Skip this step for {{beats}} that are managed by {{agent}}. * [Auditbeat](https://www.elastic.co/guide/en/beats/auditbeat/current/monitoring.html) * [Filebeat](https://www.elastic.co/guide/en/beats/filebeat/current/monitoring.html) @@ -79,14 +78,14 @@ To store monitoring data in a separate cluster: * [Packetbeat](https://www.elastic.co/guide/en/beats/packetbeat/current/monitoring.html) * [Winlogbeat](https://www.elastic.co/guide/en/beats/winlogbeat/current/monitoring.html) -6. (Optional) [Configure APM Server monitoring](/solutions/observability/apps/monitor-apm-server.md) -7. (Optional) Configure {{kib}} to collect data and send it to the monitoring cluster: +5. (Optional) [Configure APM Server monitoring](/solutions/observability/apps/monitor-apm-server.md) +6. (Optional) Configure {{kib}} to collect data and send it to the monitoring cluster: * [{{agent}} collection methods](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md) * [{{metricbeat}} collection methods](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md) * [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md) -8. (Optional) Create a dedicated {{kib}} instance for monitoring, rather than using a single {{kib}} instance to access both your production cluster and monitoring cluster. +7. (Optional) Create a dedicated {{kib}} instance for monitoring, rather than using a single {{kib}} instance to access both your production cluster and monitoring cluster. ::::{note} If you log in to {{kib}} using SAML, Kerberos, PKI, OpenID Connect, or token authentication providers, a dedicated {{kib}} instance is **required**. The security tokens that are used in these contexts are cluster-specific; therefore you cannot use a single {{kib}} instance to connect to both production and monitoring clusters. @@ -95,5 +94,5 @@ To store monitoring data in a separate cluster: 1. (Optional) Disable the collection of monitoring data in this {{kib}} instance. Set the `xpack.monitoring.kibana.collection.enabled` setting to `false` in the `kibana.yml` file. For more information about this setting, see [Monitoring settings in {{kib}}](https://www.elastic.co/guide/en/kibana/current/monitoring-settings-kb.html). -9. [Configure {{kib}} to retrieve and display the monitoring data](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md). +8. [Configure {{kib}} to retrieve and display the monitoring data](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md). 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 11afec04aa..7a19064687 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/snapshots-restore-snapshot.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/snapshots-restore-snapshot.md @@ -33,6 +33,9 @@ This guide also provides tips for [restoring to another cluster](../../../deploy If no such template exists, you can [create one](../../../manage-data/data-store/index-types/set-up-data-stream.md#create-index-template) or [restore a cluster state](../../../deploy-manage/tools/snapshot-and-restore/restore-snapshot.md#restore-entire-cluster) that contains one. Without a matching index template, a data stream can’t roll over or create backing indices. * If your snapshot contains data from App Search or Workplace Search, ensure you’ve restored the [Enterprise Search encryption key](https://www.elastic.co/guide/en/enterprise-search/current/encryption-keys.html) before restoring the snapshot. +:::{important} +Enterprise Search is not available in {{stack}} 9.0+. +::: ## Considerations [restore-snapshot-considerations] diff --git a/raw-migrated-files/observability-docs/observability/obs-ai-assistant.md b/raw-migrated-files/observability-docs/observability/obs-ai-assistant.md index fd48d19e8b..6f66bc8b8c 100644 --- a/raw-migrated-files/observability-docs/observability/obs-ai-assistant.md +++ b/raw-migrated-files/observability-docs/observability/obs-ai-assistant.md @@ -39,7 +39,7 @@ Also, the data you provide to the Observability AI assistant is *not* anonymized The AI assistant requires the following: * {{stack}} version 8.9 and later. -* An [Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/server.html) server if Elastic managed [search connectors](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-native-connectors.html) are used to populate external data into the knowledge base. +* A [self-managed](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-build-connector.html) connector service must be deployed if search connectors are used to populate external data into the knowledge base. * An account with a third-party generative AI provider that preferably supports function calling. If your AI provider does not support function calling, you can configure AI Assistant settings under **Stack Management** to simulate function calling, but this might affect performance. Refer to the [connector documentation](../../../deploy-manage/manage-connectors.md) for your provider to learn about supported and default models. @@ -151,7 +151,7 @@ The [search connectors](https://www.elastic.co/guide/en/elasticsearch/reference/ UI affordances for creating and managing search connectors are available in the Search Solution in {{kib}}. You can also use the {{es}} [Connector APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-connector) to create and manage search connectors. -The infrastructure for deploying connectors can be managed by Elastic or self-managed. Managed connectors require an [Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/server.html) server connected to the Elastic Stack. Self-managed connectors are run on your own infrastructure and don’t require the Enterprise Search service. +A [self-managed](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-build-connector.html) connector service must be deployed to run connectors. By default, the AI Assistant queries all search connector indices. To override this behavior and customize which indices are queried, adjust the **Search connector index pattern** setting on the [AI Assistant Settings](../../../solutions/observability/observability-ai-assistant.md#obs-ai-settings) page. This allows precise control over which data sources are included in AI Assistant knowledge base. diff --git a/raw-migrated-files/stack-docs/elastic-stack/air-gapped-install.md b/raw-migrated-files/stack-docs/elastic-stack/air-gapped-install.md index 3cf1b0525a..6aba51bf8c 100644 --- a/raw-migrated-files/stack-docs/elastic-stack/air-gapped-install.md +++ b/raw-migrated-files/stack-docs/elastic-stack/air-gapped-install.md @@ -12,11 +12,10 @@ Some components of the {{stack}} require additional configuration and local depe * [1.6. {{fleet-server}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-fleet) * [1.7. Elastic APM](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-apm) * [1.8. {{ems}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-maps-service) - * [1.9. {{ents}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-enterprise-search) - * [1.10. {{package-registry}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-package-registry) - * [1.11. {{artifact-registry}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-artifact-registry) - * [1.12. Elastic Endpoint Artifact Repository](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-endpoint-artifact-repository) - * [1.13 {{ml-cap}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-machine-learning) + * [1.9. {{package-registry}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-package-registry) + * [1.10. {{artifact-registry}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-artifact-registry) + * [1.11. Elastic Endpoint Artifact Repository](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-endpoint-artifact-repository) + * [1.12 {{ml-cap}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-machine-learning) * [2. Kubernetes & OpenShift Install](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-kubernetes-and-openshift) @@ -73,7 +72,6 @@ Specifically: * To be able to use {{kib}} mapping visualizations, you need to set up and configure the [Elastic Maps Service](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-maps-service). * To be able to use {{kib}} sample data, install or update hundreds of prebuilt alert rules, and explore available data integrations, you need to set up and configure the [{{package-registry}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-package-registry). * To provide detection rule updates for {{endpoint-sec}} agents, you need to set up and configure the [Elastic Endpoint Artifact Repository](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-endpoint-artifact-repository). -* To access {{ents}} capabilities (in addition to the general search capabilities of {{es}}), you need to set up and configure [{{ents}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-enterprise-search). * To access the APM integration, you need to set up and configure [Elastic APM](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-apm). * To install and use the Elastic documentation for {{kib}} AI assistants, you need to set up and configure the [Elastic product documentation for {{kib}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-kibana-product-documentation). @@ -119,12 +117,7 @@ Air-gapped setup of the APM server is possible in two ways: Refer to [Connect to {{ems}}](../../../explore-analyze/visualize/maps/maps-connect-to-ems.md) in the {{kib}} documentation to learn how to configure your firewall to connect to {{ems}}, host it locally, or disable it completely. -#### 1.9. {{ents}} [air-gapped-enterprise-search] - -Detailed install and configuration instructions are available in the [{{ents}} install documentation](https://www.elastic.co/guide/en/enterprise-search/current/installation.html). - - -#### 1.10. {{package-registry}} [air-gapped-elastic-package-registry] +#### 1.9. {{package-registry}} [air-gapped-elastic-package-registry] Air-gapped install of the EPR is possible using any OCI-compatible runtime like Podman (a typical choice for RHEL-like Linux systems) or Docker. Links to the official container image and usage guide is available on the [Air-gapped environments](https://www.elastic.co/guide/en/fleet/current/air-gapped.html) page in the {{fleet}} and {{agent}} Guide. @@ -136,7 +129,7 @@ Besides setting up the EPR service, you also need to [configure {{kib}}](../../. -#### 1.11. {{artifact-registry}} [air-gapped-elastic-artifact-registry] +#### 1.10. {{artifact-registry}} [air-gapped-elastic-artifact-registry] Air-gapped install of the {{artifact-registry}} is necessary in order to enable {{agent}} deployments to perform self-upgrades and install certain components which are needed for some of the data integrations (that is, in addition to what is also retrieved from the EPR). To learn more, refer to [Host your own artifact registry for binary downloads](https://www.elastic.co/guide/en/fleet/current/air-gapped.html#host-artifact-registry) in the {{fleet}} and {{elastic-agent}} Guide. @@ -148,12 +141,12 @@ When setting up own web server, such as NGINX, to function as the {{artifact-reg -#### 1.12. Elastic Endpoint Artifact Repository [air-gapped-elastic-endpoint-artifact-repository] +#### 1.11. Elastic Endpoint Artifact Repository [air-gapped-elastic-endpoint-artifact-repository] Air-gapped setup of this component is, essentially, identical to the setup of the [{{artifact-registry}}](../../../deploy-manage/deploy/self-managed/air-gapped-install.md#air-gapped-elastic-artifact-registry) except that different artifacts are served. To learn more, refer to [Configure offline endpoints and air-gapped environments](../../../solutions/security/configure-elastic-defend/configure-offline-endpoints-air-gapped-environments.md) in the Elastic Security guide. -#### 1.13 {{ml-cap}} [air-gapped-machine-learning] +#### 1.12 {{ml-cap}} [air-gapped-machine-learning] Some {{ml}} features, like natural language processing (NLP), require you to deploy trained models. To learn about deploying {{ml}} models in an air-gapped environment, refer to: @@ -161,7 +154,7 @@ Some {{ml}} features, like natural language processing (NLP), require you to dep * [Install trained models in an air-gapped environment with Eland](https://www.elastic.co/guide/en/elasticsearch/client/eland/current/machine-learning.html#ml-nlp-pytorch-air-gapped). -#### 1.14 {{kib}} Product documentation for AI Assistants [air-gapped-kibana-product-documentation] +#### 1.13 {{kib}} Product documentation for AI Assistants [air-gapped-kibana-product-documentation] Detailed install and configuration instructions are available in the [{{kib}} AI Assistants settings documentation](https://www.elastic.co/guide/en/kibana/current/ai-assistant-settings-kb.html). 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 b4aa356e0d..fdaad808f4 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 @@ -1,6 +1,6 @@ # Get Elastic [get-elastic] -{{ecloud}} enables you set up the {{stack}} and start using the Enterprise Search, Observability, and Security solutions in minutes. You can deploy globally in any of the dozens of supported regions across Amazon Web Services (AWS), Google Cloud, and Microsoft Azure. +{{ecloud}} enables you set up the {{stack}} and start using the Search, Observability, and Security solutions in minutes. You can deploy globally in any of the dozens of supported regions across Amazon Web Services (AWS), Google Cloud, and Microsoft Azure. If you prefer to go the self-managed route, you can install the Elastic Stack on your own hardware or on a public, private, or hybrid cloud. If you are operating multiple clusters, consider using Elastic Cloud Enterprise or Elastic Cloud for Kubernetes to orchestrate your deployments. diff --git a/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md b/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md index 32887b586a..270d9fdd0f 100644 --- a/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md +++ b/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md @@ -32,10 +32,6 @@ Throughout the Elastic docs we have a number of troubleshooting and frequently a * [Kibana troubleshooting](../../../troubleshoot/kibana.md) * [Osquery FAQ](../../../solutions/security/investigate/osquery-faq.md) -**{{ents}}** - -* [Enterprise Search troubleshooting](https://www.elastic.co/guide/en/enterprise-search/current/troubleshooting.html) - **{{observability}}** * [Observability troubleshooting](../../../troubleshoot/observability.md) diff --git a/solutions/observability/observability-ai-assistant.md b/solutions/observability/observability-ai-assistant.md index 23478acc91..c0144ca695 100644 --- a/solutions/observability/observability-ai-assistant.md +++ b/solutions/observability/observability-ai-assistant.md @@ -44,7 +44,7 @@ Also, the data you provide to the Observability AI assistant is *not* anonymized The AI assistant requires the following: * {{stack}} version 8.9 and later. -* An [Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/server.html) server if Elastic managed [search connectors](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-native-connectors.html) are used to populate external data into the knowledge base. +* A self-deployed connector service if [search connectors](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-build-connector.html) are used to populate external data into the knowledge base. * An account with a third-party generative AI provider that preferably supports function calling. If your AI provider does not support function calling, you can configure AI Assistant settings under **Stack Management** to simulate function calling, but this might affect performance. Refer to the [connector documentation](../../deploy-manage/manage-connectors.md) for your provider to learn about supported and default models. @@ -156,7 +156,7 @@ The [search connectors](https://www.elastic.co/guide/en/elasticsearch/reference/ UI affordances for creating and managing search connectors are available in the Search Solution in {{kib}}. You can also use the {{es}} [Connector APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-connector) to create and manage search connectors. -The infrastructure for deploying connectors can be managed by Elastic or self-managed. Managed connectors require an [Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/server.html) server connected to the Elastic Stack. Self-managed connectors are run on your own infrastructure and don’t require the Enterprise Search service. +The infrastructure for deploying connectors must be [self-managed](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-build-connector.html). By default, the AI Assistant queries all search connector indices. To override this behavior and customize which indices are queried, adjust the **Search connector index pattern** setting on the [AI Assistant Settings](#obs-ai-settings) page. This allows precise control over which data sources are included in AI Assistant knowledge base. diff --git a/solutions/search/site-or-app/behavioral-analytics.md b/solutions/search/site-or-app/behavioral-analytics.md index c0c89bdcf2..52643c0eda 100644 --- a/solutions/search/site-or-app/behavioral-analytics.md +++ b/solutions/search/site-or-app/behavioral-analytics.md @@ -28,7 +28,6 @@ Behavioral Analytics is a **beta feature**. Beta features are subject to change * Behavioral Analytics was introduced in Elastic **8.7.0** to the Enterprise Search service. * There was a breaking schema change in **8.8.0**. (See [Migrating from 8.7 to 8.8](https://www.elastic.co/guide/en/enterprise-search/current/analytics-migration.html) in the Search documentation if you’re upgrading from 8.7 to 8.8.) * The feature was moved to Elasticsearch in **8.10**, meaning the Enterprise Search service is no longer required as of 8.10. - :::: diff --git a/solutions/search/site-or-app/search-ui.md b/solutions/search/site-or-app/search-ui.md index 31e5e58720..1b4f37a372 100644 --- a/solutions/search/site-or-app/search-ui.md +++ b/solutions/search/site-or-app/search-ui.md @@ -20,6 +20,9 @@ A JavaScript library for the fast development of modern, engaging search experie * **Smart URLs** - Searches, paging, filtering, and more, are captured in the URL for direct result linking. * **Flexible front-end** - Not just for React. Use with any JavaScript library, even vanilla JavaScript. * **Flexible back-end** - Use it with Elasticsearch, Elastic Enterprise Search, or any other search API. +:::{important} +Enterprise Search is not available in {{stack}} 9.0+. +::: ## Live demos 👀 [overview-live-demos] diff --git a/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md b/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md index 4c8523ca3b..44a972a3c1 100644 --- a/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md +++ b/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md @@ -319,5 +319,5 @@ kubectl annotate es quickstart eck.k8s.elastic.co/suspend- ## Capture JVM heap dumps [k8s-capture-jvm-heap-dumps] -Elasticsearch and Enterprise Search are applications that run on the JVM. It can be useful to capture a heap dump to troubleshoot garbage collection issues or suspected memory leaks or to share it with Elastic. Follow the application specific instructions for [Elasticsearch](jvm-heap-dumps.md) and [Enterprise Search](../../../deploy-manage/deploy/cloud-on-k8s/troubleshooting-enterprise-search.md#k8s-enterprise-search-jvm-heap-dump). +Elasticsearch runs on the JVM. It can be useful to capture a heap dump to troubleshoot garbage collection issues or suspected memory leaks or to share it with Elastic. Follow the specific instructions for [Elasticsearch](jvm-heap-dumps.md).