diff --git a/deploy-manage/api-keys/elasticsearch-api-keys.md b/deploy-manage/api-keys/elasticsearch-api-keys.md index 7942c99213..d3c7ebfa10 100644 --- a/deploy-manage/api-keys/elasticsearch-api-keys.md +++ b/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. diff --git a/deploy-manage/api-keys/serverless-project-api-keys.md b/deploy-manage/api-keys/serverless-project-api-keys.md index 0109323677..349a79a73c 100644 --- a/deploy-manage/api-keys/serverless-project-api-keys.md +++ b/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% diff --git a/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md b/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md index 1bb1c4bcd4..9a6498a020 100644 --- a/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md +++ b/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 ::: diff --git a/deploy-manage/autoscaling/trained-model-autoscaling.md b/deploy-manage/autoscaling/trained-model-autoscaling.md index 81bedd36f0..bbd60a1d6f 100644 --- a/deploy-manage/autoscaling/trained-model-autoscaling.md +++ b/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 diff --git a/deploy-manage/cloud-organization/billing/billing-faq.md b/deploy-manage/cloud-organization/billing/billing-faq.md index 76318deff5..7802ed5b29 100644 --- a/deploy-manage/cloud-organization/billing/billing-faq.md +++ b/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. diff --git a/deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md b/deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md index eaadcb6cb9..1d1de5714a 100644 --- a/deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md +++ b/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 ::: diff --git a/deploy-manage/deploy/cloud-enterprise/create-deployment.md b/deploy-manage/deploy/cloud-enterprise/create-deployment.md index 5f0c64e486..d94c5a9ed8 100644 --- a/deploy-manage/deploy/cloud-enterprise/create-deployment.md +++ b/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 ::: diff --git a/deploy-manage/deploy/cloud-enterprise/customize-deployment.md b/deploy-manage/deploy/cloud-enterprise/customize-deployment.md index 33afd1de6f..0d8e2fd3a8 100644 --- a/deploy-manage/deploy/cloud-enterprise/customize-deployment.md +++ b/deploy-manage/deploy/cloud-enterprise/customize-deployment.md @@ -46,7 +46,7 @@ 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 ::: @@ -54,7 +54,7 @@ In the deployment edit page, you can configure the following settings and featur 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 ::: diff --git a/deploy-manage/deploy/cloud-enterprise/deploy-large-installation.md b/deploy-manage/deploy/cloud-enterprise/deploy-large-installation.md index fe2e56c516..b4930e3ed7 100644 --- a/deploy-manage/deploy/cloud-enterprise/deploy-large-installation.md +++ b/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 ::: diff --git a/deploy-manage/deploy/cloud-enterprise/deploy-medium-installation.md b/deploy-manage/deploy/cloud-enterprise/deploy-medium-installation.md index 5e5d630d11..a0c574ef8a 100644 --- a/deploy-manage/deploy/cloud-enterprise/deploy-medium-installation.md +++ b/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 ::: diff --git a/deploy-manage/deploy/cloud-enterprise/deploy-small-installation.md b/deploy-manage/deploy/cloud-enterprise/deploy-small-installation.md index 9196d92453..981796ebab 100644 --- a/deploy-manage/deploy/cloud-enterprise/deploy-small-installation.md +++ b/deploy-manage/deploy/cloud-enterprise/deploy-small-installation.md @@ -14,7 +14,7 @@ The type of installation is recommended for development, test, and small-scale u * 3 hosts with 128 GB RAM * 3 availability zones -:::{image} ../../../images/cloud-enterprise-ece-pb-3.png +:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-3.png :alt: A small baseline installation with three hosts across three availability zones ::: diff --git a/deploy-manage/deploy/cloud-enterprise/ece-architecture.md b/deploy-manage/deploy/cloud-enterprise/ece-architecture.md index cb3235be09..2036fd3010 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-architecture.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-architecture.md @@ -15,7 +15,7 @@ Elastic Cloud Enterprise has a service-oriented architecture that lets you: * Access services through the API. * Deploy each service independently in its own Docker container. -:::{image} ../../../images/cloud-enterprise-ece-architecture.png +:::{image} /deploy-manage/images/cloud-enterprise-ece-architecture.png :alt: Elastic Cloud Enterprise high level architecture ::: 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 3f3946b355..b5a6fae738 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 @@ -28,7 +28,7 @@ Before you start creating your own deployment templates, you should have: [tagge 5. Select **Create template**. The **Configure instances** page opens. 6. Choose whether or not [autoscaling](/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md) is enabled by default for deployments created using the template. Autoscaling adjusts resources available to the deployment automatically as loads change over time. - :::{image} ../../../images/cloud-enterprise-ece-create-template-autoscaling.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-autoscaling.png :alt: screencapture of the "Enable autoscaling by default" switch ::: @@ -36,19 +36,19 @@ Before you start creating your own deployment templates, you should have: [tagge * Select which [instance configuration](ece-configuring-ece-instance-configurations-create.md) to assign to the template. This allows you to optimize the performance of your deployments by matching a machine type to a use case. A hot data and content tier, for example, is best suited to be allocated with an instance configuration having fast SSD storage, while warm and cold data tiers should be allocated with an instance configuration with larger storage but likely less performant, lower cost hardware. - :::{image} ../../../images/cloud-enterprise-ece-create-template-instance-configuration.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-instance-configuration.png :alt: screencapture of the "Initial size per zone" dropdown box ::: * Adjust the default, initial amount of memory and storage. Increasing memory and storage also improves performance by increasing the CPU resources that get assigned relative to the size of the instance, meaning that a 32 GB instance gets twice as much CPU resource as a 16 GB one. These resources are just template defaults that can be adjusted further before you create actual deployments. - :::{image} ../../../images/cloud-enterprise-ece-create-template-initial-size.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-initial-size.png :alt: screencapture of the "Initial size per zone" dropdown box ::: * Configure autoscaling settings for the deployment. - :::{image} ../../../images/cloud-enterprise-ece-create-template-max-autoscaling.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-max-autoscaling.png :alt: screencapture of the "Maximum autoscaling size per zone" dropdown box ::: @@ -59,13 +59,13 @@ Before you start creating your own deployment templates, you should have: [tagge * Add [fault tolerance](ece-ha.md) (high availability) by using more than one availability zone. - :::{image} ../../../images/cloud-enterprise-ece-create-template-availability-zones.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-availability-zones.png :alt: screencapture of the "Availability zones" radio buttons ::: * Add user settings to configure how Elasticsearch and other components run. Check [Editing your user settings](edit-stack-settings.md) for details about what settings are available. - :::{image} ../../../images/cloud-enterprise-ece-create-template-user-settings.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-create-template-user-settings.png :alt: screencapture of the "User settings" expandable section ::: diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-edit.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-edit.md index c12d2ff333..4ffbbcdb0a 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-edit.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-instance-configurations-edit.md @@ -42,7 +42,7 @@ If you edit instance configurations, so that they match fewer allocators, instan For example: Enter `SSD` and `true`, if you tagged your allocators with this tag, or enter whatever tag you are using to identify allocators that can host Elasticsearch data nodes for incoming data. - :::{image} ../../../images/cloud-enterprise-ece-query-ui.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-query-ui.png :alt: Creating a query that filters on allocator tags ::: diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md index 7daf8d1c10..94f676b21b 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-tag-allocators.md @@ -62,7 +62,7 @@ If you have an allocator that meets several criteria, such as an allocator with 4. Enter values into the **Key** and **Value** fields, and then select **Add tag**. For example: You could add `SSD: true` and `highCPU: true` tags from our [example tags](#allocator-sample-tags) if your allocator meets these criteria. - :::{image} ../../../images/cloud-enterprise-ece-tagging-ui.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-tagging-ui.png :alt: Adding key-value pairs as an allocator tags ::: diff --git a/deploy-manage/deploy/cloud-enterprise/ece-networking-prereq.md b/deploy-manage/deploy/cloud-enterprise/ece-networking-prereq.md index fa5ffd550a..2163d56c48 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-networking-prereq.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-networking-prereq.md @@ -21,7 +21,7 @@ For versions 2.4.0 and 2.4.1, IPv6 should remain enabled on any host with the Pr When there are multiple hosts for each role, the inbound networking and ports can be represented by the following diagram: -![ECE networking and ports](../../../images/cloud-enterprise-ece-networking-ports.png "") +![ECE networking and ports](/deploy-manage/images/cloud-enterprise-ece-networking-ports.png "") | **Number** | **Host role** | **Inbound ports** | *Purpose* | | --- | --- | --- | --- | diff --git a/deploy-manage/deploy/cloud-enterprise/identify-deployment-scenario.md b/deploy-manage/deploy/cloud-enterprise/identify-deployment-scenario.md index 45de3ec9ef..e333326ae2 100644 --- a/deploy-manage/deploy/cloud-enterprise/identify-deployment-scenario.md +++ b/deploy-manage/deploy/cloud-enterprise/identify-deployment-scenario.md @@ -18,7 +18,7 @@ The type of deployment is recommended for development, test, and small-scale use * 3 hosts with 128 GB RAM * 3 availability zones -:::{image} ../../../images/cloud-enterprise-ece-pb-3.png +:::{image} /deploy-manage/images/cloud-enterprise-ece-pb-3.png :alt: A small baseline installation with three hosts across three availability zones ::: @@ -42,7 +42,7 @@ This type of deployment is recommended for many production setups. You need: * 3 hosts with 16 GB RAM each for proxies * 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 ::: @@ -65,7 +65,7 @@ This type of deployment is recommended for deployments with significant overall * 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 ::: diff --git a/deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md b/deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md index 2f498d69d7..cad919efd6 100644 --- a/deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md +++ b/deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md @@ -25,7 +25,7 @@ To view the activity for a deployment: 3. Select one of the resource filters to view activity for only that resource type. -:::{image} ../../../images/cloud-enterprise-ec-ce-activity-page.png +:::{image} /deploy-manage/images/cloud-enterprise-ec-ce-activity-page.png :alt: The Activity page ::: diff --git a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md index ea8a242433..6754897313 100644 --- a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md +++ b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md @@ -21,7 +21,7 @@ Using Docker or Podman as container runtime is a configuration local to the host :::: -:::{image} ../../../images/cloud-enterprise-podman-migration-overview-1.png +:::{image} /deploy-manage/images/cloud-enterprise-podman-migration-overview-1.png :alt: Migration Overview ::: @@ -42,13 +42,13 @@ Using Docker or Podman as container runtime is a configuration local to the host **Example 1** You want to migrate the Docker host `192.168.44.74` with the role `Allocator` to a podman host. Copy the role `allocator`. - :::{image} ../../../images/cloud-enterprise-podman-migration-fetch-roles-1.png + :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-1.png :alt: Migrate Allocator ::: **Example 2** You want to migrate the Docker host `192.168.44.10` with the roles `Allocator`, `Controller`, `Director`, and `Proxy` to a podman host. Copy the roles `allocator`, `coordinator`, `director`, `proxy`. - :::{image} ../../../images/cloud-enterprise-podman-migration-fetch-roles-2.png + :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-2.png :alt: Migrate Allocator ::: @@ -423,13 +423,13 @@ Using Docker or Podman as container runtime is a configuration local to the host The following screenshot shows the state where the correct roles have been applied. Both hosts in ece-zone-1 have the same color. - :::{image} ../../../images/cloud-enterprise-podman-migration-correct-role-1.png + :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-correct-role-1.png :alt: Correct role ::: The following screenshot shows the state where incorrect roles have been applied. The hosts in ece-zone-1 do not have the same coloring. - :::{image} ../../../images/cloud-enterprise-podman-migration-wrong-role-1.png + :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-wrong-role-1.png :alt: Wrong role ::: @@ -449,7 +449,7 @@ Using Docker or Podman as container runtime is a configuration local to the host :::: - :::{image} ../../../images/cloud-enterprise-podman-migration-move-instances-1.png + :::{image} /deploy-manage/images/cloud-enterprise-podman-migration-move-instances-1.png :alt: Move instances ::: diff --git a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md index f9b6d6e09a..8c64c747ae 100644 --- a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md +++ b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md @@ -16,7 +16,7 @@ The **Deployments** page in the Cloud UI provides several ways to find deploymen * Search for partial or whole deployment names or IDs in the search text box * Add filters to the **Deployments** view to filter for specific conditions: - :::{image} ../../../images/cloud-enterprise-deployment-filter.png + :::{image} /deploy-manage/images/cloud-enterprise-deployment-filter.png :alt: Add a filter ::: 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 48bb6f4a17..aaa97f0a75 100644 --- a/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md +++ b/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md @@ -323,7 +323,7 @@ To avoid this, explicitly define the requests and limits mandated by your enviro [Metricbeat](beats.md) can collect the percentage of both the CPU and the memory limits used by each Pod (or total node allocatable if resource is not limited). The two relevant metrics are `kubernetes.pod.cpu.usage.limit.pct` for CPU, and `kubernetes.pod.memory.usage.node.pct` for memory. -:::{image} ../../../images/cloud-on-k8s-metrics-explorer-cpu.png +:::{image} /deploy-manage/images/cloud-on-k8s-metrics-explorer-cpu.png :alt: cgroup CPU perforamce chart :screenshot: ::: @@ -353,7 +353,7 @@ nodeSets: The **Cgroup usage** curve shows that the CPU usage of this container has been steadily increasing up to 2 cores. Then, while the container was still requesting more CPU, the **Cgroup Throttling** curve shows how much the Elasticsearch container has been throttled: -:::{image} ../../../images/cloud-on-k8s-cgroups-cfs-stats.png +:::{image} /deploy-manage/images/cloud-on-k8s-cgroups-cfs-stats.png :alt: cgroup CPU perforamce chart :screenshot: ::: 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 60b38581f6..9265b0cf2c 100644 --- a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md @@ -42,13 +42,13 @@ Note the following terms: The following diagram shows the mapping between Microsoft Azure IDs, {{ecloud}} organization IDs, and your Elastic resources (deployments). -:::{image} ../../../images/cloud-ec-azure-billing-mapping.png +:::{image} /deploy-manage/images/cloud-ec-azure-billing-mapping.png :alt: Azure to {{ecloud}} mappings ::: The following diagram shows how your {{ecloud}} organization costs are reported in Microsoft Azure. You can also refer to our [Billing FAQ](#ec-azure-integration-billing-faq) on this page. -:::{image} ../../../images/cloud-ec-azure-billing-reporting.png +:::{image} /deploy-manage/images/cloud-ec-azure-billing-reporting.png :alt: Azure to {{ecloud}} mappings ::: @@ -156,13 +156,13 @@ $$$azure-integration-change-subscription$$$How can I change my {{ecloud}} subscr 3. In the {{ecloud}} console, select your account avatar icon at the top of the page, and then choose **Account & Billing**. 4. Select the **Billing** tab and choose **Change my subscription**. - :::{image} ../../../images/cloud-ec-marketplace-azure009.png + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure009.png :alt: The Elastic Account Billing page with Advanced Settings highlighted ::: 5. Select the [subscription level](https://elastic.co/pricing) that you’d like. - :::{image} ../../../images/cloud-ec-marketplace-azure006.png + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure006.png :alt: The Update Subscription page showing Standard ::: @@ -175,7 +175,7 @@ $$$azure-integration-azure-user-management$$$Is the {{ecloud}} Azure Native ISV 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 + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure026.png :alt: Error message displayed in the {{ecloud}} console: To access the resource {resource-name} ::: @@ -278,7 +278,7 @@ $$$azure-integration-billing-elastic-costs$$$Why can’t I see Elastic resources $$$azure-integration-billing-deployments$$$Why don’t I see my individual Elastic resources (deployments) in the Azure Marketplace Invoice? : The way Azure Marketplace Billing Integration works today, the costs for Elastic resources (deployments) are reported for an {{ecloud}} organization as a single line item, reported against the Marketplace SaaS ID. This includes the Elastic deployments created using the Azure Portal, API, SDK, or CLI, and also the Elastic deployments created directly from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) in the respective {{ecloud}} organization. For granular Elastic resources costs refer to [Monitor and analyze your acccount usage](../../cloud-organization/billing/monitor-analyze-usage.md). As well, for more detail refer to [Integrated billing](#ec-azure-integration-billing-summary). - :::{image} ../../../images/cloud-ec-azure-billing-example.png + :::{image} /deploy-manage/images/cloud-ec-azure-billing-example.png :alt: Example billing report in the {{ecloud}} console ::: @@ -290,7 +290,7 @@ $$$azure-integration-billing-instance-values$$$Why can’t I find Instance ID an `Microsoft.SaaS` (Instance name) asset is shown in the Azure Marketplace invoice and represents costs related to an {{ecloud}} organization and not individual Elastic resources (deployments). To see the cost breakdown for individual Elastic resources (deployments), refer to [Monitor and analyze your acccount usage](../../cloud-organization/billing/monitor-analyze-usage.md). - :::{image} ../../../images/cloud-ec-azure-missing-instance-id.png + :::{image} /deploy-manage/images/cloud-ec-azure-missing-instance-id.png :alt: Instance ID not found error in Azure console ::: @@ -373,7 +373,7 @@ In the Azure console, configure the ingestion of Azure logs into either a new or * When creating a new deployment, use the **Logs & metrics** tab in Azure to specify the log type and a key/value tag pair. Any Azure resources that match on the tag value automatically send log data to the {{ecloud}} deployment, once it’s been created. -:::{image} ../../../images/cloud-ec-marketplace-azure004.png +:::{image} /deploy-manage/images/cloud-ec-marketplace-azure004.png :alt: The Logs & Metrics tab on the Create Elastic Resource page ::: @@ -409,7 +409,7 @@ $$$azure-integration-ingest-metrics$$$How do I ingest metrics from my Azure serv $$$azure-integration-vm-extensions$$$How can I monitor my Azure virtual machines in {{es}}? : You can monitor your Azure virtual machines by installing the Elastic Agent VM extension. Once enabled, the VM extension downloads the Elastic Agent, installs it, and enrols it to the Fleet Server. The Elastic Agent will then send system related logs and metrics to the {{ecloud}} cluster where you can find pre-built system dashboards showing the health and performance of your virtual machines. - :::{image} ../../../images/cloud-ec-marketplace-azure010.png + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure010.png :alt: A dashboard showing system metrics for the VM ::: @@ -422,7 +422,7 @@ $$$azure-integration-vm-extensions$$$How can I monitor my Azure virtual machines 3. Select one or more virtual machines 4. Choose **Install Extension** or **Uninstall Extension**. - :::{image} ../../../images/cloud-ec-marketplace-azure011.png + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure011.png :alt: The Virtual Machines page in Azure ::: @@ -454,7 +454,7 @@ This section describes some scenarios that you may experience onboarding to {{ec $$$azure-integration-authorization-access$$$I receive an error message about not having the required authorization. : When trying to access {{ecloud}} resources, you may get an error message indicating that *the user must have the required authorization.* - :::{image} ../../../images/cloud-ec-marketplace-azure026.png + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure026.png :alt: Error message displayed in the {{ecloud}} console: To access the resource {resource-name} ::: @@ -484,7 +484,7 @@ $$$azure-integration-deployment-failed-traffic-filter$$$My {{ecloud}} deployment 2. Go to the [Traffic filters page](https://cloud.elastic.co/deployment-features/traffic-filters). 3. Edit the traffic filter and disable the **Include by default** option. - :::{image} ../../../images/cloud-ec-marketplace-azure-traffic-filter-option.png + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure-traffic-filter-option.png :alt: The Include by default option under Add to Deployments on the Traffic Filter page ::: @@ -525,7 +525,7 @@ $$$azure-integration-support$$$How do I get support? The Elastic Support team responds based on the SLA response time of your subscription. - :::{image} ../../../images/cloud-ec-marketplace-azure005.png + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure005.png :alt: The New Support Request page in Azure ::: diff --git a/deploy-manage/deploy/elastic-cloud/cloud-hosted.md b/deploy-manage/deploy/elastic-cloud/cloud-hosted.md index 498bfefb5d..b1445c4608 100644 --- a/deploy-manage/deploy/elastic-cloud/cloud-hosted.md +++ b/deploy-manage/deploy/elastic-cloud/cloud-hosted.md @@ -77,7 +77,7 @@ You can use these presets, or start from them to get the unique configuration yo Building a rich search experience, gaining actionable insight into your environment, or protecting your systems and endpoints? You can implement each of these major use cases, and more, with the solutions that are pre-built in each Elastic deployment. -:::{image} ../../../images/cloud-ec-stack-components.png +:::{image} /deploy-manage/images/cloud-ec-stack-components.png :alt: Elastic Stack components and solutions with Enterprise Search :width: 75% ::: diff --git a/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md b/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md index b64a23782c..6f3634538f 100644 --- a/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md +++ b/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md @@ -19,7 +19,7 @@ You can also create a deployment using the [Elastic Cloud API](https://www.elast 1. Log in to your [cloud.elastic.co](https://cloud.elastic.co/login) account and select **Create deployment** from the {{ecloud}} main page: - :::{image} ../../../images/cloud-ec-login-first-deployment.png + :::{image} /deploy-manage/images/cloud-ec-login-first-deployment.png :alt: Log in to create a deployment ::: @@ -29,7 +29,7 @@ You can also create a deployment using the [Elastic Cloud API](https://www.elast 1. From the main **Settings**, you can change the cloud provider and region that host your deployment, the stack version, and the hardware profile, or restore data from another deployment (**Restore snapshot data**): - :::{image} ../../../images/cloud-ec-create-deployment.png + :::{image} /deploy-manage/images/cloud-ec-create-deployment.png :alt: Create deployment :width: 50% ::: @@ -57,7 +57,7 @@ You can also create a deployment using the [Elastic Cloud API](https://www.elast At any time, you can manage and [adjust the configuration](configure.md) of your deployment to your needs, add extra layers of [security](../../users-roles/cluster-or-deployment-auth.md), or (highly recommended) set up [health monitoring](../../monitor/stack-monitoring.md). - :::{image} ../../../images/cloud-ec-deployment-mainpage.png + :::{image} /deploy-manage/images/cloud-ec-deployment-mainpage.png :alt: ESS Deployment main page ::: diff --git a/deploy-manage/deploy/elastic-cloud/create-monthly-pay-as-you-go-subscription-on-aws-marketplace.md b/deploy-manage/deploy/elastic-cloud/create-monthly-pay-as-you-go-subscription-on-aws-marketplace.md index 0c09773676..f8cb7ab87f 100644 --- a/deploy-manage/deploy/elastic-cloud/create-monthly-pay-as-you-go-subscription-on-aws-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/create-monthly-pay-as-you-go-subscription-on-aws-marketplace.md @@ -15,13 +15,13 @@ When subscribing to an annual prepaid subscription to Elastic Cloud on AWS Marke 2. Go to the [AWS Marketplace subscription page for Elastic Cloud pay-as-you-go](https://aws.amazon.com/marketplace/saas/ordering?productId=bb253a6c-e775-4634-bdf0-17bd56a69c36&offerId=b2uzdkwqj7177fqhm39o4snxy). 3. Click **Subscribe** to create an AWS Marketplace subscription under the selected AWS Account. -:::{image} ../../../images/cloud-aws-subscribe-button.png +:::{image} /deploy-manage/images/cloud-aws-subscribe-button.png :alt: Subscribe to Elastic Cloud on AWS Marketplace ::: No further steps required in AWS. Ignore the steps 1 to 3 that appear on the right side of the AWS page. -:::{image} ../../../images/cloud-aws-mp-steps-to-skip.png +:::{image} /deploy-manage/images/cloud-aws-mp-steps-to-skip.png :alt: AWS panel with steps to skip ::: @@ -29,6 +29,6 @@ You should now see the monthly *Pay as you go* subscription for Elastic Cloud in From the top-right corner, you can check that the Account ID is the same account that has your Elastic Cloud annual subscription. -:::{image} ../../../images/cloud-aws-mp-manage-subscriptions.png +:::{image} /deploy-manage/images/cloud-aws-mp-manage-subscriptions.png :alt: Account ID on top-right menu ::: diff --git a/deploy-manage/deploy/elastic-cloud/ec-change-hardware-profile.md b/deploy-manage/deploy/elastic-cloud/ec-change-hardware-profile.md index 3f60e13ef7..35ba6ff1a0 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-change-hardware-profile.md +++ b/deploy-manage/deploy/elastic-cloud/ec-change-hardware-profile.md @@ -28,20 +28,20 @@ Note that if there’s no indication that a newer version is available, that mea 1. On the deployment overview page, next to your current hardware profile where there is indication of a newer available version, select **Edit**. - :::{image} ../../../images/cloud-ec-new-hardware-profile-version.png + :::{image} /deploy-manage/images/cloud-ec-new-hardware-profile-version.png :alt: Badge indicating new hardware profile version :width: 50% ::: 2. Preview the changes for the new hardware profile version. - :::{image} ../../../images/cloud-ec-preview-hardware-profile.png + :::{image} /deploy-manage/images/cloud-ec-preview-hardware-profile.png :alt: Notification showing that a new profile version is there ::: The configuration screen summarizes hardware changes for each component of your deployment. - :::{image} ../../../images/cloud-ec-preview-profile-changes.png + :::{image} /deploy-manage/images/cloud-ec-preview-profile-changes.png :alt: Preview of the changes between the 2 versions of the hardware profile ::: @@ -55,7 +55,7 @@ When the current hardware profile of your deployment isn’t the most optimal on 1. On the deployment overview page, next to your current hardware profile, select **Edit**. 2. Select the hardware profile you wish to change to. The configuration screen summarizes hardware changes for each component of your deployment. - :::{image} ../../../images/cloud-ec-preview-different-profile-changes.png + :::{image} /deploy-manage/images/cloud-ec-preview-different-profile-changes.png :alt: Preview of the changes between the 2 hardware profiles ::: 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 049adc7ae2..b315b58e20 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md @@ -23,7 +23,7 @@ Depending upon how much data you have and what queries you plan to run, you need To change a cluster’s topology, from deployment management, select **Edit deployment** from the **Actions** dropdown. Next, select a storage and RAM setting from the **Size per zone** drop-down list, and save your changes. When downsizing the cluster, make sure to have enough resources to handle the current load, otherwise your cluster will be under stress. -:::{image} ../../../images/cloud-ec-capacity.png +:::{image} /deploy-manage/images/cloud-ec-capacity.png :alt: Capacity slider to adjust {{es}} cluster size ::: @@ -50,7 +50,7 @@ We recommend using at least 4GB RAM for dedicated master nodes. High availability is achieved by running a cluster with replicas in multiple data centers (availability zones), to prevent against downtime when infrastructure problems occur or when resizing or upgrading deployments. We offer the options of running in one, two, or three data centers. -:::{image} ../../../images/cloud-ec-fault-tolerance.png +:::{image} /deploy-manage/images/cloud-ec-fault-tolerance.png :alt: High availability features ::: @@ -72,7 +72,7 @@ The node capacity you choose is per data center. The reason for this is that the You can review your {{es}} shard activity from the {{ecloud}} Console. When viewing a hosted deployment details, at the bottom of the {{es}} page, you can hover over each part of the shard visualization for specific numbers. -:::{image} ../../../images/cloud-ec-shard-activity.gif +:::{image} /deploy-manage/images/cloud-ec-shard-activity.gif :alt: Shard activity ::: diff --git a/deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance.md b/deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance.md index 2ee9ecc31b..80ef20a82d 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance.md +++ b/deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance.md @@ -42,7 +42,7 @@ For more information, check [{{ech}} default provider instance configurations](c You can check the **Monitoring > Performance > CPU Credits** section of the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), and find the related metrics: -:::{image} /images/cloud-metrics-credits.png +:::{image} /deploy-manage/images/cloud-metrics-credits.png :alt: CPU usage versus CPU credits over time ::: diff --git a/deploy-manage/deploy/elastic-cloud/ech-getting-started-accessing.md b/deploy-manage/deploy/elastic-cloud/ech-getting-started-accessing.md index c29dd4b0b2..08b70d28b6 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-getting-started-accessing.md +++ b/deploy-manage/deploy/elastic-cloud/ech-getting-started-accessing.md @@ -7,7 +7,7 @@ mapped_pages: You use the console to manage your cluster from a web browser. Tasks that are available from the console include upgrading versions, configuring security features, working with custom plugins, and more. -:::{image} ../../../images/cloud-heroku-ech-console.png +:::{image} /deploy-manage/images/cloud-heroku-ech-console.png :alt: [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) ::: diff --git a/deploy-manage/deploy/elastic-cloud/ech-reference-hardware.md b/deploy-manage/deploy/elastic-cloud/ech-reference-hardware.md index f62ed513f1..75c00e5e73 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-reference-hardware.md +++ b/deploy-manage/deploy/elastic-cloud/ech-reference-hardware.md @@ -5,7 +5,7 @@ mapped_pages: # Elasticsearch Add-On for Heroku hardware [ech-reference-hardware] -:::{image} ../../../images/cloud-heroku-ec-cloud-platform-hardware.png +:::{image} /deploy-manage/images/cloud-heroku-ec-cloud-platform-hardware.png :alt: A banner showing a plane trailing several stylized UI sliders superimposed over cloud hardware ::: diff --git a/deploy-manage/deploy/elastic-cloud/find-cloud-id.md b/deploy-manage/deploy/elastic-cloud/find-cloud-id.md index d90ac0a7a5..888122007c 100644 --- a/deploy-manage/deploy/elastic-cloud/find-cloud-id.md +++ b/deploy-manage/deploy/elastic-cloud/find-cloud-id.md @@ -10,7 +10,7 @@ mapped_pages: The Cloud ID reduces the number of steps required to start sending data from Beats or Logstash to your hosted Elasticsearch cluster on {{ecloud}}. Because we made it easier to send data, you can start exploring visualizations in Kibana on {{ecloud}} that much more quickly. -:::{image} ../../../images/cloud-ec-ce-cloud-id-beats-logstash.png +:::{image} /deploy-manage/images/cloud-ec-ce-cloud-id-beats-logstash.png :alt: Exploring data from Beats or Logstash in Kibana after sending it to a hosted Elasticsearch cluster ::: @@ -18,7 +18,7 @@ The Cloud ID works by assigning a unique ID to your hosted Elasticsearch cluster You include your Cloud ID along with your {{ecloud}} user credentials (defined in `cloud.auth`) when you run Beats or Logstash locally, and then let {{ecloud}} handle all of the remaining connection details to send the data to your hosted cluster on {{ecloud}} safely and securely. -:::{image} ../../../images/cloud-ec-ce-cloud-id.png +:::{image} /deploy-manage/images/cloud-ec-ce-cloud-id.png :alt: The Cloud ID and `elastic` user information shown when you create a deployment ::: diff --git a/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md b/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md index 683739130c..37f86fe418 100644 --- a/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md +++ b/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md @@ -35,7 +35,7 @@ To view the activity for a deployment: 3. Select one of the resource filters to view activity for only that resource type. -:::{image} ../../../images/cloud-ec-ce-activity-page.png +:::{image} /deploy-manage/images/cloud-ec-ce-activity-page.png :alt: The Activity page ::: diff --git a/deploy-manage/distributed-architecture/reading-and-writing-documents.md b/deploy-manage/distributed-architecture/reading-and-writing-documents.md index 1ae4c0fa64..10220a5e77 100644 --- a/deploy-manage/distributed-architecture/reading-and-writing-documents.md +++ b/deploy-manage/distributed-architecture/reading-and-writing-documents.md @@ -20,7 +20,7 @@ This purpose of this section is to give a high level overview of the Elasticsear Every indexing operation in Elasticsearch is first resolved to a replication group using [routing](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-create), typically based on the document ID. Once the replication group has been determined, the operation is forwarded internally to the current *primary shard* of the group. This stage of indexing is referred to as the *coordinating stage*. -:::{image} ../../images/elasticsearch-reference-data_processing_flow.png +:::{image} /deploy-manage/images/elasticsearch-reference-data_processing_flow.png :alt: An example of a basic write model. ::: diff --git a/deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/shard-allocation-awareness.md b/deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/shard-allocation-awareness.md index 955cd3f8c6..6a6516c14e 100644 --- a/deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/shard-allocation-awareness.md +++ b/deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/shard-allocation-awareness.md @@ -65,14 +65,14 @@ To enable shard allocation awareness: With this example configuration, if you start two nodes with `node.attr.rack_id` set to `rack_one` and create an index with 5 primary shards and 1 replica of each primary, all primaries and replicas are allocated across the two node. -:::{image} ../../../images/elasticsearch-reference-shard-allocation-awareness-one-rack.png +:::{image} /deploy-manage/images/elasticsearch-reference-shard-allocation-awareness-one-rack.png :alt: All primaries and replicas are allocated across two nodes in the same rack :title: All primaries and replicas allocated across two nodes in the same rack ::: If you add two nodes with `node.attr.rack_id` set to `rack_two`, {{es}} moves shards to the new nodes, ensuring (if possible) that no two copies of the same shard are in the same rack. -:::{image} ../../../images/elasticsearch-reference-shard-allocation-awareness-two-racks.png +:::{image} /deploy-manage/images/elasticsearch-reference-shard-allocation-awareness-two-racks.png :alt: Primaries and replicas are allocated across four nodes in two racks with no two copies of the same shard in the same rack :title: Primaries and replicas allocated across four nodes in two racks, with no two copies of the same shard in the same rack ::: diff --git a/deploy-manage/images/cloud-autoops-deployment-info.png b/deploy-manage/images/cloud-autoops-deployment-info.png new file mode 100644 index 0000000000..1d5109d970 Binary files /dev/null and b/deploy-manage/images/cloud-autoops-deployment-info.png differ diff --git a/deploy-manage/images/cloud-autoops-deployment-performance.png b/deploy-manage/images/cloud-autoops-deployment-performance.png new file mode 100644 index 0000000000..8891cc035c Binary files /dev/null and b/deploy-manage/images/cloud-autoops-deployment-performance.png differ diff --git a/deploy-manage/images/cloud-autoops-deployment-view.png b/deploy-manage/images/cloud-autoops-deployment-view.png new file mode 100644 index 0000000000..d38e57dbf9 Binary files /dev/null and b/deploy-manage/images/cloud-autoops-deployment-view.png differ diff --git a/deploy-manage/images/cloud-autoops-dismiss-events.png b/deploy-manage/images/cloud-autoops-dismiss-events.png new file mode 100644 index 0000000000..6849ad54bd Binary files /dev/null and b/deploy-manage/images/cloud-autoops-dismiss-events.png differ diff --git a/deploy-manage/images/cloud-autoops-event-settings.png b/deploy-manage/images/cloud-autoops-event-settings.png new file mode 100644 index 0000000000..04bcff2621 Binary files /dev/null and b/deploy-manage/images/cloud-autoops-event-settings.png differ diff --git a/deploy-manage/images/cloud-autoops-events-settings-report.png b/deploy-manage/images/cloud-autoops-events-settings-report.png new file mode 100644 index 0000000000..a151135a25 Binary files /dev/null and b/deploy-manage/images/cloud-autoops-events-settings-report.png differ diff --git a/deploy-manage/images/cloud-autoops-events.png b/deploy-manage/images/cloud-autoops-events.png new file mode 100644 index 0000000000..23612c6f1e Binary files /dev/null and b/deploy-manage/images/cloud-autoops-events.png differ diff --git a/deploy-manage/images/cloud-autoops-how-to-access.png b/deploy-manage/images/cloud-autoops-how-to-access.png new file mode 100644 index 0000000000..f629a121fa Binary files /dev/null and b/deploy-manage/images/cloud-autoops-how-to-access.png differ diff --git a/deploy-manage/images/cloud-autoops-index-view.png b/deploy-manage/images/cloud-autoops-index-view.png new file mode 100644 index 0000000000..dde77e24eb Binary files /dev/null and b/deploy-manage/images/cloud-autoops-index-view.png differ diff --git a/deploy-manage/images/cloud-autoops-node-view.png b/deploy-manage/images/cloud-autoops-node-view.png new file mode 100644 index 0000000000..4b36ad069d Binary files /dev/null and b/deploy-manage/images/cloud-autoops-node-view.png differ diff --git a/deploy-manage/images/cloud-autoops-notification-status.png b/deploy-manage/images/cloud-autoops-notification-status.png new file mode 100644 index 0000000000..456abe9d3a Binary files /dev/null and b/deploy-manage/images/cloud-autoops-notification-status.png differ diff --git a/deploy-manage/images/cloud-autoops-notifications-report.png b/deploy-manage/images/cloud-autoops-notifications-report.png new file mode 100644 index 0000000000..474a0a9d31 Binary files /dev/null and b/deploy-manage/images/cloud-autoops-notifications-report.png differ diff --git a/deploy-manage/images/cloud-autoops-overview-page.png b/deploy-manage/images/cloud-autoops-overview-page.png new file mode 100644 index 0000000000..d98e22688f Binary files /dev/null and b/deploy-manage/images/cloud-autoops-overview-page.png differ diff --git a/deploy-manage/images/cloud-autoops-shard-view.png b/deploy-manage/images/cloud-autoops-shard-view.png new file mode 100644 index 0000000000..6c2a08279c Binary files /dev/null and b/deploy-manage/images/cloud-autoops-shard-view.png differ diff --git a/deploy-manage/images/cloud-autoops-template-optimizer.png b/deploy-manage/images/cloud-autoops-template-optimizer.png new file mode 100644 index 0000000000..915e7d4bde Binary files /dev/null and b/deploy-manage/images/cloud-autoops-template-optimizer.png differ diff --git a/deploy-manage/images/cloud-aws-mp-manage-subscriptions.png b/deploy-manage/images/cloud-aws-mp-manage-subscriptions.png new file mode 100644 index 0000000000..d20bc0ed88 Binary files /dev/null and b/deploy-manage/images/cloud-aws-mp-manage-subscriptions.png differ diff --git a/deploy-manage/images/cloud-aws-mp-steps-to-skip.png b/deploy-manage/images/cloud-aws-mp-steps-to-skip.png new file mode 100644 index 0000000000..daccd94e79 Binary files /dev/null and b/deploy-manage/images/cloud-aws-mp-steps-to-skip.png differ diff --git a/deploy-manage/images/cloud-aws-subscribe-button.png b/deploy-manage/images/cloud-aws-subscribe-button.png new file mode 100644 index 0000000000..de50ff0201 Binary files /dev/null and b/deploy-manage/images/cloud-aws-subscribe-button.png differ diff --git a/deploy-manage/images/cloud-ce-azure-inter-region-pl.png b/deploy-manage/images/cloud-ce-azure-inter-region-pl.png new file mode 100644 index 0000000000..cebd0c155e Binary files /dev/null and b/deploy-manage/images/cloud-ce-azure-inter-region-pl.png differ diff --git a/deploy-manage/images/cloud-ce-copy-remote-cluster-parameters.png b/deploy-manage/images/cloud-ce-copy-remote-cluster-parameters.png new file mode 100644 index 0000000000..325cf37509 Binary files /dev/null and b/deploy-manage/images/cloud-ce-copy-remote-cluster-parameters.png differ diff --git a/deploy-manage/images/cloud-delete-trust-environment.png b/deploy-manage/images/cloud-delete-trust-environment.png new file mode 100644 index 0000000000..a376e85672 Binary files /dev/null and b/deploy-manage/images/cloud-delete-trust-environment.png differ diff --git a/deploy-manage/images/cloud-ec-account-trust-management.png b/deploy-manage/images/cloud-ec-account-trust-management.png new file mode 100644 index 0000000000..7447a1e201 Binary files /dev/null and b/deploy-manage/images/cloud-ec-account-trust-management.png differ diff --git a/deploy-manage/images/cloud-ec-azure-billing-example.png b/deploy-manage/images/cloud-ec-azure-billing-example.png new file mode 100644 index 0000000000..c6e30253dd Binary files /dev/null and b/deploy-manage/images/cloud-ec-azure-billing-example.png differ diff --git a/deploy-manage/images/cloud-ec-azure-billing-mapping.png b/deploy-manage/images/cloud-ec-azure-billing-mapping.png new file mode 100644 index 0000000000..b61a266022 Binary files /dev/null and b/deploy-manage/images/cloud-ec-azure-billing-mapping.png differ diff --git a/deploy-manage/images/cloud-ec-azure-billing-reporting.png b/deploy-manage/images/cloud-ec-azure-billing-reporting.png new file mode 100644 index 0000000000..3ed186194f Binary files /dev/null and b/deploy-manage/images/cloud-ec-azure-billing-reporting.png differ diff --git a/deploy-manage/images/cloud-ec-azure-missing-instance-id.png b/deploy-manage/images/cloud-ec-azure-missing-instance-id.png new file mode 100644 index 0000000000..907a388d58 Binary files /dev/null and b/deploy-manage/images/cloud-ec-azure-missing-instance-id.png differ diff --git a/deploy-manage/images/cloud-ec-bill-example-new.png b/deploy-manage/images/cloud-ec-bill-example-new.png new file mode 100644 index 0000000000..e1c56dbef1 Binary files /dev/null and b/deploy-manage/images/cloud-ec-bill-example-new.png differ diff --git a/deploy-manage/images/cloud-ec-capacity.png b/deploy-manage/images/cloud-ec-capacity.png new file mode 100644 index 0000000000..89ea09316c Binary files /dev/null and b/deploy-manage/images/cloud-ec-capacity.png differ diff --git a/deploy-manage/images/cloud-ec-ce-activity-page.png b/deploy-manage/images/cloud-ec-ce-activity-page.png new file mode 100644 index 0000000000..7fa6d5bd28 Binary files /dev/null and b/deploy-manage/images/cloud-ec-ce-activity-page.png differ diff --git a/deploy-manage/images/cloud-ec-ce-cloud-id-beats-logstash.png b/deploy-manage/images/cloud-ec-ce-cloud-id-beats-logstash.png new file mode 100644 index 0000000000..f0e2dff207 Binary files /dev/null and b/deploy-manage/images/cloud-ec-ce-cloud-id-beats-logstash.png differ diff --git a/deploy-manage/images/cloud-ec-ce-cloud-id.png b/deploy-manage/images/cloud-ec-ce-cloud-id.png new file mode 100644 index 0000000000..a42e5601f2 Binary files /dev/null and b/deploy-manage/images/cloud-ec-ce-cloud-id.png differ diff --git a/deploy-manage/images/cloud-ec-create-deployment.png b/deploy-manage/images/cloud-ec-create-deployment.png new file mode 100644 index 0000000000..58ee5e8caf Binary files /dev/null and b/deploy-manage/images/cloud-ec-create-deployment.png differ diff --git a/deploy-manage/images/cloud-ec-create-from-snapshot-updated.png b/deploy-manage/images/cloud-ec-create-from-snapshot-updated.png new file mode 100644 index 0000000000..dbc7aacc01 Binary files /dev/null and b/deploy-manage/images/cloud-ec-create-from-snapshot-updated.png differ diff --git a/deploy-manage/images/cloud-ec-deployment-mainpage.png b/deploy-manage/images/cloud-ec-deployment-mainpage.png new file mode 100644 index 0000000000..10aa5cdf74 Binary files /dev/null and b/deploy-manage/images/cloud-ec-deployment-mainpage.png differ diff --git a/deploy-manage/images/cloud-ec-elasticsearch-snapshots-of-other-deployments-aws-gcp.png b/deploy-manage/images/cloud-ec-elasticsearch-snapshots-of-other-deployments-aws-gcp.png new file mode 100644 index 0000000000..c6855cd80a Binary files /dev/null and b/deploy-manage/images/cloud-ec-elasticsearch-snapshots-of-other-deployments-aws-gcp.png differ diff --git a/deploy-manage/images/cloud-ec-elasticsearch-snapshots-of-other-deployments.png b/deploy-manage/images/cloud-ec-elasticsearch-snapshots-of-other-deployments.png new file mode 100644 index 0000000000..e148ecea01 Binary files /dev/null and b/deploy-manage/images/cloud-ec-elasticsearch-snapshots-of-other-deployments.png differ diff --git a/deploy-manage/images/cloud-ec-fault-tolerance.png b/deploy-manage/images/cloud-ec-fault-tolerance.png new file mode 100644 index 0000000000..40d0c18c49 Binary files /dev/null and b/deploy-manage/images/cloud-ec-fault-tolerance.png differ diff --git a/deploy-manage/images/cloud-ec-login-first-deployment.png b/deploy-manage/images/cloud-ec-login-first-deployment.png new file mode 100644 index 0000000000..b269169d75 Binary files /dev/null and b/deploy-manage/images/cloud-ec-login-first-deployment.png differ diff --git a/deploy-manage/images/cloud-ec-marketplace-azure-traffic-filter-option.png b/deploy-manage/images/cloud-ec-marketplace-azure-traffic-filter-option.png new file mode 100644 index 0000000000..ca20c034cd Binary files /dev/null and b/deploy-manage/images/cloud-ec-marketplace-azure-traffic-filter-option.png differ diff --git a/deploy-manage/images/cloud-ec-marketplace-azure004.png b/deploy-manage/images/cloud-ec-marketplace-azure004.png new file mode 100644 index 0000000000..7cd144feaa Binary files /dev/null and b/deploy-manage/images/cloud-ec-marketplace-azure004.png differ diff --git a/deploy-manage/images/cloud-ec-marketplace-azure005.png b/deploy-manage/images/cloud-ec-marketplace-azure005.png new file mode 100644 index 0000000000..048e2e4691 Binary files /dev/null and b/deploy-manage/images/cloud-ec-marketplace-azure005.png differ diff --git a/deploy-manage/images/cloud-ec-marketplace-azure006.png b/deploy-manage/images/cloud-ec-marketplace-azure006.png new file mode 100644 index 0000000000..320d9c7367 Binary files /dev/null and b/deploy-manage/images/cloud-ec-marketplace-azure006.png differ diff --git a/deploy-manage/images/cloud-ec-marketplace-azure009.png b/deploy-manage/images/cloud-ec-marketplace-azure009.png new file mode 100644 index 0000000000..ea7befffbb Binary files /dev/null and b/deploy-manage/images/cloud-ec-marketplace-azure009.png differ diff --git a/deploy-manage/images/cloud-ec-marketplace-azure010.png b/deploy-manage/images/cloud-ec-marketplace-azure010.png new file mode 100644 index 0000000000..49f0237159 Binary files /dev/null and b/deploy-manage/images/cloud-ec-marketplace-azure010.png differ diff --git a/deploy-manage/images/cloud-ec-marketplace-azure011.png b/deploy-manage/images/cloud-ec-marketplace-azure011.png new file mode 100644 index 0000000000..5cca34e747 Binary files /dev/null and b/deploy-manage/images/cloud-ec-marketplace-azure011.png differ diff --git a/deploy-manage/images/cloud-ec-marketplace-azure026.png b/deploy-manage/images/cloud-ec-marketplace-azure026.png new file mode 100644 index 0000000000..a880eef034 Binary files /dev/null and b/deploy-manage/images/cloud-ec-marketplace-azure026.png differ diff --git a/deploy-manage/images/cloud-ec-migrate-deployment-template(2).png b/deploy-manage/images/cloud-ec-migrate-deployment-template(2).png new file mode 100644 index 0000000000..518a93287f Binary files /dev/null and b/deploy-manage/images/cloud-ec-migrate-deployment-template(2).png differ diff --git a/deploy-manage/images/cloud-ec-new-hardware-profile-version.png b/deploy-manage/images/cloud-ec-new-hardware-profile-version.png new file mode 100644 index 0000000000..bc9f4792c1 Binary files /dev/null and b/deploy-manage/images/cloud-ec-new-hardware-profile-version.png differ diff --git a/deploy-manage/images/cloud-ec-oidc-endpoints-azure.png b/deploy-manage/images/cloud-ec-oidc-endpoints-azure.png new file mode 100644 index 0000000000..540c496186 Binary files /dev/null and b/deploy-manage/images/cloud-ec-oidc-endpoints-azure.png differ diff --git a/deploy-manage/images/cloud-ec-oidc-new-app-azure.png b/deploy-manage/images/cloud-ec-oidc-new-app-azure.png new file mode 100644 index 0000000000..094f418a34 Binary files /dev/null and b/deploy-manage/images/cloud-ec-oidc-new-app-azure.png differ diff --git a/deploy-manage/images/cloud-ec-oidc-new-app-okta.png b/deploy-manage/images/cloud-ec-oidc-new-app-okta.png new file mode 100644 index 0000000000..cfce07abef Binary files /dev/null and b/deploy-manage/images/cloud-ec-oidc-new-app-okta.png differ diff --git a/deploy-manage/images/cloud-ec-oidc-oauth-create-credentials-azure.png b/deploy-manage/images/cloud-ec-oidc-oauth-create-credentials-azure.png new file mode 100644 index 0000000000..461132d525 Binary files /dev/null and b/deploy-manage/images/cloud-ec-oidc-oauth-create-credentials-azure.png differ diff --git a/deploy-manage/images/cloud-ec-oidc-oauth-create-credentials-google.png b/deploy-manage/images/cloud-ec-oidc-oauth-create-credentials-google.png new file mode 100644 index 0000000000..5902ab224e Binary files /dev/null and b/deploy-manage/images/cloud-ec-oidc-oauth-create-credentials-google.png differ diff --git a/deploy-manage/images/cloud-ec-preview-different-profile-changes.png b/deploy-manage/images/cloud-ec-preview-different-profile-changes.png new file mode 100644 index 0000000000..6eee388f1a Binary files /dev/null and b/deploy-manage/images/cloud-ec-preview-different-profile-changes.png differ diff --git a/deploy-manage/images/cloud-ec-preview-hardware-profile.png b/deploy-manage/images/cloud-ec-preview-hardware-profile.png new file mode 100644 index 0000000000..ebc4fa9775 Binary files /dev/null and b/deploy-manage/images/cloud-ec-preview-hardware-profile.png differ diff --git a/deploy-manage/images/cloud-ec-preview-profile-changes.png b/deploy-manage/images/cloud-ec-preview-profile-changes.png new file mode 100644 index 0000000000..5e3e242f0b Binary files /dev/null and b/deploy-manage/images/cloud-ec-preview-profile-changes.png differ diff --git a/deploy-manage/images/cloud-ec-private-link-azure-json-view.png b/deploy-manage/images/cloud-ec-private-link-azure-json-view.png new file mode 100644 index 0000000000..3dbcd414af Binary files /dev/null and b/deploy-manage/images/cloud-ec-private-link-azure-json-view.png differ diff --git a/deploy-manage/images/cloud-ec-private-link-azure-properties.png b/deploy-manage/images/cloud-ec-private-link-azure-properties.png new file mode 100644 index 0000000000..099aa0f05a Binary files /dev/null and b/deploy-manage/images/cloud-ec-private-link-azure-properties.png differ diff --git a/deploy-manage/images/cloud-ec-private-link-cname.png b/deploy-manage/images/cloud-ec-private-link-cname.png new file mode 100644 index 0000000000..0830e977e8 Binary files /dev/null and b/deploy-manage/images/cloud-ec-private-link-cname.png differ diff --git a/deploy-manage/images/cloud-ec-private-link-endpoint-id.png b/deploy-manage/images/cloud-ec-private-link-endpoint-id.png new file mode 100644 index 0000000000..94288d95d7 Binary files /dev/null and b/deploy-manage/images/cloud-ec-private-link-endpoint-id.png differ diff --git a/deploy-manage/images/cloud-ec-private-link-private-hosted-zone-example.png b/deploy-manage/images/cloud-ec-private-link-private-hosted-zone-example.png new file mode 100644 index 0000000000..aff9c990a6 Binary files /dev/null and b/deploy-manage/images/cloud-ec-private-link-private-hosted-zone-example.png differ diff --git a/deploy-manage/images/cloud-ec-private-link-service.png b/deploy-manage/images/cloud-ec-private-link-service.png new file mode 100644 index 0000000000..965fd891a7 Binary files /dev/null and b/deploy-manage/images/cloud-ec-private-link-service.png differ diff --git a/deploy-manage/images/cloud-ec-saml-azuread-create-app.png b/deploy-manage/images/cloud-ec-saml-azuread-create-app.png new file mode 100644 index 0000000000..d18a477bac Binary files /dev/null and b/deploy-manage/images/cloud-ec-saml-azuread-create-app.png differ diff --git a/deploy-manage/images/cloud-ec-saml-azuread-kibana-config.png b/deploy-manage/images/cloud-ec-saml-azuread-kibana-config.png new file mode 100644 index 0000000000..5fb5412e8c Binary files /dev/null and b/deploy-manage/images/cloud-ec-saml-azuread-kibana-config.png differ diff --git a/deploy-manage/images/cloud-ec-saml-azuread-user-attributes.png b/deploy-manage/images/cloud-ec-saml-azuread-user-attributes.png new file mode 100644 index 0000000000..9a5cb8d51c Binary files /dev/null and b/deploy-manage/images/cloud-ec-saml-azuread-user-attributes.png differ diff --git a/deploy-manage/images/cloud-ec-saml-azuread-users-and-groups.png b/deploy-manage/images/cloud-ec-saml-azuread-users-and-groups.png new file mode 100644 index 0000000000..fd62c2b7cc Binary files /dev/null and b/deploy-manage/images/cloud-ec-saml-azuread-users-and-groups.png differ diff --git a/deploy-manage/images/cloud-ec-shard-activity.gif b/deploy-manage/images/cloud-ec-shard-activity.gif new file mode 100644 index 0000000000..beaa58db74 Binary files /dev/null and b/deploy-manage/images/cloud-ec-shard-activity.gif differ diff --git a/deploy-manage/images/cloud-ec-stack-components.png b/deploy-manage/images/cloud-ec-stack-components.png new file mode 100644 index 0000000000..f01e8b14c6 Binary files /dev/null and b/deploy-manage/images/cloud-ec-stack-components.png differ diff --git a/deploy-manage/images/cloud-edit-trust-environment.png b/deploy-manage/images/cloud-edit-trust-environment.png new file mode 100644 index 0000000000..7528bab224 Binary files /dev/null and b/deploy-manage/images/cloud-edit-trust-environment.png differ diff --git a/deploy-manage/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png b/deploy-manage/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png new file mode 100644 index 0000000000..325cf37509 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png differ diff --git a/deploy-manage/images/cloud-enterprise-ce-create-from-snapshot-updated.png b/deploy-manage/images/cloud-enterprise-ce-create-from-snapshot-updated.png new file mode 100644 index 0000000000..dbc7aacc01 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ce-create-from-snapshot-updated.png differ diff --git a/deploy-manage/images/cloud-enterprise-ce-environment-trust-management.png b/deploy-manage/images/cloud-enterprise-ce-environment-trust-management.png new file mode 100644 index 0000000000..1a0013e2ac Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ce-environment-trust-management.png differ diff --git a/deploy-manage/images/cloud-enterprise-delete-trust-environment.png b/deploy-manage/images/cloud-enterprise-delete-trust-environment.png new file mode 100644 index 0000000000..a376e85672 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-delete-trust-environment.png differ diff --git a/deploy-manage/images/cloud-enterprise-deployment-filter.png b/deploy-manage/images/cloud-enterprise-deployment-filter.png new file mode 100644 index 0000000000..56aaf7fbeb Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-deployment-filter.png differ diff --git a/deploy-manage/images/cloud-enterprise-ec-ce-activity-page.png b/deploy-manage/images/cloud-enterprise-ec-ce-activity-page.png new file mode 100644 index 0000000000..7fa6d5bd28 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ec-ce-activity-page.png differ diff --git a/deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png b/deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png new file mode 100644 index 0000000000..f650fdfb28 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-data-summary2.png differ diff --git a/deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png b/deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png new file mode 100644 index 0000000000..8380f8736d Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ec-ce-autoscaling-ml-summary2.png differ diff --git a/deploy-manage/images/cloud-enterprise-ec-ce-cloud-id.png b/deploy-manage/images/cloud-enterprise-ec-ce-cloud-id.png new file mode 100644 index 0000000000..a42e5601f2 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ec-ce-cloud-id.png differ diff --git a/deploy-manage/images/cloud-enterprise-ec-customize-deployment2.png b/deploy-manage/images/cloud-enterprise-ec-customize-deployment2.png new file mode 100644 index 0000000000..962409b57f Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ec-customize-deployment2.png differ diff --git a/deploy-manage/images/cloud-enterprise-ec-number-of-nodes.png b/deploy-manage/images/cloud-enterprise-ec-number-of-nodes.png new file mode 100644 index 0000000000..65b8f1db00 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ec-number-of-nodes.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-architecture.png b/deploy-manage/images/cloud-enterprise-ece-architecture.png new file mode 100644 index 0000000000..a84725121c Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-architecture.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-available-capacity.png b/deploy-manage/images/cloud-enterprise-ece-available-capacity.png new file mode 100644 index 0000000000..fe22914e33 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-available-capacity.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-create-deployment.png b/deploy-manage/images/cloud-enterprise-ece-create-deployment.png new file mode 100644 index 0000000000..f8bf8c15cf Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-create-deployment.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-create-template-autoscaling.png b/deploy-manage/images/cloud-enterprise-ece-create-template-autoscaling.png new file mode 100644 index 0000000000..c2dfa513cb Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-create-template-autoscaling.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-create-template-availability-zones.png b/deploy-manage/images/cloud-enterprise-ece-create-template-availability-zones.png new file mode 100644 index 0000000000..b7a18b6c3b Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-create-template-availability-zones.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-create-template-initial-size.png b/deploy-manage/images/cloud-enterprise-ece-create-template-initial-size.png new file mode 100644 index 0000000000..b45a673d9a Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-create-template-initial-size.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-create-template-instance-configuration.png b/deploy-manage/images/cloud-enterprise-ece-create-template-instance-configuration.png new file mode 100644 index 0000000000..57bb530c45 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-create-template-instance-configuration.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-create-template-max-autoscaling.png b/deploy-manage/images/cloud-enterprise-ece-create-template-max-autoscaling.png new file mode 100644 index 0000000000..5902e557bb Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-create-template-max-autoscaling.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-create-template-user-settings.png b/deploy-manage/images/cloud-enterprise-ece-create-template-user-settings.png new file mode 100644 index 0000000000..eeb621a395 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-create-template-user-settings.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-minio-deployment.png b/deploy-manage/images/cloud-enterprise-ece-minio-deployment.png new file mode 100644 index 0000000000..2770043ded Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-minio-deployment.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-minio-large-arch.png b/deploy-manage/images/cloud-enterprise-ece-minio-large-arch.png new file mode 100644 index 0000000000..18be3a7902 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-minio-large-arch.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-minio-repository.png b/deploy-manage/images/cloud-enterprise-ece-minio-repository.png new file mode 100644 index 0000000000..2bbda07681 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-minio-repository.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-networking-ports.png b/deploy-manage/images/cloud-enterprise-ece-networking-ports.png new file mode 100644 index 0000000000..54bba51fdd Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-networking-ports.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-pb-3.png b/deploy-manage/images/cloud-enterprise-ece-pb-3.png new file mode 100644 index 0000000000..8ad4d736f1 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-pb-3.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-pb-6.png b/deploy-manage/images/cloud-enterprise-ece-pb-6.png new file mode 100644 index 0000000000..c8679e9ffa Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-pb-6.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-pb-9.png b/deploy-manage/images/cloud-enterprise-ece-pb-9.png new file mode 100644 index 0000000000..f0b5b93f71 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-pb-9.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-query-ui.png b/deploy-manage/images/cloud-enterprise-ece-query-ui.png new file mode 100644 index 0000000000..ddfa8d0d38 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-query-ui.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-secure-settings.png b/deploy-manage/images/cloud-enterprise-ece-secure-settings.png new file mode 100644 index 0000000000..b87f9cf69e Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-secure-settings.png differ diff --git a/deploy-manage/images/cloud-enterprise-ece-tagging-ui.png b/deploy-manage/images/cloud-enterprise-ece-tagging-ui.png new file mode 100644 index 0000000000..8441726ffe Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-ece-tagging-ui.png differ diff --git a/deploy-manage/images/cloud-enterprise-edit-trust-environment.png b/deploy-manage/images/cloud-enterprise-edit-trust-environment.png new file mode 100644 index 0000000000..7528bab224 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-edit-trust-environment.png differ diff --git a/deploy-manage/images/cloud-enterprise-podman-migration-correct-role-1.png b/deploy-manage/images/cloud-enterprise-podman-migration-correct-role-1.png new file mode 100644 index 0000000000..d1b413a076 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-podman-migration-correct-role-1.png differ diff --git a/deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-1.png b/deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-1.png new file mode 100644 index 0000000000..4f3df81598 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-1.png differ diff --git a/deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-2.png b/deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-2.png new file mode 100644 index 0000000000..48daa7bd15 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-podman-migration-fetch-roles-2.png differ diff --git a/deploy-manage/images/cloud-enterprise-podman-migration-move-instances-1.png b/deploy-manage/images/cloud-enterprise-podman-migration-move-instances-1.png new file mode 100644 index 0000000000..647d8f6986 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-podman-migration-move-instances-1.png differ diff --git a/deploy-manage/images/cloud-enterprise-podman-migration-overview-1.png b/deploy-manage/images/cloud-enterprise-podman-migration-overview-1.png new file mode 100644 index 0000000000..99607bc853 Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-podman-migration-overview-1.png differ diff --git a/deploy-manage/images/cloud-enterprise-podman-migration-wrong-role-1.png b/deploy-manage/images/cloud-enterprise-podman-migration-wrong-role-1.png new file mode 100644 index 0000000000..b077760d1e Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-podman-migration-wrong-role-1.png differ diff --git a/deploy-manage/images/cloud-enterprise-remote-clusters-proxy-certificate.png b/deploy-manage/images/cloud-enterprise-remote-clusters-proxy-certificate.png new file mode 100644 index 0000000000..31ee3b83cd Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-remote-clusters-proxy-certificate.png differ diff --git a/deploy-manage/images/cloud-enterprise-restore-from-snapshot.png b/deploy-manage/images/cloud-enterprise-restore-from-snapshot.png new file mode 100644 index 0000000000..87d6dcdfdd Binary files /dev/null and b/deploy-manage/images/cloud-enterprise-restore-from-snapshot.png differ diff --git a/deploy-manage/images/cloud-es-health-page-table.png b/deploy-manage/images/cloud-es-health-page-table.png new file mode 100644 index 0000000000..dacc627160 Binary files /dev/null and b/deploy-manage/images/cloud-es-health-page-table.png differ diff --git a/deploy-manage/images/cloud-es-health-page.png b/deploy-manage/images/cloud-es-health-page.png new file mode 100644 index 0000000000..27a219eecf Binary files /dev/null and b/deploy-manage/images/cloud-es-health-page.png differ diff --git a/deploy-manage/images/cloud-heroku-ec-cloud-platform-hardware.png b/deploy-manage/images/cloud-heroku-ec-cloud-platform-hardware.png new file mode 100644 index 0000000000..bf0c0b642f Binary files /dev/null and b/deploy-manage/images/cloud-heroku-ec-cloud-platform-hardware.png differ diff --git a/deploy-manage/images/cloud-heroku-ech-console.png b/deploy-manage/images/cloud-heroku-ech-console.png new file mode 100644 index 0000000000..cabe55ac8f Binary files /dev/null and b/deploy-manage/images/cloud-heroku-ech-console.png differ diff --git a/deploy-manage/images/cloud-memory-pressure-indicator.png b/deploy-manage/images/cloud-memory-pressure-indicator.png new file mode 100644 index 0000000000..fef68031bd Binary files /dev/null and b/deploy-manage/images/cloud-memory-pressure-indicator.png differ diff --git a/deploy-manage/images/cloud-metrics-cpu-credits.png b/deploy-manage/images/cloud-metrics-cpu-credits.png new file mode 100644 index 0000000000..1b5304a520 Binary files /dev/null and b/deploy-manage/images/cloud-metrics-cpu-credits.png differ diff --git a/deploy-manage/images/cloud-metrics-cpu-usage.png b/deploy-manage/images/cloud-metrics-cpu-usage.png new file mode 100644 index 0000000000..f676f365bb Binary files /dev/null and b/deploy-manage/images/cloud-metrics-cpu-usage.png differ diff --git a/deploy-manage/images/cloud-metrics-credits.png b/deploy-manage/images/cloud-metrics-credits.png new file mode 100644 index 0000000000..7c77e5857d Binary files /dev/null and b/deploy-manage/images/cloud-metrics-credits.png differ diff --git a/deploy-manage/images/cloud-metrics-gc-overhead-per-node.png b/deploy-manage/images/cloud-metrics-gc-overhead-per-node.png new file mode 100644 index 0000000000..d86e03265b Binary files /dev/null and b/deploy-manage/images/cloud-metrics-gc-overhead-per-node.png differ diff --git a/deploy-manage/images/cloud-metrics-hover.png b/deploy-manage/images/cloud-metrics-hover.png new file mode 100644 index 0000000000..397af04849 Binary files /dev/null and b/deploy-manage/images/cloud-metrics-hover.png differ diff --git a/deploy-manage/images/cloud-metrics-index-response-times.png b/deploy-manage/images/cloud-metrics-index-response-times.png new file mode 100644 index 0000000000..d5e068c37d Binary files /dev/null and b/deploy-manage/images/cloud-metrics-index-response-times.png differ diff --git a/deploy-manage/images/cloud-metrics-memory-pressure-per-node.png b/deploy-manage/images/cloud-metrics-memory-pressure-per-node.png new file mode 100644 index 0000000000..dcd423f3e9 Binary files /dev/null and b/deploy-manage/images/cloud-metrics-memory-pressure-per-node.png differ diff --git a/deploy-manage/images/cloud-metrics-number-of-requests.png b/deploy-manage/images/cloud-metrics-number-of-requests.png new file mode 100644 index 0000000000..cf17f14936 Binary files /dev/null and b/deploy-manage/images/cloud-metrics-number-of-requests.png differ diff --git a/deploy-manage/images/cloud-metrics-pan.png b/deploy-manage/images/cloud-metrics-pan.png new file mode 100644 index 0000000000..04cc42d6ad Binary files /dev/null and b/deploy-manage/images/cloud-metrics-pan.png differ diff --git a/deploy-manage/images/cloud-metrics-reset.png b/deploy-manage/images/cloud-metrics-reset.png new file mode 100644 index 0000000000..400aa02386 Binary files /dev/null and b/deploy-manage/images/cloud-metrics-reset.png differ diff --git a/deploy-manage/images/cloud-metrics-search-response-times.png b/deploy-manage/images/cloud-metrics-search-response-times.png new file mode 100644 index 0000000000..1880e9719c Binary files /dev/null and b/deploy-manage/images/cloud-metrics-search-response-times.png differ diff --git a/deploy-manage/images/cloud-metrics-zoom.png b/deploy-manage/images/cloud-metrics-zoom.png new file mode 100644 index 0000000000..d0524c52be Binary files /dev/null and b/deploy-manage/images/cloud-metrics-zoom.png differ diff --git a/deploy-manage/images/cloud-on-k8s-cgroups-cfs-stats.png b/deploy-manage/images/cloud-on-k8s-cgroups-cfs-stats.png new file mode 100644 index 0000000000..f95841b67f Binary files /dev/null and b/deploy-manage/images/cloud-on-k8s-cgroups-cfs-stats.png differ diff --git a/deploy-manage/images/cloud-on-k8s-metrics-explorer-cpu.png b/deploy-manage/images/cloud-on-k8s-metrics-explorer-cpu.png new file mode 100644 index 0000000000..19336b1ba6 Binary files /dev/null and b/deploy-manage/images/cloud-on-k8s-metrics-explorer-cpu.png differ diff --git a/deploy-manage/images/cloud-remote-clusters-proxy-certificate.png b/deploy-manage/images/cloud-remote-clusters-proxy-certificate.png new file mode 100644 index 0000000000..31ee3b83cd Binary files /dev/null and b/deploy-manage/images/cloud-remote-clusters-proxy-certificate.png differ diff --git a/deploy-manage/images/elastic-stack-install-stack-metrics-dashboard.png b/deploy-manage/images/elastic-stack-install-stack-metrics-dashboard.png new file mode 100644 index 0000000000..890b4d4650 Binary files /dev/null and b/deploy-manage/images/elastic-stack-install-stack-metrics-dashboard.png differ diff --git a/deploy-manage/images/elasticsearch-reference-architecture.png b/deploy-manage/images/elasticsearch-reference-architecture.png new file mode 100644 index 0000000000..769618c0cc Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-architecture.png differ diff --git a/deploy-manage/images/elasticsearch-reference-authorization.png b/deploy-manage/images/elasticsearch-reference-authorization.png new file mode 100644 index 0000000000..1d692f2e3a Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-authorization.png differ diff --git a/deploy-manage/images/elasticsearch-reference-auto-follow-patterns.png b/deploy-manage/images/elasticsearch-reference-auto-follow-patterns.png new file mode 100644 index 0000000000..69e1cc8641 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-auto-follow-patterns.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-arch-bi-directional.png b/deploy-manage/images/elasticsearch-reference-ccr-arch-bi-directional.png new file mode 100644 index 0000000000..9c936cd9f4 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-arch-bi-directional.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-arch-central-reporting.png b/deploy-manage/images/elasticsearch-reference-ccr-arch-central-reporting.png new file mode 100644 index 0000000000..c89346e290 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-arch-central-reporting.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-arch-chain-dcs.png b/deploy-manage/images/elasticsearch-reference-ccr-arch-chain-dcs.png new file mode 100644 index 0000000000..042a8185c7 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-arch-chain-dcs.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-arch-data-locality.png b/deploy-manage/images/elasticsearch-reference-ccr-arch-data-locality.png new file mode 100644 index 0000000000..a2b67b0728 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-arch-data-locality.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-arch-disaster-recovery.png b/deploy-manage/images/elasticsearch-reference-ccr-arch-disaster-recovery.png new file mode 100644 index 0000000000..244c71910f Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-arch-disaster-recovery.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-arch-multiple-dcs.png b/deploy-manage/images/elasticsearch-reference-ccr-arch-multiple-dcs.png new file mode 100644 index 0000000000..2a2fd05a00 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-arch-multiple-dcs.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-bi-directional-disaster-recovery.png b/deploy-manage/images/elasticsearch-reference-ccr-bi-directional-disaster-recovery.png new file mode 100644 index 0000000000..ad597160d3 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-bi-directional-disaster-recovery.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-follower-index.png b/deploy-manage/images/elasticsearch-reference-ccr-follower-index.png new file mode 100644 index 0000000000..dee64c5272 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-follower-index.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-tutorial-clusters.png b/deploy-manage/images/elasticsearch-reference-ccr-tutorial-clusters.png new file mode 100644 index 0000000000..23e72702fd Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-tutorial-clusters.png differ diff --git a/deploy-manage/images/elasticsearch-reference-ccr-uni-directional-disaster-recovery.png b/deploy-manage/images/elasticsearch-reference-ccr-uni-directional-disaster-recovery.png new file mode 100644 index 0000000000..ad6e19fa13 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-ccr-uni-directional-disaster-recovery.png differ diff --git a/deploy-manage/images/elasticsearch-reference-data_processing_flow.png b/deploy-manage/images/elasticsearch-reference-data_processing_flow.png new file mode 100644 index 0000000000..9b2f58ad61 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-data_processing_flow.png differ diff --git a/deploy-manage/images/elasticsearch-reference-elas_0202.png b/deploy-manage/images/elasticsearch-reference-elas_0202.png new file mode 100644 index 0000000000..36b31cc378 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-elas_0202.png differ diff --git a/deploy-manage/images/elasticsearch-reference-elas_0204.png b/deploy-manage/images/elasticsearch-reference-elas_0204.png new file mode 100644 index 0000000000..788d46e09f Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-elas_0204.png differ diff --git a/deploy-manage/images/elasticsearch-reference-elastic-security-overview.png b/deploy-manage/images/elasticsearch-reference-elastic-security-overview.png new file mode 100644 index 0000000000..4cf6b08f5a Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-elastic-security-overview.png differ diff --git a/deploy-manage/images/elasticsearch-reference-metricbeat.png b/deploy-manage/images/elasticsearch-reference-metricbeat.png new file mode 100644 index 0000000000..f74f856653 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-metricbeat.png differ diff --git a/deploy-manage/images/elasticsearch-reference-shard-allocation-awareness-one-rack.png b/deploy-manage/images/elasticsearch-reference-shard-allocation-awareness-one-rack.png new file mode 100644 index 0000000000..d5a3040cc5 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-shard-allocation-awareness-one-rack.png differ diff --git a/deploy-manage/images/elasticsearch-reference-shard-allocation-awareness-two-racks.png b/deploy-manage/images/elasticsearch-reference-shard-allocation-awareness-two-racks.png new file mode 100644 index 0000000000..ce2ce6b2a9 Binary files /dev/null and b/deploy-manage/images/elasticsearch-reference-shard-allocation-awareness-two-racks.png differ diff --git a/deploy-manage/images/kibana-access-agreement.png b/deploy-manage/images/kibana-access-agreement.png new file mode 100644 index 0000000000..b7b762a88e Binary files /dev/null and b/deploy-manage/images/kibana-access-agreement.png differ diff --git a/deploy-manage/images/kibana-api-keys.png b/deploy-manage/images/kibana-api-keys.png new file mode 100644 index 0000000000..6dec5730a1 Binary files /dev/null and b/deploy-manage/images/kibana-api-keys.png differ diff --git a/deploy-manage/images/kibana-assign-base-privilege.png b/deploy-manage/images/kibana-assign-base-privilege.png new file mode 100644 index 0000000000..17be4b9ef2 Binary files /dev/null and b/deploy-manage/images/kibana-assign-base-privilege.png differ diff --git a/deploy-manage/images/kibana-assign-subfeature-privilege.png b/deploy-manage/images/kibana-assign-subfeature-privilege.png new file mode 100644 index 0000000000..c83cd6b165 Binary files /dev/null and b/deploy-manage/images/kibana-assign-subfeature-privilege.png differ diff --git a/deploy-manage/images/kibana-change-space.png b/deploy-manage/images/kibana-change-space.png new file mode 100644 index 0000000000..7c55ed0c2d Binary files /dev/null and b/deploy-manage/images/kibana-change-space.png differ diff --git a/deploy-manage/images/kibana-connector-delete.png b/deploy-manage/images/kibana-connector-delete.png new file mode 100644 index 0000000000..991333c546 Binary files /dev/null and b/deploy-manage/images/kibana-connector-delete.png differ diff --git a/deploy-manage/images/kibana-connector-filter-by-type.png b/deploy-manage/images/kibana-connector-filter-by-type.png new file mode 100644 index 0000000000..5892278279 Binary files /dev/null and b/deploy-manage/images/kibana-connector-filter-by-type.png differ diff --git a/deploy-manage/images/kibana-connector-select-type.png b/deploy-manage/images/kibana-connector-select-type.png new file mode 100644 index 0000000000..90f26778dd Binary files /dev/null and b/deploy-manage/images/kibana-connector-select-type.png differ diff --git a/deploy-manage/images/kibana-connectors-with-missing-secrets.png b/deploy-manage/images/kibana-connectors-with-missing-secrets.png new file mode 100644 index 0000000000..498ba64a55 Binary files /dev/null and b/deploy-manage/images/kibana-connectors-with-missing-secrets.png differ diff --git a/deploy-manage/images/kibana-create-ccr-api-key.png b/deploy-manage/images/kibana-create-ccr-api-key.png new file mode 100644 index 0000000000..00b5cf546b Binary files /dev/null and b/deploy-manage/images/kibana-create-ccr-api-key.png differ diff --git a/deploy-manage/images/kibana-create-role-dls-example.png b/deploy-manage/images/kibana-create-role-dls-example.png new file mode 100644 index 0000000000..0899fce010 Binary files /dev/null and b/deploy-manage/images/kibana-create-role-dls-example.png differ diff --git a/deploy-manage/images/kibana-create-role-index-example.png b/deploy-manage/images/kibana-create-role-index-example.png new file mode 100644 index 0000000000..68c833b244 Binary files /dev/null and b/deploy-manage/images/kibana-create-role-index-example.png differ diff --git a/deploy-manage/images/kibana-create-role-remote-index-example.png b/deploy-manage/images/kibana-create-role-remote-index-example.png new file mode 100644 index 0000000000..8008c8efd6 Binary files /dev/null and b/deploy-manage/images/kibana-create-role-remote-index-example.png differ diff --git a/deploy-manage/images/kibana-create-space-privilege.png b/deploy-manage/images/kibana-create-space-privilege.png new file mode 100644 index 0000000000..093a339122 Binary files /dev/null and b/deploy-manage/images/kibana-create-space-privilege.png differ diff --git a/deploy-manage/images/kibana-kibana-login.png b/deploy-manage/images/kibana-kibana-login.png new file mode 100644 index 0000000000..cd9df9f563 Binary files /dev/null and b/deploy-manage/images/kibana-kibana-login.png differ diff --git a/deploy-manage/images/kibana-kibana-privileges-with-reporting-basic.png b/deploy-manage/images/kibana-kibana-privileges-with-reporting-basic.png new file mode 100644 index 0000000000..6d2c3ba645 Binary files /dev/null and b/deploy-manage/images/kibana-kibana-privileges-with-reporting-basic.png differ diff --git a/deploy-manage/images/kibana-kibana-privileges-with-reporting.png b/deploy-manage/images/kibana-kibana-privileges-with-reporting.png new file mode 100644 index 0000000000..0675d893e4 Binary files /dev/null and b/deploy-manage/images/kibana-kibana-privileges-with-reporting.png differ diff --git a/deploy-manage/images/kibana-metricbeat.png b/deploy-manage/images/kibana-metricbeat.png new file mode 100644 index 0000000000..17b9516e91 Binary files /dev/null and b/deploy-manage/images/kibana-metricbeat.png differ diff --git a/deploy-manage/images/kibana-monitoring-beats-detail.png b/deploy-manage/images/kibana-monitoring-beats-detail.png new file mode 100644 index 0000000000..8fbd4b62a5 Binary files /dev/null and b/deploy-manage/images/kibana-monitoring-beats-detail.png differ diff --git a/deploy-manage/images/kibana-monitoring-beats.png b/deploy-manage/images/kibana-monitoring-beats.png new file mode 100644 index 0000000000..4b297a9795 Binary files /dev/null and b/deploy-manage/images/kibana-monitoring-beats.png differ diff --git a/deploy-manage/images/kibana-monitoring-dashboard.png b/deploy-manage/images/kibana-monitoring-dashboard.png new file mode 100644 index 0000000000..34c008dcbe Binary files /dev/null and b/deploy-manage/images/kibana-monitoring-dashboard.png differ diff --git a/deploy-manage/images/kibana-monitoring-elasticsearch.png b/deploy-manage/images/kibana-monitoring-elasticsearch.png new file mode 100644 index 0000000000..cb8448c8c5 Binary files /dev/null and b/deploy-manage/images/kibana-monitoring-elasticsearch.png differ diff --git a/deploy-manage/images/kibana-monitoring-kibana-alerting-notification.png b/deploy-manage/images/kibana-monitoring-kibana-alerting-notification.png new file mode 100644 index 0000000000..90951d18e6 Binary files /dev/null and b/deploy-manage/images/kibana-monitoring-kibana-alerting-notification.png differ diff --git a/deploy-manage/images/kibana-monitoring-kibana-overview.png b/deploy-manage/images/kibana-monitoring-kibana-overview.png new file mode 100644 index 0000000000..a23abd3277 Binary files /dev/null and b/deploy-manage/images/kibana-monitoring-kibana-overview.png differ diff --git a/deploy-manage/images/kibana-monitoring-logstash-overview.png b/deploy-manage/images/kibana-monitoring-logstash-overview.png new file mode 100644 index 0000000000..48cd4d1644 Binary files /dev/null and b/deploy-manage/images/kibana-monitoring-logstash-overview.png differ diff --git a/deploy-manage/images/kibana-monitoring-overview.png b/deploy-manage/images/kibana-monitoring-overview.png new file mode 100644 index 0000000000..3b47ee544b Binary files /dev/null and b/deploy-manage/images/kibana-monitoring-overview.png differ diff --git a/deploy-manage/images/kibana-mutual-tls-role-mapping.png b/deploy-manage/images/kibana-mutual-tls-role-mapping.png new file mode 100644 index 0000000000..42ba56a2ca Binary files /dev/null and b/deploy-manage/images/kibana-mutual-tls-role-mapping.png differ diff --git a/deploy-manage/images/kibana-privilege-example-1.png b/deploy-manage/images/kibana-privilege-example-1.png new file mode 100644 index 0000000000..59e71e3cb3 Binary files /dev/null and b/deploy-manage/images/kibana-privilege-example-1.png differ diff --git a/deploy-manage/images/kibana-privilege-example-2.png b/deploy-manage/images/kibana-privilege-example-2.png new file mode 100644 index 0000000000..36b26b131a Binary files /dev/null and b/deploy-manage/images/kibana-privilege-example-2.png differ diff --git a/deploy-manage/images/kibana-privilege-example-3.png b/deploy-manage/images/kibana-privilege-example-3.png new file mode 100644 index 0000000000..a000490502 Binary files /dev/null and b/deploy-manage/images/kibana-privilege-example-3.png differ diff --git a/deploy-manage/images/kibana-role-mappings-create-step-1.png b/deploy-manage/images/kibana-role-mappings-create-step-1.png new file mode 100644 index 0000000000..06ee1f3bc4 Binary files /dev/null and b/deploy-manage/images/kibana-role-mappings-create-step-1.png differ diff --git a/deploy-manage/images/kibana-role-mappings-create-step-2.gif b/deploy-manage/images/kibana-role-mappings-create-step-2.gif new file mode 100644 index 0000000000..766158a96b Binary files /dev/null and b/deploy-manage/images/kibana-role-mappings-create-step-2.gif differ diff --git a/deploy-manage/images/kibana-role-mappings-grid.png b/deploy-manage/images/kibana-role-mappings-grid.png new file mode 100644 index 0000000000..8044096e15 Binary files /dev/null and b/deploy-manage/images/kibana-role-mappings-grid.png differ diff --git a/deploy-manage/images/kibana-spaces-configure-landing-page.png b/deploy-manage/images/kibana-spaces-configure-landing-page.png new file mode 100644 index 0000000000..335a64dc1c Binary files /dev/null and b/deploy-manage/images/kibana-spaces-configure-landing-page.png differ diff --git a/deploy-manage/images/kibana-spaces-roles.png b/deploy-manage/images/kibana-spaces-roles.png new file mode 100644 index 0000000000..ed62b7f1bc Binary files /dev/null and b/deploy-manage/images/kibana-spaces-roles.png differ diff --git a/deploy-manage/images/kibana-tutorial-secure-access-example-1-role.png b/deploy-manage/images/kibana-tutorial-secure-access-example-1-role.png new file mode 100644 index 0000000000..a27b56315e Binary files /dev/null and b/deploy-manage/images/kibana-tutorial-secure-access-example-1-role.png differ diff --git a/deploy-manage/images/kibana-tutorial-secure-access-example-1-space.png b/deploy-manage/images/kibana-tutorial-secure-access-example-1-space.png new file mode 100644 index 0000000000..a48fdeaa6e Binary files /dev/null and b/deploy-manage/images/kibana-tutorial-secure-access-example-1-space.png differ diff --git a/deploy-manage/images/kibana-tutorial-secure-access-example-1-test.png b/deploy-manage/images/kibana-tutorial-secure-access-example-1-test.png new file mode 100644 index 0000000000..2ff4fb4b09 Binary files /dev/null and b/deploy-manage/images/kibana-tutorial-secure-access-example-1-test.png differ diff --git a/deploy-manage/images/kibana-tutorial-secure-access-example-1-user.png b/deploy-manage/images/kibana-tutorial-secure-access-example-1-user.png new file mode 100644 index 0000000000..8df26cf28e Binary files /dev/null and b/deploy-manage/images/kibana-tutorial-secure-access-example-1-user.png differ diff --git a/deploy-manage/images/machine-learning-ml-nlp-deployment-id-elser-v2.png b/deploy-manage/images/machine-learning-ml-nlp-deployment-id-elser-v2.png new file mode 100644 index 0000000000..d549ea8154 Binary files /dev/null and b/deploy-manage/images/machine-learning-ml-nlp-deployment-id-elser-v2.png differ diff --git a/deploy-manage/images/reference-architectures-frozen.png b/deploy-manage/images/reference-architectures-frozen.png new file mode 100644 index 0000000000..5e7d53bffa Binary files /dev/null and b/deploy-manage/images/reference-architectures-frozen.png differ diff --git a/deploy-manage/images/reference-architectures-hot-frozen.png b/deploy-manage/images/reference-architectures-hot-frozen.png new file mode 100644 index 0000000000..1e12b4b25a Binary files /dev/null and b/deploy-manage/images/reference-architectures-hot-frozen.png differ diff --git a/deploy-manage/images/reference-architectures-hot.png b/deploy-manage/images/reference-architectures-hot.png new file mode 100644 index 0000000000..ebfab39255 Binary files /dev/null and b/deploy-manage/images/reference-architectures-hot.png differ diff --git a/deploy-manage/images/reference-architectures-kibana.png b/deploy-manage/images/reference-architectures-kibana.png new file mode 100644 index 0000000000..78a39ae749 Binary files /dev/null and b/deploy-manage/images/reference-architectures-kibana.png differ diff --git a/deploy-manage/images/reference-architectures-machine-learning.png b/deploy-manage/images/reference-architectures-machine-learning.png new file mode 100644 index 0000000000..3508f04784 Binary files /dev/null and b/deploy-manage/images/reference-architectures-machine-learning.png differ diff --git a/deploy-manage/images/reference-architectures-master.png b/deploy-manage/images/reference-architectures-master.png new file mode 100644 index 0000000000..9de92464c2 Binary files /dev/null and b/deploy-manage/images/reference-architectures-master.png differ diff --git a/deploy-manage/images/serverless-api-key-management.png b/deploy-manage/images/serverless-api-key-management.png new file mode 100644 index 0000000000..0b8b110214 Binary files /dev/null and b/deploy-manage/images/serverless-api-key-management.png differ diff --git a/deploy-manage/images/serverless-create-personal-api-key.png b/deploy-manage/images/serverless-create-personal-api-key.png new file mode 100644 index 0000000000..1eba110e74 Binary files /dev/null and b/deploy-manage/images/serverless-create-personal-api-key.png differ diff --git a/deploy-manage/images/serverless-custom-roles-cluster-privileges.png b/deploy-manage/images/serverless-custom-roles-cluster-privileges.png new file mode 100644 index 0000000000..6f9bb58823 Binary files /dev/null and b/deploy-manage/images/serverless-custom-roles-cluster-privileges.png differ diff --git a/deploy-manage/images/serverless-custom-roles-index-privileges.png b/deploy-manage/images/serverless-custom-roles-index-privileges.png new file mode 100644 index 0000000000..ed1662ba6d Binary files /dev/null and b/deploy-manage/images/serverless-custom-roles-index-privileges.png differ diff --git a/deploy-manage/images/serverless-custom-roles-kibana-privileges.png b/deploy-manage/images/serverless-custom-roles-kibana-privileges.png new file mode 100644 index 0000000000..5550fa2a8d Binary files /dev/null and b/deploy-manage/images/serverless-custom-roles-kibana-privileges.png differ diff --git a/deploy-manage/images/serverless-es-badge.svg b/deploy-manage/images/serverless-es-badge.svg new file mode 100644 index 0000000000..8176b81d2b --- /dev/null +++ b/deploy-manage/images/serverless-es-badge.svg @@ -0,0 +1,14 @@ + + + + + + + + + + + + + + diff --git a/deploy-manage/images/serverless-obs-badge.svg b/deploy-manage/images/serverless-obs-badge.svg new file mode 100644 index 0000000000..0996e309a2 --- /dev/null +++ b/deploy-manage/images/serverless-obs-badge.svg @@ -0,0 +1,14 @@ + + + + + + + + + + + + + + diff --git a/deploy-manage/images/serverless-sec-badge.svg b/deploy-manage/images/serverless-sec-badge.svg new file mode 100644 index 0000000000..1e743a20cf --- /dev/null +++ b/deploy-manage/images/serverless-sec-badge.svg @@ -0,0 +1,7 @@ + + + + + + + diff --git a/deploy-manage/kibana-reporting-configuration.md b/deploy-manage/kibana-reporting-configuration.md index 09b11f4297..ae8d15425c 100644 --- a/deploy-manage/kibana-reporting-configuration.md +++ b/deploy-manage/kibana-reporting-configuration.md @@ -100,7 +100,7 @@ When security is enabled, you grant users access to {{report-features}} with [{{ ::: - :::{image} /images/kibana-kibana-privileges-with-reporting.png + :::{image} /deploy-manage/images/kibana-kibana-privileges-with-reporting.png :alt: Kibana privileges with Reporting options, Gold or higher license :screenshot: ::: @@ -183,7 +183,7 @@ With a Basic license, sub-feature [application privileges](/deploy-manage/users- Example using Kibana UI: -:::{image} /images/kibana-kibana-privileges-with-reporting-basic.png +:::{image} /deploy-manage/images/kibana-kibana-privileges-with-reporting-basic.png :alt: Kibana privileges with Reporting options, Basic license :screenshot: ::: diff --git a/deploy-manage/maintenance/add-and-remove-elasticsearch-nodes.md b/deploy-manage/maintenance/add-and-remove-elasticsearch-nodes.md index d515ecd7ab..8d458aefec 100644 --- a/deploy-manage/maintenance/add-and-remove-elasticsearch-nodes.md +++ b/deploy-manage/maintenance/add-and-remove-elasticsearch-nodes.md @@ -12,7 +12,7 @@ When you start an instance of {{es}}, you are starting a *node*. An {{es}} *clus If you are running a single instance of {{es}}, you have a cluster of one node. All primary shards reside on the single node. No replica shards can be allocated, therefore the cluster state remains yellow. The cluster is fully functional but is at risk of data loss in the event of a failure. -:::{image} ../../images/elasticsearch-reference-elas_0202.png +:::{image} /deploy-manage/images/elasticsearch-reference-elas_0202.png :alt: A cluster with one node and three primary shards ::: @@ -20,7 +20,7 @@ You add nodes to a cluster to increase its capacity and reliability. By default, When you add more nodes to a cluster, it automatically allocates replica shards. When all primary and replica shards are active, the cluster state changes to green. -:::{image} ../../images/elasticsearch-reference-elas_0204.png +:::{image} /deploy-manage/images/elasticsearch-reference-elas_0204.png :alt: A cluster with three nodes ::: diff --git a/deploy-manage/maintenance/ece/scale-out-installation.md b/deploy-manage/maintenance/ece/scale-out-installation.md index bc736cb8a5..367e793bbf 100644 --- a/deploy-manage/maintenance/ece/scale-out-installation.md +++ b/deploy-manage/maintenance/ece/scale-out-installation.md @@ -16,7 +16,7 @@ Check the available capacity: 2. From the **Platform** menu, select **Allocators** to view the available capacity. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. In this case 3 GB and 6 GB on two different allocators: - :::{image} ../../../images/cloud-enterprise-ece-available-capacity.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-available-capacity.png :alt: The available capacity in an installation ::: diff --git a/deploy-manage/manage-connectors.md b/deploy-manage/manage-connectors.md index 4162b1ea65..059a87357b 100644 --- a/deploy-manage/manage-connectors.md +++ b/deploy-manage/manage-connectors.md @@ -32,14 +32,14 @@ If you're using {{stack}}, use the [action configuration settings](kibana://refe In **{{stack-manage-app}} > {{connectors-ui}}**, you can find a list of the connectors in the current space. You can use the search bar to find specific connectors by name and type. The **Type** dropdown also enables you to filter to a subset of connector types. -:::{image} ../images/kibana-connector-filter-by-type.png +:::{image} /deploy-manage/images/kibana-connector-filter-by-type.png :alt: Filtering the connector list by types of connectors :screenshot: ::: You can delete individual connectors using the trash icon. Alternatively, select multiple connectors and delete them in bulk using the **Delete** button. -:::{image} ../images/kibana-connector-delete.png +:::{image} /deploy-manage/images/kibana-connector-delete.png :alt: Deleting connectors individually or in bulk :screenshot: ::: @@ -57,7 +57,7 @@ New connectors can be created with the **Create connector** button, which guides Some connector types are paid commercial features, while others are free. For a comparison of the Elastic subscription levels, go to [the subscription page](https://www.elastic.co/subscriptions). :::: -:::{image} ../images/kibana-connector-select-type.png +:::{image} /deploy-manage/images/kibana-connector-select-type.png :alt: Connector select type :screenshot: :width: 75% @@ -79,7 +79,7 @@ To import and export connectors, use the [Saved Objects Management UI](/explore- If a connector is missing sensitive information after the import, a **Fix** button appears in **{{connectors-ui}}**. -:::{image} ../images/kibana-connectors-with-missing-secrets.png +:::{image} /deploy-manage/images/kibana-connectors-with-missing-secrets.png :alt: Connectors with missing secrets :screenshot: ::: diff --git a/deploy-manage/manage-spaces.md b/deploy-manage/manage-spaces.md index 90c0599c94..e123fd5946 100644 --- a/deploy-manage/manage-spaces.md +++ b/deploy-manage/manage-spaces.md @@ -17,7 +17,7 @@ mapped_urls: {{kib}} creates a default space for you. When you create more spaces, users are asked to choose a space when they log in, and can change their current space at any time from the top menu. -:::{image} ../images/kibana-change-space.png +:::{image} /deploy-manage/images/kibana-change-space.png :alt: Change current space menu :screenshot: ::: @@ -131,7 +131,7 @@ You can create a custom experience for users by configuring the {{kib}} landing To configure the landing page, use the default route setting in [Stack Management > {{kib}} > Advanced settings](kibana://reference/advanced-settings.md#kibana-general-settings). For example, you might set the default route to `/app/dashboards`. -:::{image} ../images/kibana-spaces-configure-landing-page.png +:::{image} /deploy-manage/images/kibana-spaces-configure-landing-page.png :alt: Configure space-level landing page :screenshot: ::: \ No newline at end of file diff --git a/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md b/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md index 2534980936..2308a5817c 100644 --- a/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md +++ b/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md @@ -31,7 +31,7 @@ The following metrics are available: ### CPU usage [ec_cpu_usage] -:::{image} /images/cloud-metrics-cpu-usage.png +:::{image} /deploy-manage/images/cloud-metrics-cpu-usage.png :alt: Graph showing CPU usage ::: @@ -43,7 +43,7 @@ This chart reports the maximum CPU values over the sampling period. [Logs and me ### CPU credits [ec_cpu_credits] -:::{image} /images/cloud-metrics-cpu-credits.png +:::{image} /deploy-manage/images/cloud-metrics-cpu-credits.png :alt: Graph showing available CPU credits ::: @@ -52,7 +52,7 @@ Shows your remaining CPU credits, measured in seconds of CPU time. CPU credits e ### Number of requests [ec_number_of_requests] -:::{image} /images/cloud-metrics-number-of-requests.png +:::{image} /deploy-manage/images/cloud-metrics-number-of-requests.png :alt: Graph showing the number of requests ::: @@ -61,7 +61,7 @@ Shows the number of requests that your cluster receives per second, separated in ### Search response times [ec_search_response_times] -:::{image} /images/cloud-metrics-search-response-times.png +:::{image} /deploy-manage/images/cloud-metrics-search-response-times.png :alt: Graph showing search response times ::: @@ -70,7 +70,7 @@ Indicates the amount of time that it takes for your {{es}} cluster to complete a ### Index response times [ec_index_response_times] -:::{image} /images/cloud-metrics-index-response-times.png +:::{image} /deploy-manage/images/cloud-metrics-index-response-times.png :alt: Graph showing index response times ::: @@ -79,7 +79,7 @@ Indicates the amount of time that it takes for your {{es}} cluster to complete a ### Memory pressure per node [ec_memory_pressure_per_node] -:::{image} /images/cloud-metrics-memory-pressure-per-node.png +:::{image} /deploy-manage/images/cloud-metrics-memory-pressure-per-node.png :alt: Graph showing memory pressure per node ::: @@ -88,7 +88,7 @@ Indicates the total memory used by the JVM heap over time. We’ve configured {{ ### GC overhead per node [ec_gc_overhead_per_node] -:::{image} /images/cloud-metrics-gc-overhead-per-node.png +:::{image} /deploy-manage/images/cloud-metrics-gc-overhead-per-node.png :alt: Graph showing the garbage collection overhead per node ::: @@ -112,17 +112,17 @@ Work with the metrics shown in **Cluster Performance Metrics** section to help y * Hover on any part of a graph to get additional information. For example, hovering on a section of a graph that shows response times reveals the percentile that responses fall into at that point in time: - :::{image} /images/cloud-metrics-hover.png + :::{image} /deploy-manage/images/cloud-metrics-hover.png :alt: Hover over the metric graph ::: * Zoom in on a graph by drawing a rectangle to select a specific time window. As you zoom in one metric, other performance metrics change to show data for the same time window. - :::{image} /images/cloud-metrics-zoom.png + :::{image} /deploy-manage/images/cloud-metrics-zoom.png :alt: Zoom the metric graph ::: -* Pan around with ![Pan in a metric graph](/images/cloud-metrics-pan.png "") to make sure that you can get the right parts of a metric graph as you zoom in. -* Reset the metric graph axes with ![Reset the metric graph](/images/cloud-metrics-reset.png ""), which returns the graphs to their original scale. +* Pan around with ![Pan in a metric graph](/deploy-manage/images/cloud-metrics-pan.png "") to make sure that you can get the right parts of a metric graph as you zoom in. +* Reset the metric graph axes with ![Reset the metric graph](/deploy-manage/images/cloud-metrics-reset.png ""), which returns the graphs to their original scale. Cluster performance metrics are shown per node and are color-coded to indicate which running {{es}} instance they belong to. \ No newline at end of file diff --git a/deploy-manage/monitor/autoops.md b/deploy-manage/monitor/autoops.md index 378078c6e9..d374d8f170 100644 --- a/deploy-manage/monitor/autoops.md +++ b/deploy-manage/monitor/autoops.md @@ -12,7 +12,7 @@ AutoOps diagnoses issues in Elasticsearch by analyzing hundreds of metrics, prov AutoOps is currently only available for [{{ech}} deployments](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md). -:::{image} ../../images/cloud-autoops-overview-page.png +:::{image} /deploy-manage/images/cloud-autoops-overview-page.png :alt: The Overview page ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md b/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md index c5480d5ade..d949f004f8 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md @@ -10,7 +10,7 @@ applies_to: The **Deployment** view is the event control panel that allows you to see which issues are affecting the {{es}} cluster and get a list of action items to address them. -:::{image} /images/cloud-autoops-deployment-view.png +:::{image} /deploy-manage/images/cloud-autoops-deployment-view.png :alt: The Deployment view ::: @@ -35,7 +35,7 @@ The **Events History** panel lists events that happened at some point and that h The **Deployment Info** panel provides a quick overview of the {{es}} cluster resources in the selected deployment, such as {{es}} version, cluster status (indicated by the colors green, yellow, or red) at the top right, number of nodes distributed by role, and resources metrics. -:::{image} /images/cloud-autoops-deployment-info.png +:::{image} /deploy-manage/images/cloud-autoops-deployment-info.png :alt: The AutoOps Deployment Info ::: @@ -44,7 +44,7 @@ The **Deployment Info** panel provides a quick overview of the {{es}} cluster re The **Performance** panel shows key performance metrics, aggregated at both the cluster level and the selected tier levels: -:::{image} /images/cloud-autoops-deployment-performance.png +:::{image} /deploy-manage/images/cloud-autoops-deployment-performance.png :alt: The AutoOps Deployment Performance ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md b/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md index 5aabfebabd..64bc4d7e22 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md +++ b/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md @@ -10,7 +10,7 @@ applies_to: Some events that are triggered may not require your attention immediately, or at all. Users with the appropriate permissions can choose to dismiss an event, preventing AutoOps from opening it. This action can be reversed using the Dismiss events report. -:::{image} /images/cloud-autoops-dismiss-events.png +:::{image} /deploy-manage/images/cloud-autoops-dismiss-events.png :alt: Dismiss events ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-event-settings.md b/deploy-manage/monitor/autoops/ec-autoops-event-settings.md index f3955a2496..7b3910f3c8 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-event-settings.md +++ b/deploy-manage/monitor/autoops/ec-autoops-event-settings.md @@ -23,7 +23,7 @@ The event settings include: * Index patterns to exclude - AutoOps will exclude system indices to prevent unnecessary events from opening. You can add or remove indices from the list. * Data roles tier to exclude from indications - Add threshold based on the type of data tier. -:::{image} /images/cloud-autoops-event-settings.png +:::{image} /deploy-manage/images/cloud-autoops-event-settings.png :alt: Event settings ::: @@ -34,7 +34,7 @@ The **Event Settings** report provides a list of all the events for which the se From the **Event Settings** report, you can click **Add** to add new settings, or select the edit icon to modify the existing settings. -:::{image} /images/cloud-autoops-events-settings-report.png +:::{image} /deploy-manage/images/cloud-autoops-events-settings-report.png :alt: Event settings report ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-events.md b/deploy-manage/monitor/autoops/ec-autoops-events.md index bc1fdf0bd1..532818c11a 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-events.md +++ b/deploy-manage/monitor/autoops/ec-autoops-events.md @@ -10,7 +10,7 @@ applies_to: An AutoOps event provides a detailed analysis of a specific issue, including why it was triggered and the steps needed to resolve it. -:::{image} /images/cloud-autoops-events.png +:::{image} /deploy-manage/images/cloud-autoops-events.png :alt: AutoOps events ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md b/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md index 043f9c2119..107e55e42e 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md +++ b/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md @@ -20,6 +20,6 @@ To access AutoOps from your Elastic Cloud console, follow these steps: 3. Click **Manage** on the right side of the selected deployment. 4. On the deployment details page, click **Open AutoOps**. -:::{image} /images/cloud-autoops-how-to-access.png +:::{image} /deploy-manage/images/cloud-autoops-how-to-access.png :alt: How to access AutoOps ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-index-view.md b/deploy-manage/monitor/autoops/ec-autoops-index-view.md index 3d5b1b28a2..05a3523db0 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-index-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-index-view.md @@ -10,7 +10,7 @@ applies_to: The **Indices** view provides detailed statistics for each {{es}} index in your deployment. -:::{image} /images/cloud-autoops-index-view.png +:::{image} /deploy-manage/images/cloud-autoops-index-view.png :alt: The Indices view ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md b/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md index 171199adbe..7f4afbf350 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md @@ -10,7 +10,7 @@ applies_to: The **Nodes** view provides a thorough overview on the essential metrics for all monitored deployment nodes. You can delve into specific nodes to observe metrics over extended periods. This includes data on the indexing rate and latency, search rate and latency, as well as details concerning thread pools, data, circuit breakers, network, disk, and additional elements. -:::{image} /images/cloud-autoops-node-view.png +:::{image} /deploy-manage/images/cloud-autoops-node-view.png :alt: The Node view ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md b/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md index 6f80cb46cb..422545f483 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md +++ b/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md @@ -217,7 +217,7 @@ When the connector settings have been completed, continue to set up the notifica From the **Notifications** report, you can check all the notifications sent. The report lists all the events that were set up in the notification filters and provide their status. -:::{image} /images/cloud-autoops-notifications-report.png +:::{image} /deploy-manage/images/cloud-autoops-notifications-report.png :alt: The Notifications report ::: @@ -232,6 +232,6 @@ The notification can have one of the following statuses: The notification status appears also in the event details window. -:::{image} /images/cloud-autoops-notification-status.png +:::{image} /deploy-manage/images/cloud-autoops-notification-status.png :alt: Notification status ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-overview-view.md b/deploy-manage/monitor/autoops/ec-autoops-overview-view.md index df0f555908..5c92ff3d5c 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-overview-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-overview-view.md @@ -10,7 +10,7 @@ applies_to: The **Overview** page displays the current status of customer deployments in Elastic Cloud Hosted that are linked to the same Elastic organization. -:::{image} /images/cloud-autoops-overview-page.png +:::{image} /deploy-manage/images/cloud-autoops-overview-page.png :alt: The Overview page ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-shards-view.md b/deploy-manage/monitor/autoops/ec-autoops-shards-view.md index b94f38df77..7c47ce7f20 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-shards-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-shards-view.md @@ -10,7 +10,7 @@ applies_to: The **Shards** view allows you to manage and monitor shards allocated to each node, ensuring optimal performance and reliability of your search and indexing operations. -:::{image} /images/cloud-autoops-shard-view.png +:::{image} /deploy-manage/images/cloud-autoops-shard-view.png :alt: The Shards view ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md b/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md index 79de068ce4..0dae3c61fa 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md +++ b/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md @@ -10,7 +10,7 @@ applies_to: The **Template Optimizer View** offers detailed recommendations for optimizing templates. -:::{image} /images/cloud-autoops-template-optimizer.png +:::{image} /deploy-manage/images/cloud-autoops-template-optimizer.png :alt: The Template Optimizer view ::: diff --git a/deploy-manage/monitor/cloud-health-perf.md b/deploy-manage/monitor/cloud-health-perf.md index 7fb7cfff12..b9de218a4e 100644 --- a/deploy-manage/monitor/cloud-health-perf.md +++ b/deploy-manage/monitor/cloud-health-perf.md @@ -31,7 +31,7 @@ The **Health** page provides the following information: * Health issues for {{kib}}, Enterprise Search, 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-es-health-page.png +:::{image} /deploy-manage/images/cloud-es-health-page.png :alt: {{es}} Health page ::: @@ -41,7 +41,7 @@ The **Health** page provides the following information: You can also search and filter the table based on affected resources, such as indices, repositories, nodes, or SLM policies. Individual issues can be further expanded to get more details and guided troubleshooting. -:::{image} /images/cloud-es-health-page-table.png +:::{image} /deploy-manage/images/cloud-es-health-page-table.png :alt: {{es}} Health page with details and troubleshooting ::: @@ -121,7 +121,7 @@ Elastic Cloud allows smaller instance sizes to get temporarily boosted vCPU when You can check the **Monitoring > Performance > CPU Credits** section of the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), and find the related metrics: -:::{image} /images/cloud-metrics-credits.png +:::{image} /deploy-manage/images/cloud-metrics-credits.png :alt: CPU usage versus CPU credits over time ::: diff --git a/deploy-manage/monitor/ec-memory-pressure.md b/deploy-manage/monitor/ec-memory-pressure.md index 1bfd8d9ed4..899d0ee63c 100644 --- a/deploy-manage/monitor/ec-memory-pressure.md +++ b/deploy-manage/monitor/ec-memory-pressure.md @@ -14,7 +14,7 @@ In addition to the more detailed [cluster performance metrics](/deploy-manage/mo The percentage number used in the JVM memory pressure indicator is actually the fill rate of the old generation pool. For a detailed explanation of why this metric is used, refer to [Understanding memory pressure](https://www.elastic.co/blog/found-understanding-memory-pressure-indicator/). -:::{image} /images/cloud-memory-pressure-indicator.png +:::{image} /deploy-manage/images/cloud-memory-pressure-indicator.png :alt: Memory pressure indicator ::: diff --git a/deploy-manage/monitor/monitoring-data/beats-page.md b/deploy-manage/monitor/monitoring-data/beats-page.md index 74919921b4..87f7482a02 100644 --- a/deploy-manage/monitor/monitoring-data/beats-page.md +++ b/deploy-manage/monitor/monitoring-data/beats-page.md @@ -16,7 +16,7 @@ applies_to: If you are monitoring Beats, the **Stack Monitoring** page in {{kib}} contains a panel for Beats in the cluster overview. -:::{image} /images/kibana-monitoring-beats.png +:::{image} /deploy-manage/images/kibana-monitoring-beats.png :alt: Monitoring Beats :screenshot: ::: @@ -25,7 +25,7 @@ To view an overview of the Beats data in the cluster, click **Overview**. The ov To view a listing of the individual Beat instances in the cluster, click **Beats**. The table listing shows each Beat instance that reports data to the monitoring cluster. All columns are sortable. Clicking a Beat name takes you to the detail page. For example: -:::{image} /images/kibana-monitoring-beats-detail.png +:::{image} /deploy-manage/images/kibana-monitoring-beats-detail.png :alt: Monitoring details for Filebeat :screenshot: ::: diff --git a/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md b/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md index 141a461d83..4c10e71f8f 100644 --- a/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md +++ b/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md @@ -14,7 +14,7 @@ applies_to: The {{stack}} {{monitor-features}} provide [Alerting rules](../../../explore-analyze/alerts-cases/alerts.md) out-of-the box to notify you of potential issues in the {{stack}}. These rules are preconfigured based on the best practices recommended by Elastic. However, you can tailor them to meet your specific needs. -:::{image} /images/kibana-monitoring-kibana-alerting-notification.png +:::{image} /deploy-manage/images/kibana-monitoring-kibana-alerting-notification.png :alt: {{kib}} alerting notifications in {{stack-monitor-app}} :screenshot: ::: diff --git a/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md b/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md index 9838fdfe72..d034bf37b8 100644 --- a/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md +++ b/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md @@ -16,7 +16,7 @@ applies_to: You can drill down into the status of your {{es}} cluster in {{kib}} by clicking the [Overview](#cluster-overview-page), [Nodes](#nodes-page), [Indices](#indices-overview-page) and [Logs](#logs-monitor-page) links on the **Stack Monitoring** page. -:::{image} /images/kibana-monitoring-elasticsearch.png +:::{image} /deploy-manage/images/kibana-monitoring-elasticsearch.png :alt: Monitoring clusters :screenshot: ::: @@ -35,7 +35,7 @@ Conditions that require your attention are listed at the top of the Clusters pag The panel at the top shows the current cluster statistics, the charts show the search and indexing performance over time, and the table at the bottom shows information about any shards that are being recovered. If you use {{filebeat}} to collect log data from this cluster, you can also see its recent logs. -:::{image} /images/kibana-monitoring-overview.png +:::{image} /deploy-manage/images/kibana-monitoring-overview.png :alt: Elasticsearch Cluster Overview :screenshot: ::: diff --git a/deploy-manage/monitor/monitoring-data/kibana-page.md b/deploy-manage/monitor/monitoring-data/kibana-page.md index d44d8103ec..6bae59aa30 100644 --- a/deploy-manage/monitor/monitoring-data/kibana-page.md +++ b/deploy-manage/monitor/monitoring-data/kibana-page.md @@ -16,7 +16,7 @@ applies_to: To view the key metrics that indicate the overall health of {{kib}} itself, click **Overview** in the {{kib}} section of the **Stack Monitoring** page. -:::{image} /images/kibana-monitoring-kibana-overview.png +:::{image} /deploy-manage/images/kibana-monitoring-kibana-overview.png :alt: Kibana Overview :screenshot: ::: diff --git a/deploy-manage/monitor/monitoring-data/logstash-page.md b/deploy-manage/monitor/monitoring-data/logstash-page.md index ed43c4096f..ed49ac1de7 100644 --- a/deploy-manage/monitor/monitoring-data/logstash-page.md +++ b/deploy-manage/monitor/monitoring-data/logstash-page.md @@ -16,7 +16,7 @@ applies_to: If you are monitoring Logstash nodes, click **Overview** in the Logstash section of the **Stack Monitoring** page in {{kib}}. You can view the overall health of the Logstash nodes. -:::{image} /images/kibana-monitoring-logstash-overview.png +:::{image} /deploy-manage/images/kibana-monitoring-logstash-overview.png :alt: Logstash Overview :screenshot: ::: diff --git a/deploy-manage/monitor/stack-monitoring.md b/deploy-manage/monitor/stack-monitoring.md index fd9a9ae69f..1364b8399e 100644 --- a/deploy-manage/monitor/stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring.md @@ -36,7 +36,7 @@ You can collect and ship data directly to your monitoring cluster rather than ro The following diagram illustrates a typical monitoring architecture with separate production and monitoring clusters. This example shows {{metricbeat}}, but you can use {{agent}} instead. -:::{image} /images/elasticsearch-reference-architecture.png +:::{image} /deploy-manage/images/elasticsearch-reference-architecture.png :alt: A typical monitoring environment ::: diff --git a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md index a02f7b5293..98abde274b 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md @@ -18,7 +18,7 @@ You can use {{metricbeat}} to collect data about {{es}} and ship it to the monit Want to use {{agent}} instead? Refer to [Collecting monitoring data with {{agent}}](collecting-monitoring-data-with-elastic-agent.md). ::: -:::{image} /images/elasticsearch-reference-metricbeat.png +:::{image} /deploy-manage/images/elasticsearch-reference-metricbeat.png :alt: Example monitoring architecture :width: 550px ::: diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md index 0b2959484d..6f65caafb9 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md @@ -86,7 +86,7 @@ If you are using a separate monitoring cluster, you do not need to turn on data On the **Stack Monitoring** page, you’ll see cluster alerts that require your attention and a summary of the available monitoring metrics for {{es}}, Logstash, {{kib}}, and Beats. To view additional information, click the **Overview**, **Nodes**, **Indices**, or **Instances** links. For more information about these metrics, refer to [](../monitoring-data/visualizing-monitoring-data.md). For information about configuring alerts for these metrics, refer to [](/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md). -:::{image} /images/kibana-monitoring-dashboard.png +:::{image} /deploy-manage/images/kibana-monitoring-dashboard.png :alt: Monitoring dashboard :screenshot: ::: diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md index 7a23905e34..8eaa2b1613 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md @@ -16,7 +16,7 @@ Yu can use {{metricbeat}} to collect data about {{kib}} and ship it to the monit To learn about monitoring in general, refer to [](/deploy-manage/monitor/stack-monitoring.md). -:::{image} /images/kibana-metricbeat.png +:::{image} /deploy-manage/images/kibana-metricbeat.png :alt: Example monitoring architecture :width: 450px ::: diff --git a/deploy-manage/reference-architectures/hotfrozen-high-availability.md b/deploy-manage/reference-architectures/hotfrozen-high-availability.md index 48c4c70869..76df4710bf 100644 --- a/deploy-manage/reference-architectures/hotfrozen-high-availability.md +++ b/deploy-manage/reference-architectures/hotfrozen-high-availability.md @@ -38,7 +38,7 @@ This Hot/Frozen – High Availability architecture is intended for organizations ## Architecture [hot-frozen-architecture-diagram] -:::{image} ../../images/reference-architectures-hot-frozen.png +:::{image} /deploy-manage/images/reference-architectures-hot-frozen.png :alt: A Hot/Frozen Highly available architecture ::: @@ -64,11 +64,11 @@ This table shows our specific recommendations for nodes in a Hot/Frozen architec | Type | AWS | Azure | GCP | Physical | | --- | --- | --- | --- | --- | -| ![Hot data node](../../images/reference-architectures-hot.png "") | c6gd | f32sv2 | N2 | 16-32 vCPU
64 GB RAM
2-6 TB NVMe SSD | -| ![Frozen data node](../../images/reference-architectures-frozen.png "") | i3en | e8dsv4 | N2 | 8 vCPU
64 GB RAM
6-20+ TB NVMe SSD
Depending on days cached | -| ![Machine learning node](../../images/reference-architectures-machine-learning.png "") | m6gd | f16sv2 | N2 | 16 vCPU
64 GB RAM
256 GB SSD | -| ![Master node](../../images/reference-architectures-master.png "") | c5d | f16sv2 | N2 | 8 vCPU
16 GB RAM
256 GB SSD | -| ![Kibana node](../../images/reference-architectures-kibana.png "") | c6gd | f16sv2 | N2 | 8-16 vCPU
8 GB RAM
256 GB SSD | +| ![Hot data node](/deploy-manage/images/reference-architectures-hot.png "") | c6gd | f32sv2 | N2 | 16-32 vCPU
64 GB RAM
2-6 TB NVMe SSD | +| ![Frozen data node](/deploy-manage/images/reference-architectures-frozen.png "") | i3en | e8dsv4 | N2 | 8 vCPU
64 GB RAM
6-20+ TB NVMe SSD
Depending on days cached | +| ![Machine learning node](/deploy-manage/images/reference-architectures-machine-learning.png "") | m6gd | f16sv2 | N2 | 16 vCPU
64 GB RAM
256 GB SSD | +| ![Master node](/deploy-manage/images/reference-architectures-master.png "") | c5d | f16sv2 | N2 | 8 vCPU
16 GB RAM
256 GB SSD | +| ![Kibana node](/deploy-manage/images/reference-architectures-kibana.png "") | c6gd | f16sv2 | N2 | 8-16 vCPU
8 GB RAM
256 GB SSD | ## Important considerations [hot-frozen-considerations] diff --git a/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md b/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md index a91d17c715..383fa133ee 100644 --- a/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md +++ b/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md @@ -28,7 +28,7 @@ With this method, you can only remove trusted environments relying exclusively o 2. In the list of trusted environments, locate the one you want to remove. 3. Remove it using the corresponding `delete` icon. - :::{image} ../../images/cloud-delete-trust-environment.png + :::{image} /deploy-manage/images/cloud-delete-trust-environment.png :alt: button for deleting a trusted environment ::: @@ -42,7 +42,7 @@ With this method, you can only remove trusted environments relying exclusively o 2. In the list of trusted environments, locate the one you want to edit. 3. Open its details by selecting the `Edit` icon. - :::{image} ../../images/cloud-edit-trust-environment.png + :::{image} /deploy-manage/images/cloud-edit-trust-environment.png :alt: button for editing a trusted environment ::: diff --git a/deploy-manage/remote-clusters/ec-migrate-ccs.md b/deploy-manage/remote-clusters/ec-migrate-ccs.md index 5403f2bc3d..31f1360f3e 100644 --- a/deploy-manage/remote-clusters/ec-migrate-ccs.md +++ b/deploy-manage/remote-clusters/ec-migrate-ccs.md @@ -25,7 +25,7 @@ You can use a PUT request to update your deployment, changing both the deploymen You can also find the template in the [list of templates available for each region](cloud://reference/cloud-hosted/ec-regions-templates-instances.md). - :::{image} ../../images/cloud-ec-migrate-deployment-template(2).png + :::{image} /deploy-manage/images/cloud-ec-migrate-deployment-template(2).png :alt: Deployment Template ID :screenshot: ::: @@ -271,7 +271,7 @@ You can make this change in the user [{{ecloud}} Console](https://cloud.elastic. 1. From the deployment menu, open the **Snapshots** page and click **Take Snapshot now**. Wait for the snapshot to finish. 2. From the main **Deployments** page, click **Create deployment**. Next to **Settings** toggle on **Restore snapshot data**, and then select your deployment and the snapshot that you created. - :::{image} ../../images/cloud-ec-create-from-snapshot-updated.png + :::{image} /deploy-manage/images/cloud-ec-create-from-snapshot-updated.png :alt: Create a Deployment using a snapshot :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md index f1cf440759..6d397aeb0d 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md @@ -107,7 +107,7 @@ If you later need to update the remote connection with different permissions, yo 3. Click **Copy root certificate** and paste it into a new file. The root certificate is the last certificate shown in the chain. 4. Save that file as `.crt`. It is now ready to be uploaded. - :::{image} ../../images/cloud-remote-clusters-proxy-certificate.png + :::{image} /deploy-manage/images/cloud-remote-clusters-proxy-certificate.png :alt: Certificate to copy from the chain ::: @@ -207,7 +207,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. * **Server name**: This value can be found on the **Security** page of the {{ech}} deployment you want to use as a remote. - :::{image} ../../images/cloud-ce-copy-remote-cluster-parameters.png + :::{image} /deploy-manage/images/cloud-ce-copy-remote-cluster-parameters.png :alt: Remote Cluster Parameters in Deployment :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md index edbab1f492..df64b3f678 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md @@ -145,7 +145,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. * **Server name**: This value can be found on the **Security** page of the {{ech}} deployment you want to use as a remote. - :::{image} ../../images/cloud-ce-copy-remote-cluster-parameters.png + :::{image} /deploy-manage/images/cloud-ce-copy-remote-cluster-parameters.png :alt: Remote Cluster Parameters in Deployment :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md index 109ed05504..cbaa499258 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md @@ -83,7 +83,7 @@ By default, any deployment that you create trusts all other deployments in the s * Trust all my deployments - All of your organization’s deployments created while this option is selected already trust each other. If you keep this option, that includes any deployments you’ll create in the future. You can directly jump to [Connect to the remote cluster](/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md#ec_connect_to_the_remote_cluster) to finalize the CCS or CCR configuration. * Trust no deployment - New deployments won’t trust any other deployment when they are created. You can instead configure trust individually for each of them in their security settings, as described in the next section. -:::{image} ../../images/cloud-ec-account-trust-management.png +:::{image} /deploy-manage/images/cloud-ec-account-trust-management.png :alt: Trust management at the account Level :screenshot: ::: @@ -181,7 +181,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. * **Server name**: This value can be found on the **Security** page of the {{ech}} deployment you want to use as a remote. - :::{image} ../../images/cloud-ce-copy-remote-cluster-parameters.png + :::{image} /deploy-manage/images/cloud-ce-copy-remote-cluster-parameters.png :alt: Remote Cluster Parameters in Deployment :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md index 57f9eaad28..f779f84524 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md @@ -233,7 +233,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. * **Server name**: This value can be found on the **Security** page of the {{ech}} deployment you want to use as a remote. - :::{image} ../../images/cloud-ce-copy-remote-cluster-parameters.png + :::{image} /deploy-manage/images/cloud-ce-copy-remote-cluster-parameters.png :alt: Remote Cluster Parameters in Deployment :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md b/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md index 5fb727793f..44bcd4e1dd 100644 --- a/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md +++ b/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md @@ -28,7 +28,7 @@ With this method, you can only remove trusted environments relying exclusively o 2. In the list of trusted environments, locate the one you want to remove. 3. Remove it using the corresponding `delete` icon. - :::{image} ../../images/cloud-enterprise-delete-trust-environment.png + :::{image} /deploy-manage/images/cloud-enterprise-delete-trust-environment.png :alt: button for deleting a trusted environment ::: @@ -42,7 +42,7 @@ With this method, you can only remove trusted environments relying exclusively o 2. In the list of trusted environments, locate the one you want to edit. 3. Open its details by selecting the `Edit` icon. - :::{image} ../../images/cloud-enterprise-edit-trust-environment.png + :::{image} /deploy-manage/images/cloud-enterprise-edit-trust-environment.png :alt: button for editing a trusted environment ::: diff --git a/deploy-manage/remote-clusters/ece-migrate-ccs.md b/deploy-manage/remote-clusters/ece-migrate-ccs.md index 6bc9a5de0f..b54d269fc3 100644 --- a/deploy-manage/remote-clusters/ece-migrate-ccs.md +++ b/deploy-manage/remote-clusters/ece-migrate-ccs.md @@ -22,7 +22,7 @@ You can make this change in the user Cloud UI. The only drawback of this method 2. From the deployment menu, open the **Snapshots** page and click **Take Snapshot now**. Wait for the snapshot to finish. 3. From the main **Deployments** page, click **Create deployment**. Next to **Settings** toggle on **Restore snapshot data**, and then select your deployment and the snapshot that you created. - :::{image} ../../images/cloud-enterprise-ce-create-from-snapshot-updated.png + :::{image} /deploy-manage/images/cloud-enterprise-ce-create-from-snapshot-updated.png :alt: Create a Deployment using a snapshot :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md index e036dd2e25..1146eeff72 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md @@ -152,7 +152,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. * **Server name**: This value can be found on the **Security** page of the {{ece}} deployment you want to use as a remote. - :::{image} ../../images/cloud-enterprise-ce-copy-remote-cluster-parameters.png + :::{image} /deploy-manage/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png :alt: Remote Cluster Parameters in Deployment :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md index 6e1c1535cc..0f83c48041 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md @@ -104,7 +104,7 @@ If you later need to update the remote connection with different permissions, yo 3. Click **Copy root certificate** and paste it into a new file. The root certificate is the last certificate shown in the chain. 4. Save that file as `.crt`. It is now ready to be uploaded. - :::{image} ../../images/cloud-enterprise-remote-clusters-proxy-certificate.png + :::{image} /deploy-manage/images/cloud-enterprise-remote-clusters-proxy-certificate.png :alt: Certificate to copy from the chain ::: @@ -224,7 +224,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. * **Server name**: This value can be found on the **Security** page of the {{ece}} deployment you want to use as a remote. - :::{image} ../../images/cloud-enterprise-ce-copy-remote-cluster-parameters.png + :::{image} /deploy-manage/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png :alt: Remote Cluster Parameters in Deployment :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md index 1a436be28d..3fa409911c 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md @@ -82,7 +82,7 @@ By default, any deployment that you or your users create trusts all other deploy * Trust all my deployments - All of your organization’s deployments created while this option is selected already trust each other. If you keep this option, that includes any deployments you’ll create in the future. You can directly jump to [Connect to the remote cluster](/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md#ece_connect_to_the_remote_cluster) to finalize the CCS or CCR configuration. * Trust no deployment - New deployments won’t trust any other deployment when they are created. You can instead configure trust individually for each of them in their security settings, as described in the next section. -:::{image} ../../images/cloud-enterprise-ce-environment-trust-management.png +:::{image} /deploy-manage/images/cloud-enterprise-ce-environment-trust-management.png :alt: Trust management at the environment Level :screenshot: ::: @@ -180,7 +180,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. * **Server name**: This value can be found on the **Security** page of the {{ece}} deployment you want to use as a remote. - :::{image} ../../images/cloud-enterprise-ce-copy-remote-cluster-parameters.png + :::{image} /deploy-manage/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png :alt: Remote Cluster Parameters in Deployment :screenshot: ::: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md index 71e88888e9..7c44080bee 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md @@ -231,7 +231,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API. * **Server name**: This value can be found on the **Security** page of the {{ece}} deployment you want to use as a remote. - :::{image} ../../images/cloud-enterprise-ce-copy-remote-cluster-parameters.png + :::{image} /deploy-manage/images/cloud-enterprise-ce-copy-remote-cluster-parameters.png :alt: Remote Cluster Parameters in Deployment :screenshot: ::: diff --git a/deploy-manage/security/aws-privatelink-traffic-filters.md b/deploy-manage/security/aws-privatelink-traffic-filters.md index 4eebda33eb..ae2bbdc1a4 100644 --- a/deploy-manage/security/aws-privatelink-traffic-filters.md +++ b/deploy-manage/security/aws-privatelink-traffic-filters.md @@ -135,7 +135,7 @@ The mapping will be different for your region. Our production VPC Service for `u Use [the service name for your region](/deploy-manage/security/aws-privatelink-traffic-filters.md#ec-private-link-service-names-aliases). - :::{image} /images/cloud-ec-private-link-service.png + :::{image} /deploy-manage/images/cloud-ec-private-link-service.png :alt: PrivateLink :screenshot: ::: @@ -146,7 +146,7 @@ The mapping will be different for your region. Our production VPC Service for `u 1. Create a *Private hosted zone*. Consult *Private hosted zone domain name* in *PrivateLink service names and aliases* for the name of the zone. For example, in *us-east-1* use `vpce.us-east-1.aws.elastic-cloud.com` as the zone domain name. Don’t forget to associate the zone with your VPC. - :::{image} /images/cloud-ec-private-link-private-hosted-zone-example.png + :::{image} /deploy-manage/images/cloud-ec-private-link-private-hosted-zone-example.png :alt: Private hosted zone example :screenshot: ::: @@ -155,7 +155,7 @@ The mapping will be different for your region. Our production VPC Service for `u Follow the [AWS instructions](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html) for details on creating a CNAME record which points to your VPC endpoint DNS name. - :::{image} /images/cloud-ec-private-link-cname.png + :::{image} /deploy-manage/images/cloud-ec-private-link-cname.png :alt: PrivateLink CNAME :screenshot: ::: @@ -212,7 +212,7 @@ Follow these high-level steps to add private link rules to your deployments. Having trouble finding your VPC endpoint ID? You can find it in the AWS console. -:::{image} /images/cloud-ec-private-link-endpoint-id.png +:::{image} /deploy-manage/images/cloud-ec-private-link-endpoint-id.png :alt: VPC Endpoint ID :screenshot: ::: diff --git a/deploy-manage/security/azure-private-link-traffic-filters.md b/deploy-manage/security/azure-private-link-traffic-filters.md index 8aa0cfd968..f205b6f398 100644 --- a/deploy-manage/security/azure-private-link-traffic-filters.md +++ b/deploy-manage/security/azure-private-link-traffic-filters.md @@ -147,12 +147,12 @@ Follow these high-level steps to add Private Link rules to your deployments. 2. Select **JSON View**. 3. Copy the value of the **properties.resourceGUID** property. -:::{image} /images/cloud-ec-private-link-azure-json-view.png +:::{image} /deploy-manage/images/cloud-ec-private-link-azure-json-view.png :alt: Private endpoint JSON View :screenshot: ::: -:::{image} /images/cloud-ec-private-link-azure-properties.png +:::{image} /deploy-manage/images/cloud-ec-private-link-azure-properties.png :alt: Private endpoint Properties :screenshot: ::: @@ -317,7 +317,7 @@ Azure supports inter-region Private Link as described in the [Azure documentatio This means your deployment on {{ecloud}} can be in a different region than the Private Link endpoints or the clients that consume the deployment endpoints. -:::{image} /images/cloud-ce-azure-inter-region-pl.png +:::{image} /deploy-manage/images/cloud-ce-azure-inter-region-pl.png :alt: Inter-region Private Link :screenshot: ::: diff --git a/deploy-manage/security/install-stack-demo-secure.md b/deploy-manage/security/install-stack-demo-secure.md index db34807184..cfa523849f 100644 --- a/deploy-manage/security/install-stack-demo-secure.md +++ b/deploy-manage/security/install-stack-demo-secure.md @@ -884,7 +884,7 @@ View your system metrics data: 2. In the query field, search for `Metrics System`. 3. Select the `[Metrics System] Host overview` link. The {{kib}} Dashboard opens with visualizations of host metrics including CPU usage, memory usage, running processes, and more. - :::{image} /images/elastic-stack-install-stack-metrics-dashboard.png + :::{image} /deploy-manage/images/elastic-stack-install-stack-metrics-dashboard.png :alt: The System metrics host overview showing CPU usage, memory usage, and other visualizations ::: diff --git a/deploy-manage/security/manually-configure-security-in-self-managed-cluster.md b/deploy-manage/security/manually-configure-security-in-self-managed-cluster.md index d4d1971d18..a79552ddc3 100644 --- a/deploy-manage/security/manually-configure-security-in-self-managed-cluster.md +++ b/deploy-manage/security/manually-configure-security-in-self-managed-cluster.md @@ -35,7 +35,7 @@ Even with security enabled, never expose {{es}} to public internet traffic. Usin ## Common security scenarios -:::{image} ../../images/elasticsearch-reference-elastic-security-overview.png +:::{image} /deploy-manage/images/elasticsearch-reference-elastic-security-overview.png :alt: Elastic Security layers ::: diff --git a/deploy-manage/security/secure-http-communications.md b/deploy-manage/security/secure-http-communications.md index 76831407d7..5787ae2701 100644 --- a/deploy-manage/security/secure-http-communications.md +++ b/deploy-manage/security/secure-http-communications.md @@ -132,7 +132,7 @@ If you haven’t already, start {{kib}} and connect it to {{es}} using the [enro This role mapping will assign the `kibana_system` role to any user that matches the included mapping rule, which is set to equal the client certificate’s DN attribute: - ![Role mapping for the {{kib}} client certificate](/images/kibana-mutual-tls-role-mapping.png "") + ![Role mapping for the {{kib}} client certificate](/deploy-manage/images/kibana-mutual-tls-role-mapping.png "") For more information, see [](/deploy-manage/users-roles/cluster-or-deployment-auth/mapping-users-groups-to-roles.md). diff --git a/deploy-manage/tools/cross-cluster-replication.md b/deploy-manage/tools/cross-cluster-replication.md index 8a7e696aa9..dfc2445bd0 100644 --- a/deploy-manage/tools/cross-cluster-replication.md +++ b/deploy-manage/tools/cross-cluster-replication.md @@ -86,7 +86,7 @@ Disaster recovery provides your mission-critical applications with the tolerance In this configuration, data is replicated from the production datacenter to the disaster recovery datacenter. Because the follower indices replicate the leader index, your application can use the disaster recovery datacenter if the production datacenter is unavailable. -:::{image} ../../images/elasticsearch-reference-ccr-arch-disaster-recovery.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-arch-disaster-recovery.png :alt: Production datacenter that replicates data to a disaster recovery datacenter ::: @@ -97,7 +97,7 @@ You can replicate data from one datacenter to multiple datacenters. This configu In the following diagram, data from Datacenter A is replicated to Datacenter B and Datacenter C, which both have a read-only copy of the leader index from Datacenter A. -:::{image} ../../images/elasticsearch-reference-ccr-arch-multiple-dcs.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-arch-multiple-dcs.png :alt: Production datacenter that replicates data to two other datacenters ::: @@ -106,7 +106,7 @@ In the following diagram, data from Datacenter A is replicated to Datacenter B a You can replicate data across multiple datacenters to form a replication chain. In the following diagram, Datacenter A contains the leader index. Datacenter B replicates data from Datacenter A, and Datacenter C replicates from the follower indices in Datacenter B. The connection between these datacenters forms a chained replication pattern. -:::{image} ../../images/elasticsearch-reference-ccr-arch-chain-dcs.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-arch-chain-dcs.png :alt: Three datacenters connected to form a replication chain ::: @@ -117,7 +117,7 @@ In a [bi-directional replication](https://www.elastic.co/blog/bi-directional-rep This configuration requires no manual intervention when a cluster or datacenter is unavailable. In the following diagram, if Datacenter A is unavailable, you can continue using Datacenter B without manual failover. When Datacenter A comes online, replication resumes between the clusters. -:::{image} ../../images/elasticsearch-reference-ccr-arch-bi-directional.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-arch-bi-directional.png :alt: Bi-directional configuration where each cluster contains both a leader index and follower indices ::: @@ -130,7 +130,7 @@ Bringing data closer to your users or application server can reduce latency and In the following diagram, data is replicated from one datacenter to three additional datacenters, each in their own region. The central datacenter contains the leader index, and the additional datacenters contain follower indices that replicate data in that particular region. This configuration puts data closer to the application accessing it. -:::{image} ../../images/elasticsearch-reference-ccr-arch-data-locality.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-arch-data-locality.png :alt: A centralized datacenter replicated across three other datacenters ::: @@ -143,7 +143,7 @@ For example, a large global bank might have 100 {{es}} clusters around the world In the following diagram, data from three datacenters in different regions is replicated to a centralized reporting cluster. This configuration enables you to copy data from regional hubs to a central cluster, where you can run all reports locally. -:::{image} ../../images/elasticsearch-reference-ccr-arch-central-reporting.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-arch-central-reporting.png :alt: Three clusters in different regions sending data to a centralized reporting cluster for analysis ::: diff --git a/deploy-manage/tools/cross-cluster-replication/_connect_to_a_remote_cluster.md b/deploy-manage/tools/cross-cluster-replication/_connect_to_a_remote_cluster.md index 8e98139c9c..7f27617fb8 100644 --- a/deploy-manage/tools/cross-cluster-replication/_connect_to_a_remote_cluster.md +++ b/deploy-manage/tools/cross-cluster-replication/_connect_to_a_remote_cluster.md @@ -14,7 +14,7 @@ applies_to: To replicate an index on a remote cluster (Cluster A) to a local cluster (Cluster B), you configure Cluster A as a remote on Cluster B. -:::{image} ../../../images/elasticsearch-reference-ccr-tutorial-clusters.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-tutorial-clusters.png :alt: ClusterA contains the leader index and ClusterB contains the follower index ::: diff --git a/deploy-manage/tools/cross-cluster-replication/bi-directional-disaster-recovery.md b/deploy-manage/tools/cross-cluster-replication/bi-directional-disaster-recovery.md index f8bcd6804d..5688c99052 100644 --- a/deploy-manage/tools/cross-cluster-replication/bi-directional-disaster-recovery.md +++ b/deploy-manage/tools/cross-cluster-replication/bi-directional-disaster-recovery.md @@ -24,7 +24,7 @@ This tutorial works with {{ls}} as the source of ingestion. It takes advantage o * Setting up bi-directional cross-cluster replication with exclusion patterns. * Setting up {{ls}} with multiple hosts to allow automatic load balancing and switching during disasters. -:::{image} ../../../images/elasticsearch-reference-ccr-bi-directional-disaster-recovery.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-bi-directional-disaster-recovery.png :alt: Bi-directional cross cluster replication failover and failback ::: diff --git a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md index b378edf887..d0bc758b3b 100644 --- a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md +++ b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md @@ -26,7 +26,7 @@ To create an auto-follow pattern from Stack Management in {{kib}}: As new indices matching these patterns are created on the remote, {{es}} automatically replicates them to local follower indices. -:::{image} ../../../images/elasticsearch-reference-auto-follow-patterns.png +:::{image} /deploy-manage/images/elasticsearch-reference-auto-follow-patterns.png :alt: The Auto-follow patterns page in {{kib}} :screenshot: ::: diff --git a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md index 95ee053934..c29d3de9b9 100644 --- a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md +++ b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md @@ -25,7 +25,7 @@ To create a follower index from Stack Management in {{kib}}: When you index documents into your leader index, {{es}} replicates the documents in the follower index. -:::{image} ../../../images/elasticsearch-reference-ccr-follower-index.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-follower-index.png :alt: The Cross-Cluster Replication page in {{kib}} :screenshot: ::: diff --git a/deploy-manage/tools/cross-cluster-replication/uni-directional-disaster-recovery.md b/deploy-manage/tools/cross-cluster-replication/uni-directional-disaster-recovery.md index 673023e7dc..fa643e4556 100644 --- a/deploy-manage/tools/cross-cluster-replication/uni-directional-disaster-recovery.md +++ b/deploy-manage/tools/cross-cluster-replication/uni-directional-disaster-recovery.md @@ -22,7 +22,7 @@ Learn how to failover and failback between two clusters based on uni-directional * Failover - If `clusterA` goes offline, `clusterB` needs to "promote" follower indices to regular indices to allow write operations. All ingestion will need to be redirected to `clusterB`, this is controlled by the clients ({{ls}}, {{beats}}, {{agents}}, etc). * Failback - When `clusterA` is back online, it assumes the role of a follower and replicates the leader indices from `clusterB`. -:::{image} ../../../images/elasticsearch-reference-ccr-uni-directional-disaster-recovery.png +:::{image} /deploy-manage/images/elasticsearch-reference-ccr-uni-directional-disaster-recovery.png :alt: Uni-directional cross cluster replication failover and failback ::: diff --git a/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-new-deployment.md b/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-new-deployment.md index edf06bf6f0..2439405b4a 100644 --- a/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-new-deployment.md +++ b/deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-into-new-deployment.md @@ -13,7 +13,7 @@ applies_to: 1. First, [create a new deployment](../../deploy/cloud-enterprise/create-deployment.md) and select **Restore snapshot data**. Select the deployment that you want to restore a snapshot *from*. If you don’t know the exact name, you can enter a few characters and then select from the list of matching deployments. 2. Select the snapshot that you want to restore from. If none is chosen, the latest successful snapshot from the cluster you selected is restored on the new cluster when you create it. - ![Restoring from a snapshot](../../../images/cloud-enterprise-restore-from-snapshot.png "") + ![Restoring from a snapshot](/deploy-manage/images/cloud-enterprise-restore-from-snapshot.png "") 3. Manually recreate users using the X-Pack security features or using Shield on the new cluster. User information is not included when you restore across clusters. diff --git a/deploy-manage/tools/snapshot-and-restore/google-cloud-storage-gcs-repository.md b/deploy-manage/tools/snapshot-and-restore/google-cloud-storage-gcs-repository.md index 1507d376d1..abc3de0412 100644 --- a/deploy-manage/tools/snapshot-and-restore/google-cloud-storage-gcs-repository.md +++ b/deploy-manage/tools/snapshot-and-restore/google-cloud-storage-gcs-repository.md @@ -50,7 +50,7 @@ To save deployment snapshots to the custom GCS repository: 1. Add a [secure setting](../../security/secure-settings.md) named `gcs.client.acme-snapshots.credentials_file` as a JSON block. Make sure that the client name is the same one you provided when configuring the snapshot repository. - :::{image} ../../../images/cloud-enterprise-ece-secure-settings.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-secure-settings.png :alt: GCS client secret configuration ::: diff --git a/deploy-manage/tools/snapshot-and-restore/minio-on-premise-repository.md b/deploy-manage/tools/snapshot-and-restore/minio-on-premise-repository.md index 9a22b41288..3a2cafe889 100644 --- a/deploy-manage/tools/snapshot-and-restore/minio-on-premise-repository.md +++ b/deploy-manage/tools/snapshot-and-restore/minio-on-premise-repository.md @@ -33,7 +33,7 @@ We recommend: * Using a single Minio endpoint with the Elastic Cloud Enterprise installation, to simplify repository management. * Securing access to the Minio endpoint with TLS. -:::{image} ../../../images/cloud-enterprise-ece-minio-large-arch.png +:::{image} /deploy-manage/images/cloud-enterprise-ece-minio-large-arch.png :alt: Architecture diagram :name: img-ece-minio-large-arch ::: @@ -104,7 +104,7 @@ You must add the new repository to Elastic Cloud Enterprise before it can be use } ``` - :::{image} ../../../images/cloud-enterprise-ece-minio-repository.png + :::{image} /deploy-manage/images/cloud-enterprise-ece-minio-repository.png :alt: Create form :name: img-ece-minio-repository ::: @@ -113,7 +113,7 @@ You must add the new repository to Elastic Cloud Enterprise before it can be use The Minio repository is now available from the drop-down list of repositories when creating deployments. -:::{image} ../../../images/cloud-enterprise-ece-minio-deployment.png +:::{image} /deploy-manage/images/cloud-enterprise-ece-minio-deployment.png :alt: Create deployment :name: img-ece-minio-deployment ::: diff --git a/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md b/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md index 8d269bab18..d95a6462ed 100644 --- a/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md +++ b/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md @@ -33,7 +33,7 @@ If the repository is still in use (for example by mounted searchable snapshots), :::: -:::{image} ../../../images/cloud-ec-elasticsearch-snapshots-of-other-deployments-aws-gcp.png +:::{image} /deploy-manage/images/cloud-ec-elasticsearch-snapshots-of-other-deployments-aws-gcp.png :alt: View of the old snapshot repository in the Cloud UI ::: diff --git a/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md b/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md index 2b54bb57d2..43741afcb9 100644 --- a/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md +++ b/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md @@ -40,7 +40,7 @@ If the repository is still in use (for example by mounted searchable snapshots), :::: -:::{image} ../../../images/cloud-ec-elasticsearch-snapshots-of-other-deployments.png +:::{image} /deploy-manage/images/cloud-ec-elasticsearch-snapshots-of-other-deployments.png :alt: View of the old snapshot repository in the Cloud UI ::: diff --git a/deploy-manage/users-roles/cloud-organization/user-roles.md b/deploy-manage/users-roles/cloud-organization/user-roles.md index c83200a198..f425188644 100644 --- a/deploy-manage/users-roles/cloud-organization/user-roles.md +++ b/deploy-manage/users-roles/cloud-organization/user-roles.md @@ -91,20 +91,20 @@ You can optionally [create custom roles in a project](/deploy-manage/users-roles | Name | Description | Available | | --- | --- | --- | -| Admin | Has full access to project management, properties, and security privileges. Admins log into projects with superuser role privileges. | [![Elasticsearch](../../../images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Observability](../../../images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Developer | Creates API keys, indices, data streams, adds connectors, and builds visualizations. | [![Elasticsearch](../../../images/serverless-es-badge.svg "")](../../../solutions/search.md) | -| Viewer | Has read-only access to project details, data, and features. | [![Elasticsearch](../../../images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Observability](../../../images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Editor | Configures all Observability or Security projects. Has read-only access to data indices. Has full access to all project features. | [![Observability](../../../images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Tier 1 analyst | Ideal for initial alert triage. General read access, can create dashboards and visualizations. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Tier 2 analyst | Ideal for alert triage and beginning the investigation process. Can create cases. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Tier 3 analyst | Deeper investigation capabilities. Access to rules, lists, cases, Osquery, and response actions. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Threat intelligence analyst | Access to alerts, investigation tools, and intelligence pages. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Rule author | Access to detection engineering and rule creation. Can create rules from available data sources and add exceptions to reduce false positives. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| SOC manager | Access to alerts, cases, investigation tools, endpoint policy management, and response actions. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Endpoint operations analyst | Access to endpoint response actions. Can manage endpoint policies, {{fleet}}, and integrations. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Platform engineer | Access to {{fleet}}, integrations, endpoints, and detection content. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Detections admin | All available detection engine permissions to include creating rule actions, such as notifications to third-party systems. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | -| Endpoint policy manager | Access to endpoint policy management and related artifacts. Can manage {{fleet}} and integrations. | [![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Admin | Has full access to project management, properties, and security privileges. Admins log into projects with superuser role privileges. | [![Elasticsearch](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Observability](/deploy-manage/images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Developer | Creates API keys, indices, data streams, adds connectors, and builds visualizations. | [![Elasticsearch](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md) | +| Viewer | Has read-only access to project details, data, and features. | [![Elasticsearch](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Observability](/deploy-manage/images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Editor | Configures all Observability or Security projects. Has read-only access to data indices. Has full access to all project features. | [![Observability](/deploy-manage/images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Tier 1 analyst | Ideal for initial alert triage. General read access, can create dashboards and visualizations. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Tier 2 analyst | Ideal for alert triage and beginning the investigation process. Can create cases. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Tier 3 analyst | Deeper investigation capabilities. Access to rules, lists, cases, Osquery, and response actions. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Threat intelligence analyst | Access to alerts, investigation tools, and intelligence pages. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Rule author | Access to detection engineering and rule creation. Can create rules from available data sources and add exceptions to reduce false positives. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| SOC manager | Access to alerts, cases, investigation tools, endpoint policy management, and response actions. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Endpoint operations analyst | Access to endpoint response actions. Can manage endpoint policies, {{fleet}}, and integrations. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Platform engineer | Access to {{fleet}}, integrations, endpoints, and detection content. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Detections admin | All available detection engine permissions to include creating rule actions, such as notifications to third-party systems. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | +| Endpoint policy manager | Access to endpoint policy management and related artifacts. Can manage {{fleet}} and integrations. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) | ## Role scopes [ec-role-scoping] diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/access-agreement.md b/deploy-manage/users-roles/cluster-or-deployment-auth/access-agreement.md index 31c0e84479..3fa128b599 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/access-agreement.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/access-agreement.md @@ -37,7 +37,7 @@ xpack.security.authc.providers: When you authenticate using `basic.basic1`, you’ll see the following agreement that you must acknowledge before you can access {{kib}}: -:::{image} ../../../images/kibana-access-agreement.png +:::{image} /deploy-manage/images/kibana-access-agreement.png :alt: Access Agreement UI :screenshot: ::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md index bca152fb38..8b725c232b 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md @@ -66,7 +66,7 @@ xpack.security.authc.providers: enabled: false ``` -:::{image} ../../../images/kibana-kibana-login.png +:::{image} /deploy-manage/images/kibana-kibana-login.png :alt: Login Selector UI :screenshot: ::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md index 71a4bdf495..1413f0ae2e 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md @@ -31,7 +31,7 @@ $$$kibana-privileges-all$$$ From the role management screen: -:::{image} ../../../images/kibana-assign-base-privilege.png +:::{image} /deploy-manage/images/kibana-assign-base-privilege.png :alt: Assign base privilege :screenshot: ::: @@ -76,7 +76,7 @@ Some features allow for finer access control than the `all` and `read` privilege From the role management screen: -:::{image} ../../../images/kibana-assign-subfeature-privilege.png +:::{image} /deploy-manage/images/kibana-assign-subfeature-privilege.png :alt: Assign feature privilege :screenshot: ::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-role-management.md b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-role-management.md index 43e6e6255f..b6ffd5bdbe 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-role-management.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-role-management.md @@ -43,7 +43,7 @@ Document-level and field-level security affords you even more granularity when i 2. `read` and `view_index_metadata` in the **Privileges** field.
-:::{image} ../../../images/kibana-create-role-index-example.png +:::{image} /deploy-manage/images/kibana-create-role-index-example.png :alt: Create role with index privileges :screenshot: ::: @@ -74,7 +74,7 @@ Document-level and field-level security affords you even more granularity when i ::::
-:::{image} ../../../images/kibana-create-role-dls-example.png +:::{image} /deploy-manage/images/kibana-create-role-dls-example.png :alt: Create role with DLS index privileges :screenshot: ::: @@ -97,7 +97,7 @@ You can assign the same privileges, document-level, and field-level as for [loca 3. The allowed actions in the **Privileges** field. (e.g. `read` and `view_index_metadata`)
-:::{image} ../../../images/kibana-create-role-remote-index-example.png +:::{image} /deploy-manage/images/kibana-create-role-remote-index-example.png :alt: Create role with remote index privileges :screenshot: ::: @@ -107,7 +107,7 @@ You can assign the same privileges, document-level, and field-level as for [loca To assign {{kib}} privileges to the role, click **Add {{kib}} privilege** in the {{kib}} section.
-:::{image} ../../../images/kibana-spaces-roles.png +:::{image} /deploy-manage/images/kibana-spaces-roles.png :alt: Add {{kib}} privileges :screenshot: :width: 650px @@ -127,7 +127,7 @@ When using the **Customize by feature** option, you can choose either **All**, * To apply your changes, click **Add {{kib}} privilege**. The privilege shows up under the {{kib}} privileges section of the role.
-:::{image} ../../../images/kibana-create-space-privilege.png +:::{image} /deploy-manage/images/kibana-create-space-privilege.png :alt: Add {{kib}} privilege :screenshot: ::: @@ -165,7 +165,7 @@ To view a summary of the privileges granted, click **View privilege summary**. 5. Click **Add {{kib}} privilege**.
-:::{image} ../../../images/kibana-privilege-example-1.png +:::{image} /deploy-manage/images/kibana-privilege-example-1.png :alt: Privilege example 1 :screenshot: :width: 650px @@ -183,7 +183,7 @@ To view a summary of the privileges granted, click **View privilege summary**. 7. Click **Add {{kib}} privilege**.
-:::{image} ../../../images/kibana-privilege-example-2.png +:::{image} /deploy-manage/images/kibana-privilege-example-2.png :alt: Privilege example 2 :screenshot: ::: @@ -200,7 +200,7 @@ To view a summary of the privileges granted, click **View privilege summary**. 7. Click **Add {{kib}} privilege**.
-:::{image} ../../../images/kibana-privilege-example-3.png +:::{image} /deploy-manage/images/kibana-privilege-example-3.png :alt: Privilege example 3 :screenshot: ::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/mapping-users-groups-to-roles.md b/deploy-manage/users-roles/cluster-or-deployment-auth/mapping-users-groups-to-roles.md index 37b87786ae..eb8d1c5ab0 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/mapping-users-groups-to-roles.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/mapping-users-groups-to-roles.md @@ -64,7 +64,7 @@ With **Role mappings**, you can: * View your configured role mappings * Create, edit, or delete role mappings -![Role mappings](../../../images/kibana-role-mappings-grid.png "") +![Role mappings](/deploy-manage/images/kibana-role-mappings-grid.png "") ### Required permissions [_required_permissions_8] @@ -87,11 +87,11 @@ Let’s create a `sales-users` role mapping, which assigns a `sales` role to use 1. Give the role mapping a name, and assign the `sales` role: - ![Create role mapping, step 1](../../../images/kibana-role-mappings-create-step-1.png "") + ![Create role mapping, step 1](/deploy-manage/images/kibana-role-mappings-create-step-1.png "") 2. Define the two rules, making sure to set the group to **Any are true**: - ![Create role mapping, step 2](../../../images/kibana-role-mappings-create-step-2.gif "") + ![Create role mapping, step 2](/deploy-manage/images/kibana-role-mappings-create-step-2.gif "") 1. When you're finished defining rules, click **Save role mapping**. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/native.md b/deploy-manage/users-roles/cluster-or-deployment-auth/native.md index 89b770e401..d6d1664d1e 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/native.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/native.md @@ -73,7 +73,7 @@ Elastic enables you to easily manage users in {{kib}} on the **Stack Management 4. Optional: assign [roles](/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md) to the user. 5. Click **Create user**. -:::{image} ../../../images/kibana-tutorial-secure-access-example-1-user.png +:::{image} /deploy-manage/images/kibana-tutorial-secure-access-example-1-user.png :alt: Create user UI :screenshot: ::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md b/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md index 0bf9ef2975..0afcca94bc 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md @@ -32,7 +32,7 @@ For more information about OpenID connect in Azure, refer to [Azure OAuth 2.0 an 1. Sign into the [Azure Portal](https://portal.azure.com/) and go to **Entra** (formerly Azure Active Directory). From there, select **App registrations** > **New registration** to register a new application. - :::{image} ../../../images/cloud-ec-oidc-new-app-azure.png + :::{image} /deploy-manage/images/cloud-ec-oidc-new-app-azure.png :alt: A screenshot of the Azure Owned Applications tab on the New Registration page ::: @@ -50,7 +50,7 @@ For more information about OpenID connect in Azure, refer to [Azure OAuth 2.0 an 1. From the application that you created, go to **Certificates & secrets** and create a new secret under **Client secrets** > **New client secret**. - :::{image} ../../../images/cloud-ec-oidc-oauth-create-credentials-azure.png + :::{image} /deploy-manage/images/cloud-ec-oidc-oauth-create-credentials-azure.png :alt: A screenshot of the Azure Add a Client Secret dialog ::: @@ -66,7 +66,7 @@ For more information about OpenID connect in Azure, refer to [Azure OAuth 2.0 an To learn more about the available endpoints provided by Microsoft Azure, refer to the **Endpoints** details in the application that you configured. - :::{image} ../../../images/cloud-ec-oidc-endpoints-azure.png + :::{image} /deploy-manage/images/cloud-ec-oidc-endpoints-azure.png :alt: A screenshot of the Azure Endpoints dialog with fields for Display Name ::: @@ -166,7 +166,7 @@ For more information about OpenID connect in Google, refer to [Google OpenID Con 1. Navigate to the **APIs & Services** and open the [Credentials](https://console.cloud.google.com/apis/credentials) tab to create your OAuth client ID. - :::{image} ../../../images/cloud-ec-oidc-oauth-create-credentials-google.png + :::{image} /deploy-manage/images/cloud-ec-oidc-oauth-create-credentials-google.png :alt: A screenshot of the Google Cloud console Create Credentials dialog with the OAuth client ID field highlighted ::: @@ -280,7 +280,7 @@ For more information about OpenID connect in Okta, refer to [Okta OAuth 2.0 docu 1. Go to **Applications** > **Add Application**. - :::{image} ../../../images/cloud-ec-oidc-new-app-okta.png + :::{image} /deploy-manage/images/cloud-ec-oidc-new-app-okta.png :alt: A screenshot of the Get Started tab on the Okta Create A New Application page ::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md index 0a5e93c6d7..0ff51f7c19 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md @@ -67,7 +67,7 @@ Create a **Marketing** space for your marketing analysts to use. If you’ve followed the example above, you should end up with a space that looks like this: - :::{image} ../../../images/kibana-tutorial-secure-access-example-1-space.png + :::{image} /deploy-manage/images/kibana-tutorial-secure-access-example-1-space.png :alt: Create space UI :screenshot: ::: @@ -105,7 +105,7 @@ To create the role: If you’ve followed the example above, you should end up with a role that looks like this: - :::{image} ../../../images/kibana-tutorial-secure-access-example-1-role.png + :::{image} /deploy-manage/images/kibana-tutorial-secure-access-example-1-role.png :alt: Create role UI :screenshot: ::: @@ -122,7 +122,7 @@ Now that you created a role, create a user account. 4. Assign the **marketing_dashboards_role** that you previously created to this new user. 5. Click **Create user**. -:::{image} ../../../images/kibana-tutorial-secure-access-example-1-user.png +:::{image} /deploy-manage/images/kibana-tutorial-secure-access-example-1-user.png :alt: Create user UI :screenshot: ::: @@ -137,7 +137,7 @@ Verify that the user and role are working correctly. You’re taken into the `Marketing` space, and the main navigation shows only the **Dashboard** application. - :::{image} ../../../images/kibana-tutorial-secure-access-example-1-test.png + :::{image} /deploy-manage/images/kibana-tutorial-secure-access-example-1-test.png :alt: Verifying access to dashboards :screenshot: ::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/saml-entra.md b/deploy-manage/users-roles/cluster-or-deployment-auth/saml-entra.md index b1213b102b..c3136d53a5 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/saml-entra.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/saml-entra.md @@ -29,13 +29,13 @@ Follow these steps to configure SAML with Microsoft Entra ID as an identity prov 2. Click **Enterprise applications** and then **New application** to register a new application. 3. Click **Create your own application**, provide a name, and select the **Integrate any other application you don’t find in the gallery** option. - :::{image} ../../../images/cloud-ec-saml-azuread-create-app.png + :::{image} /deploy-manage/images/cloud-ec-saml-azuread-create-app.png :alt: The Azure Create your own application flyout ::: 4. Navigate to the new application, click **Users and groups**, and add all necessary users and groups. Only the users and groups that you add here will have SSO access to the {{stack}}. - :::{image} ../../../images/cloud-ec-saml-azuread-users-and-groups.png + :::{image} /deploy-manage/images/cloud-ec-saml-azuread-users-and-groups.png :alt: The Entra User and groups page ::: @@ -53,13 +53,13 @@ Follow these steps to configure SAML with Microsoft Entra ID as an identity prov For example, `https://saml-azure.kb.northeurope.azure.elastic-cloud.com:443/logout`. - :::{image} ../../../images/cloud-ec-saml-azuread-kibana-config.png + :::{image} /deploy-manage/images/cloud-ec-saml-azuread-kibana-config.png :alt: The Entra SAML configuration page with {{kib}} settings ::: 6. Navigate to **SAML-based Single sign-on**, open the **User Attributes & Claims** configuration, and update the fields to suit your needs. These settings control what information from will be made available to the {{stack}} during SSO. This information can be used to identify a user in the {{stack}} and/or to assign different roles to users in the {{stack}}. We suggest that you configure a proper value for the `Unique User Identifier (Name ID)` claim that identifies the user uniquely and is not prone to changes. - :::{image} ../../../images/cloud-ec-saml-azuread-user-attributes.png + :::{image} /deploy-manage/images/cloud-ec-saml-azuread-user-attributes.png :alt: The Entra ID User Attributes & Claims page ::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md b/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md index bb6ca111d4..3d2a7496e2 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md @@ -27,7 +27,7 @@ You must authenticate users at the same level where you implement RBAC. For exam Role-based access control (RBAC) enables you to authorize users by assigning privileges to roles and assigning roles to users or groups. This is the primary way of controlling access to resources in {{stack}}.
-:::{image} ../../../images/elasticsearch-reference-authorization.png +:::{image} /deploy-manage/images/elasticsearch-reference-authorization.png :alt: This image illustrates role-based access control ::: diff --git a/deploy-manage/users-roles/serverless-custom-roles.md b/deploy-manage/users-roles/serverless-custom-roles.md index fb087f75c1..c085e9b227 100644 --- a/deploy-manage/users-roles/serverless-custom-roles.md +++ b/deploy-manage/users-roles/serverless-custom-roles.md @@ -37,7 +37,7 @@ You can manage custom roles from within your project, in **{{project-settings}} Cluster privileges grant access to monitoring and management features in {{es}}. They also enable some stack management capabilities in your project. -:::{image} ../../images/serverless-custom-roles-cluster-privileges.png +:::{image} /deploy-manage/images/serverless-custom-roles-cluster-privileges.png :alt: Create a custom role and define {{es}} cluster privileges :screenshot: ::: @@ -49,7 +49,7 @@ Refer to [cluster privileges](/deploy-manage/users-roles/cluster-or-deployment-a Each role can grant access to multiple data indices, and each index can have a different set of privileges. Typically, you will grant the `read` and `view_index_metadata` privileges to each index that you expect your users to work with. For example, grant access to indices that match an `acme-marketing-*` pattern: -:::{image} ../../images/serverless-custom-roles-index-privileges.png +:::{image} /deploy-manage/images/serverless-custom-roles-index-privileges.png :alt: Create a custom role and define {{es}} index privileges :screenshot: ::: @@ -81,7 +81,7 @@ Document-level and field-level security affords you even more granularity when i When you create a custom role, click **Add Kibana privilege** to grant access to specific features. The features that are available vary depending on the project type. For example, in {{es-serverless}}: -:::{image} ../../images/serverless-custom-roles-kibana-privileges.png +:::{image} /deploy-manage/images/serverless-custom-roles-kibana-privileges.png :alt: Create a custom role and define {{kib}} privileges :screenshot: :::