# ISM policy for the AWS ES domain

**URL:** <https://discuss.elastic.co/t/ism-policy-for-the-aws-es-domain/257263>\
**Category:** Elasticsearch\
**Created:** [December 1, 2020, 6:46pm UTC](https://discuss.elastic.co/t/ism-policy-for-the-aws-es-domain/257263 "2020-12-01T18:46:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikhilesh](https://avatars.discourse-cdn.com/v4/letter/n/46a35a/32.png) [@nikhilesh](https://discuss.elastic.co/u/nikhilesh)\
**Post date:** [December 1, 2020, 6:46pm UTC](https://discuss.elastic.co/t/ism-policy-for-the-aws-es-domain/257263/1 "2020-12-01T18:46:57Z")

</div>

Hi Team,

I am using AWS ES domain of version 7.7. would like to create and apply a index management policy to delete the logs older than 30 days.

so, for this i have created a policy and then applied the existing indices to the policy. but if tomorrow new indices came ,it is not applying to the policy.

is there any way to create a index pattern like ( samplelogs-\*) to apply to the policy

Thanks  
Nikhilesh Gade

---

<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:** [December 1, 2020, 7:06pm UTC](https://discuss.elastic.co/t/ism-policy-for-the-aws-es-domain/257263/2 "2020-12-01T19:06:30Z")

</div>

We don't support this service here.  
We do have an official ILM feature which is available in our official service.

Did you look at [Cloud by Elastic](https://www.elastic.co/cloud), also available if needed from [AWS Marketplace](https://aws.amazon.com/marketplace/pp/B01N6YCISK) ?

Cloud by elastic is one way to have access to **all features** , all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, Maps UI, Alerting and built-in solutions named [Observability](https://www.elastic.co/observability), [Security](https://www.elastic.co/security), [Enterprise Search](https://www.elastic.co/enterprise-search) and what is coming next 🙂 ...

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 1, 2020, 8:11pm UTC](https://discuss.elastic.co/t/ism-policy-for-the-aws-es-domain/257263/3 "2020-12-01T20:11:35Z")

</div>

AWS ES doesn't support ILM at all sorry to say.

---

<div class="post-metadata">

**Author:** ![nikhilesh](https://avatars.discourse-cdn.com/v4/letter/n/46a35a/32.png) [@nikhilesh](https://discuss.elastic.co/u/nikhilesh)\
**Post date:** [December 10, 2020, 4:24am UTC](https://discuss.elastic.co/t/ism-policy-for-the-aws-es-domain/257263/4 "2020-12-10T04:24:47Z")

</div>

Thanks Warkolm for the reply

---

<div class="post-metadata">

**Author:** ![nikhilesh](https://avatars.discourse-cdn.com/v4/letter/n/46a35a/32.png) [@nikhilesh](https://discuss.elastic.co/u/nikhilesh)\
**Post date:** [December 10, 2020, 4:25am UTC](https://discuss.elastic.co/t/ism-policy-for-the-aws-es-domain/257263/5 "2020-12-10T04:25:11Z")

</div>

Thanks dadoonet for the solution

---

<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:** [January 7, 2021, 4:25am UTC](https://discuss.elastic.co/t/ism-policy-for-the-aws-es-domain/257263/6 "2021-01-07T04:25:12Z")

</div>

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