# ILM policy without alias

**URL:** <https://discuss.elastic.co/t/ilm-policy-without-alias/277188>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [June 28, 2021, 8:52am UTC](https://discuss.elastic.co/t/ilm-policy-without-alias/277188 "2021-06-28T08:52:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![francois75](https://avatars.discourse-cdn.com/v4/letter/f/278dde/32.png) [@francois75](https://discuss.elastic.co/u/francois75)\
**Post date:** [June 28, 2021, 8:52am UTC](https://discuss.elastic.co/t/ilm-policy-without-alias/277188/1 "2021-06-28T08:52:04Z")

</div>

To smoothly transit from Elasticsearch curator to ILM I want to implement a simple ILM policy that change index status according to its age.

So I've create a policy and added to existing indices as following:

```auto
{
  "index": {
    "lifecycle": {
      "name": "filebeat-bla"
    },
  }
}

```

But this failed as complaining for missing rollover\_alias:

```auto
illegal_argument_exception: setting [index.lifecycle.rollover_alias] for index [filebeat-bla-bla-2021.05.06] is empty or not defined

```

So I added an alias:

```auto
{
  "index": {
    "lifecycle": {
      "name": "filebeat-bla"
      "rollover_alias": "filebeat-bla"
    },
  }
}

```

But this failed too

```auto
illegal_argument_exception: index.lifecycle.rollover_alias [filebeat-bla] does not point to index [filebeat-bla-bla-2021.06.19]

```

Is there a way to use ILM without changing the income logstash configuration ?

---

<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:** [July 26, 2021, 8:52am UTC](https://discuss.elastic.co/t/ilm-policy-without-alias/277188/2 "2021-07-26T08:52:25Z")

</div>

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