# Shrinked index should have same security settings than original index

**URL:** <https://discuss.elastic.co/t/shrinked-index-should-have-same-security-settings-than-original-index/298512>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security, ilm-index-lifecycle-management\
**Created:** [March 1, 2022, 1:27pm UTC](https://discuss.elastic.co/t/shrinked-index-should-have-same-security-settings-than-original-index/298512 "2022-03-01T13:27:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [March 1, 2022, 1:27pm UTC](https://discuss.elastic.co/t/shrinked-index-should-have-same-security-settings-than-original-index/298512/1 "2022-03-01T13:27:54Z")

</div>

When using ILM to reduce index, the new index change its name: "shrink-zda-original".

When using security, we configure some permissions to "original" index.

ILM will break permissions, this is really annoying using elastic-hadoop library because the lib uses the index behind the alias, hence give security errors.

As a dirty workaround, I see also permissions against:

```auto
  indices:
  - names:
    - events
    - "events-*"
    - "shrink-*-events-*"
    privileges:
    - read

```

---

<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 29, 2022, 1:28pm UTC](https://discuss.elastic.co/t/shrinked-index-should-have-same-security-settings-than-original-index/298512/2 "2022-03-29T13:28:14Z")

</div>

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