From fbae1ad200bb94dfc9d5c2192ae6b02439286a6d Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Thu, 14 Aug 2025 15:18:45 -0400 Subject: [PATCH 1/3] Create 'Migrate to ILM' landing page --- .../manage-existing-indices.md | 4 +-- .../index-lifecycle-management/migrate-ilm.md | 27 +++++++++++++++++++ .../migrate-index-management.md | 2 +- manage-data/toc.yml | 3 ++- 4 files changed, 32 insertions(+), 4 deletions(-) create mode 100644 manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md diff --git a/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md b/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md index 6ab39588bd..3ce9f9d72d 100644 --- a/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md +++ b/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md @@ -7,9 +7,9 @@ products: - id: elasticsearch --- -# Manage existing indices [ilm-with-existing-indices] +# Migrate to {{ilm-init}} ({{stack}}) [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. diff --git a/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md b/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md new file mode 100644 index 0000000000..cc809faaf9 --- /dev/null +++ b/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 using index curation, which is now deprecated, or another mechanism to manage the lifecycle of your indices. To help you adapt your existing indices from using earlier lifecycle mechanisms to use {{ilm}}, a few guides are available: + +[](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md) +: Describes how to migrate {{es}} indices in an {{ech}} or {{ece}} deployment from using deprecated index curation to use {{ilm}}. + +[](/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md) +: Describes how to migrate {{es}} indices in any {{stack}} 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) +: Describes how to migrate from using custom node attributes and attribute-based allocation filters to move indices through data tiers in a hot-warm-cold architecture, to use {{ilm}}. + +If you are configuring {{ilm-init}} for new indices, refer to [Configure a lifecycle policy](/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 [Manually apply a lifecycle policy to an index](/manage-data/lifecycle/index-lifecycle-management/policy-apply.md). \ No newline at end of file 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 c81a371a97..9a75d5adb2 100644 --- a/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md +++ b/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md @@ -9,7 +9,7 @@ products: - id: cloud-hosted --- -# Migrate to index lifecycle management +# Migrate to {{ilm-init}} ({{ecloud}}) ::::{important} Index curation is deprecated. Any deployments using index curation are prompted to migrate to ILM. diff --git a/manage-data/toc.yml b/manage-data/toc.yml index f647dafbdd..d686c379e6 100644 --- a/manage-data/toc.yml +++ b/manage-data/toc.yml @@ -130,8 +130,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 From 4dcc567b2be7371a3750b7728bb6cd98fac8a822 Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Fri, 12 Sep 2025 11:16:14 -0400 Subject: [PATCH 2/3] fixup --- .../manage-existing-indices.md | 5 ++++- .../index-lifecycle-management/migrate-ilm.md | 10 +++++----- .../migrate-index-management.md | 8 ++++++-- 3 files changed, 15 insertions(+), 8 deletions(-) diff --git a/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md b/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md index 3ce9f9d72d..42642fda94 100644 --- a/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md +++ b/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md @@ -1,13 +1,16 @@ --- +navigation_title: Migrate to {{ilm-init}} (self-managed) mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-with-existing-indices.html applies_to: stack: ga + deployment: + self: ga products: - id: elasticsearch --- -# Migrate to {{ilm-init}} ({{stack}}) [ilm-with-existing-indices] +# Migrate to {{ilm-init}} on self-managed deployments [ilm-with-existing-indices] 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): diff --git a/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md b/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md index cc809faaf9..2cc02e5c35 100644 --- a/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md +++ b/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md @@ -15,13 +15,13 @@ products: You may already be using index curation, which is now deprecated, or another mechanism to manage the lifecycle of your indices. To help you adapt your existing indices from using earlier lifecycle mechanisms to use {{ilm}}, a few guides are available: -[](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md) -: Describes how to migrate {{es}} indices in an {{ech}} or {{ece}} deployment from using deprecated index curation to use {{ilm}}. +[](/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) -: Describes how to migrate {{es}} indices in any {{stack}} environment from using deprecated index curation, or any other lifecycle mechanism, to use {{ilm}}. +[](/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md) {applies_to}`self:` +: 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) +[](/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 move indices through data tiers in a hot-warm-cold architecture, to use {{ilm}}. If you are configuring {{ilm-init}} for new indices, refer to [Configure a lifecycle policy](/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 [Manually apply a lifecycle policy to an index](/manage-data/lifecycle/index-lifecycle-management/policy-apply.md). \ No newline at end of file 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 9a75d5adb2..423ec049be 100644 --- a/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md +++ b/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md @@ -1,15 +1,19 @@ --- +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 {{ilm-init}} ({{ecloud}}) +# 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. @@ -17,7 +21,7 @@ Index curation is deprecated. Any deployments using index curation are prompted 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. From df80e17cf0a2ef6a75ccd0b4d557673bd3a38f16 Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Wed, 17 Sep 2025 14:30:37 -0400 Subject: [PATCH 3/3] review fixes --- .../index-lifecycle-management/manage-existing-indices.md | 6 +++--- .../lifecycle/index-lifecycle-management/migrate-ilm.md | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md b/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md index 42642fda94..139176dbca 100644 --- a/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md +++ b/manage-data/lifecycle/index-lifecycle-management/manage-existing-indices.md @@ -1,16 +1,16 @@ --- -navigation_title: Migrate to {{ilm-init}} (self-managed) +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 --- -# Migrate to {{ilm-init}} on self-managed deployments [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 of options when [migrating to {{ilm-init}}](./migrate-index-management.md): diff --git a/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md b/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md index 2cc02e5c35..41dd34c85c 100644 --- a/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md +++ b/manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md @@ -13,15 +13,15 @@ products: # Migrate to {{ilm-init}} [migrate-ilm] -You may already be using index curation, which is now deprecated, or another mechanism to manage the lifecycle of your indices. To help you adapt your existing indices from using earlier lifecycle mechanisms to use {{ilm}}, a few guides are available: +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:` +[](/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 move indices through data tiers in a hot-warm-cold architecture, to use {{ilm}}. +: 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 [Configure a lifecycle policy](/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 [Manually apply a lifecycle policy to an index](/manage-data/lifecycle/index-lifecycle-management/policy-apply.md). \ No newline at end of file +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). \ No newline at end of file