# \[Elastic Cloud\] Logs are shipped without ILM policy **URL:** \ **Category:** Elasticsearch\ **Created:** [October 8, 2020, 6:41am UTC](https://discuss.elastic.co/t/elastic-cloud-logs-are-shipped-without-ilm-policy/251377 "2020-10-08T06:41:45Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\ **Post date:** [October 8, 2020, 6:41am UTC](https://discuss.elastic.co/t/elastic-cloud-logs-are-shipped-without-ilm-policy/251377/1 "2020-10-08T06:41:45Z")
Recently, Elastic Cloud has added the ability to also ship logs to a remote monitoring cluster. Enabling that feature worked great, except for one single thing. The index called `elastic-cloud-logs-7-2020.10.08-000001` was created successfully and the logs are indexed properly. However, the index has been created with the following settings... ```auto "index.lifecycle.name": "elastic-cloud-logs" "index.lifecycle.rollover_alias": "elastic-cloud-logs-7" ``` ...yet no ILM policy named `elastic-cloud-logs` has been created as can be seen when looking at the index details: ![Capture d’écran 2020-10-08 à 08.39.08](https://us1.discourse-cdn.com/elastic/original/3X/1/e/1e4ae1baa448d361afb476c267f5c2b0f3a61916.png) If it's a bug, I'm not sure where to file it since there's no Github repo for Elastic Cloud, hence why I'm "filing" it here. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 5, 2020, 6:42am UTC](https://discuss.elastic.co/t/elastic-cloud-logs-are-shipped-without-ilm-policy/251377/2 "2020-11-05T06:42:00Z")
Closed on November 5, 2020, 6:42am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.