From 522bc357577505b15c3752a27775be5f6075eb7e Mon Sep 17 00:00:00 2001 From: Florent Le Borgne Date: Mon, 31 Mar 2025 13:00:33 +0200 Subject: [PATCH 1/6] Deployments page renamed to Hosted deployments --- .../autoscaling/autoscaling-in-ece-and-ech.md | 4 ++-- .../deploy/cloud-enterprise/access-kibana.md | 2 +- .../cloud-enterprise/add-custom-bundles-plugins.md | 2 +- deploy-manage/deploy/cloud-enterprise/add-plugins.md | 2 +- .../advanced-cluster-configuration.md | 2 +- .../deploy/cloud-enterprise/customize-deployment.md | 2 +- .../cloud-enterprise/edit-stack-settings-apm.md | 2 +- .../edit-stack-settings-elasticsearch.md | 2 +- .../edit-stack-settings-enterprise.md | 2 +- .../cloud-enterprise/edit-stack-settings-kibana.md | 2 +- .../keep-track-of-deployment-activity.md | 2 +- .../deploy/cloud-enterprise/resize-deployment.md | 4 ++-- .../cloud-enterprise/search-filter-deployments.md | 2 +- deploy-manage/deploy/elastic-cloud/access-kibana.md | 4 ++-- deploy-manage/deploy/elastic-cloud/configure.md | 4 ++-- .../deploy/elastic-cloud/edit-stack-settings.md | 8 ++++---- .../keep-track-of-deployment-activity.md | 4 ++-- .../elastic-cloud/upload-custom-plugins-bundles.md | 10 +++++----- .../start-stop-services/restart-an-ece-deployment.md | 2 +- .../access-performance-metrics-on-elastic-cloud.md | 4 ++-- deploy-manage/monitor/cloud-health-perf.md | 2 +- .../orchestrators/ece-monitoring-ece-access.md | 2 +- .../_snippets/cloud-monitoring-access.md | 2 +- .../stack-monitoring/ece-ech-stack-monitoring.md | 2 +- deploy-manage/remote-clusters/ec-migrate-ccs.md | 2 +- .../remote-clusters/ec-remote-cluster-ece.md | 8 ++++---- .../remote-clusters/ec-remote-cluster-other-ess.md | 4 ++-- .../remote-clusters/ec-remote-cluster-same-ess.md | 4 ++-- .../ec-remote-cluster-self-managed.md | 8 ++++---- deploy-manage/remote-clusters/ece-migrate-ccs.md | 2 +- .../remote-clusters/ece-remote-cluster-ece-ess.md | 2 +- .../remote-clusters/ece-remote-cluster-other-ece.md | 4 ++-- .../remote-clusters/ece-remote-cluster-same-ece.md | 2 +- .../ece-remote-cluster-self-managed.md | 4 ++-- .../security/aws-privatelink-traffic-filters.md | 4 ++-- deploy-manage/security/ip-traffic-filtering.md | 4 ++-- .../logging-configuration/enabling-audit-logs.md | 4 ++-- deploy-manage/security/secure-settings.md | 12 ++++++------ .../tools/snapshot-and-restore/cloud-enterprise.md | 2 +- .../minio-on-premise-repository.md | 2 +- deploy-manage/uninstall/delete-a-cloud-deployment.md | 6 +++--- .../upgrade/deployment-or-cluster/upgrade-on-ece.md | 4 ++-- .../upgrade/deployment-or-cluster/upgrade-on-ech.md | 4 ++-- .../manage-elastic-user-cloud.md | 4 ++-- .../machine-learning/nlp/ml-nlp-ner-example.md | 2 +- .../nlp/ml-nlp-text-emb-vector-search-example.md | 2 +- manage-data/lifecycle/data-tiers.md | 8 ++++---- .../migrate-index-management.md | 8 ++++---- ...e-use-elasticsearch-to-manage-time-series-data.md | 2 +- reference/apm/cloud-enterprise/apm-settings.md | 2 +- reference/apm/cloud/apm-settings.md | 4 ++-- solutions/observability/apps/configure-apm-server.md | 4 ++-- solutions/security/ai/connect-to-azure-openai.md | 2 +- .../deployments/cloud-enterprise/cloud-enterprise.md | 2 +- .../cloud-enterprise/deployment-health-warnings.md | 2 +- .../deployments/cloud-enterprise/heap-dumps.md | 6 +++--- .../deployments/cloud-enterprise/thread-dumps.md | 2 +- 57 files changed, 103 insertions(+), 103 deletions(-) diff --git a/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md b/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md index 9a6498a020..d0292aae04 100644 --- a/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md +++ b/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md @@ -98,7 +98,7 @@ To enable or disable autoscaling on a deployment: 1. Log in to the ECE [Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md) or [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. @@ -117,7 +117,7 @@ Each autoscaling setting is configured with a default value. You can adjust thes 1. Log in to the ECE [Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md) or [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. diff --git a/deploy-manage/deploy/cloud-enterprise/access-kibana.md b/deploy-manage/deploy/cloud-enterprise/access-kibana.md index 0cf330bb65..8553e08a36 100644 --- a/deploy-manage/deploy/cloud-enterprise/access-kibana.md +++ b/deploy-manage/deploy/cloud-enterprise/access-kibana.md @@ -18,7 +18,7 @@ Most deployment templates include a Kibana instance, but if it wasn’t part of To access Kibana: 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md b/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md index d8ff85c74f..dc6f9bfc79 100644 --- a/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md +++ b/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md @@ -37,7 +37,7 @@ Here are some examples of custom bundles you can add: Custom plugins can include the official Elasticsearch plugins not provided with Elastic Cloud Enterprise, any of the community-sourced plugins, or plugins that you write yourself. 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. From the **Deployments** page, select your deployment. +2. From the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/add-plugins.md b/deploy-manage/deploy/cloud-enterprise/add-plugins.md index 773003eb9d..f55a7930be 100644 --- a/deploy-manage/deploy/cloud-enterprise/add-plugins.md +++ b/deploy-manage/deploy/cloud-enterprise/add-plugins.md @@ -36,7 +36,7 @@ The deployment spins up with the plugins installed. To add plugins to an existing deployment: 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/advanced-cluster-configuration.md b/deploy-manage/deploy/cloud-enterprise/advanced-cluster-configuration.md index a3c4df4dc0..92a5471472 100644 --- a/deploy-manage/deploy/cloud-enterprise/advanced-cluster-configuration.md +++ b/deploy-manage/deploy/cloud-enterprise/advanced-cluster-configuration.md @@ -13,7 +13,7 @@ Most configuration changes can be made safely from other parts of the Cloud UI. To edit the cluster configuration directly: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/customize-deployment.md b/deploy-manage/deploy/cloud-enterprise/customize-deployment.md index 9be26ecc73..016c5a665d 100644 --- a/deploy-manage/deploy/cloud-enterprise/customize-deployment.md +++ b/deploy-manage/deploy/cloud-enterprise/customize-deployment.md @@ -20,7 +20,7 @@ The configurable components and allowed values available on the Edit page depend To customize your deployment: 1. [Log into the Cloud UI](./log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other [filters](./search-filter-deployments.md). To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md index 43f17daf3e..064e499f34 100644 --- a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md +++ b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md @@ -49,7 +49,7 @@ Be aware that some settings could break your cluster if set incorrectly and that To change APM settings: 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md index 030e1a8cb4..633bf25a0f 100644 --- a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md +++ b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md @@ -18,7 +18,7 @@ ECE blocks the configuration of certain settings that could break your cluster i To change {{es}} user settings: 1. [Log into the Cloud UI](./log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md index 16ede35b35..0b75f79171 100644 --- a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md +++ b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md @@ -20,7 +20,7 @@ Refer to the [Configuration settings reference](https://www.elastic.co/guide/en/ To add user settings: 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md index b7fc953934..11c7b44113 100644 --- a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md +++ b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md @@ -18,7 +18,7 @@ Be aware that some settings that could break your cluster if set incorrectly and To change Kibana settings: 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 cad919efd6..e9ed1229d2 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 @@ -13,7 +13,7 @@ The deployment **Activity** page gives you a convenient way to follow all config To view the activity for a deployment: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/resize-deployment.md b/deploy-manage/deploy/cloud-enterprise/resize-deployment.md index c7002ba696..94db3a6d10 100644 --- a/deploy-manage/deploy/cloud-enterprise/resize-deployment.md +++ b/deploy-manage/deploy/cloud-enterprise/resize-deployment.md @@ -17,7 +17,7 @@ You can also enable autoscaling on a deployment to have the available resources To resize a deployment: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -46,7 +46,7 @@ This example shows you how to change an existing, very basic deployment to use h To scale your deployment from very small to very large: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md index 8c64c747ae..940fcd74af 100644 --- a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md +++ b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md @@ -10,7 +10,7 @@ mapped_pages: When you installed Elastic Cloud Enterprise and [logged into the Cloud UI](log-into-cloud-ui.md) for the first time, you were greeted by two deployments. We’ve also shown you how to [create your own first deployment](create-deployment.md), but that still only makes a few deployments. What if you had hundreds of deployments to look after or maybe even a thousand? How would you find the ones that need your attention? -The **Deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system: +The **Hosted deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system: * Check the visual health indicators of deployments * Search for partial or whole deployment names or IDs in the search text box diff --git a/deploy-manage/deploy/elastic-cloud/access-kibana.md b/deploy-manage/deploy/elastic-cloud/access-kibana.md index cd9ec6d9d1..68356596b8 100644 --- a/deploy-manage/deploy/elastic-cloud/access-kibana.md +++ b/deploy-manage/deploy/elastic-cloud/access-kibana.md @@ -31,9 +31,9 @@ For new Elasticsearch clusters, we automatically create a Kibana instance for yo To access Kibana: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. Under **Applications**, select the Kibana **Launch** link and wait for Kibana to open. diff --git a/deploy-manage/deploy/elastic-cloud/configure.md b/deploy-manage/deploy/elastic-cloud/configure.md index 5cfef00d5c..21fd9d9414 100644 --- a/deploy-manage/deploy/elastic-cloud/configure.md +++ b/deploy-manage/deploy/elastic-cloud/configure.md @@ -38,9 +38,9 @@ If you use a Platform-as-a-Service provider like Heroku, the administration cons To change your deployment: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From the deployment menu, select **Edit**. 4. Let the user interface guide you through the cluster configuration for your cluster. diff --git a/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md b/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md index 9c92bb9403..68bd5f02f5 100644 --- a/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md +++ b/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md @@ -69,9 +69,9 @@ You can also update [dynamic cluster settings](../../../deploy-manage/deploy/sel To add or edit user settings: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From your deployment menu, go to the **Edit** page. 4. In the **Elasticsearch** section, select **Manage user settings and extensions**. @@ -93,9 +93,9 @@ For a list of supported settings, check [Kibana settings](kibana://reference/clo To change Kibana settings: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From your deployment menu, go to the **Edit** page. 4. In the **Kibana** section, select **Edit user settings**. For deployments with existing user settings, you may have to expand the **Edit kibana.yml** caret instead. 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 37f86fe418..02e2bf8209 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 @@ -23,9 +23,9 @@ The deployment **Activity** page gives you a convenient way to follow all config To view the activity for a deployment: 1. Log in to the [{{ech}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. In your deployment menu, select **Activity**. 4. You can: diff --git a/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md b/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md index 0b38fef93f..8563fb9cc6 100644 --- a/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md +++ b/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md @@ -105,7 +105,7 @@ Bundles You must upload your files before you can apply them to your cluster configuration: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. 3. Under **Features**, select **Extensions**. 4. Select **Upload extension**. 5. Complete the extension fields, including the {{es}} version. @@ -133,9 +133,9 @@ Refer to [Managing plugins and extensions through the API](../../../deploy-manag After uploading your files, you can select to enable them when creating a new {{es}} deployment. For existing deployments, you must update your deployment configuration to use the new files: 1. Log in to the [{{ech}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From the **Actions** dropdown, select **Edit deployment**. 4. Select **Manage user settings and extensions**. @@ -164,9 +164,9 @@ To update an extension with a new file version, 1. Prepare a new plugin or bundle. 2. On the **Extensions** page, [upload a new extension](../../../deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md#ec-add-your-plugin). 3. Make your new files available by uploading them. -4. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +4. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 5. From the **Actions** dropdown, select **Edit deployment**. 6. Select **Manage user settings and extensions**. diff --git a/deploy-manage/maintenance/start-stop-services/restart-an-ece-deployment.md b/deploy-manage/maintenance/start-stop-services/restart-an-ece-deployment.md index 55d4697ac5..e42666eb41 100644 --- a/deploy-manage/maintenance/start-stop-services/restart-an-ece-deployment.md +++ b/deploy-manage/maintenance/start-stop-services/restart-an-ece-deployment.md @@ -11,7 +11,7 @@ applies_to: To restart a running or a stopped deployment: 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 aab632556e..de1726406a 100644 --- a/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md +++ b/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md @@ -20,9 +20,9 @@ For {{ece}} deployments, you can use [platform monitoring](/deploy-manage/monito To access cluster performance metrics: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention. 3. From your deployment menu, go to the **Performance** page. diff --git a/deploy-manage/monitor/cloud-health-perf.md b/deploy-manage/monitor/cloud-health-perf.md index b9de218a4e..6c54f03d51 100644 --- a/deploy-manage/monitor/cloud-health-perf.md +++ b/deploy-manage/monitor/cloud-health-perf.md @@ -23,7 +23,7 @@ The deployment **Health** page provides detailed information on health issues, i To view the health for a deployment: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) or [Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. 3. In your deployment menu, select **Health**. The **Health** page provides the following information: diff --git a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md index fe854796ff..32a41d7a94 100644 --- a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md +++ b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md @@ -29,7 +29,7 @@ If a {{kib}} instance exists for the deployment, the following {{kib}} logs and To access logs and metrics for your deployment: 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. From the **Deployments** page, select your deployment. +2. From the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md b/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md index 10499a2e7b..cba5306286 100644 --- a/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md +++ b/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md @@ -1,5 +1,5 @@ 1. Log into [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) (ECH) or [the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md) (ECE). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md index 7ea03caf5f..9a2556d48b 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md @@ -68,7 +68,7 @@ Elastic manages the installation and configuration of the monitoring agent for y To enable monitoring on your deployment: 1. Log into [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) (ECH) or [the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md) (ECE). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/remote-clusters/ec-migrate-ccs.md b/deploy-manage/remote-clusters/ec-migrate-ccs.md index 31f1360f3e..8c901c08e3 100644 --- a/deploy-manage/remote-clusters/ec-migrate-ccs.md +++ b/deploy-manage/remote-clusters/ec-migrate-ccs.md @@ -269,7 +269,7 @@ Note that the `ref_id` and version numbers for your resources may not be the sam You can make this change in the user [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). The only drawback of this method is that it changes the URL used to access the {{es}} cluster and {{kib}}. 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. +2. From the main **Hosted 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} /deploy-manage/images/cloud-ec-create-from-snapshot-updated.png :alt: Create a Deployment using a snapshot diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md index 6d397aeb0d..464303a64c 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md @@ -55,9 +55,9 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo ::::{dropdown} The CA is public 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From the deployment menu, select **Security**. 4. Locate **Remote connections** and select **Add an API key**. @@ -83,9 +83,9 @@ If you later need to update the remote connection with different permissions, yo ::::{dropdown} The CA is private 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. Access the **Security** page of the deployment. 4. Select **Remote Connections > Add trusted environment** and choose **{{ece}}**. Then click **Next**. 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 df64b3f678..94668183fd 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md @@ -51,9 +51,9 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From the deployment menu, select **Security**. 4. Locate **Remote connections** and select **Add an API key**. 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 cbaa499258..3adced22d4 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md @@ -51,9 +51,9 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From the deployment menu, select **Security**. 4. Locate **Remote connections** and select **Add an API key**. 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 f779f84524..c1350ab8e7 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md @@ -55,9 +55,9 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo ::::{dropdown} The CA is public 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From the deployment menu, select **Security**. 4. Locate **Remote connections** and select **Add an API key**. @@ -83,9 +83,9 @@ If you later need to update the remote connection with different permissions, yo ::::{dropdown} The CA is private 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. Access the **Security** page of the deployment. 4. Select **Remote Connections > Add trusted environment** and choose **Self-managed**. Then click **Next**. diff --git a/deploy-manage/remote-clusters/ece-migrate-ccs.md b/deploy-manage/remote-clusters/ece-migrate-ccs.md index b54d269fc3..af36c9e2d0 100644 --- a/deploy-manage/remote-clusters/ece-migrate-ccs.md +++ b/deploy-manage/remote-clusters/ece-migrate-ccs.md @@ -20,7 +20,7 @@ You can make this change in the user Cloud UI. The only drawback of this method 1. The first step for any approach is to remove the remote clusters from your deployment. You will need to add them back later. 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. +3. From the main **Hosted 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} /deploy-manage/images/cloud-enterprise-ce-create-from-snapshot-updated.png :alt: Create a Deployment using a snapshot 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 1146eeff72..cae29c18ef 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md @@ -51,7 +51,7 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore. 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 0f83c48041..a02593a8fa 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md @@ -52,7 +52,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo ::::{dropdown} The CA is public 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -80,7 +80,7 @@ If you later need to update the remote connection with different permissions, yo ::::{dropdown} The CA is private 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 3fa409911c..3f8abdf807 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md @@ -50,7 +50,7 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore. 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 7c44080bee..19a589344f 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md @@ -54,7 +54,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo ::::{dropdown} The CA is public 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -82,7 +82,7 @@ If you later need to update the remote connection with different permissions, yo ::::{dropdown} The CA is private 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/security/aws-privatelink-traffic-filters.md b/deploy-manage/security/aws-privatelink-traffic-filters.md index c55524a4fa..a90fe860a1 100644 --- a/deploy-manage/security/aws-privatelink-traffic-filters.md +++ b/deploy-manage/security/aws-privatelink-traffic-filters.md @@ -211,7 +211,7 @@ Having trouble finding your VPC endpoint ID? You can find it in the AWS console. Once you know your VPC endpoint ID you can create a private link traffic filter rule set. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. 3. Under the **Features** tab, open the **Traffic filters** page. 4. Select **Create filter**. 5. Select **Private link endpoint**. @@ -272,7 +272,7 @@ The settings `xpack.fleet.agents.fleet_server.hosts` and `xpack.fleet.outputs` t You can edit a rule set name or to change the VPC endpoint ID. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. 3. Under the **Features** tab, open the **Traffic filters** page. 4. Find the rule set you want to edit. 5. Select the **Edit** icon. diff --git a/deploy-manage/security/ip-traffic-filtering.md b/deploy-manage/security/ip-traffic-filtering.md index bee688bbf0..e221493c5b 100644 --- a/deploy-manage/security/ip-traffic-filtering.md +++ b/deploy-manage/security/ip-traffic-filtering.md @@ -56,7 +56,7 @@ You can combine any rules into a set, so we recommend that you group rules accor To create a rule set: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. 3. Under the **Features** tab, open the **Traffic filters** page. 4. Select **Create filter**. 5. Select **IP filtering rule set**. @@ -108,7 +108,7 @@ If you want to remove any traffic restrictions from a deployment or delete a rul You can edit a rule set name or change the allowed traffic sources using IPv4, or a range of addresses with CIDR. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. 3. Under the **Features** tab, open the **Traffic filters** page. 4. Find the rule set you want to edit. 5. Select the **Edit** icon. diff --git a/deploy-manage/security/logging-configuration/enabling-audit-logs.md b/deploy-manage/security/logging-configuration/enabling-audit-logs.md index f6a73999e4..db602ac601 100644 --- a/deploy-manage/security/logging-configuration/enabling-audit-logs.md +++ b/deploy-manage/security/logging-configuration/enabling-audit-logs.md @@ -67,7 +67,7 @@ To enable audit logging in an {{ech}} deployment: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. 3. From your deployment menu, go to the **Edit** page. @@ -91,7 +91,7 @@ To enable audit logging in an ECE deployment: 1. [Log in to the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. 3. From your deployment menu, go to the **Edit** page. diff --git a/deploy-manage/security/secure-settings.md b/deploy-manage/security/secure-settings.md index 11e3e28def..c6f0c34004 100644 --- a/deploy-manage/security/secure-settings.md +++ b/deploy-manage/security/secure-settings.md @@ -57,9 +57,9 @@ There are three types of secrets that you can use: Add keys and secret values to the keystore. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From your deployment menu, select **Security**. 4. Locate **{{es}} keystore** and select **Add settings**. @@ -73,9 +73,9 @@ Add keys and secret values to the keystore. When your keys and secret values are no longer needed, delete them from the keystore. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From your deployment menu, select **Security**. 4. From the **Existing keystores** list, use the delete icon next to the **Setting Name** that you want to delete. @@ -99,7 +99,7 @@ There are three types of secrets that you can use: Add keys and secret values to the keystore. 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -116,7 +116,7 @@ Add keys and secret values to the keystore. When your keys and secret values are no longer needed, delete them from the keystore. 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md b/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md index dd7a57b31a..24d9336096 100644 --- a/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md +++ b/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md @@ -89,7 +89,7 @@ To change the snapshot repository for an existing Elasticsearch cluster: 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). 2. Optional: If you need to use a repository that is not yet listed, add a snapshot repository configuration first. -3. From the **Deployments** page, select your deployment. +3. From the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 3a2cafe889..984d71633a 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 @@ -144,7 +144,7 @@ As an extra verification step, you can restore a cluster using the snapshots tha 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). 2. Get the plan from your test cluster. - 1. From the **Deployments** page, select your deployment. + 1. From the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/uninstall/delete-a-cloud-deployment.md b/deploy-manage/uninstall/delete-a-cloud-deployment.md index 0db6e69163..0579b790af 100644 --- a/deploy-manage/uninstall/delete-a-cloud-deployment.md +++ b/deploy-manage/uninstall/delete-a-cloud-deployment.md @@ -54,7 +54,7 @@ All data is lost. Billing for usage is by the hour and any outstanding charges f To delete an {{ece}} deployment: 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -72,7 +72,7 @@ Terminating a deployment stops all running instances and **deletes all data**. O To terminate an {{ece}} deployment, 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -86,7 +86,7 @@ You can restore a deployment that was previously terminated to its original conf To restore a terminated deployment, 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 3. In the **Deployment Management** section, select **Restore** and then acknowledge the confirmation message. diff --git a/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md b/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md index d1e1805da0..15ae9aff03 100644 --- a/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md +++ b/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md @@ -21,7 +21,7 @@ Once you're [prepared to upgrade](/deploy-manage/upgrade/prepare-to-upgrade.md), ## Perform the upgrade 1. [Log in to the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -30,7 +30,7 @@ Once you're [prepared to upgrade](/deploy-manage/upgrade/prepare-to-upgrade.md), 3. Click **Upgrade**, then **Confirm upgrade**. The new configuration takes a few minutes to create. ::::{note} - If any incompatibilities are detected when you attempt to upgrade, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. After resolving the issues, return to the **Deployments** page and restart the upgrade. Also check the [release notes](/release-notes/index.md) to stay aware of changes and known issues for the version you're upgrading to. + If any incompatibilities are detected when you attempt to upgrade, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. After resolving the issues, return to the **Hosted deployments** page and restart the upgrade. Also check the [release notes](/release-notes/index.md) to stay aware of changes and known issues for the version you're upgrading to. :::: **Security realm settings** diff --git a/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md b/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md index d810456b4e..17480457ea 100644 --- a/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md +++ b/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md @@ -25,7 +25,7 @@ Although it’s simple to upgrade an {{ecloud}} deployment, the new version migh Log in to your {{ecloud}} environment: 1. Log in to the [{{ech}} console](https://cloud.elastic.co/login). -2. Select your deployment on the home page in the {{ech}} card or go to the **Deployments** page. +2. Select your deployment on the home page in the {{ech}} card or go to the **Hosted deployments** page. Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. @@ -37,7 +37,7 @@ To upgrade a deployment: 3. Click **Upgrade**, then **Confirm upgrade**. The new configuration takes a few minutes to create. ::::{note} - If any incompatibilities are detected when you attempt to upgrade, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. After resolving the issues, return to the **Deployments** page and restart the upgrade. Also check the [release notes](/release-notes/index.md) to stay aware of changes and known issues for the version you're upgrading to. + If any incompatibilities are detected when you attempt to upgrade, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. After resolving the issues, return to the **Hosted deployments** page and restart the upgrade. Also check the [release notes](/release-notes/index.md) to stay aware of changes and known issues for the version you're upgrading to. :::: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md b/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md index c07745aa60..51608b0805 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md @@ -29,9 +29,9 @@ The `elastic` user should be not be used unless you have no other way to access To reset the password: 1. Log in to the Elastic Cloud Console. -2. Find your deployment on the home page and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From your deployment menu, go to **Security**. 4. Select **Reset password**. diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md b/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md index 09441c35b4..2add42f12a 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-ner-example.md @@ -43,7 +43,7 @@ docker run -it --rm docker.elastic.co/eland/eland \ --start ``` -You need to provide an administrator username and its password and replace the `$CLOUD_ID` with the ID of your Cloud deployment. This Cloud ID can be copied from the **Deployments** page on your Cloud website. +You need to provide an administrator username and its password and replace the `$CLOUD_ID` with the ID of your Cloud deployment. This Cloud ID can be copied from the **Hosted deployments** page on your Cloud website. Since the `--start` option is used at the end of the Eland import command, {{es}} deploys the model ready to use. If you have multiple models and want to select which model to deploy, you can use the **{{ml-app}} > Model Management** user interface in {{kib}} to manage the starting and stopping of models. diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-text-emb-vector-search-example.md b/explore-analyze/machine-learning/nlp/ml-nlp-text-emb-vector-search-example.md index 84522f9b2a..bcff026515 100644 --- a/explore-analyze/machine-learning/nlp/ml-nlp-text-emb-vector-search-example.md +++ b/explore-analyze/machine-learning/nlp/ml-nlp-text-emb-vector-search-example.md @@ -47,7 +47,7 @@ docker run -it --rm docker.elastic.co/eland/eland \ --start ``` -You need to provide an administrator username and password and replace the `$CLOUD_ID` with the ID of your Cloud deployment. This Cloud ID can be copied from the **Deployments** page on your Cloud website. +You need to provide an administrator username and password and replace the `$CLOUD_ID` with the ID of your Cloud deployment. This Cloud ID can be copied from the **Hosted deployments** page on your Cloud website. Since the `--start` option is used at the end of the Eland import command, {{es}} deploys the model ready to use. If you have multiple models and want to select which model to deploy, you can use the **{{ml-app}} > Model Management** user interface in {{kib}} to manage the starting and stopping of models. diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index 5793151f67..6ca9b1b0c7 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -104,7 +104,7 @@ To add a warm, cold, or frozen tier when you create a deployment: To add a data tier to an existing deployment: 1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body) or the {{ece}} admin console. -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. 3. In your deployment menu, select **Edit**. 4. Click **+ Add capacity** for any data tiers to add. 5. Click **Save** at the bottom of the page to save your changes. @@ -154,9 +154,9 @@ To make sure that all data can be migrated from the data tier you want to disabl ::::{tab-item} {{ech}} 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - 2. From the **Deployments** page, select your deployment. + 2. From the **Hosted deployments** page, select your deployment. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. Filter the list of instances by the Data tier you want to disable. @@ -170,7 +170,7 @@ To make sure that all data can be migrated from the data tier you want to disabl ::::{tab-item} Elastic Cloud Enterprise 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). - 2. From the **Deployments** page, select your deployment. + 2. From the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md b/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md index 4f923f1d57..e6f14c1b32 100644 --- a/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md +++ b/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md @@ -27,9 +27,9 @@ To configure ILM Migration in the console: :::{tab-item} {{ech}} 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. From the **Deployments** page, select your deployment. +2. From the **Hosted deployments** page, select your deployment. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. Near the top of the deployment overview, you should get a message to migrate from index curation to index lifecycle management (ILM) along with a **Start migration** button. 4. Select which index curation pattern you wish to migrate. @@ -38,9 +38,9 @@ To configure ILM Migration in the console: :::{tab-item} Elastic Cloud Enterprise 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. From the **Deployments** page, select your deployment. +2. From the **Hosted deployments** page, select your deployment. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. Near the top of the deployment overview, you should get a message to migrate from index curation to index lifecycle management (ILM) along with a **Start migration** button. 4. Select which index curation pattern you wish to migrate. diff --git a/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md b/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md index d86b16b54d..45240145e1 100644 --- a/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md +++ b/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md @@ -24,7 +24,7 @@ The steps for setting up data tiers vary based on your deployment type: ::::::{tab-item} {{ech}} 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co/registration?page=docs&placement=docs-body). -2. Add or select your deployment from the {{ecloud}} home page or the **Deployments** page. +2. Add or select your deployment from the {{ecloud}} home page or the **Hosted deployments** page. 3. From your deployment menu, select **Edit deployment**. 4. To enable a data tier, click **Add capacity**. diff --git a/reference/apm/cloud-enterprise/apm-settings.md b/reference/apm/cloud-enterprise/apm-settings.md index 866eb63891..0a81883bd3 100644 --- a/reference/apm/cloud-enterprise/apm-settings.md +++ b/reference/apm/cloud-enterprise/apm-settings.md @@ -45,7 +45,7 @@ Be aware that some settings could break your cluster if set incorrectly and that To change APM settings: 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/reference/apm/cloud/apm-settings.md b/reference/apm/cloud/apm-settings.md index c4ca425302..7b2a70fc8b 100644 --- a/reference/apm/cloud/apm-settings.md +++ b/reference/apm/cloud/apm-settings.md @@ -28,9 +28,9 @@ User settings are appended to the `apm-server.yml` configuration file for your i To add user settings: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From your deployment menu, go to the **Edit** page. 4. In the **APM** section, select **Edit user settings**. (For existing deployments with user settings, you may have to expand the **Edit apm-server.yml** caret instead.) diff --git a/solutions/observability/apps/configure-apm-server.md b/solutions/observability/apps/configure-apm-server.md index c8bdca17c2..1b94fcf711 100644 --- a/solutions/observability/apps/configure-apm-server.md +++ b/solutions/observability/apps/configure-apm-server.md @@ -55,9 +55,9 @@ User settings are appended to the `apm-server.yml` configuration file for your i To add user settings: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. - On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. From your deployment menu, go to the **Edit** page. 4. In the **APM** section, select **Edit user settings**. (For existing deployments with user settings, you may have to expand the **Edit apm-server.yml** caret instead.) diff --git a/solutions/security/ai/connect-to-azure-openai.md b/solutions/security/ai/connect-to-azure-openai.md index f9db301361..12e4073ce3 100644 --- a/solutions/security/ai/connect-to-azure-openai.md +++ b/solutions/security/ai/connect-to-azure-openai.md @@ -49,7 +49,7 @@ The following video demonstrates these steps (click to watch). Now, set up the Azure OpenAI model: 1. From within your Azure OpenAI deployment, select **Model deployments**, then click **Manage deployments**. -2. On the **Deployments** page, select **Create new deployment**. +2. On the **Hosted deployments** page, select **Create new deployment**. 3. Under **Select a model**, choose `gpt-4o` or `gpt-4 turbo`. 4. Set the model version to "Auto-update to default". diff --git a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md index 01bbd9863e..f01da9b3d9 100644 --- a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md +++ b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md @@ -14,7 +14,7 @@ mapped_urls: When you installed Elastic Cloud Enterprise and [logged into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md) for the first time, you were greeted by two deployments. We’ve also shown you how to [create your own first deployment](../../../deploy-manage/deploy/cloud-enterprise/create-deployment.md), but that still only makes a few deployments. What if you had hundreds of deployments to look after or maybe even a thousand? How would you find the ones that need your attention? -The **Deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system: +The **Hosted deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system: * Check the visual health indicators of deployments * Search for partial or whole deployment names or IDs in the search text box diff --git a/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md b/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md index 39b5dd1566..d5d416e704 100644 --- a/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md +++ b/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md @@ -9,7 +9,7 @@ mapped_pages: # Troubleshoot deployment health warnings [ece-deployment-no-op] -The {{ece}} **Deployments** page shows the current status of your active deployments. From time to time you may get one or more health warnings, such as the following: +The {{ece}} **Hosted deployments** page shows the current status of your active deployments. From time to time you may get one or more health warnings, such as the following: :::{image} /troubleshoot/images/cloud-ec-ce-deployment-health-warning.png :alt: A screen capture of the deployment page showing a typical warning: Deployment health warning: Latest change to {{es}} configuration failed. diff --git a/troubleshoot/deployments/cloud-enterprise/heap-dumps.md b/troubleshoot/deployments/cloud-enterprise/heap-dumps.md index 1f11c0ea2f..2fa1dfba2f 100644 --- a/troubleshoot/deployments/cloud-enterprise/heap-dumps.md +++ b/troubleshoot/deployments/cloud-enterprise/heap-dumps.md @@ -16,7 +16,7 @@ From the Elastic Cloud Enterprise console you can capture JVM heap dumps from de You can view and download captured heap dumps for a given deployment. 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -45,7 +45,7 @@ The JVM will be paused while the heap dump is being captured, so there may be a 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -54,7 +54,7 @@ The JVM will be paused while the heap dump is being captured, so there may be a Alternatively, you can capture an on-demand heap dump directly from the **Heap dumps** page. 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/troubleshoot/deployments/cloud-enterprise/thread-dumps.md b/troubleshoot/deployments/cloud-enterprise/thread-dumps.md index 318505803b..722cee179b 100644 --- a/troubleshoot/deployments/cloud-enterprise/thread-dumps.md +++ b/troubleshoot/deployments/cloud-enterprise/thread-dumps.md @@ -16,7 +16,7 @@ You can capture JVM thread dumps from deployment instances. This can help discov You can capture a thread dump from the deployment overview page. 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Deployments** page, select your deployment. +2. On the **Hosted deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. From 01eb4be4d9e9bb8b21de61b490c9e49302c34bab Mon Sep 17 00:00:00 2001 From: Florent Le Borgne Date: Tue, 1 Apr 2025 16:04:18 +0200 Subject: [PATCH 2/6] scanned for more changes and wording updates --- deploy-manage/deploy/cloud-enterprise/create-deployment.md | 2 +- .../cloud-enterprise/ece-regional-deployment-aliases.md | 4 ++-- .../deploy/cloud-enterprise/search-filter-deployments.md | 2 +- deploy-manage/deploy/elastic-cloud/configure.md | 2 +- .../deploy/elastic-cloud/custom-endpoint-aliases.md | 4 ++-- deploy-manage/deploy/elastic-cloud/edit-stack-settings.md | 4 ++-- .../deploy/elastic-cloud/upload-custom-plugins-bundles.md | 6 +++--- .../monitor/access-performance-metrics-on-elastic-cloud.md | 2 +- .../monitor/stack-monitoring/kibana-monitoring-data.md | 2 +- deploy-manage/security/_snippets/create-filter.md | 2 +- deploy-manage/security/ip-filtering-cloud.md | 6 +++--- .../security/logging-configuration/enabling-audit-logs.md | 2 +- deploy-manage/security/secure-settings.md | 4 ++-- deploy-manage/security/traffic-filtering.md | 2 +- .../cloud-enterprise-orchestrator/manage-users-roles.md | 2 +- reference/apm/cloud/apm-settings.md | 2 +- solutions/observability/apps/configure-apm-server.md | 2 +- solutions/observability/apps/secret-token.md | 2 +- .../deployments/cloud-enterprise/cloud-enterprise.md | 2 +- troubleshoot/ingest/elastic-serverless-forwarder.md | 2 +- 20 files changed, 28 insertions(+), 28 deletions(-) diff --git a/deploy-manage/deploy/cloud-enterprise/create-deployment.md b/deploy-manage/deploy/cloud-enterprise/create-deployment.md index d94c5a9ed8..c36ab0aae0 100644 --- a/deploy-manage/deploy/cloud-enterprise/create-deployment.md +++ b/deploy-manage/deploy/cloud-enterprise/create-deployment.md @@ -14,7 +14,7 @@ Each deployment is based on a [deployment template](./deployment-templates.md), To create a deployment in ECE: -1. From the Cloud UI **Deployments** view, select **Create deployment**. +1. From the Cloud UI **Hosted deployments** view, select **Create deployment**. 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. diff --git a/deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md b/deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md index 9d0118dd31..f409de70ff 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md @@ -19,7 +19,7 @@ Before setting up your custom alias, your platform administrator must enable the To add an alias to an existing deployment: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. From the **Deployments** menu, select a deployment. +2. From the **Hosted deployments** menu, select a deployment. 3. Under **Custom endpoint alias**, select **Edit**. 4. Define a new alias. Make sure you choose something meaningful to you. @@ -34,7 +34,7 @@ To add an alias to an existing deployment: To remove an alias from your deployment, or if you want to re-assign an alias to another deployment, follow these steps: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. From the **Deployments** menu, select a deployment. +2. From the **Hosted deployments** menu, select a deployment. 3. Under **Custom endpoint alias**, select **Edit**. 4. Remove the text from the **Custom endpoint alias** text box. 5. Select **Update alias**. diff --git a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md index 940fcd74af..f87b0035d4 100644 --- a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md +++ b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md @@ -14,7 +14,7 @@ The **Hosted deployments** page in the Cloud UI provides several ways to find de * Check the visual health indicators of deployments * 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: +* Add filters to the **Hosted deployments** view to filter for specific conditions: :::{image} /deploy-manage/images/cloud-enterprise-deployment-filter.png :alt: Add a filter diff --git a/deploy-manage/deploy/elastic-cloud/configure.md b/deploy-manage/deploy/elastic-cloud/configure.md index 21fd9d9414..337d8d89a7 100644 --- a/deploy-manage/deploy/elastic-cloud/configure.md +++ b/deploy-manage/deploy/elastic-cloud/configure.md @@ -38,7 +38,7 @@ If you use a Platform-as-a-Service provider like Heroku, the administration cons To change your deployment: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. diff --git a/deploy-manage/deploy/elastic-cloud/custom-endpoint-aliases.md b/deploy-manage/deploy/elastic-cloud/custom-endpoint-aliases.md index ba9f9ce4d5..4bad9e3fcd 100644 --- a/deploy-manage/deploy/elastic-cloud/custom-endpoint-aliases.md +++ b/deploy-manage/deploy/elastic-cloud/custom-endpoint-aliases.md @@ -29,7 +29,7 @@ New deployments are assigned a default alias derived from the deployment name. T To add an alias to an existing deployment: -1. From the **Deployments** menu, select a deployment. +1. From the **Hosted deployments** menu, select a deployment. 2. Under **Custom endpoint alias**, select **Edit**. 3. Define a new alias. Make sure you choose something meaningful to you. @@ -44,7 +44,7 @@ To add an alias to an existing deployment: To remove an alias from your deployment, or if you want to re-assign an alias to another deployment, follow these steps: -1. From the **Deployments** menu, select a deployment. +1. From the **Hosted deployments** menu, select a deployment. 2. Under **Custom endpoint alias**, select **Edit**. 3. Remove the text from the **Custom endpoint alias** text box. 4. Select **Update alias**. diff --git a/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md b/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md index 68bd5f02f5..d3fbe32d7e 100644 --- a/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md +++ b/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md @@ -69,7 +69,7 @@ You can also update [dynamic cluster settings](../../../deploy-manage/deploy/sel To add or edit user settings: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. @@ -93,7 +93,7 @@ For a list of supported settings, check [Kibana settings](kibana://reference/clo To change Kibana settings: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. diff --git a/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md b/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md index 8563fb9cc6..f1f4dcfeb7 100644 --- a/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md +++ b/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md @@ -105,7 +105,7 @@ Bundles You must upload your files before you can apply them to your cluster configuration: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. 3. Under **Features**, select **Extensions**. 4. Select **Upload extension**. 5. Complete the extension fields, including the {{es}} version. @@ -133,7 +133,7 @@ Refer to [Managing plugins and extensions through the API](../../../deploy-manag After uploading your files, you can select to enable them when creating a new {{es}} deployment. For existing deployments, you must update your deployment configuration to use the new files: 1. Log in to the [{{ech}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. @@ -164,7 +164,7 @@ To update an extension with a new file version, 1. Prepare a new plugin or bundle. 2. On the **Extensions** page, [upload a new extension](../../../deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles.md#ec-add-your-plugin). 3. Make your new files available by uploading them. -4. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +4. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 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 de1726406a..b911ff34ec 100644 --- a/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md +++ b/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md @@ -20,7 +20,7 @@ For {{ece}} deployments, you can use [platform monitoring](/deploy-manage/monito To access cluster performance metrics: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention. diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md index 6f65caafb9..ed7e8d61e7 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md @@ -94,5 +94,5 @@ On the **Stack Monitoring** page, you’ll see cluster alerts that require your If you encounter problems, see [Troubleshooting monitoring](../monitoring-data/monitor-troubleshooting.md). :::{tip} -If you're using {{ech}} or {{ece}}, then you can also get a direct link to the relevant **Stack Monitoring** page from the **Deployments** > **Logs and metrics** page. [Learn more](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md#access-kibana-monitoring). +If you're using {{ech}} or {{ece}}, then you can also get a direct link to the relevant **Stack Monitoring** page from the **Hosted deployments** > **Logs and metrics** page. [Learn more](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md#access-kibana-monitoring). :::: \ No newline at end of file diff --git a/deploy-manage/security/_snippets/create-filter.md b/deploy-manage/security/_snippets/create-filter.md index 129dd5ec17..72cfe87c62 100644 --- a/deploy-manage/security/_snippets/create-filter.md +++ b/deploy-manage/security/_snippets/create-filter.md @@ -1,4 +1,4 @@ 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. 3. Under the **Features** tab, open the **Traffic filters** page. 4. Select **Create filter**. \ No newline at end of file diff --git a/deploy-manage/security/ip-filtering-cloud.md b/deploy-manage/security/ip-filtering-cloud.md index db4b6fbda3..4078555bac 100644 --- a/deploy-manage/security/ip-filtering-cloud.md +++ b/deploy-manage/security/ip-filtering-cloud.md @@ -57,7 +57,7 @@ To create a rule set: :::{tab-item} {{ech}} :sync: ech 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - 2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. + 2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. 3. Under the **Features** tab, open the **Traffic filters** page. ::: :::{tab-item} {{ece}} @@ -112,7 +112,7 @@ You can edit a rule set name or change the allowed traffic sources using IPv4, o :::{tab-item} {{ech}} :sync: ech 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - 2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. + 2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. 3. Under the **Features** tab, open the **Traffic filters** page. ::: :::{tab-item} {{ece}} @@ -141,7 +141,7 @@ To delete a rule set with all its rules: :::{tab-item} {{ech}} :sync: ech 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - 2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. + 2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. 3. Under the **Features** tab, open the **Traffic filters** page. ::: :::{tab-item} {{ece}} diff --git a/deploy-manage/security/logging-configuration/enabling-audit-logs.md b/deploy-manage/security/logging-configuration/enabling-audit-logs.md index db602ac601..56042a354c 100644 --- a/deploy-manage/security/logging-configuration/enabling-audit-logs.md +++ b/deploy-manage/security/logging-configuration/enabling-audit-logs.md @@ -67,7 +67,7 @@ To enable audit logging in an {{ech}} deployment: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. 3. From your deployment menu, go to the **Edit** page. diff --git a/deploy-manage/security/secure-settings.md b/deploy-manage/security/secure-settings.md index c6f0c34004..038bc20a01 100644 --- a/deploy-manage/security/secure-settings.md +++ b/deploy-manage/security/secure-settings.md @@ -57,7 +57,7 @@ There are three types of secrets that you can use: Add keys and secret values to the keystore. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. @@ -73,7 +73,7 @@ Add keys and secret values to the keystore. When your keys and secret values are no longer needed, delete them from the keystore. 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. diff --git a/deploy-manage/security/traffic-filtering.md b/deploy-manage/security/traffic-filtering.md index 8b60f40956..b39ed1e886 100644 --- a/deploy-manage/security/traffic-filtering.md +++ b/deploy-manage/security/traffic-filtering.md @@ -95,7 +95,7 @@ To identify which rule sets are automatically applied to new deployments in your :::{tab-item} {{ech}} :sync: ech 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - 2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Deployments** page to view all of your deployments. + 2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. 3. Under the **Features** tab, open the **Traffic filters** page. ::: :::{tab-item} {{ece}} diff --git a/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md b/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md index 3bcbdf3c11..36538fdf53 100644 --- a/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md +++ b/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md @@ -62,7 +62,7 @@ We strongly recommend using three availability zones with at least 1 GB {{es}} n 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. Go to **Deployments** a select the **security-cluster**. +2. Go to **Hosted deployments** a select the **security-cluster**. 3. Configure regular [snapshots](/deploy-manage/tools/snapshot-and-restore/create-snapshots.md) of the security deployment. This is critical if you plan to create any native users. 4. Optional: [Enable monitoring](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md) on the security deployment to a dedicated monitoring deployment. diff --git a/reference/apm/cloud/apm-settings.md b/reference/apm/cloud/apm-settings.md index 7b2a70fc8b..dcb83bb0d8 100644 --- a/reference/apm/cloud/apm-settings.md +++ b/reference/apm/cloud/apm-settings.md @@ -28,7 +28,7 @@ User settings are appended to the `apm-server.yml` configuration file for your i To add user settings: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. diff --git a/solutions/observability/apps/configure-apm-server.md b/solutions/observability/apps/configure-apm-server.md index 1b94fcf711..1513f70baa 100644 --- a/solutions/observability/apps/configure-apm-server.md +++ b/solutions/observability/apps/configure-apm-server.md @@ -55,7 +55,7 @@ User settings are appended to the `apm-server.yml` configuration file for your i To add user settings: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Find your deployment on the home page in the **Hosted deployments** card and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +2. Find your deployment on the home page or on the **Hosted deployments** page, then select **Manage** to access its settings menus. On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. diff --git a/solutions/observability/apps/secret-token.md b/solutions/observability/apps/secret-token.md index de2cb0fcf3..71d023aea9 100644 --- a/solutions/observability/apps/secret-token.md +++ b/solutions/observability/apps/secret-token.md @@ -27,7 +27,7 @@ Secret tokens are not applicable for the RUM Agent, as there is no way to preven ## Create a secret token [apm-create-secret-token] ::::{note} -{{ech}} and {{ece}} deployments provision a secret token when the deployment is created. The secret token can be found and reset in the {{ecloud}} Console under **Deployments** — **APM & Fleet**. +{{ech}} and {{ece}} deployments provision a secret token when the deployment is created. The secret token can be found and reset in the {{ecloud}} Console under **Hosted deployments** — **APM & Fleet**. :::: diff --git a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md index f01da9b3d9..22b8f6a55a 100644 --- a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md +++ b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md @@ -18,7 +18,7 @@ The **Hosted deployments** page in the Cloud UI provides several ways to find de * Check the visual health indicators of deployments * 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: +* Add filters to the **Hosted deployments** view to filter for specific conditions: :::{image} /troubleshoot/images/cloud-enterprise-deployment-filter.png :alt: Add a filter diff --git a/troubleshoot/ingest/elastic-serverless-forwarder.md b/troubleshoot/ingest/elastic-serverless-forwarder.md index b64811f768..b3344e7353 100644 --- a/troubleshoot/ingest/elastic-serverless-forwarder.md +++ b/troubleshoot/ingest/elastic-serverless-forwarder.md @@ -17,7 +17,7 @@ mapped_pages: You can view the status of deployment actions and get additional information on events, including why a particular event fails e.g. misconfiguration details. -1. On the Applications page for **serverlessrepo-elastic-serverless-forwarder**, click **Deployments**. +1. On the Applications page for **serverlessrepo-elastic-serverless-forwarder**, click **Hosted deployments**. 2. You can view the **Deployment history** here and refresh the page for updates as the application deploys. It should take around 5 minutes to deploy — if the deployment fails for any reason, the create events will be rolled back, and you will be able to see an explanation for which event failed. ::::{note} From d08d44d50b558a6c00dfd4ef89d5dc260dac8667 Mon Sep 17 00:00:00 2001 From: Florent Le Borgne Date: Thu, 3 Apr 2025 15:43:17 +0200 Subject: [PATCH 3/6] revert to Deployments when it's not explicitly about ECH --- .../find-manage-deployment-ech-and-ece.md | 9 ++++++++ .../autoscaling/autoscaling-in-ece-and-ech.md | 23 +++++++------------ .../deploy/cloud-enterprise/access-kibana.md | 2 +- .../add-custom-bundles-plugins.md | 2 +- .../deploy/cloud-enterprise/add-plugins.md | 2 +- .../advanced-cluster-configuration.md | 2 +- .../cloud-enterprise/customize-deployment.md | 2 +- .../edit-stack-settings-apm.md | 2 +- .../edit-stack-settings-elasticsearch.md | 2 +- .../edit-stack-settings-enterprise.md | 2 +- .../edit-stack-settings-kibana.md | 2 +- .../keep-track-of-deployment-activity.md | 2 +- .../cloud-enterprise/resize-deployment.md | 4 ++-- .../search-filter-deployments.md | 2 +- .../restart-an-ece-deployment.md | 4 ++-- deploy-manage/monitor/cloud-health-perf.md | 7 +++--- .../ece-monitoring-ece-access.md | 2 +- .../_snippets/cloud-monitoring-access.md | 8 +++---- .../ece-ech-stack-monitoring.md | 8 +++---- .../remote-clusters/ece-migrate-ccs.md | 2 +- .../ece-remote-cluster-ece-ess.md | 2 +- .../ece-remote-cluster-other-ece.md | 4 ++-- .../ece-remote-cluster-same-ece.md | 2 +- .../ece-remote-cluster-self-managed.md | 4 ++-- .../enabling-audit-logs.md | 2 +- deploy-manage/security/secure-settings.md | 4 ++-- deploy-manage/security/traffic-filtering.md | 2 +- .../snapshot-and-restore/cloud-enterprise.md | 2 +- .../minio-on-premise-repository.md | 2 +- .../uninstall/delete-a-cloud-deployment.md | 6 ++--- .../deployment-or-cluster/upgrade-on-ece.md | 4 ++-- manage-data/lifecycle/data-tiers.md | 9 ++++---- .../migrate-index-management.md | 4 ++-- .../apm/cloud-enterprise/apm-settings.md | 2 +- reference/fleet/fleet-server-scalability.md | 4 ++-- .../security/ai/connect-to-azure-openai.md | 2 +- .../cloud-enterprise/cloud-enterprise.md | 4 ++-- .../deployment-health-warnings.md | 2 +- .../cloud-enterprise/heap-dumps.md | 6 ++--- .../cloud-enterprise/thread-dumps.md | 2 +- 40 files changed, 79 insertions(+), 79 deletions(-) create mode 100644 deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md diff --git a/deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md b/deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md new file mode 100644 index 0000000000..642769da81 --- /dev/null +++ b/deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md @@ -0,0 +1,9 @@ +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) or ECE [Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). + +2. On the home page, find your deployment. + + :::{tip} + If you have many deployments, you can instead go to the **Hosted deployments** ({{ech}}) or **Deployments** ({{ece}}) page. On that page, you can narrow your deployments by name, ID, or choose from several other filters. + ::: + +3. Select **Manage**. \ No newline at end of file diff --git a/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md b/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md index 219ab0389c..44df11fb16 100644 --- a/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md +++ b/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md @@ -96,16 +96,12 @@ In {{ece}}, the following additional limitations apply: To enable or disable autoscaling on a deployment: -1. Log in to the ECE [Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md) or [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - -2. On the **Hosted deployments** page, select your deployment. - - Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. - +:::{include} ../_snippets/find-manage-deployment-ech-and-ece.md +::: -3. In your deployment menu, select **Edit**. -4. Select desired autoscaling configuration for this deployment using **Enable Autoscaling for:** dropdown menu. -5. Select **Confirm** to have the autoscaling change and any other settings take effect. All plan changes are shown on the Deployment **Activity** page. +4. Under the deployment's name in the navigation menu, select **Edit**. +5. Select desired autoscaling configuration for this deployment using **Enable Autoscaling for:** dropdown menu. +6. Select **Confirm** to have the autoscaling change and any other settings take effect. All plan changes are shown on the Deployment **Activity** page. When autoscaling has been enabled, the autoscaled nodes resize according to the [autoscaling settings](#ec-autoscaling-update). Current sizes are shown on the deployment overview page. @@ -115,13 +111,10 @@ When autoscaling has been disabled, you need to adjust the size of data tiers an Each autoscaling setting is configured with a default value. You can adjust these if necessary, as follows: -1. Log in to the ECE [Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md) or [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - -2. On the **Hosted deployments** page, select your deployment. - - Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. +:::{include} ../_snippets/find-manage-deployment-ech-and-ece.md +::: -3. In your deployment menu, select **Edit**. +3. Under the deployment's name in the navigation menu, select **Edit**. 4. To update a data tier: 1. Use the dropdown box to set the **Maximum size per zone** to the largest amount of resources that should be allocated to the data tier automatically. The resources will not scale above this value. diff --git a/deploy-manage/deploy/cloud-enterprise/access-kibana.md b/deploy-manage/deploy/cloud-enterprise/access-kibana.md index 8553e08a36..0cf330bb65 100644 --- a/deploy-manage/deploy/cloud-enterprise/access-kibana.md +++ b/deploy-manage/deploy/cloud-enterprise/access-kibana.md @@ -18,7 +18,7 @@ Most deployment templates include a Kibana instance, but if it wasn’t part of To access Kibana: 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md b/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md index dc6f9bfc79..d8ff85c74f 100644 --- a/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md +++ b/deploy-manage/deploy/cloud-enterprise/add-custom-bundles-plugins.md @@ -37,7 +37,7 @@ Here are some examples of custom bundles you can add: Custom plugins can include the official Elasticsearch plugins not provided with Elastic Cloud Enterprise, any of the community-sourced plugins, or plugins that you write yourself. 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. From the **Hosted deployments** page, select your deployment. +2. From the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/add-plugins.md b/deploy-manage/deploy/cloud-enterprise/add-plugins.md index f55a7930be..773003eb9d 100644 --- a/deploy-manage/deploy/cloud-enterprise/add-plugins.md +++ b/deploy-manage/deploy/cloud-enterprise/add-plugins.md @@ -36,7 +36,7 @@ The deployment spins up with the plugins installed. To add plugins to an existing deployment: 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/advanced-cluster-configuration.md b/deploy-manage/deploy/cloud-enterprise/advanced-cluster-configuration.md index 92a5471472..a3c4df4dc0 100644 --- a/deploy-manage/deploy/cloud-enterprise/advanced-cluster-configuration.md +++ b/deploy-manage/deploy/cloud-enterprise/advanced-cluster-configuration.md @@ -13,7 +13,7 @@ Most configuration changes can be made safely from other parts of the Cloud UI. To edit the cluster configuration directly: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/customize-deployment.md b/deploy-manage/deploy/cloud-enterprise/customize-deployment.md index 016c5a665d..9be26ecc73 100644 --- a/deploy-manage/deploy/cloud-enterprise/customize-deployment.md +++ b/deploy-manage/deploy/cloud-enterprise/customize-deployment.md @@ -20,7 +20,7 @@ The configurable components and allowed values available on the Edit page depend To customize your deployment: 1. [Log into the Cloud UI](./log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other [filters](./search-filter-deployments.md). To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md index 396b97013f..cbfbebd156 100644 --- a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md +++ b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md @@ -49,7 +49,7 @@ Be aware that some settings could break your cluster if set incorrectly and that To change APM settings: 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md index f7ed38c90a..4c517d2a18 100644 --- a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md +++ b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md @@ -18,7 +18,7 @@ ECE blocks the configuration of certain settings that could break your cluster i To change {{es}} user settings: 1. [Log into the Cloud UI](./log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md index b7b4779ff9..103fb14f2e 100644 --- a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md +++ b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md @@ -20,7 +20,7 @@ Refer to the [Configuration settings reference](https://www.elastic.co/guide/en/ To add user settings: 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md index 1df08fe84c..5484b911fd 100644 --- a/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md +++ b/deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md @@ -18,7 +18,7 @@ Be aware that some settings that could break your cluster if set incorrectly and To change Kibana settings: 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 e9ed1229d2..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 @@ -13,7 +13,7 @@ The deployment **Activity** page gives you a convenient way to follow all config To view the activity for a deployment: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/resize-deployment.md b/deploy-manage/deploy/cloud-enterprise/resize-deployment.md index 94db3a6d10..c7002ba696 100644 --- a/deploy-manage/deploy/cloud-enterprise/resize-deployment.md +++ b/deploy-manage/deploy/cloud-enterprise/resize-deployment.md @@ -17,7 +17,7 @@ You can also enable autoscaling on a deployment to have the available resources To resize a deployment: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -46,7 +46,7 @@ This example shows you how to change an existing, very basic deployment to use h To scale your deployment from very small to very large: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md index f87b0035d4..558dafdbef 100644 --- a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md +++ b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md @@ -10,7 +10,7 @@ mapped_pages: When you installed Elastic Cloud Enterprise and [logged into the Cloud UI](log-into-cloud-ui.md) for the first time, you were greeted by two deployments. We’ve also shown you how to [create your own first deployment](create-deployment.md), but that still only makes a few deployments. What if you had hundreds of deployments to look after or maybe even a thousand? How would you find the ones that need your attention? -The **Hosted deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system: +The **Deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system: * Check the visual health indicators of deployments * Search for partial or whole deployment names or IDs in the search text box diff --git a/deploy-manage/maintenance/start-stop-services/restart-an-ece-deployment.md b/deploy-manage/maintenance/start-stop-services/restart-an-ece-deployment.md index e42666eb41..87d070e1ac 100644 --- a/deploy-manage/maintenance/start-stop-services/restart-an-ece-deployment.md +++ b/deploy-manage/maintenance/start-stop-services/restart-an-ece-deployment.md @@ -3,7 +3,7 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-restart-deployment.html applies_to: deployment: - ece: + ece: all --- # Restart an ECE deployment [ece-restart-deployment] @@ -11,7 +11,7 @@ applies_to: To restart a running or a stopped deployment: 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/monitor/cloud-health-perf.md b/deploy-manage/monitor/cloud-health-perf.md index 79a94dfe2b..c83c333dc4 100644 --- a/deploy-manage/monitor/cloud-health-perf.md +++ b/deploy-manage/monitor/cloud-health-perf.md @@ -22,9 +22,10 @@ The deployment **Health** page provides detailed information on health issues, i To view the health for a deployment: -1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) or [Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. -3. In your deployment menu, select **Health**. +:::{include} ../_snippets/find-manage-deployment-ech-and-ece.md +::: + +3. Under the deployment's name in the navigation menu, select **Health**. The **Health** page provides the following information: diff --git a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md index 32a41d7a94..fe854796ff 100644 --- a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md +++ b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md @@ -29,7 +29,7 @@ If a {{kib}} instance exists for the deployment, the following {{kib}} logs and To access logs and metrics for your deployment: 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. From the **Hosted deployments** page, select your deployment. +2. From the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md b/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md index cba5306286..c73aacaf0e 100644 --- a/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md +++ b/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md @@ -1,9 +1,7 @@ -1. Log into [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) (ECH) or [the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md) (ECE). -2. On the **Hosted deployments** page, select your deployment. +:::{include} ../_snippets/find-manage-deployment-ech-and-ece.md +::: - Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. - -3. From your deployment menu, go to the **Logs and Metrics** page. +3. Under the deployment's name in the navigation menu, select **Logs and metrics**. 4. Select the corresponding **View** button to check the logs or metrics data. Alternatively, you can access logs and metrics directly on the {{kib}} **Logs** and **Stack Monitoring** pages in the target monitoring deployment. \ No newline at end of file diff --git a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md index 86e41766a5..094dd2b5b2 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md @@ -72,12 +72,10 @@ Elastic manages the installation and configuration of the monitoring agent for y To enable monitoring on your deployment: -1. Log into [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) (ECH) or [the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md) (ECE). -2. On the **Hosted deployments** page, select your deployment. - - Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. +:::{include} ../_snippets/find-manage-deployment-ech-and-ece.md +::: -3. From your deployment menu, go to the **Logs and metrics** page. +3. Under the deployment's name in the navigation menu, select **Logs and metrics**. 4. Under **Ship to a deployment**, select **Enable**. 5. Choose where to send your logs and metrics. Select **Save**. diff --git a/deploy-manage/remote-clusters/ece-migrate-ccs.md b/deploy-manage/remote-clusters/ece-migrate-ccs.md index af36c9e2d0..b54d269fc3 100644 --- a/deploy-manage/remote-clusters/ece-migrate-ccs.md +++ b/deploy-manage/remote-clusters/ece-migrate-ccs.md @@ -20,7 +20,7 @@ You can make this change in the user Cloud UI. The only drawback of this method 1. The first step for any approach is to remove the remote clusters from your deployment. You will need to add them back later. 2. From the deployment menu, open the **Snapshots** page and click **Take Snapshot now**. Wait for the snapshot to finish. -3. From the main **Hosted deployments** page, click **Create deployment**. Next to **Settings** toggle on **Restore snapshot data**, and then select your deployment and the snapshot that you created. +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} /deploy-manage/images/cloud-enterprise-ce-create-from-snapshot-updated.png :alt: Create a Deployment using a snapshot 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 cae29c18ef..1146eeff72 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md @@ -51,7 +51,7 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore. 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 a02593a8fa..0f83c48041 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md @@ -52,7 +52,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo ::::{dropdown} The CA is public 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -80,7 +80,7 @@ If you later need to update the remote connection with different permissions, yo ::::{dropdown} The CA is private 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 3f8abdf807..3fa409911c 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md @@ -50,7 +50,7 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore. 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 19a589344f..7c44080bee 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md @@ -54,7 +54,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo ::::{dropdown} The CA is public 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -82,7 +82,7 @@ If you later need to update the remote connection with different permissions, yo ::::{dropdown} The CA is private 1. [Log into the Cloud UI](../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/security/logging-configuration/enabling-audit-logs.md b/deploy-manage/security/logging-configuration/enabling-audit-logs.md index 56042a354c..f977098e3c 100644 --- a/deploy-manage/security/logging-configuration/enabling-audit-logs.md +++ b/deploy-manage/security/logging-configuration/enabling-audit-logs.md @@ -91,7 +91,7 @@ To enable audit logging in an ECE deployment: 1. [Log in to the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. 3. From your deployment menu, go to the **Edit** page. diff --git a/deploy-manage/security/secure-settings.md b/deploy-manage/security/secure-settings.md index eada51e087..b1aae0c58a 100644 --- a/deploy-manage/security/secure-settings.md +++ b/deploy-manage/security/secure-settings.md @@ -99,7 +99,7 @@ There are three types of secrets that you can use: Add keys and secret values to the keystore. 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -116,7 +116,7 @@ Add keys and secret values to the keystore. When your keys and secret values are no longer needed, delete them from the keystore. 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/security/traffic-filtering.md b/deploy-manage/security/traffic-filtering.md index 149df82765..472d95f8cb 100644 --- a/deploy-manage/security/traffic-filtering.md +++ b/deploy-manage/security/traffic-filtering.md @@ -77,7 +77,7 @@ This section offers suggestions on how to manage and analyze the impact of your #### Review the rule sets associated with a deployment 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) or [Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. 3. Select the **Security** tab on the left-hand side menu bar. Traffic filter rule sets are listed under **Traffic filters**. diff --git a/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md b/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md index 1c8d0f6e7e..8760cde90e 100644 --- a/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md +++ b/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md @@ -89,7 +89,7 @@ To change the snapshot repository for an existing Elasticsearch cluster: 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). 2. Optional: If you need to use a repository that is not yet listed, add a snapshot repository configuration first. -3. From the **Hosted deployments** page, select your deployment. +3. From the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 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 914d4b27d6..7327b6831b 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 @@ -144,7 +144,7 @@ As an extra verification step, you can restore a cluster using the snapshots tha 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). 2. Get the plan from your test cluster. - 1. From the **Hosted deployments** page, select your deployment. + 1. From the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/deploy-manage/uninstall/delete-a-cloud-deployment.md b/deploy-manage/uninstall/delete-a-cloud-deployment.md index a41e5b7a35..9c0851425b 100644 --- a/deploy-manage/uninstall/delete-a-cloud-deployment.md +++ b/deploy-manage/uninstall/delete-a-cloud-deployment.md @@ -54,7 +54,7 @@ All data is lost. Billing for usage is by the hour and any outstanding charges f To delete an {{ece}} deployment: 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -72,7 +72,7 @@ Terminating a deployment stops all running instances and **deletes all data**. O To terminate an {{ece}} deployment, 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -86,7 +86,7 @@ You can restore a deployment that was previously terminated to its original conf To restore a terminated deployment, 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. 3. In the **Deployment Management** section, select **Restore** and then acknowledge the confirmation message. diff --git a/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md b/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md index 15ae9aff03..d1e1805da0 100644 --- a/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md +++ b/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ece.md @@ -21,7 +21,7 @@ Once you're [prepared to upgrade](/deploy-manage/upgrade/prepare-to-upgrade.md), ## Perform the upgrade 1. [Log in to the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -30,7 +30,7 @@ Once you're [prepared to upgrade](/deploy-manage/upgrade/prepare-to-upgrade.md), 3. Click **Upgrade**, then **Confirm upgrade**. The new configuration takes a few minutes to create. ::::{note} - If any incompatibilities are detected when you attempt to upgrade, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. After resolving the issues, return to the **Hosted deployments** page and restart the upgrade. Also check the [release notes](/release-notes/index.md) to stay aware of changes and known issues for the version you're upgrading to. + If any incompatibilities are detected when you attempt to upgrade, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. After resolving the issues, return to the **Deployments** page and restart the upgrade. Also check the [release notes](/release-notes/index.md) to stay aware of changes and known issues for the version you're upgrading to. :::: **Security realm settings** diff --git a/manage-data/lifecycle/data-tiers.md b/manage-data/lifecycle/data-tiers.md index 2d05641adc..39a4be484d 100644 --- a/manage-data/lifecycle/data-tiers.md +++ b/manage-data/lifecycle/data-tiers.md @@ -103,9 +103,10 @@ To add a warm, cold, or frozen tier when you create a deployment: To add a data tier to an existing deployment: -1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body) or the {{ece}} admin console. -2. On the **Hosted deployments** page, select your deployment. -3. In your deployment menu, select **Edit**. +:::{include} /deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md +::: + +3. Under the deployment's name in the navigation menu, select **Edit**. 4. Click **+ Add capacity** for any data tiers to add. 5. Click **Save** at the bottom of the page to save your changes. @@ -170,7 +171,7 @@ To make sure that all data can be migrated from the data tier you want to disabl ::::{tab-item} Elastic Cloud Enterprise 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). - 2. From the **Hosted deployments** page, select your deployment. + 2. From the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md b/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md index e6f14c1b32..2be1b052cb 100644 --- a/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md +++ b/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md @@ -38,9 +38,9 @@ To configure ILM Migration in the console: :::{tab-item} Elastic Cloud Enterprise 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. From the **Hosted deployments** page, select your deployment. +2. From the **Deployments** page, select your deployment. - On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. + On the **Deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. 3. Near the top of the deployment overview, you should get a message to migrate from index curation to index lifecycle management (ILM) along with a **Start migration** button. 4. Select which index curation pattern you wish to migrate. diff --git a/reference/apm/cloud-enterprise/apm-settings.md b/reference/apm/cloud-enterprise/apm-settings.md index 0a81883bd3..866eb63891 100644 --- a/reference/apm/cloud-enterprise/apm-settings.md +++ b/reference/apm/cloud-enterprise/apm-settings.md @@ -45,7 +45,7 @@ Be aware that some settings could break your cluster if set incorrectly and that To change APM settings: 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/reference/fleet/fleet-server-scalability.md b/reference/fleet/fleet-server-scalability.md index f39f4a0f3e..f793558673 100644 --- a/reference/fleet/fleet-server-scalability.md +++ b/reference/fleet/fleet-server-scalability.md @@ -14,8 +14,8 @@ Refer to the [Scaling recommendations](#agent-policy-scaling-recommendations) se First modify your {{fleet}} deployment settings in {{ecloud}}: -1. Log in to {{ecloud}} and go to your deployment. -2. Under **Deployments > *deployment name***, click **Edit**. +1. Log in to {{ecloud}} and find your deployment. +2. Select **Manage**, then under the deployment's name in the navigation menu, click **Edit**. 3. Under {{integrations-server}}: * Modify the compute resources available to the server to accommodate a higher scale of {{agent}}s diff --git a/solutions/security/ai/connect-to-azure-openai.md b/solutions/security/ai/connect-to-azure-openai.md index 475f11e79a..389c21c16a 100644 --- a/solutions/security/ai/connect-to-azure-openai.md +++ b/solutions/security/ai/connect-to-azure-openai.md @@ -49,7 +49,7 @@ The following video demonstrates these steps (click to watch). Now, set up the Azure OpenAI model: 1. From within your Azure OpenAI deployment, select **Model deployments**, then click **Manage deployments**. -2. On the **Hosted deployments** page, select **Create new deployment**. +2. On the **Deployments** page, select **Create new deployment**. 3. Under **Select a model**, choose `gpt-4o` or `gpt-4 turbo`. 4. Set the model version to "Auto-update to default". diff --git a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md index 24623fbc80..4bb18650ac 100644 --- a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md +++ b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md @@ -14,11 +14,11 @@ mapped_pages: When you installed Elastic Cloud Enterprise and [logged into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md) for the first time, you were greeted by two deployments. We’ve also shown you how to [create your own first deployment](../../../deploy-manage/deploy/cloud-enterprise/create-deployment.md), but that still only makes a few deployments. What if you had hundreds of deployments to look after or maybe even a thousand? How would you find the ones that need your attention? -The **Hosted deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system: +The **Deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system: * Check the visual health indicators of deployments * Search for partial or whole deployment names or IDs in the search text box -* Add filters to the **Hosted deployments** view to filter for specific conditions: +* Add filters to the **Deployments** view to filter for specific conditions: :::{image} /troubleshoot/images/cloud-enterprise-deployment-filter.png :alt: Add a filter diff --git a/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md b/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md index d5d416e704..39b5dd1566 100644 --- a/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md +++ b/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md @@ -9,7 +9,7 @@ mapped_pages: # Troubleshoot deployment health warnings [ece-deployment-no-op] -The {{ece}} **Hosted deployments** page shows the current status of your active deployments. From time to time you may get one or more health warnings, such as the following: +The {{ece}} **Deployments** page shows the current status of your active deployments. From time to time you may get one or more health warnings, such as the following: :::{image} /troubleshoot/images/cloud-ec-ce-deployment-health-warning.png :alt: A screen capture of the deployment page showing a typical warning: Deployment health warning: Latest change to {{es}} configuration failed. diff --git a/troubleshoot/deployments/cloud-enterprise/heap-dumps.md b/troubleshoot/deployments/cloud-enterprise/heap-dumps.md index 2fa1dfba2f..1f11c0ea2f 100644 --- a/troubleshoot/deployments/cloud-enterprise/heap-dumps.md +++ b/troubleshoot/deployments/cloud-enterprise/heap-dumps.md @@ -16,7 +16,7 @@ From the Elastic Cloud Enterprise console you can capture JVM heap dumps from de You can view and download captured heap dumps for a given deployment. 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -45,7 +45,7 @@ The JVM will be paused while the heap dump is being captured, so there may be a 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. @@ -54,7 +54,7 @@ The JVM will be paused while the heap dump is being captured, so there may be a Alternatively, you can capture an on-demand heap dump directly from the **Heap dumps** page. 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. diff --git a/troubleshoot/deployments/cloud-enterprise/thread-dumps.md b/troubleshoot/deployments/cloud-enterprise/thread-dumps.md index 722cee179b..318505803b 100644 --- a/troubleshoot/deployments/cloud-enterprise/thread-dumps.md +++ b/troubleshoot/deployments/cloud-enterprise/thread-dumps.md @@ -16,7 +16,7 @@ You can capture JVM thread dumps from deployment instances. This can help discov You can capture a thread dump from the deployment overview page. 1. [Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. On the **Hosted deployments** page, select your deployment. +2. On the **Deployments** page, select your deployment. Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. From 597972765c60a67d4313c1d117cdbc86fbc20413 Mon Sep 17 00:00:00 2001 From: Florent Le Borgne Date: Thu, 3 Apr 2025 15:58:12 +0200 Subject: [PATCH 4/6] more fixes --- .../deploy/cloud-enterprise/create-deployment.md | 2 +- .../cloud-enterprise/ece-regional-deployment-aliases.md | 4 ++-- .../deploy/cloud-enterprise/search-filter-deployments.md | 2 +- .../monitor/stack-monitoring/kibana-monitoring-data.md | 2 +- .../cloud-enterprise-orchestrator/manage-users-roles.md | 2 +- .../manage-elastic-user-cloud.md | 8 +++----- solutions/observability/apps/secret-token.md | 4 +++- troubleshoot/ingest/elastic-serverless-forwarder.md | 2 +- 8 files changed, 13 insertions(+), 13 deletions(-) diff --git a/deploy-manage/deploy/cloud-enterprise/create-deployment.md b/deploy-manage/deploy/cloud-enterprise/create-deployment.md index 885db51e1d..631f477afc 100644 --- a/deploy-manage/deploy/cloud-enterprise/create-deployment.md +++ b/deploy-manage/deploy/cloud-enterprise/create-deployment.md @@ -14,7 +14,7 @@ Each deployment is based on a [deployment template](./deployment-templates.md), To create a deployment in ECE: -1. From the Cloud UI **Hosted deployments** view, select **Create deployment**. +1. From the Cloud UI **Deployments** view, select **Create deployment**. 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. diff --git a/deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md b/deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md index f409de70ff..9d0118dd31 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-regional-deployment-aliases.md @@ -19,7 +19,7 @@ Before setting up your custom alias, your platform administrator must enable the To add an alias to an existing deployment: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. From the **Hosted deployments** menu, select a deployment. +2. From the **Deployments** menu, select a deployment. 3. Under **Custom endpoint alias**, select **Edit**. 4. Define a new alias. Make sure you choose something meaningful to you. @@ -34,7 +34,7 @@ To add an alias to an existing deployment: To remove an alias from your deployment, or if you want to re-assign an alias to another deployment, follow these steps: 1. [Log into the Cloud UI](log-into-cloud-ui.md). -2. From the **Hosted deployments** menu, select a deployment. +2. From the **Deployments** menu, select a deployment. 3. Under **Custom endpoint alias**, select **Edit**. 4. Remove the text from the **Custom endpoint alias** text box. 5. Select **Update alias**. diff --git a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md index 558dafdbef..8c64c747ae 100644 --- a/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md +++ b/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md @@ -14,7 +14,7 @@ The **Deployments** page in the Cloud UI provides several ways to find deploymen * Check the visual health indicators of deployments * Search for partial or whole deployment names or IDs in the search text box -* Add filters to the **Hosted deployments** view to filter for specific conditions: +* Add filters to the **Deployments** view to filter for specific conditions: :::{image} /deploy-manage/images/cloud-enterprise-deployment-filter.png :alt: Add a filter diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md index ed7e8d61e7..b1f791e7ea 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md @@ -94,5 +94,5 @@ On the **Stack Monitoring** page, you’ll see cluster alerts that require your If you encounter problems, see [Troubleshooting monitoring](../monitoring-data/monitor-troubleshooting.md). :::{tip} -If you're using {{ech}} or {{ece}}, then you can also get a direct link to the relevant **Stack Monitoring** page from the **Hosted deployments** > **Logs and metrics** page. [Learn more](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md#access-kibana-monitoring). +If you're using {{ech}} or {{ece}}, then you can also get a direct link to the relevant **Stack Monitoring** page from the deployment's **Logs and metrics** page. [Learn more](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md#access-kibana-monitoring). :::: \ No newline at end of file diff --git a/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md b/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md index 36538fdf53..3bcbdf3c11 100644 --- a/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md +++ b/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md @@ -62,7 +62,7 @@ We strongly recommend using three availability zones with at least 1 GB {{es}} n 1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md). -2. Go to **Hosted deployments** a select the **security-cluster**. +2. Go to **Deployments** a select the **security-cluster**. 3. Configure regular [snapshots](/deploy-manage/tools/snapshot-and-restore/create-snapshots.md) of the security deployment. This is critical if you plan to create any native users. 4. Optional: [Enable monitoring](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md) on the security deployment to a dedicated monitoring deployment. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md b/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md index 51608b0805..f52cd9aab6 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md @@ -28,12 +28,10 @@ The `elastic` user should be not be used unless you have no other way to access To reset the password: -1. Log in to the Elastic Cloud Console. -2. Find your deployment on the home page and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments. +:::{include} /deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md +::: - On the **Hosted deployments** page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. - -3. From your deployment menu, go to **Security**. +3. Under the deployment's name in the navigation menu, select **Security**. 4. Select **Reset password**. 5. Copy down the auto-generated a password for the `elastic` user. diff --git a/solutions/observability/apps/secret-token.md b/solutions/observability/apps/secret-token.md index 71d023aea9..b40d0d6658 100644 --- a/solutions/observability/apps/secret-token.md +++ b/solutions/observability/apps/secret-token.md @@ -26,8 +26,10 @@ Secret tokens are not applicable for the RUM Agent, as there is no way to preven ## Create a secret token [apm-create-secret-token] +% This should be checked and updated, it doesn't looks like it's there by default vv + ::::{note} -{{ech}} and {{ece}} deployments provision a secret token when the deployment is created. The secret token can be found and reset in the {{ecloud}} Console under **Hosted deployments** — **APM & Fleet**. +{{ech}} and {{ece}} deployments provision a secret token when the deployment is created. The secret token can be found and reset in the {{ecloud}} Console under the deployment's **APM & Fleet** page. :::: diff --git a/troubleshoot/ingest/elastic-serverless-forwarder.md b/troubleshoot/ingest/elastic-serverless-forwarder.md index b3344e7353..b64811f768 100644 --- a/troubleshoot/ingest/elastic-serverless-forwarder.md +++ b/troubleshoot/ingest/elastic-serverless-forwarder.md @@ -17,7 +17,7 @@ mapped_pages: You can view the status of deployment actions and get additional information on events, including why a particular event fails e.g. misconfiguration details. -1. On the Applications page for **serverlessrepo-elastic-serverless-forwarder**, click **Hosted deployments**. +1. On the Applications page for **serverlessrepo-elastic-serverless-forwarder**, click **Deployments**. 2. You can view the **Deployment history** here and refresh the page for updates as the application deploys. It should take around 5 minutes to deploy — if the deployment fails for any reason, the create events will be rolled back, and you will be able to see an explanation for which event failed. ::::{note} From bfd38420f367bab17056bbc7343acaa65670cec5 Mon Sep 17 00:00:00 2001 From: Florent Le Borgne Date: Thu, 3 Apr 2025 16:01:25 +0200 Subject: [PATCH 5/6] absolutely use absolute links sometimes --- .../monitor/stack-monitoring/ece-ech-stack-monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md index 094dd2b5b2..4826cb6a33 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md @@ -72,7 +72,7 @@ Elastic manages the installation and configuration of the monitoring agent for y To enable monitoring on your deployment: -:::{include} ../_snippets/find-manage-deployment-ech-and-ece.md +:::{include} /deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md ::: 3. Under the deployment's name in the navigation menu, select **Logs and metrics**. From 397fccdc45381a65e98e45fad7d0192cdb2d6241 Mon Sep 17 00:00:00 2001 From: Florent Le Borgne Date: Thu, 3 Apr 2025 16:21:22 +0200 Subject: [PATCH 6/6] Did I already mention absolute links are absolutely the best? --- .../stack-monitoring/_snippets/cloud-monitoring-access.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md b/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md index c73aacaf0e..b18c7f958e 100644 --- a/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md +++ b/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md @@ -1,4 +1,4 @@ -:::{include} ../_snippets/find-manage-deployment-ech-and-ece.md +:::{include} /deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md ::: 3. Under the deployment's name in the navigation menu, select **Logs and metrics**.