# ILM: Routing data based on AWS availability zones **URL:** \ **Category:** Elasticsearch\ **Tags:** ilm-index-lifecycle-management\ **Created:** [October 22, 2019, 6:58pm UTC](https://discuss.elastic.co/t/ilm-routing-data-based-on-aws-availability-zones/204713 "2019-10-22T18:58:03Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![dwilches](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwilches/32/48586_2.png) [@dwilches](https://discuss.elastic.co/u/dwilches)\ **Post date:** [October 22, 2019, 6:58pm UTC](https://discuss.elastic.co/t/ilm-routing-data-based-on-aws-availability-zones/204713/1 "2019-10-22T18:58:04Z")
We currently have hot and warm nodes spread around 3 availability zones (AZ) in AWS. I want to start using ILM, and I'd like to know how to configure the data transfer between warm and hot nodes so that hot nodes in an AZ always sends the data to warm nodes in the same AZ. This is because AWS charges for moving data **between** AZs, but not when we move data **within** an AZ. Is it possible to do this using ILM? Thanks. ---
**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\ **Post date:** [October 24, 2019, 9:13pm UTC](https://discuss.elastic.co/t/ilm-routing-data-based-on-aws-availability-zones/204713/2 "2019-10-24T21:13:11Z")
Hi dwilches, ILM can move data based on [node attributes](https://www.elastic.co/guide/en/elasticsearch/reference/7.4/shard-allocation-filtering.html), so as long as the nodes have different attributes assigned to them within an AZ, then you would be able to configure ILM actions to move the data between different nodes. I would recommend checking out [https://www.elastic.co/blog/implementing-hot-warm-cold-in-elasticsearch-with-index-lifecycle-management](https://www.elastic.co/blog/implementing-hot-warm-cold-in-elasticsearch-with-index-lifecycle-management) for an example of how to do it (you don't necessarily have to use "hot", "warm", or "cold" for attributes. ---
**Author:** ![dwilches](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwilches/32/48586_2.png) [@dwilches](https://discuss.elastic.co/u/dwilches)\ **Post date:** [November 5, 2019, 8:42pm UTC](https://discuss.elastic.co/t/ilm-routing-data-based-on-aws-availability-zones/204713/3 "2019-11-05T20:42:58Z")
Thanks! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 3, 2019, 8:42pm UTC](https://discuss.elastic.co/t/ilm-routing-data-based-on-aws-availability-zones/204713/4 "2019-12-03T20:42:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.