# Logstash-output-s3

**URL:** <https://discuss.elastic.co/t/logstash-output-s3/83545>\
**Category:** Logstash\
**Created:** [April 25, 2017, 10:35am UTC](https://discuss.elastic.co/t/logstash-output-s3/83545 "2017-04-25T10:35:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ticktockhouse](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ticktockhouse/32/16801_2.png) [@ticktockhouse](https://discuss.elastic.co/u/ticktockhouse)\
**Post date:** [April 25, 2017, 10:35am UTC](https://discuss.elastic.co/t/logstash-output-s3/83545/1 "2017-04-25T10:35:46Z")

</div>

I'm seeing an issue with the above plugin, version 5.2. I'm running it in a docker container on kubernetes. It works for about 5 hours before crashing the container with errors like this:

```
09:51:44.250 [[main]-pipeline-manager] ERROR logstash.outputs.s3 - Error validating bucket write permissions! {:message=>"No space left on device", :class=>"IOError"}

```

and

```
 @output_class=LogStash::Outputs::S3>", :error=>"Logstash must have the privileges to write to root bucket `cnc-logs`, check you credentials or your permissions."}

```

It quite happily writes to the bucket before this, though. I haven't yet checked the disk space usage on the host node. Could that be what's causing this behaviour?

Thanks in advance...

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [April 28, 2017, 2:02pm UTC](https://discuss.elastic.co/t/logstash-output-s3/83545/2 "2017-04-28T14:02:44Z")

</div>

> 09:51:44.250 [[main]-pipeline-manager] ERROR logstash.outputs.s3 - Error validating bucket write permissions! {:message=\>"No space left on device", :class=\>"IOError"}

The S3 output use the local file system to asynchronously publish events to S3, so this mean the output can't write more stuff to the disk. You can use the `temporary_directory` option to specify the directory to use, by default Logstash will use the OS TMP dir.

> @output\_class=LogStash::Outputs::S3\>", :error=\>"Logstash must have the privileges to write to root bucket `cnc-logs`, check you credentials or your permissions."}

Usually Logstash expects to be able to have full permission to write stuff on the bucket (this is the mon common configuration), do you only allow the logstash users to write in some directory in the bucket? If you are using finer grained control on the bucket you can disable this by adding this to your configuration `validate_credentials_on_root_bucket => false`

---

<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:** [May 26, 2017, 2:14pm UTC](https://discuss.elastic.co/t/logstash-output-s3/83545/3 "2017-05-26T14:14:02Z")

</div>

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