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 f5d597fb0b..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 **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 **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/elastic-cloud/access-kibana.md b/deploy-manage/deploy/elastic-cloud/access-kibana.md index 82e8c0011d..6b29b10b49 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 9d71c9bcf9..89e74dbfca 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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/custom-endpoint-aliases.md b/deploy-manage/deploy/elastic-cloud/custom-endpoint-aliases.md index 565d194af5..c72e59fd80 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 39c2f50ae0..ff65d1c3dd 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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 4efc0c4ec8..64fc93fc39 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 103fd256c9..753138ec3c 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 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,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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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..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] 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 b663b37a1d..19e412aa6d 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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 56840c4710..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 **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/stack-monitoring/_snippets/cloud-monitoring-access.md b/deploy-manage/monitor/stack-monitoring/_snippets/cloud-monitoring-access.md index 10499a2e7b..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,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 **Deployments** page, select your deployment. +:::{include} /deploy-manage/_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 4f8db3d3f5..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,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 **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} /deploy-manage/_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/monitor/stack-monitoring/kibana-monitoring-data.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md index 6f65caafb9..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 **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/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/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/ip-traffic-filtering.md b/deploy-manage/security/ip-traffic-filtering.md index ed447d4f87..1c6c3bff69 100644 --- a/deploy-manage/security/ip-traffic-filtering.md +++ b/deploy-manage/security/ip-traffic-filtering.md @@ -20,5 +20,4 @@ The way that you configure IP traffic filters depends on your deployment type: * **In {{eck}} and self-managed clusters**, traffic filters are applied at the cluster level using `elasticsearch.yml`. [Learn how to configure traffic filtering at the cluster level](/deploy-manage/security/ip-filtering-basic.md). -If you use {{ech}} or {{eck}}, then other [traffic filtering](/deploy-manage/security/traffic-filtering.md) methods are also available. - +If you use {{ech}} or {{eck}}, then other [traffic filtering](/deploy-manage/security/traffic-filtering.md) methods are also available. \ No newline at end of file diff --git a/deploy-manage/security/logging-configuration/enabling-audit-logs.md b/deploy-manage/security/logging-configuration/enabling-audit-logs.md index f6a73999e4..f977098e3c 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 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 2550d7bae7..b1aae0c58a 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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. diff --git a/deploy-manage/security/traffic-filtering.md b/deploy-manage/security/traffic-filtering.md index bc93371412..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**. @@ -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/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..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 **Deployments** page to view all of your deployments. +:::{include} /deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md +::: - 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. 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/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 c44977b1df..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 **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. @@ -154,9 +155,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. 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..2be1b052cb 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. 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/apm-settings.md b/reference/apm/cloud/apm-settings.md index c4ca425302..dcb83bb0d8 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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/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/observability/apps/configure-apm-server.md b/solutions/observability/apps/configure-apm-server.md index a8e07831be..a87f40f2c4 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 or on the **Hosted deployments** page, then select **Manage** to access its settings menus. - 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/secret-token.md b/solutions/observability/apps/secret-token.md index de2cb0fcf3..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 **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. ::::