# ILM and alias confusion

**URL:** <https://discuss.elastic.co/t/ilm-and-alias-confusion/208753>\
**Category:** Elasticsearch\
**Created:** [November 20, 2019, 6:38pm UTC](https://discuss.elastic.co/t/ilm-and-alias-confusion/208753 "2019-11-20T18:38:00Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [November 22, 2019, 4:10pm UTC](https://discuss.elastic.co/t/ilm-and-alias-confusion/208753/8 "2019-11-22T16:10:16Z")

</div>

Ok, if there is an index "firewall-traffic", it was probably created when the config wasn't "perfect". It won't let an alias exist with that name. You'll have to delete that index or use a different alias. If the index is empty, just delete it.

You'll probably need to restart logstash after removing the index--alias conflict.

---

_[View the full topic](https://discuss.elastic.co/t/ilm-and-alias-confusion/208753)._