# Index name to match the pattern \`\`^.\*-\\d+\`

**URL:** <https://discuss.elastic.co/t/index-name-to-match-the-pattern-d/364098>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [July 31, 2024, 4:01am UTC](https://discuss.elastic.co/t/index-name-to-match-the-pattern-d/364098 "2024-07-31T04:01:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sundar.s](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@sundar.s](https://discuss.elastic.co/u/sundar.s)\
**Post date:** [July 31, 2024, 4:01am UTC](https://discuss.elastic.co/t/index-name-to-match-the-pattern-d/364098/1 "2024-07-31T04:01:37Z")

</div>

As per the Elastic search documentation, we could see that there is a prerequisite on the indexing name conventions.

```auto
**`index name [x] does not match pattern ``^.*-\d+`

The index name’s regex pattern matching is a prerequisite for rollover to work. The most common implication users miss is not realizing the index name needs to end with trailing digits, e.g. *my-index-000001* and instead only use *my-index* which does match the pattern requirement

```

Could you please advise us, if this is applicable across all the deploying models, like Elasticsearch Managed Services, On premise deployments ?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 31, 2024, 6:49am UTC](https://discuss.elastic.co/t/index-name-to-match-the-pattern-d/364098/2 "2024-07-31T06:49:47Z")

</div>

Yes. This applies to all Elasticsearch services wherever it's running.