Migrate to a hot-warm architectureedit

Starting in Elastic stack version 7.10, all deployments on Elasticsearch Service support hot, warm, and cold data tiers. You no longer need to use a dedicated hot-warm architecture profile to manage your time series data, so this profile type is no longer available.

When you create a deployment hosted on Elasticsearch Service, it uses one of the available solutions to preconfigure the Elastic Stack for your use case. If you have a deployment that is getting overwhelmed by the volume of incoming data or that contains logging data that doesn’t all need to be on fast storage, you can migrate your deployment to a hot-warm architecture by adding another data configuration. You use this added data configuration to store less frequently queried data.

Before you beginedit

A hot-warm architecture works by initially creating new indices on a hot data configuration that provides fast, SSD-based storage where they can be accessed quickly. Over time, automatic index curation then moves these indices to warm nodes that provide slower, more affordable spinning-disk storage by changing their shard allocation.

Not all deployments can migrate to the hot-warm architecture template by adding another data configurations. To be able to migrate, you must originally have created the deployment using the Elastic Stack solution with the I/O optimized hardware profile. If you are not sure what you used, try the steps in this task to check if you can migrate.

If you cannot migrate to a hot-warm architecture directly, you can also create a new deployment using the hot-warm hardware profile and then restore your data from a snapshot there.

To learn more about how deployment templates and a hot-warm architecture work, see What are hardware profiles?.

Once you have migrated your deployment to a hot-warm architecture, you cannot change it back to a hot-only architecture without creating a new deployment and migrating your data.


  1. Log in to the Elasticsearch Service Console.
  2. Select a deployment that was created with the Elastic Stack solution with the I/O optimized hardware profile.

    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. Check if there is an Enable button that lets you add another data configuration:

    A screenshot of a data configuration that shows the Enable button

    If there is an Enable button, continue with the next step. If there is no button, this deployment does not support adding more data configurations and you cannot migrate to the hot-warm template directly.

  5. Click Enable.
  6. Click Save and then Confirm.

After the configuration change has been applied, your deployment uses the hot-warm architecture template.