move images

Author: colleenmcginnis

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/deploy/cloud-enterprise/connect-elasticsearch.md

@@ -69,7 +69,7 @@ Connections through Cloud IDs are only supported in Beats and Logstash.
 
 Cloud IDs are available in every deployment page, as showed below:
 
-:::{image} ../../../images/cloud-enterprise-ec-ce-cloud-id.png
+:::{image} /deploy-manage/images/cloud-enterprise-ec-ce-cloud-id.png
 :alt: The Cloud ID and `elastic` user information shown when you create a deployment
 :::
 

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

@@ -18,7 +18,7 @@ To create a deployment in ECE:
 
     You can quickly create a deployment by setting the basic parameters shown in the UI. If you need more control, select **Advanced settings** to configure additional options, as detailed below.
 
-    :::{image} ../../../images/cloud-enterprise-ece-create-deployment.png
+    :::{image} /deploy-manage/images/cloud-enterprise-ece-create-deployment.png
     :alt: Create a deployment
     :::
 

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

@@ -46,15 +46,15 @@ In the deployment edit page, you can configure the following settings and featur
 
     * From the **Size per zone** drop-down menu, select what best fits your requirements.
 
-        :::{image} ../../../images/cloud-enterprise-ec-customize-deployment2.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ec-customize-deployment2.png
         :alt: Customize hot data and content tier nodes
         :::
 
         Based on the size you select for a tier, ECE automatically calculates the required number of nodes. Before adding additional nodes, the system scales up existing nodes to the maximum size allowed by their instance configuration, as defined in the deployment template. The maximum size for an {{es}} instance using the default templates typically ranges between 58GB and 64GB RAM.
         
         The **Architecture** summary displays the total number of nodes per zone, where each circle color represents a different node type:
 
-        :::{image} ../../../images/cloud-enterprise-ec-number-of-nodes.png
+        :::{image} /deploy-manage/images/cloud-enterprise-ec-number-of-nodes.png
         :alt: Number of nodes per deployment size
         :::
 

deploy-manage/deploy/cloud-enterprise/deploy-large-installation.md

@@ -21,7 +21,7 @@ This type of installation is recommended for deployments with significant overal
 * 3 hosts with 16 GB RAM each for proxies
 * 3 availability zones
 
-:::{image} ../../../images/cloud-enterprise-ece-pb-9.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-9.png
 :alt: A large installation with nine to twelve hosts across three availability zones
 :::
 

deploy-manage/deploy/cloud-enterprise/deploy-medium-installation.md

@@ -15,7 +15,7 @@ This type of installation is recommended for many production setups. You need:
 * 3 hosts with 256 GB RAM each for allocators
 * 3 availability zones
 
-:::{image} ../../../images/cloud-enterprise-ece-pb-6.png
+:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-6.png
 :alt: A medium installation with nine to twelve hosts across three availability zones
 :::