# Auto-creating indices even though configured not to

**URL:** <https://discuss.elastic.co/t/auto-creating-indices-even-though-configured-not-to/226027>\
**Category:** Elasticsearch\
**Created:** [April 1, 2020, 10:51am UTC](https://discuss.elastic.co/t/auto-creating-indices-even-though-configured-not-to/226027 "2020-04-01T10:51:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![simonauner-bookbeat](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@simonauner-bookbeat](https://discuss.elastic.co/u/simonauner-bookbeat)\
**Post date:** [April 1, 2020, 10:51am UTC](https://discuss.elastic.co/t/auto-creating-indices-even-though-configured-not-to/226027/1 "2020-04-01T10:51:36Z")

</div>

I want to have full control over what indices are created in my cluster, so I have configured

```
PUT _cluster/settings
{
    "persistent": {
        "action.auto_create_index": "false" 
    }
}

```

Still, when using NEST to send a `BulkUpdateOperation`, indices are auto-created, but I expect them to return 404.

```
new BulkUpdateOperation<RankedDto, Dto>(
          new RankedDto { Id = dto.Id }, dto, true) 
         {Index = "something_something"}

```

This operation gives me a 201 with index "something\_something" created, even though I would expect it to give me a 404.

Do I need to configure something else as well?

I'm using Elastic Cloud 7.6.1

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [April 3, 2020, 2:37pm UTC](https://discuss.elastic.co/t/auto-creating-indices-even-though-configured-not-to/226027/2 "2020-04-03T14:37:54Z")

</div>

Hey,

you can change that setting under your deployment in the "Edit" part and then search for `Elasticsearch plugins and settings` - there is a checkbox to select this.

--Alex

---

<div class="post-metadata">

**Author:** ![simonauner-bookbeat](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@simonauner-bookbeat](https://discuss.elastic.co/u/simonauner-bookbeat)\
**Post date:** [April 6, 2020, 8:41am UTC](https://discuss.elastic.co/t/auto-creating-indices-even-though-configured-not-to/226027/3 "2020-04-06T08:41:05Z")

</div>

@spinscale Ok, thanks! That seems to affect both

```
"persistent": {
        "action.auto_create_index": "false" 
    }

```

and

```
"transient": {
        "action.auto_create_index": "false" 
    }

```

so perhaps that was the answer I was looking for.

In other words: this is not enough:

```
PUT _cluster/settings
{
    "persistent": {
        "action.auto_create_index": "false" 
    }
}

```

This should be correct:

```
PUT _cluster/settings
{
    "persistent": {
        "action.auto_create_index": "false" 
    },
  "transient": {
        "action.auto_create_index": "false" 
    }
}

```

thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 4, 2020, 8:41am UTC](https://discuss.elastic.co/t/auto-creating-indices-even-though-configured-not-to/226027/4 "2020-05-04T08:41:12Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.