A newer version is available. For the latest information, see the current release documentation.
« Delete a deployment Disable an Elasticsearch data tier »
Elastic Docs ›Elastic Cloud Enterprise Reference [3.4] ›Administering deployments

Migrate to index lifecycle management

edit

Migrate to index lifecycle management

edit

Index curation is deprecated. For Elastic Stack version 6.7 and later, any deployments using index curation will be prompted to migrate to ILM.

The index lifecycle management (ILM) feature of the Elastic 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:

  • 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 6.7+ deployment that has ILM enabled.

To learn more about configuring index lifecycle management for Elastic Cloud Enterprise or about all of the features that are available with ILM, see:

To configure ILM Migration in the console:

  1. Log into the Cloud UI.

  2. From the Deployments page, select your deployment.

    Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.

  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.
  5. Set the ILM policy name for each data view (formerly index pattern).

Beginning with Elastic Stack version 8.0, Kibana index patterns have been renamed to data views. To learn more, check the Kibana What’s new in 8.0 page.

  1. Set the shard allocation attribute for the data view.

    • You can set different node attributes per data view to allow for more in-depth configuration in Kibana, or
    • You may choose to add one node attribute that applies to all data views.
    • If you do not wish to migrate a certain data view to ILM, you can deselect the checkbox in the associated row.
    • You may also wish to migrate to ILM without carrying over any of your current data views by deselecting all patterns. This means that those data views will no longer be curated, and you will have the option to set up new ILM policies in Kibana.
  2. Select Migrate.

After you get the notification that confirms that migration was completed successfully, you can view your ILM policies in Kibana.

« Delete a deployment Disable an Elasticsearch data tier »