# Using S3 as storage for elasticsearch

**URL:** <https://discuss.elastic.co/t/using-s3-as-storage-for-elasticsearch/202986>\
**Category:** Elasticsearch\
**Created:** [October 10, 2019, 9:10am UTC](https://discuss.elastic.co/t/using-s3-as-storage-for-elasticsearch/202986 "2019-10-10T09:10:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [October 10, 2019, 9:27am UTC](https://discuss.elastic.co/t/using-s3-as-storage-for-elasticsearch/202986/2 "2019-10-10T09:27:50Z")

</div>

You can save snapshots of your indices on S3, but S3 doesn't support the features Elasticsearch needs for search. See this post for more details:

> [@Is there a way to install ealsticsearch in object storage env?](https://discuss.elastic.co/t/is-there-a-way-to-install-ealsticsearch-in-object-storage-env/199993/4):
>
> I don't think S3FS will work either. Elasticsearch expects its filesystem to behave like a filesystem, supporting features like fast atomic renames, cheap random access, consistent directory listings, and hard links. S3 doesn't have these features, and although S3FS looks a bit like a filesystem I think it also doesn't accurately simulate these features either.

---

_[View the full topic](https://discuss.elastic.co/t/using-s3-as-storage-for-elasticsearch/202986)._