# Automatic curation of cluster indices **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Tags:** curator\ **Created:** [February 21, 2019, 10:32am UTC](https://discuss.elastic.co/t/automatic-curation-of-cluster-indices/169386 "2019-02-21T10:32:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![keinproblem](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keinproblem/32/41181_2.png) [@keinproblem](https://discuss.elastic.co/u/keinproblem)\ **Post date:** [February 21, 2019, 10:32am UTC](https://discuss.elastic.co/t/automatic-curation-of-cluster-indices/169386/1 "2019-02-21T10:32:34Z")
Hi, I would like to automatically evict logs that exceed a specific lifetime in ES. The Curator provides a [delete\_indices](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/delete_indices.html) action in order to realize log eviction in a comfortable fashion. ECE provides the possibility of setting up curation specs as documented in [Update cluster curation settings](https://www.elastic.co/guide/en/cloud-enterprise/current/Clusters_-_Elasticsearch_-_CRUD_-_Configuration.html#update-es-cluster-curation-settings). This seems to be only applicable to Hot-Warn deployments, since it will only shift the indices [between instances of specified instance configurations](https://www.elastic.co/guide/en/cloud-enterprise/current/definitions.html#ElasticsearchCuration). Is it possible to perform a very similar operation as the [delete\_indices](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/delete_indices.html) does with ECE? If so, how could this be achieved? Thanks in advance! ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [February 21, 2019, 1:43pm UTC](https://discuss.elastic.co/t/automatic-curation-of-cluster-indices/169386/2 "2019-02-21T13:43:49Z")
A future release will permit the use of the new Index Lifecycle Management UI in ECE. Until then, you can use Curator to accomplish this in ECE. ---
**Author:** ![keinproblem](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keinproblem/32/41181_2.png) [@keinproblem](https://discuss.elastic.co/u/keinproblem)\ **Post date:** [February 21, 2019, 2:39pm UTC](https://discuss.elastic.co/t/automatic-curation-of-cluster-indices/169386/3 "2019-02-21T14:39:42Z")
Thanks for your input on this, Aaron! Will the new Index Lifecycle Management UI come with an API extension? Summarizing: The ECE API in it's current latest version (2.1.0 when composing this message) does not come with the functionality of managing log deletion. Running a Curator in the "traditional" way would be required for each ES cluster within ECE, as a possible solution to achieve time based index deletion. Looking forward into seeing the Index Lifecycle Management UI and API in ECE! ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [February 21, 2019, 3:01pm UTC](https://discuss.elastic.co/t/automatic-curation-of-cluster-indices/169386/4 "2019-02-21T15:01:44Z")
> [@keinproblem](#): > > Will the new Index Lifecycle Management UI come with an API extension? Yes. Everything ILM will be API-driven. Your summary is accurate. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 7, 2019, 3:01pm UTC](https://discuss.elastic.co/t/automatic-curation-of-cluster-indices/169386/5 "2019-03-07T15:01:46Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.