anchor.diff:  
   [discrete]
   [[remove-custom-allocation-settings]]
  -=== Remove custom allocation settings from existing {ilm-init} policies
  +==== Remove custom allocation settings from existing {ilm-init} policies
   
   Update the allocate action for each lifecycle phase to remove the attribute-based
   allocation settings. {ilm-init} will inject a
  
positive.code: 
  [discrete]
  [[stop-setting-custom-hot-attribute]]
  === Stop setting the custom hot attribute on new indices
  
  When you create a data stream, its first backing index
  is now automatically assigned to `data_hot` nodes.
  
negative.code: you can still use attribute-based allocation filters to
  control shard allocation for other purposes.
  
  {ess} and {ece} can perform the migration automatically. For self-managed
  deployments, you need to manually update your configuration, ILM policies, and
  indices to switch to node roles. 
  
  [discrete]
  [[cloud-migrate-to-node-roles]]
  === Automatically migrate to node roles on {ess} or {ece}
  
  If you are using node attributes on {ess} or {ece}, you will be
  prompted to switch to node roles when you:
  
  * Upgrade to {es} 7.10 or higher
  * Deploy a warm, cold, or frozen data tier
  * {cloud}/ec-autoscaling.html[Enable autoscaling]
  
  These actions automatically update your cluster configuration
  and {ilm-init} policies to use node roles. Additionally, upgrading to
  version 7.14 or higher automatically update {ilm-init} policies
  whenever any configuration change is applied to your deployment.
  
  
  If you use custom index templates, check them after the automatic migration
  completes and remove any <<shard-allocation-filtering, attribute-based
  allocation filters>>.
  
  NOTE: You do not need to take any further action after the automatic migration.
  The following manual steps are only necessary if you do not allow the automatic
  migration or have a self-managed deployment.
  
  [discrete]
  [[on-prem-migrate-to-node-roles]]
  === Migrate to node roles on self-managed deployments
  
  To switch to using node roles:
  
  . <<assign-data-tier, Assign data nodes>> to the appropriate data tier.
  