# Intelligent Tiering & Snapshots

**URL:** <https://discuss.elastic.co/t/intelligent-tiering-snapshots/167510>\
**Category:** Elasticsearch\
**Created:** [February 7, 2019, 7:00pm UTC](https://discuss.elastic.co/t/intelligent-tiering-snapshots/167510 "2019-02-07T19:00:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ogg](https://avatars.discourse-cdn.com/v4/letter/o/e36b37/32.png) [@ogg](https://discuss.elastic.co/u/ogg)\
**Post date:** [February 7, 2019, 7:00pm UTC](https://discuss.elastic.co/t/intelligent-tiering-snapshots/167510/1 "2019-02-07T19:00:02Z")

</div>

I have some questions regarding snapshots to s3 and [Intelligent Tiering](https://aws.amazon.com/about-aws/whats-new/2018/11/s3-intelligent-tiering/), we are seeking to save some $$ on our snapshot storage, however, If the snapshot process needs to access past snapshots to create the new snapshots, Intelligent Tiering may not save us much at all. Has anyone used this storage class with snapshots? I know glacier is not supported by the current plugin, but ideally, it would be nice to use glacier in the future.

Thanks.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 12, 2019, 8:18pm UTC](https://discuss.elastic.co/t/intelligent-tiering-snapshots/167510/2 "2019-02-12T20:18:02Z")

</div>

> [@ogg](#):
>
> If the snapshot process needs to access past snapshots to create the new snapshots, Intelligent Tiering may not save us much at all.

The snapshot process only really looks at a few metadata objects when performing subsequent snapshots, and doesn't look at most of the data that's there. I think it does list all the objects in the repository, but it's not clear from the AWS docs whether this Intelligent Tiering counts listing objects as "access". I'd hope not, and it seems worth a go.

---

<div class="post-metadata">

**Author:** ![ogg](https://avatars.discourse-cdn.com/v4/letter/o/e36b37/32.png) [@ogg](https://discuss.elastic.co/u/ogg)\
**Post date:** [February 12, 2019, 8:19pm UTC](https://discuss.elastic.co/t/intelligent-tiering-snapshots/167510/3 "2019-02-12T20:19:08Z")

</div>

Awesome, thanks for clarifying this!

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 13, 2019, 8:45am UTC](https://discuss.elastic.co/t/intelligent-tiering-snapshots/167510/4 "2019-02-13T08:45:57Z")

</div>

I opened [https://github.com/elastic/elasticsearch/issues/38836](https://github.com/elastic/elasticsearch/issues/38836) recommending that we natively support this storage class in a future version. A PR is, of course, more than welcome 🙂

---

<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 13, 2019, 8:46am UTC](https://discuss.elastic.co/t/intelligent-tiering-snapshots/167510/5 "2019-03-13T08:46:01Z")

</div>

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