# Enable ILM for different filebeat indices **URL:** \ **Category:** Elasticsearch\ **Tags:** ilm-index-lifecycle-management\ **Created:** [September 29, 2020, 11:59am UTC](https://discuss.elastic.co/t/enable-ilm-for-different-filebeat-indices/250350 "2020-09-29T11:59:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![borna\_talebi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/borna_talebi/32/76317_2.png) [@borna\_talebi](https://discuss.elastic.co/u/borna_talebi)\ **Post date:** [September 29, 2020, 11:59am UTC](https://discuss.elastic.co/t/enable-ilm-for-different-filebeat-indices/250350/1 "2020-09-29T11:59:46Z")
Hi, I have two different indices in my filebeat. one for cisco module (cisco-beats-0001) and one for the rest of the logs(default filebeat index). so far: - I've disabled ILM in filebeat - I've created an index lifecycle policy (rollover policy) - I've added my policy to my cisco index template I'm not sure what to do now. according to the docs I have to bootstrap the first index. should I create the first index myself or wait for the filebeat to create the next one (cisco-beats-0002)? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 1, 2020, 1:40am UTC](https://discuss.elastic.co/t/enable-ilm-for-different-filebeat-indices/250350/2 "2020-10-01T01:40:22Z")
You can wait till the first index is automatically created, then just make sure it has the appropriate ILM aliases attached to it. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 29, 2020, 1:40am UTC](https://discuss.elastic.co/t/enable-ilm-for-different-filebeat-indices/250350/3 "2020-10-29T01:40:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.