# Is there any way to send to logs to s3 to overcome the space issue in elk server? **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [June 17, 2019, 1:11pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-send-to-logs-to-s3-to-overcome-the-space-issue-in-elk-server/186069 "2019-06-17T13:11:08Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![krish2](https://avatars.discourse-cdn.com/v4/letter/k/b5a626/32.png) [@krish2](https://discuss.elastic.co/u/krish2)\ **Post date:** [June 17, 2019, 1:11pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-send-to-logs-to-s3-to-overcome-the-space-issue-in-elk-server/186069/1 "2019-06-17T13:11:09Z")
Hi , I'm facing a problem with my elk server. I have installed filebeat and metricbeat in my server . The root mount is getting filled with the logs and having space issue. Due to that the new logs are not getting loaded in elasticsearch. Can we overcome this problem to send logs to S3 from filebeat /metricbeat ? Is there any scenario like filebeat(logs) --\>S3--\> kibana? Please help on this... ---
**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\ **Post date:** [June 18, 2019, 8:55am UTC](https://discuss.elastic.co/t/is-there-any-way-to-send-to-logs-to-s3-to-overcome-the-space-issue-in-elk-server/186069/2 "2019-06-18T08:55:48Z")
Hi @krish2 ! 🙂 You can use ILM to move your older indexes to cheaper machines ([https://www.elastic.co/guide/en/beats/metricbeat/master/ilm.html](https://www.elastic.co/guide/en/beats/metricbeat/master/ilm.html) and [https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-management.html](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-management.html)) or use snapshots and move that data to S3 as a backup [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html). However, you cannot consume data directly from S3. I hope it helps ---
**Author:** ![krish2](https://avatars.discourse-cdn.com/v4/letter/k/b5a626/32.png) [@krish2](https://discuss.elastic.co/u/krish2)\ **Post date:** [June 19, 2019, 10:59am UTC](https://discuss.elastic.co/t/is-there-any-way-to-send-to-logs-to-s3-to-overcome-the-space-issue-in-elk-server/186069/3 "2019-06-19T10:59:21Z")
Thank you Mario\_Castro for the good suggestion . But I have a doubt that if we want to old indices to be presented in the elasticsearch so that to see the historical log monitoring, what is the best way for that? Thanks in advance. And one more I just enabled and started the filebeat . My root mount size is 20 GB in that available is 13GB . After I started filebeat and logstash with in one hour the logstash throwing an error and the root mount almost full. How can I overcome this issue. please help me on this.. ---
**Author:** ![krish2](https://avatars.discourse-cdn.com/v4/letter/k/b5a626/32.png) [@krish2](https://discuss.elastic.co/u/krish2)\ **Post date:** [June 19, 2019, 12:49pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-send-to-logs-to-s3-to-overcome-the-space-issue-in-elk-server/186069/4 "2019-06-19T12:49:03Z")
Hi,, I have removed two directories from the location /var/lib/elasticsearch/nodes/0/indices These are the two indices that I removed from the above location. after that I restarted the elasticsearch , It is failed to start. Please help on this. 3cQZvpsjRBmfAz\_SLcWdpQ uIxRIDZ0SLmHeJD-eREypA ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 17, 2019, 12:49pm UTC](https://discuss.elastic.co/t/is-there-any-way-to-send-to-logs-to-s3-to-overcome-the-space-issue-in-elk-server/186069/5 "2019-07-17T12:49:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.