# S3 output behaviour when internet goes down?

**URL:** <https://discuss.elastic.co/t/s3-output-behaviour-when-internet-goes-down/115850>\
**Category:** Logstash\
**Created:** [January 17, 2018, 9:00am UTC](https://discuss.elastic.co/t/s3-output-behaviour-when-internet-goes-down/115850 "2018-01-17T09:00:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sjaak01](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@Sjaak01](https://discuss.elastic.co/u/Sjaak01)\
**Post date:** [January 17, 2018, 9:00am UTC](https://discuss.elastic.co/t/s3-output-behaviour-when-internet-goes-down/115850/1 "2018-01-17T09:00:57Z")

</div>

Hi,

As per the subject, how does the S3 output react when the internet connection is interrupted?

- Are all temporarily files saved until the connection comes back up?
- If a connection fails during transmission, will the output resend the failed file once the connection is back up?
- Different topic but how good is the gzip compression? Is it comparable to the file output .gz compression?

I will be sending logs over slow and unstable connections. Timeouts and interruptions are expected. The current strategy is to have logstash output to a file and upload to S3 from there but that has some downsides as well.

---

<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:** [February 14, 2018, 9:00am UTC](https://discuss.elastic.co/t/s3-output-behaviour-when-internet-goes-down/115850/2 "2018-02-14T09:00:58Z")

</div>

Closed on February 14, 2018, 9:00am UTC

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