# Is it safe to set action.auto\_create\_index to false?

**URL:** <https://discuss.elastic.co/t/is-it-safe-to-set-action-auto-create-index-to-false/372809>\
**Category:** Elastic Search\
**Created:** [January 5, 2025, 2:20pm UTC](https://discuss.elastic.co/t/is-it-safe-to-set-action-auto-create-index-to-false/372809 "2025-01-05T14:20:01Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Richard\_Zhang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richard_zhang/32/140473_2.png) [@Richard\_Zhang](https://discuss.elastic.co/u/Richard_Zhang)\
**Post date:** [January 14, 2025, 2:20am UTC](https://discuss.elastic.co/t/is-it-safe-to-set-action-auto-create-index-to-false/372809/13 "2025-01-14T02:20:36Z")

</div>

> [@RainTown](#):
>
> Note use of “before ct1” there, which I think is slightly ambiguous as ct1 should be ignored.

Yes, I agree with you, ct1 is just ignored and ct2 is applied with all of its settings/mappings/aliases.

Legacy index template has the order-and-merge behavior, which is useful to avoiding wrong field mappings(the problem for this topic). but as its name indicates, I feel like it's a recommended option for us since it's a legacy feature and might be discontinued someday.

So we're circling back, setting auto\_create\_index as a whitelist is a valid options to solve the problem we're facing.

Actually there is already another topic going on [What is .ent-search-\*-logs-\*,-.ent-search-\*? where is it from?](https://discuss.elastic.co/t/what-is-ent-search-logs-ent-search-where-is-it-from/372873)

I've been so happy discussing this topic with you by which we've made a good understanding about index templates. You're so helpful.

---

_[View the full topic](https://discuss.elastic.co/t/is-it-safe-to-set-action-auto-create-index-to-false/372809)._