# Setting index.uuid on ES 5

**URL:** <https://discuss.elastic.co/t/setting-index-uuid-on-es-5/76778>\
**Category:** Elasticsearch\
**Created:** [February 28, 2017, 1:01pm UTC](https://discuss.elastic.co/t/setting-index-uuid-on-es-5/76778 "2017-02-28T13:01:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bevans88](https://avatars.discourse-cdn.com/v4/letter/b/a698b9/32.png) [@bevans88](https://discuss.elastic.co/u/bevans88)\
**Post date:** [February 28, 2017, 1:01pm UTC](https://discuss.elastic.co/t/setting-index-uuid-on-es-5/76778/1 "2017-02-28T13:01:49Z")

</div>

Hi,

I was wondering if there's any reason/objections to not allowing the index.uuid to be set when creating an index?

I understand that this would mean that the user would need to to guarantee index uuid uniqueness across clusters, but for some this wouldn't be a problem. We currently need this for a use case which involves encrypting per-index, so full disk encryption will not work (I do have a workaround, but supplying the index.uuid would be preferable).

Thanks,

Brent

---

<div class="post-metadata">

**Author:** ![bevans88](https://avatars.discourse-cdn.com/v4/letter/b/a698b9/32.png) [@bevans88](https://discuss.elastic.co/u/bevans88)\
**Post date:** [February 28, 2017, 3:25pm UTC](https://discuss.elastic.co/t/setting-index-uuid-on-es-5/76778/2 "2017-02-28T15:25:43Z")

</div>

I've created an issue to cover this: [https://github.com/elastic/elasticsearch/issues/23413](https://github.com/elastic/elasticsearch/issues/23413)

---

<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:** [March 28, 2017, 3:25pm UTC](https://discuss.elastic.co/t/setting-index-uuid-on-es-5/76778/3 "2017-03-28T15:25:50Z")

</div>

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