Merge branch 'main' into ts-applies-ece

Author: natasha-moore-elastic

deploy-manage/_snippets/field-doc-sec-limitations.md

@@ -6,7 +6,7 @@ When a user’s role enables [document level security](/deploy-manage/users-role
 
 * Document level security doesn’t affect global index statistics that relevancy scoring uses. This means that scores are computed without taking the role query into account. Documents that don’t match the role query are never returned.
 * The `has_child` and `has_parent` queries aren’t supported as query parameters in the role definition. The `has_child` and `has_parent` queries can be used in the search API with document level security enabled.
-* [Date math](elasticsearch://reference/elasticsearch/rest-apis/common-options.md#date-math) expressions cannot contain `now` in [range queries with date fields](elasticsearch://reference/query-languages/query-dsl-range-query.md#ranges-on-dates).
+* [Date math](elasticsearch://reference/elasticsearch/rest-apis/common-options.md#date-math) expressions cannot contain `now` in [range queries with date fields](elasticsearch://reference/query-languages/query-dsl/query-dsl-range-query.md#ranges-on-dates).
 * Any query that makes remote calls to fetch query data isn’t supported, including the following queries:
 
     * `terms` query with terms lookup
@@ -16,7 +16,7 @@ When a user’s role enables [document level security](/deploy-manage/users-role
 * If suggesters are specified and document level security is enabled, the specified suggesters are ignored.
 * A search request cannot be profiled if document level security is enabled.
 * The [terms enum API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-terms-enum) does not return terms if document level security is enabled.
-* The [`multi_match`](elasticsearch://reference/query-languages/query-dsl-multi-match-query.md) query does not support specifying fields using wildcards.
+* The [`multi_match`](elasticsearch://reference/query-languages/query-dsl/query-dsl-multi-match-query.md) query does not support specifying fields using wildcards.
 
 :::{note}
 While document-level security prevents users from viewing restricted documents, it’s still possible to write search requests that return aggregate information about the entire index. A user whose access is restricted to specific documents in an index could still learn about field names and terms that only exist in inaccessible documents, and count how many inaccessible documents contain a given term.

deploy-manage/cloud-organization/billing/manage-subscription.md

@@ -4,6 +4,7 @@ mapped_urls:
   - https://www.elastic.co/guide/en/cloud/current/ec-subscription-overview.html
   - https://www.elastic.co/guide/en/cloud/current/ec-select-subscription-level.html
   - https://www.elastic.co/guide/en/cloud/current/ec-licensing.html
+  - https://www.elastic.co/guide/en/cloud-heroku/current/ech-licensing.html
 applies_to:
   deployment:
     ess: all

deploy-manage/cloud-organization/service-status.md

@@ -4,6 +4,9 @@ mapped_urls:
   - https://www.elastic.co/guide/en/cloud/current/ec_subscribe_to_individual_regionscomponents.html
   - https://www.elastic.co/guide/en/cloud/current/ec_service_status_api.html
   - https://www.elastic.co/guide/en/serverless/current/general-serverless-status.html
+  - https://www.elastic.co/guide/en/cloud-heroku/current/ech-service-status.html
+  - https://www.elastic.co/guide/en/cloud-heroku/current/echservice_status_api.html
+  - https://www.elastic.co/guide/en/cloud-heroku/current/echsubscribe_to_individual_regionscomponents.html
 applies_to:
   deployment:
     ess: all

deploy-manage/cloud-organization/tools-and-apis.md

@@ -37,7 +37,7 @@ 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)
-    * [Fleet APIs](/reference/ingestion-tools/fleet/fleet-api-docs.md)
+    * [Fleet APIs](/reference/fleet/fleet-api-docs.md)
     * [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)
 

deploy-manage/deploy.md

@@ -23,7 +23,7 @@ Your choice of deployment type determines how you'll set up and manage these cor
 This section focuses on deploying and managing {{es}} and {{kib}}, as well as supporting orchestration technologies. However, depending on your use case, you might need to deploy [other {{stack}} components](/get-started/the-stack.md). For example, you might need to add components to ingest logs or metrics.
 
 To learn how to deploy optional {{stack}} components, refer to the following sections:
-* [Fleet and Elastic Agent](/reference/ingestion-tools/fleet/index.md)
+* [Fleet and Elastic Agent](/reference/fleet/index.md)
 * [APM](/solutions/observability/apps/application-performance-monitoring-apm.md)
 * [Beats](beats://reference/index.md)
 * [Logstash](logstash://reference/index.md)

deploy-manage/deploy/_snippets/installation-order.md

@@ -3,7 +3,7 @@ If you're deploying the {{stack}} in a self-managed cluster, then install the {{
 * {{es}}
 * {{kib}}
 * [Logstash](logstash://reference/index.md)
-* [{{agent}}](/reference/ingestion-tools/fleet/index.md) or [Beats](beats://reference/index.md)
+* [{{agent}}](/reference/fleet/index.md) or [Beats](beats://reference/index.md)
 * [APM](/solutions/observability/apps/application-performance-monitoring-apm.md)
 * [Elasticsearch Hadoop](elasticsearch-hadoop://reference/index.md)
 

deploy-manage/deploy/cloud-enterprise/air-gapped-install.md

@@ -19,7 +19,7 @@ Before you start, you must:
 * Follow the same prerequisites described in [](./install.md#ece-install-prerequisites). This includes [](./identify-deployment-scenario.md) and [](./prepare-environment.md) steps.
 * [Configure your operating system](./configure-operating-system.md) in all ECE hosts.
 * Be part of the `docker` group to run the installation script. You should not install Elastic Cloud Enterprise as the `root` user.
-* Set up and run a local copy of the Elastic Package Repository, otherwise your deployments with APM server and Elastic agent won’t work. Refer to the [Running EPR in air-gapped environments](/reference/ingestion-tools/fleet/air-gapped.md#air-gapped-diy-epr) documentation.
+* Set up and run a local copy of the Elastic Package Repository, otherwise your deployments with APM server and Elastic agent won’t work. Refer to the [Running EPR in air-gapped environments](/reference/fleet/air-gapped.md#air-gapped-diy-epr) documentation.
 
 When you are ready to install ECE, you can proceed:
 

deploy-manage/deploy/cloud-enterprise/customize-deployment.md

@@ -79,10 +79,10 @@ When you select **Save changes** on the **Edit deployment** page, the orchestrat
 * **Grow and shrink**: The orchestrator creates new instances with the new configuration, then migrates the data, and eventually deletes the original ones. This strategy is automatically selected when adding or removing master-eligible instances.
 * **Rolling grow and shrink**: Similar to grow and shrink, but creating one instance at a time. This strategy can take a lot longer than grow and shrink.
 
-The `Extended maintenance` optional flag will make ECE to [stop routing requests](../../maintenance/ece/start-stop-routing-requests.md) to all instances during the plan execution. The cluster will be unavailable for external connections while the configuration changes are in progress.
+The `Extended maintenance` optional flag will make ECE to [stop routing requests](../../maintenance/start-stop-routing-requests.md) to all instances during the plan execution. The cluster will be unavailable for external connections while the configuration changes are in progress.
 
 ::::{note}
-If you enable the **Extended maintenance** optional flag, ECE will [stop routing requests](../../maintenance/ece/start-stop-routing-requests.md) to all instances during the plan execution, making the cluster unavailable for external connections while configuration changes are in progress.
+If you enable the **Extended maintenance** optional flag, ECE will [stop routing requests](../../maintenance/start-stop-routing-requests.md) to all instances during the plan execution, making the cluster unavailable for external connections while configuration changes are in progress.
 
 This option introduces downtime and is rarely needed. Use it only when you need to block all traffic to the cluster during the update.
 ::::

deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md

@@ -33,7 +33,7 @@ Users running {{stack}} versions 7.16 or 7.17 need to manually configure TLS. Th
 
 Pick one of the following options:
 
-1. Upload and configure a publicly signed {{es}} TLS certificates. Check [Encrypt traffic in clusters with a self-managed Fleet Server](/reference/ingestion-tools/fleet/secure-connections.md) for details.
+1. Upload and configure a publicly signed {{es}} TLS certificates. Check [Encrypt traffic in clusters with a self-managed Fleet Server](/reference/fleet/secure-connections.md) for details.
 2. Change the {{es}} hosts where {{agent}}s send data from the default public URL, to the internal URL. In {{kib}}, navigate to **Fleet** and select the **Elastic Cloud agent policy**. Click **Fleet settings** and update the {{es}} hosts URL. For example, if the current URL is `https://123abc.us-central1.gcp.foundit.no:9244`, change it to `http://123abc.containerhost:9244`.
 
 

deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md

@@ -8,7 +8,7 @@ mapped_urls:
 
 # Manage your Integrations Server [ece-manage-integrations-server]
 
-For deployments that are version 8.0 and later, you have the option to add a combined [Application Performance Monitoring (APM) Server](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Fleet Server](/reference/ingestion-tools/fleet/index.md) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. Fleet allows you to centrally manage Elastic Agents on many hosts.
+For deployments that are version 8.0 and later, you have the option to add a combined [Application Performance Monitoring (APM) Server](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Fleet Server](/reference/fleet/index.md) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. Fleet allows you to centrally manage Elastic Agents on many hosts.
 
 As part of provisioning, the APM Server and Fleet Server are already configured to work with Elasticsearch and Kibana. At the end of provisioning, you are shown the secret token to configure communication between the APM Server and the backend [APM Agents](https://www.elastic.co/guide/en/apm/agent/index.html). The APM Agents get deployed within your services and applications.