ece manage deployments complete section refined

Author: eedugon

deploy-manage/deploy/cloud-enterprise.md

@@ -11,7 +11,7 @@ mapped_urls:
 
 {{ece}} (ECE) is an Elastic self-managed solution for deploying, orchestrating, and managing {{es}} clusters at scale. It provides a centralized platform that allows organizations to run {{es}}, {{kib}}, and other {{stack}} components across multiple machines.
 
-ECE evolves from the Elastic hosted Cloud SaaS offering into a standalone product. You can deploy ECE on public or private clouds, virtual machines, or your own premises.
+ECE evolves from the [{{ech}}](./elastic-cloud.md) offering into a standalone product. You can deploy ECE on public or private clouds, virtual machines, or your own premises.
 
 With {{ece}}, you can:
 

deploy-manage/deploy/cloud-enterprise/access-kibana.md

@@ -19,7 +19,7 @@ To access Kibana:
 
     Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
 
-3. Under **Applications**, select the Kibana **Launch** link and wait for Kibana to open.
+3. Under **Applications**, select the Kibana **Open** link and wait for Kibana to open.
 
     ::::{note} 
     Both ports 443 and 9243 can be used to access Kibana. SSO only works with 9243 on older deployments, where you will see an option in the Cloud UI to migrate the default to port 443. In addition, any version upgrade will automatically migrate the default port to 443.

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

@@ -7,63 +7,38 @@ mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-change-deployment.html
 ---
 
-# Configure your deployment [ece-change-deployment]
-
-In this section you will learn the different ways and possibilities to change your deployment configuration. There are several reasons why you might want to change the configuration of a deployment:
-
-* To increase or decrease deployment capacity by changing the amount of reserved memory and storage.
-* To enable [autoscaling](../../../deploy-manage/autoscaling.md) so that available resources for certain deployment components adjust automatically as the demands on them change.
-* To enable high availability by adjusting the number of availability zones that your deployment runs in.
-* To add, remove, or update {{es}} or {{kib}} configuration settings.
-* To upgrade to new versions of Elasticsearch. You can upgrade from one major version to another, such as from 7.17 to 8.0, or from one minor version to another, such as 8.9.0 to 8.9.2. You can’t downgrade versions.
-* To update Elasticsearch clusters and Kibana after an updated Elastic Stack pack for a particular version has been added to your Elastic Cloud Enterprise installation.
-* To change what plugins are available on your deployment.
-
-
-You can perform the following configuration changes to your deployments:
-
-* [](./customize-deployment.md): Learn how to change your deployment architecture, configure resources, autoscaling, data tiers, and other {{stack}} components, from the Edit UI.
-* [](./edit-stack-settings.md): Add, remove, or update {{es}} or {{kib}} YML configuration settings.
-* [](./resize-deployment.md): Scale 
-* [](./add-plugins.md): Enable or disable plugins from the list of available plugins.
-* [](./add-custom-bundles-plugins.md): Add custom plugins or configuration files to your {{es}} instances.
-* [](./resource-overrides.md): In certain use cases, extend the cluster capacity temporary.
-* [](./advanced-cluster-configuration.md): ...
-* 
+% document scope: introduction to deployment configuration use cases
 
-From the deployment menu you can also access to the configuration of the following features:
-
-* Logs and metrics (Stack monitoring).
-* Snapshots
-* Secure settings
-
-## Configuration use cases
-
-There are several reasons why you might want to change the configuration of a deployment:
+# Configure your deployment [ece-change-deployment]
 
-* To increase or decrease deployment capacity by changing the amount of reserved memory and storage.
-* To enable [autoscaling](../../../deploy-manage/autoscaling.md) so that available resources for certain deployment components adjust automatically as the demands on them change.
-* To enable high availability by adjusting the number of availability zones that your deployment runs in.
-* To add, remove, or update {{es}} or {{kib}} configuration settings.
-* To upgrade to new versions of Elasticsearch. You can upgrade from one major version to another, such as from 7.17 to 8.0, or from one minor version to another, such as 8.9.0 to 8.9.2. You can’t downgrade versions.
-* To update Elasticsearch clusters and Kibana after an updated Elastic Stack pack for a particular version has been added to your Elastic Cloud Enterprise installation.
-* To change what plugins are available on your deployment.
+You might want to change the configuration of your deployment to:
 
-## Applying changes
+* Add features, such as machine learning or APM (application performance monitoring).
+* Increase or decrease capacity by changing the amount of reserved memory and storage for different parts of your deployment.
+* Enable [autoscaling](../../../deploy-manage/autoscaling.md) so that the available resources for deployment components, such as data tiers and machine learning nodes, adjust automatically as the demands on them change over time.
+* Enable [high availability](./ece-ha.md), also known as fault tolerance, by adjusting the number of availability zones that parts of your deployment run on.
+* Upgrade to new versions of {{es}}. You can upgrade from one major version to another, such as from 6.8.23 to 7.17.27, or from one minor version to another, such as 6.1 to 6.2. You can’t downgrade versions.
+* Change what plugins or custom bundles are available on your {{es}} cluster.
+* Change {{es}}, {{kib}}, or other stack application YML configuration settings.
 
 For single availability zone deployments, there is downtime to portions of your cluster when changes are applied. For HA deployments and with the exception of major version upgrades, we can perform all these changes without interrupting your deployment. During the application of these changes, you can continue to search and index.
 
-Many changes can also be done in bulk: in one action, you can add more memory and storage, upgrade minor versions, adjust the number of plugins and adjust fault tolerance by changing the number of availability zones. Elastic Cloud Enterprise performs all of these changes with a grow-and-shrink operation, making an Elasticsearch cluster and other instances with the new configuration join the existing deployment. After re-joining, updated nodes recover their indexes and start handling requests. When all updated new nodes are ready, the old nodes that were replaced are removed. If you do a major version upgrade, you cannot change the cluster configuration at the same time. Perform these configuration changes separately.
+When updating an existing deployment, you can make multiple changes in a single configuration update. For example, you increase memory and storage, upgrade minor versions, adjust the number of plugins, and adjust fault tolerance by changing the number of availability zones—all in one action.
 
-::::{tip}
-When you scale up a deployment, existing data may be migrated to new nodes. For clusters containing large amounts of data, this migration can take some time, especially if your deployment is under a heavy workload. (Is your deployment under a heavy load? You might need to [stop routing requests](../../../deploy-manage/maintenance/ece/deployments-maintenance.md) first.)
+::::{note}
+When applying changes, existing data may be migrated to new nodes. For clusters containing large amounts of data, this migration can take some time, especially if your deployment is under a heavy workload. Refer to [Configuration strategies](./customize-deployment.md#configuration-strategies) to learn about the different ways ECE applies changes.
 ::::
 
-TBD - EDU
+## Preparing a deployment for production [ece-prepare-production]
+
+To make sure you’re all set for production, consider the following actions:
 
-This section describes how to configure and customize your deployments and the different features available for your deployments, such as:
+* [](./customize-deployment.md): Learn how to change your deployment architecture, configure resources, autoscaling, data tiers, and other {{stack}} components, from the **Edit** deployment view.
+* [](./edit-stack-settings.md): Add, remove, or update {{es}} or {{kib}} YML configuration settings.
+* [](./resize-deployment.md): Considerations when scaling deployments.
+* [](./add-plugins.md): Enable or disable plugins from the list of available extensions in ECE.
+* [](./add-custom-bundles-plugins.md): Add custom plugins or external configuration files to your {{es}} instances.
+* [](./ece-regional-deployment-aliases.md): Configure custom aliases to create predictable and human-readable URLs for your {{stack}} components, making them easier to share and use.
+* [](./resource-overrides.md): Temporary extend cluster capacity to improve stability.
 
-* Stack settings: 
-* Plugins and extensions: 
-* Custom bundles and plugins
-* 
+Refer to [](./working-with-deployments.md) for additional actions and configurable features for your deployments, such as snapshots, secure settings, and monitoring.

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, 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 customize the deployment parameters, including autoscaling, storage, memory, data tiers, and additional Elastic Stack components. Refer to [](./customize-deployment.md) for more information.
 
@@ -31,7 +31,7 @@ To create a deployment in ECE:
     * If the system templates do not meet your requirements, you can [modify them](./ece-configuring-ece-configure-system-templates.md) or [create your own custom templates](../../../deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md).
     ::::
 
-4. Choose your {{stack}} version. To manage available versions, refer to [](./manage-elastic-stack-versions.md).
+4. Choose your {{stack}} version. To manage available versions at platform level, refer to [](./manage-elastic-stack-versions.md).
 
 5. Optionally, [use snapshots](../../tools/snapshot-and-restore/cloud-enterprise.md) to back up your data, or [restore data from another deployment](../../tools/snapshot-and-restore/ece-restore-across-clusters.md).
 
@@ -53,26 +53,8 @@ After a deployment is spun up, you can scale the size and add other features; ho
 
 ## Next steps
 
-% TBD, we have to refine a bit this section
-
 That’s it! Now that you are up and running, you may want to:
 
 * [Start exploring with {{kib}}](./access-kibana.md), our open-source visualization tool. If you’re not familiar with adding data, yet, {{kib}} can show you how to index your data into {{es}}.
 * [Connect your applications to {{es}}](./connect-elasticsearch.md) to start [ingesting data](../../../manage-data/ingest.md)
 * Learn how to configure and [manage your deployment](./working-with-deployments.md)
-
-% From Shaina in Cloud, TBD.
-
-## Preparing a deployment for production [ec-prepare-production]
-
-To make sure you’re all set for production, consider the following actions:
-
-* [Plan for your expected workloads](/deploy-manage/production-guidance/pl) and consider how many availability zones you’ll need.
-* [Create a deployment](/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md) on the region you need and with a hardware profile that matches your use case.
-* [Change your configuration](/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md) by turning on autoscaling, adding high availability, or adjusting components of the Elastic Stack.
-* [Add extensions and plugins](/deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md) to use Elastic supported extensions or add your own custom dictionaries and scripts.
-* [Edit settings and defaults](/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) to fine tune the performance of specific features.
-* [Manage your deployment](/deploy-manage/deploy/elastic-cloud/manage-deployments.md) as a whole to restart, upgrade, stop routing, or delete.
-* [Set up monitoring](/deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) to learn how to configure your deployments for observability, which includes metric and log collection, troubleshooting views, and cluster alerts to automate performance monitoring.
-
-

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

@@ -7,12 +7,11 @@ mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-customize-deployment.html
 ---
 
-% Background and scope note: this document is about the Deployment -> Edit page, how ECE applies changes, and links to other configurable features
+% document scope: this document focuses on the Deployment -> Edit page, how ECE applies changes, and links to other configurable features
 
-# Customize your deployment [ece-customize-deployment]
+# Customize your deployment components [ece-customize-deployment]
 
-% TBD, refine this intro after checking the UI
-In ECE, you can customize your deployment at any time by selecting **Edit** from the deployment page. This allows you to modify the deployment architecture, adjust configuration settings, availability zones, resources, and enable or disable data tiers.
+In ECE, you can customize your deployment at any time by selecting **Edit** from the deployment page. This allows you to fine-tune its capacity and architecture, adjust configuration settings, availability zones, and enable or disable [data tiers](/manage-data/lifecycle/data-tiers.md).
 
 ::::{note}
 The configurable components and allowed values available on the Edit page depend on the [deployment template](./deployment-templates.md) and [instance configurations](./ece-configuring-ece-instance-configurations-default.md) associated with the deployment.
@@ -27,13 +26,23 @@ To customize your deployment:
 
 3. From your deployment menu, go to the **Edit** page.
 
-## Editing deployment
+4. Let the user interface guide you through the cluster configuration for your cluster. Refer to [](#ece-edit-deployment) for more details.
 
-In the deployment edit page, you can change the following settings:
+    ::::{tip}
+        When updating an existing deployment, you can make multiple changes to your {{es}} cluster with a single configuration update.
+    ::::
+
+5. Select a [configuration strategy](#configuration-strategies) and **Save your changes**. The orchestrator will prepare and execute a plan to apply the requested changes.
+
+Review the changes to your configuration on the **Activity** page, with a tab for {{es}} and one for {{kib}}.
+
+## Editing deployment [ece-edit-deployment]
+
+In the deployment edit page, you can configure the following settings and features:
 
 * Enable [autoscaling](../../autoscaling.md) so that the available resources adjust automatically as demands on the deployment change.
 
-* If you don’t want to autoscale your deployment, you can manually increase or decrease capacity by adjusting the size of hot, warm, cold, and frozen [data tiers](../../../manage-data/lifecycle/data-tiers.md) nodes. For example, you might want to add warm or cold tier nodes if you have time series data that is accessed less-frequently and rarely needs to be updated.
+* If you don’t want to autoscale your deployment, you can manually increase or decrease capacity of each [data tier](../../../manage-data/lifecycle/data-tiers.md) and component. For example, you might add warm or cold tier nodes for time series data that is accessed infrequently, or expand {{kib}} capacity to handle higher workloads.
 
     * From the **Size per zone** drop-down menu, select what best fits your requirements.
 
@@ -49,31 +58,27 @@ In the deployment edit page, you can change the following settings:
         :alt: Number of nodes per deployment size
         :::
 
-    * Adjust the number of **Availability zones** to increase fault tolerance for the deployment.
-
-* Select **Edit user settings** to add configuration settings to the YML file of any component and further customize its behavior.
-
-  For more information, refer to [](edit-stack-settings.md).
+* Adjust the number of **Availability zones** for each component to enhance [fault tolerance](./ece-ha.md) in your deployment.
 
-* Enable specific {{es}} plugins which are not enabled by default.
-* Enable additional features, such as Machine Learning or coordinating nodes.
-* Set specific configuration parameters for your {{es}} nodes or {{kib}} instances.
+* Enable additional components, such as [Machine Learning](../../../explore-analyze/machine-learning.md) nodes or an [Integrations server](./manage-integrations-server.md).
 
-## Applying changes
+* Select **Manage user settings and extensions** at {{es}} level, or **Edit user settings** for other components, to customize the YML configuration settings and plugin extensions. For more details, refer to [](edit-stack-settings.md) and [](./add-plugins.md).
 
-When clicking on **Save changes** in the Edit deployment page
+* Select the **Advanced edit** link at the bottom of the page to access the [](./advanced-cluster-configuration.md) view.
 
-% TBD, explain a bit the different type of plans
+    ::::{warning}
+    You can break things when using the advanced cluster configuration editor. Use this functionality only if you know what you are doing or if you are being directed by someone from Elastic.
+    ::::
 
-* Select the method to apply changes
-  * Rolling inline
-  * Grow and shrink
+## Configuration strategies [configuration-strategies]
 
-## Other configuration changes
+When you select **Save changes** on the Edit deployment page, the orchestrator initiates a plan to apply the new configuration to your deployment. You can control how these changes are applied to minimize disruption and ensure a smooth transition.
 
-The following configuration settings are not available within the Edit deployment page:
+* Autodetect strategy (**recommended**): Let ECE will determine the strategy depending on the type changes to apply.
+* Rolling change per node: One node at a time. This strategy performs inline, rolling configuration changes that mutate existing containers. Recommended for most configuration changes.
+* Grow and shrink: The orchestrator creates nodes with the new configuration, then migrates data from the old ones, and eventually delete the original nodes. This strategy is automatically selected when adding or removing master-eligibie nodes.
+* Rolling grow and shrink: Similar to grow and shrink, but creating one node at a time. This strategy can take a lot longer than grow and shrink.
 
-* Logs and Metrics (monitoring)
-* Secure settings (keystore settings)
-* Snapshots
+The `Extended maintenance` option will make ECE to [stop routing requests](../../maintenance/ece/start-stop-routing-requests.md) to all instances during the plan execution. The cluster will be unavailable for external connections while the configuration changes are in progress.
 
+When executing plans, always review the reported configuration changes and track progress on the Activity page of the deployment, which includes separate tabs for {{es}} and {{kib}}.

raw-migrated-files/cloud/cloud-enterprise/ece-integrations-server-api-example.md renamed to deploy-manage/deploy/cloud-enterprise/ece-integrations-server-api-example.md

@@ -1,8 +1,16 @@
+---
+applies_to:
+  deployment:
+    ece: all
+mapped_urls:
+  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-integrations-server-api-example.html
+---
+
 # Enable Integrations Server through the API [ece-integrations-server-api-example]
 
 This example demonstrates how to use the Elastic Cloud Enterprise RESTful API to create a deployment with Integrations Server enabled.
 
-For more information on how to manage Integrations Server from the UI, check [Manage your Integrations Server](../../../deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md)
+For more information on how to manage Integrations Server from the UI, check [Manage your Integrations Server](manage-integrations-server.md)
 
 
 ## Requirements [ece_requirements_4]