Merge branch 'main' into 2979-automatic-import-format-update

Author: theletterf

deploy-manage/tools/snapshot-and-restore/s3-repository.md

@@ -125,6 +125,9 @@ The following list contains the available S3 client settings. Those that must be
 `max_retries`
 :   The number of retries to use when an S3 request fails. The default value is `3`.
 
+`connection_max_idle_time`
+:   ([time value](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#time-units)) The timeout after which {{es}} will close an idle connection. The default value is 60 seconds.
+
 `path_style_access`
 :   Whether to force the use of the path style access pattern. If `true`, the path style access pattern will be used. If `false`, the access pattern will be automatically determined by the AWS Java SDK (See [AWS documentation](https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Builder.html#setPathStyleAccessEnabled-java.lang.Boolean-) for details). Defaults to `false`.
 

manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md

@@ -1,15 +1,18 @@
 ---
+navigation_title: Migrate to {{ilm-init}} (self-managed and ECK)
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-with-existing-indices.html
 applies_to:
-  stack: ga
+  deployment:
+    self: ga
+    eck: ga
 products:
   - id: elasticsearch
 ---
 
-# Manage existing indices [ilm-with-existing-indices]
+# Migrate to {{ilm-init}} on self-managed and {{eck}} deployments [ilm-with-existing-indices]
 
-If you’ve been using Curator or some other mechanism to manage periodic indices, you have a couple options when [migrating to {{ilm-init}}](./migrate-index-management.md):
+If you’ve been using Curator or some other mechanism to manage periodic indices, you have a couple of options when [migrating to {{ilm-init}}](./migrate-index-management.md):
 
 * Set up your index templates to use an {{ilm-init}} policy to manage your new indices. Once {{ilm-init}} is managing your current write index, you can apply an appropriate policy to your old indices.
 * Reindex into an {{ilm-init}}-managed index.

manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md

@@ -0,0 +1,27 @@
+---
+navigation_title: Migrate to {{ilm-init}}
+mapped_pages:
+  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-migrate-index-management.html
+  - https://www.elastic.co/guide/en/cloud/current/ec-migrate-index-management.html
+applies_to:
+  stack: ga
+products:
+  - id: elasticsearch
+  - id: cloud-enterprise
+  - id: cloud-hosted
+---
+
+# Migrate to {{ilm-init}} [migrate-ilm]
+
+You may already be another mechanism to manage the lifecycle of your indices. To help you adapt your existing indices to use {{ilm}}, a few guides are available:
+
+[](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md) {applies_to}`ess:` {applies_to}`ece:`
+:   Describes how to migrate {{es}} indices in an {{ech}} or {{ece}} deployment from using deprecated index curation or another periodic indices management mechanism to use {{ilm}}.
+
+[](/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md)  {applies_to}`self:` {applies_to}`eck:`
+:   Describes how to migrate {{es}} indices in a self-managed environment from using deprecated index curation, or any other lifecycle mechanism, to use {{ilm}}.
+
+[](/manage-data/lifecycle/index-lifecycle-management/migrate-index-allocation-filters-to-node-roles.md) {applies_to}`stack:`
+:   Describes how to migrate from using custom node attributes and attribute-based allocation filters to using built-in node roles, enabling {{ilm-init}} to automatically move indices between data tiers.
+
+If you are configuring {{ilm-init}} for new indices, refer to [](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md). If you plan to manually apply an {{ilm}} policy to existing indices that are not already using another type of lifecycle management, refer to [](/manage-data/lifecycle/index-lifecycle-management/policy-apply.md).

manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md

@@ -1,23 +1,27 @@
 ---
+navigation_title: Migrate to {{ilm-init}} (ECH or ECE)
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-migrate-index-management.html
   - https://www.elastic.co/guide/en/cloud/current/ec-migrate-index-management.html
 applies_to:
   stack: ga
+  deployment:
+    ece: ga
+    ess: ga
 products:
   - id: cloud-enterprise
   - id: cloud-hosted
 ---
 
-# Migrate to index lifecycle management
+# Migrate to {{ilm-init}} on {{ech}} or {{ece}} deployments
 
 ::::{important}
 Index curation is deprecated. Any deployments using index curation are prompted to migrate to ILM.
 ::::
 
 The index lifecycle management (ILM) feature of the {{stack}} provides an integrated and streamlined way to manage time-based data, making it easier to follow best practices for managing your indices. Compared to index curation, migrating to ILM gives you more fine-grained control over the lifecycle of each index.
 
-For existing hot-warm deployments that are currently using index curation, there are a couple of options for migrating to index lifecycle management (ILM). You can:
+For existing {{ecloud}} hot-warm deployments that are currently using index curation, there are a couple of options for migrating to index lifecycle management (ILM). You can:
 
 * Use the migration process in the console to change an existing deployment to ILM.
 * Take a snapshot and restore your data to a new Elastic Stack deployment that has ILM enabled.

manage-data/toc.yml

@@ -134,8 +134,9 @@ toc:
           - file: lifecycle/index-lifecycle-management/restore-managed-data-stream-index.md
           - file: lifecycle/index-lifecycle-management/tutorial-customize-built-in-policies.md
           - hidden: lifecycle/index-lifecycle-management/index-management-in-kibana.md
-          - file: lifecycle/index-lifecycle-management/migrate-index-management.md
+          - file: lifecycle/index-lifecycle-management/migrate-ilm.md
             children:
+              - file: lifecycle/index-lifecycle-management/migrate-index-management.md
               - file: lifecycle/index-lifecycle-management/manage-existing-indices.md
               - file: lifecycle/index-lifecycle-management/migrate-index-allocation-filters-to-node-roles.md
       - file: lifecycle/data-stream.md