# Hot-Warm Arch, without ILM
**URL:** https://discuss.elastic.co/t/hot-warm-arch-without-ilm/210959
**Category:** Logstash
**Created:** [December 7, 2019, 10:23am UTC](https://discuss.elastic.co/t/hot-warm-arch-without-ilm/210959 "2019-12-07T10:23:10Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Securitybits](https://discuss.elastic.co/u/Securitybits)
#### Post date: [December 7, 2019, 10:23am UTC](https://discuss.elastic.co/t/hot-warm-arch-without-ilm/210959/1 "2019-12-07T10:23:10Z")
Long time lurker, but first time poster! So lets see if this works!
Currently implementing a Hot-Warm architecture. Which consists of
3 dedicated Master Nodes
3 Hot Nodes
3 Warm Nodes
The Attrib is set by
`node.attr.box_type: master/hot/warm`
Now what is not Elastic specific is that the cluster is deployed using Salt Stack, which comes into play later.
i Ingest my data from File/Audit-Beat etc. through a Logstash Pipe.
Output Looking like
`elasticsearch { hosts => ["elasticsearch-hot-01:9200","elasticsearch-hot-02:9200","elasticsearch-hot-03:9200"] manage_template => false index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}" }`
And that creates daily indices as intended.
Now comes the issue, which is that logstash is creating the indicies on all nodes. But i would only like it to use the Hot nodes as those are on SSDs. Makes sense right!
Now what i really dont want to do is to use the Rest API to ILM the issue. Simply because that would create a really bad implementation with the Salt state.
Moving the index to Warm nodes will be achieved using Curator.
So simply put, is there any way to using logstash to set the created indexes to only exist on Hot, instead of Hot and Warm nodes? without having to use Rest API Calls?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [December 7, 2019, 1:47pm UTC](https://discuss.elastic.co/t/hot-warm-arch-without-ilm/210959/2 "2019-12-07T13:47:21Z")
> [@Securitybits](#):
>
> So simply put, is there any way to using logstash to set the created indexes to only exist on Hot, instead of Hot and Warm nodes? without having to use Rest API Calls?
You generally control this through an index tempate, which automatically assigns the appropraite settings on index creation, resulting in all new indices being created on the hot nodes.
You can manage this yourself or create one and let Logstash upload it on startup.
---
### Author:  [@Securitybits](https://discuss.elastic.co/u/Securitybits)
#### Post date: [December 7, 2019, 7:07pm UTC](https://discuss.elastic.co/t/hot-warm-arch-without-ilm/210959/3 "2019-12-07T19:07:13Z")
So i assume that theres no easy way other then doing the index lifecycle management way in making logstash create indexes on the "hot" nodes?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [December 8, 2019, 8:09am UTC](https://discuss.elastic.co/t/hot-warm-arch-without-ilm/210959/4 "2019-12-08T08:09:22Z")
I am not sure I understand your question. The index template specifies the settings that makes new indices be allocated to hot nodes. You can then use ILM or Curator to manage the lifecycle. If you are looking for some other way to manage this I am not aware of any.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 5, 2020, 8:09am UTC](https://discuss.elastic.co/t/hot-warm-arch-without-ilm/210959/5 "2020-01-05T08:09:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.