# Using http\_proxy in the S3 output plugin?

**URL:** <https://discuss.elastic.co/t/using-http-proxy-in-the-s3-output-plugin/112180>\
**Category:** Logstash\
**Created:** [December 18, 2017, 9:02am UTC](https://discuss.elastic.co/t/using-http-proxy-in-the-s3-output-plugin/112180 "2017-12-18T09:02:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patrik\_Iselind](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrik_iselind/32/25744_2.png) [@Patrik\_Iselind](https://discuss.elastic.co/u/Patrik_Iselind)\
**Post date:** [December 18, 2017, 9:02am UTC](https://discuss.elastic.co/t/using-http-proxy-in-the-s3-output-plugin/112180/1 "2017-12-18T09:02:38Z")

</div>

I am having issues using the S3 output plugin

```
logstash_1 | [2017-12-18T08:37:47,589][ERROR][logstash.outputs.s3] Error validating bucket write permissions! {:message=>"Network is unreachable", :class=>"Seahorse::Client::NetworkingError"}

```

I guess it's due to the corporate proxy. How do i get the output plugin to use the {http,http}\_proxy environment variables to get passed the proxy?

I have tried to specify both, both upper case and lower case. Nothing seems to bite.

It all works just fine in our Kubernetes cluster which is not protected by the corporate proxy.

---

<div class="post-metadata">

**Author:** ![Patrik\_Iselind](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrik_iselind/32/25744_2.png) [@Patrik\_Iselind](https://discuss.elastic.co/u/Patrik_Iselind)\
**Post date:** [December 20, 2017, 2:08pm UTC](https://discuss.elastic.co/t/using-http-proxy-in-the-s3-output-plugin/112180/2 "2017-12-20T14:08:09Z")

</div>

Is there any information missing? Let me know!

---

<div class="post-metadata">

**Author:** ![Patrik\_Iselind](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrik_iselind/32/25744_2.png) [@Patrik\_Iselind](https://discuss.elastic.co/u/Patrik_Iselind)\
**Post date:** [January 11, 2018, 9:18am UTC](https://discuss.elastic.co/t/using-http-proxy-in-the-s3-output-plugin/112180/3 "2018-01-11T09:18:21Z")

</div>

I happen to stumble on the solution the other day, thought i'd share it with the world. The s3 {in,out}put plugins have a proxy\_uri property instead of using the http\_proxy environment variables.

---

<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 8, 2018, 9:18am UTC](https://discuss.elastic.co/t/using-http-proxy-in-the-s3-output-plugin/112180/4 "2018-02-08T09:18:34Z")

</div>

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