# Using managed integration assets with different lifecycle policy/rollover alias

**URL:** <https://discuss.elastic.co/t/using-managed-integration-assets-with-different-lifecycle-policy-rollover-alias/373951>\
**Category:** Elasticsearch\
**Created:** [January 31, 2025, 2:28pm UTC](https://discuss.elastic.co/t/using-managed-integration-assets-with-different-lifecycle-policy-rollover-alias/373951 "2025-01-31T14:28:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![smashley](https://avatars.discourse-cdn.com/v4/letter/s/6a8cbe/32.png) [@smashley](https://discuss.elastic.co/u/smashley)\
**Post date:** [January 31, 2025, 2:28pm UTC](https://discuss.elastic.co/t/using-managed-integration-assets-with-different-lifecycle-policy-rollover-alias/373951/1 "2025-01-31T14:28:05Z")

</div>

I'm running ES 8.17.0 on basic subscription, ingesting logs from Cloudwatch. Note we are not using the Agent to pull these logs, but rather send them to \_bulk with a lambda function.

We had been ingesting these to an index, but not leveraging any ECS capabilities, so I'm in the process of migrating to using the aws-cloudwatch managed templates/pipelines etc.

My question is this: I have multiple environments/namespaces with different lifecycle needs, and I can't quite get my head around how to specify a different lifecycle policy and rollover alias using the \*@custom component templates. The doc below suggests something like this should be possible using variables like '{index}-alias' for the rollover alias, but in practice this just seems to make the alias the literal string.

[https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-component-template.html#\_component\_template\_with\_index\_aliases](https://Doc)

Is this a bug or am I going about this the wrong way?