# S3 Output - Minio Connection Error

**URL:** <https://discuss.elastic.co/t/s3-output-minio-connection-error/156360>\
**Category:** Logstash\
**Created:** [November 12, 2018, 10:16pm UTC](https://discuss.elastic.co/t/s3-output-minio-connection-error/156360 "2018-11-12T22:16:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bitva77](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitva77/32/66694_2.png) [@bitva77](https://discuss.elastic.co/u/bitva77)\
**Post date:** [November 12, 2018, 10:16pm UTC](https://discuss.elastic.co/t/s3-output-minio-connection-error/156360/1 "2018-11-12T22:16:25Z")

</div>

Hi! We're trying to output to Minio via the S3 output plugin. We specify the name of the server via `endpoint:` and we're getting this error:

> [ERROR][logstash.outputs.s3] Uploading failed, retrying. {:exception=\>Seahorse::Client::NetworkingError, :message=\>"Failed to open TCP connection to [click-data.minio.ourdomain.com:80](http://click-data.minio.ourdomain.com:80) (initialize: name or service not known)"

`click-data` is the name of the bucket. [minio.ourdomain.com](http://minio.ourdomain.com) exists and I can access it from within the container via port 80.

In fact, I can put the minio client in the Logstash container and access the server and bucket.

It looks like it's combining the bucket and the endpoint to create the server name. Here's the config:

```
	s3 {
		secret_access_key => "reallylongstring"
		access_key_id => "anotherreallylongstring"
		endpoint => "http://minio.ourdomain.com"
		bucket => "click-data"
		prefix => "%{+YYYY-MM}"
        ...otherstuff...
        }

```

Any ideas?

---

<div class="post-metadata">

**Author:** ![bitva77](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitva77/32/66694_2.png) [@bitva77](https://discuss.elastic.co/u/bitva77)\
**Post date:** [November 13, 2018, 3:32am UTC](https://discuss.elastic.co/t/s3-output-minio-connection-error/156360/2 "2018-11-13T03:32:02Z")

</div>

Thinking that the plugin is literally tryingto connect to [http://bucket.endpoint:80](http://bucket.endpoint:80) - I put that in the hosts file on the box ([click-data.minio.ourdomain.com](http://click-data.minio.ourdomain.com))

Now we get this error message:

```
[ERROR][logstash.outputs.s3] Uploading failed, retrying. {:exception=>Aws::S3::Errors::NoSuchBucket, :message=>"The specified bucket does not exist" 

```

Which sort of confirms that. tcpdump show's the same, it's using the bucket name as part of the server to connect to via the endpoint.

---

<div class="post-metadata">

**Author:** ![bitva77](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitva77/32/66694_2.png) [@bitva77](https://discuss.elastic.co/u/bitva77)\
**Post date:** [November 13, 2018, 5:14pm UTC](https://discuss.elastic.co/t/s3-output-minio-connection-error/156360/3 "2018-11-13T17:14:57Z")

</div>

I've confirmed that if we use a date prefix, that prefix becomes the bucket and uploads succeed. Not what we want at all and I don't believe this is how that plugin should work.

I've filed an issue on the github project page.

---

<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:** [December 11, 2018, 5:15pm UTC](https://discuss.elastic.co/t/s3-output-minio-connection-error/156360/4 "2018-12-11T17:15:06Z")

</div>

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