Merge branch 'main' into docs-clean-up-raw-migrated-files

Author: shainaraskas

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/api-keys/elasticsearch-api-keys.md

@@ -15,7 +15,7 @@ Several types of {{es}} API keys exist:
 
 To manage API keys in {{kib}}, go to the **API Keys** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md).
 
-![API Keys UI](../../images/kibana-api-keys.png "")
+![API Keys UI](/deploy-manage/images/kibana-api-keys.png "")
 
 
 ## Security privileges [api-keys-security-privileges]
@@ -33,7 +33,7 @@ To manage roles, go to the **Roles** management page using the navigation menu o
 
 To create an API key, go to the **API Keys** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and select **Create API key**.
 
-![Create API Key UI](../../images/kibana-create-ccr-api-key.png "")
+![Create API Key UI](/deploy-manage/images/kibana-create-ccr-api-key.png "")
 
 Refer to the [Create API key](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-api-key) documentation to learn more about creating user API keys.
 

deploy-manage/api-keys/serverless-project-api-keys.md

@@ -14,7 +14,7 @@ In serverless projects, the following types of API keys exist:
 
 You can manage your keys in **{{project-settings}} → {{manage-app}} → {{api-keys-app}}**:
 
-:::{image} ../../images/serverless-api-key-management.png
+:::{image} /deploy-manage/images/serverless-api-key-management.png
 :alt: API keys UI
 :screenshot:
 :::
@@ -24,7 +24,7 @@ You can manage your keys in **{{project-settings}} → {{manage-app}} → {{api-
 
 In **{{api-keys-app}}**, click **Create API key**:
 
-:::{image} ../../images/serverless-create-personal-api-key.png
+:::{image} /deploy-manage/images/serverless-create-personal-api-key.png
 :alt: Create API key UI
 :screenshot:
 :width: 50%

deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

@@ -163,7 +163,7 @@ To help you better understand the available autoscaling settings, this example d
 
         The fault tolerance for the data tier is set to 2 availability zones.
 
-        :::{image} ../../images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png
         :alt: A screenshot showing sizing information for the autoscaled data tier
         :::
 
@@ -181,7 +181,7 @@ To help you better understand the available autoscaling settings, this example d
 
         The fault tolerance for the machine learning instance is set to 1 availability zone.
 
-        :::{image} ../../images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png
         :alt: A screenshot showing sizing information for the autoscaled machine learning node
         :::
 

deploy-manage/autoscaling/trained-model-autoscaling.md

@@ -70,7 +70,7 @@ You can choose from three levels of resource usage for your trained model deploy
 
 Refer to the tables in the [Model deployment resource matrix](#model-deployment-resource-matrix) section to find out the setings for the level you selected.
 
-:::{image} ../../images/machine-learning-ml-nlp-deployment-id-elser-v2.png
+:::{image} /deploy-manage/images/machine-learning-ml-nlp-deployment-id-elser-v2.png
 :alt: ELSER deployment with adaptive resources enabled.
 :screenshot:
 :width: 500px

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

@@ -54,7 +54,7 @@ $$$faq-cost$$$Is there a way for me to estimate how much {{ecloud}} will cost?
 $$$faq-consumption$$$Where can I find a detailed view of my consumption?
 :   To make it easy to track the ongoing cost of {{ecloud}}, we’ve added line items to the downloadable [invoices](https://cloud.elastic.co/billing/overview?page=docs&placement=docs-body).
 
-    ![Example invoice](../../../images/cloud-ec-bill-example-new.png)
+    ![Example invoice](/deploy-manage/images/cloud-ec-bill-example-new.png)
 
     Additionally, on the {{ecloud}} [Usage](https://cloud.elastic.co/billing/usage?page=docs&placement=docs-body) page, the **Month-to-date usage** tile shows accrued costs and can help you to better estimate the next charge amount.
 

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)