# Pushing logs to S3 vs local backups!

**URL:** <https://discuss.elastic.co/t/pushing-logs-to-s3-vs-local-backups/112183>\
**Category:** Logstash\
**Created:** [December 18, 2017, 9:13am UTC](https://discuss.elastic.co/t/pushing-logs-to-s3-vs-local-backups/112183 "2017-12-18T09:13:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Milad\_Hamid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milad_hamid/32/24327_2.png) [@Milad\_Hamid](https://discuss.elastic.co/u/Milad_Hamid)\
**Post date:** [December 18, 2017, 9:13am UTC](https://discuss.elastic.co/t/pushing-logs-to-s3-vs-local-backups/112183/1 "2017-12-18T09:13:59Z")

</div>

Hi,  
I wanted to know which is better to have parsed logs backup into S3 bucket or write on local disk. Local disk is cheaper. With S3 output creates temporary files into the OS temporary directory, then will transfer the files to the S3 bucket, so is it once per day! as i understating it!

So even with S3 output we have to think about the storage capacity on the ELK server machine, since it creates temporary directory to save the files.

Which way is cheaper and safer, local buckups, S3, or Elsaticsearch snapshot?

---

<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:** [January 15, 2018, 9:14am UTC](https://discuss.elastic.co/t/pushing-logs-to-s3-vs-local-backups/112183/2 "2018-01-15T09:14:10Z")

</div>

Closed on January 15, 2018, 9:14am UTC

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