# Elasticsearch HOT/WARM infrastructure with S3 mounted as a filesystem using S3FS problem **URL:** \ **Category:** Elasticsearch\ **Created:** [December 6, 2018, 6:37am UTC](https://discuss.elastic.co/t/elasticsearch-hot-warm-infrastructure-with-s3-mounted-as-a-filesystem-using-s3fs-problem/159660 "2018-12-06T06:37:42Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [December 6, 2018, 8:14am UTC](https://discuss.elastic.co/t/elasticsearch-hot-warm-infrastructure-with-s3-mounted-as-a-filesystem-using-s3fs-problem/159660/3 "2018-12-06T08:14:27Z")
This kind of set-up is a bad idea. I recommend you have a look at this thread: > [@Elasticsearch indices stored on S3 mounted with S3FS](https://discuss.elastic.co/t/elasticsearch-indices-stored-on-s3-mounted-with-s3fs/157400): > > Hi, So I've a really specific infrastructure where I need to store my "Older than 30 days" indices on COLD/WARM nodes. Those nodes have a S3 bucket (1 bucket for all 4 nodes) mounted as a filesystem on each node in /data/ folder. Of course, /data/ is set as path for those nodes to store indices etc. Setup is : 4 Hot, 4 Cold/Warm, 15GB RAM each (7GB Heap) What I'd like to ask is: When we are talking about 100GB of data daily (right now) and something like 500GB of data daily in the future - do… --- _[View the full topic](https://discuss.elastic.co/t/elasticsearch-hot-warm-infrastructure-with-s3-mounted-as-a-filesystem-using-s3fs-problem/159660)._