# Optimizing Storage Costs for Historical Data in Elasticsearch on Azure: Seeking Community Advice

**URL:** <https://discuss.elastic.co/t/optimizing-storage-costs-for-historical-data-in-elasticsearch-on-azure-seeking-community-advice/348440>\
**Category:** Elasticsearch\
**Tags:** slm-snapshot-lifecycle-management\
**Created:** [December 1, 2023, 3:41pm UTC](https://discuss.elastic.co/t/optimizing-storage-costs-for-historical-data-in-elasticsearch-on-azure-seeking-community-advice/348440 "2023-12-01T15:41:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![identifysun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/identifysun/32/128403_2.png) [@identifysun](https://discuss.elastic.co/u/identifysun)\
**Post date:** [December 1, 2023, 3:41pm UTC](https://discuss.elastic.co/t/optimizing-storage-costs-for-historical-data-in-elasticsearch-on-azure-seeking-community-advice/348440/1 "2023-12-01T15:41:26Z")

</div>

I have an Elasticsearch cluster deployed on Azure. I need to retain historical data in Elasticsearch and currently use snapshot policies to store snapshots in Azure Blob storage. However, over time, I noticed that the storage costs for Azure Blob are becoming significant. I'm considering using Azure Blob's lifecycle management policy to move blobs older than 1 year to the Archive tier. This way, I can save costs while still being able to unfreeze and restore the archived data if needed. Is this a reasonable approach?

---

<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:** [December 29, 2023, 3:41pm UTC](https://discuss.elastic.co/t/optimizing-storage-costs-for-historical-data-in-elasticsearch-on-azure-seeking-community-advice/348440/2 "2023-12-29T15:41:33Z")

</div>

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