# Automatic Rollover on Elastic Serverless deployment?

**URL:** <https://discuss.elastic.co/t/automatic-rollover-on-elastic-serverless-deployment/376406>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management, serverless\
**Created:** [March 26, 2025, 8:50am UTC](https://discuss.elastic.co/t/automatic-rollover-on-elastic-serverless-deployment/376406 "2025-03-26T08:50:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nicolo\_Boschi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolo_boschi/32/142259_2.png) [@Nicolo\_Boschi](https://discuss.elastic.co/u/Nicolo_Boschi)\
**Post date:** [March 26, 2025, 8:50am UTC](https://discuss.elastic.co/t/automatic-rollover-on-elastic-serverless-deployment/376406/1 "2025-03-26T08:50:33Z")

</div>

I wanted to configure automatic rollover for my index in a new Elastic Serverless deployment. From the docs, it looks like it _should_ be managed automatically by the platform itself.  
Is it true? What is the threshold?

I've tried to setup a index template, create an index with "is\_write\_index": true. When I try to call the Rollover API on the alias, I get "co.elastic.clients.elasticsearch.\_types.ElasticsearchException: [es/indices.rollover] failed: [illegal\_argument\_exception] rollover with conditions is not supported in serverless mode"

which seems to be confirming the automated behaviour.  
Testing the same on a local elasticsearch instance works just fine.

---

<div class="post-metadata">

**Author:** ![Quentin\_Pradet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quentin_pradet/32/94192_2.png) [@Quentin\_Pradet](https://discuss.elastic.co/u/Quentin_Pradet)\
**Post date:** [March 26, 2025, 11:09am UTC](https://discuss.elastic.co/t/automatic-rollover-on-elastic-serverless-deployment/376406/2 "2025-03-26T11:09:48Z")

</div>

Hello, correct, rollover is automatic on Serverless. More precisely, it's managed with [Data stream lifecycles](https://www.elastic.co/guide/en/elasticsearch/reference/current/data-stream-lifecycle.html), as ILM is not available on Serverless.

---

<div class="post-metadata">

**Author:** ![Nicolo\_Boschi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolo_boschi/32/142259_2.png) [@Nicolo\_Boschi](https://discuss.elastic.co/u/Nicolo_Boschi)\
**Post date:** [March 26, 2025, 12:24pm UTC](https://discuss.elastic.co/t/automatic-rollover-on-elastic-serverless-deployment/376406/3 "2025-03-26T12:24:27Z")

</div>

Thanks for the clarification.  
Does it apply also on Index Templates with Data Stream flag set to False?

---

<div class="post-metadata">

**Author:** ![Quentin\_Pradet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quentin_pradet/32/94192_2.png) [@Quentin\_Pradet](https://discuss.elastic.co/u/Quentin_Pradet)\
**Post date:** [March 26, 2025, 1:19pm UTC](https://discuss.elastic.co/t/automatic-rollover-on-elastic-serverless-deployment/376406/4 "2025-03-26T13:19:13Z")

</div>

No. My understanding is that using an index alias + index templates + rollover is not supported on Serverless, you need to switch to data streams instead. Note that data stream lifecycles are also supported in standard Elasticsearch.