# Using Ultrawarm storage on AWS ElasticSearch

**URL:** <https://discuss.elastic.co/t/using-ultrawarm-storage-on-aws-elasticsearch/265121>\
**Category:** Elasticsearch\
**Created:** [February 22, 2021, 8:09pm UTC](https://discuss.elastic.co/t/using-ultrawarm-storage-on-aws-elasticsearch/265121 "2021-02-22T20:09:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![codejunkie78](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/codejunkie78/32/84251_2.png) [@codejunkie78](https://discuss.elastic.co/u/codejunkie78)\
**Post date:** [February 22, 2021, 8:09pm UTC](https://discuss.elastic.co/t/using-ultrawarm-storage-on-aws-elasticsearch/265121/1 "2021-02-22T20:09:49Z")

</div>

I have a long lived index on ElasticSearch for eg. events which is not partitioned by time. I can store about 3 months data in hot storage. After that I want to move it to warm. If I migrate the entire index to warm, do I have to now create a brand new index events\_2 in hot and refer to the warm index as events. Can I setup a process once 3 months are over everyday one day of data be moved to warm? Can I create an index low\_priority\_index in UltraWarm storage and write to that while keeping important events in the events index?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 22, 2021, 9:23pm UTC](https://discuss.elastic.co/t/using-ultrawarm-storage-on-aws-elasticsearch/265121/2 "2021-02-22T21:23:44Z")

</div>

For specific questions about ultra warm storage you will likely need to ask AWS support. On a more general level cold storage is especially useful for complete indices that are no longer updated or written to, e.g. time series data in time-based indices, where this types of cheaper low-performance can be used for rarely queries data. Based on your description it sounds like any kind of bold storage would be a bad fit unless you adopt time-based indices.

---

<div class="post-metadata">

**Author:** ![codejunkie78](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/codejunkie78/32/84251_2.png) [@codejunkie78](https://discuss.elastic.co/u/codejunkie78)\
**Post date:** [February 22, 2021, 10:39pm UTC](https://discuss.elastic.co/t/using-ultrawarm-storage-on-aws-elasticsearch/265121/3 "2021-02-22T22:39:18Z")

</div>

In my case an event once written can't be mutated. So if it is a read only store it works well for me. My question was more related to how do I manage my queries. For eg. if I have events index that I then move to ultrawarm every 3 months. The best option would be to be able to just move data that is more than 3 months old to ultrawarm. However, as per the docs I have to move an entire index and it doesn't just selectively move data older than 3 months to ultrawarm. So now my queries that used to query the events index will have to query a new index also events\_1 (in ultrawarm). How can I manage that without changing my query code? Is using multi-target query the right way [Multi-target syntax | Elasticsearch Reference [7.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-index.html) ?

---

<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:** [February 22, 2021, 10:44pm UTC](https://discuss.elastic.co/t/using-ultrawarm-storage-on-aws-elasticsearch/265121/4 "2021-02-22T22:44:36Z")

</div>

We don't support the aws fork sorry. You'd really need to ask them how this works with the APIs.

We do have [ILM][ILM: Manage the index lifecycle | Elasticsearch Reference [7.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html)), which manages all of that for you and takes away the complexity. You can get it via our Elasticsearch Service that's available [on the AWS marketplace](https://aws.amazon.com/marketplace/pp/Elastic-Elastic-Cloud-Elasticsearch-managed-servic/B01N6YCISK).

---

<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:** [March 22, 2021, 10:45pm UTC](https://discuss.elastic.co/t/using-ultrawarm-storage-on-aws-elasticsearch/265121/5 "2021-03-22T22:45:11Z")

</div>

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