# S3 input plugin behind proxy

**URL:** <https://discuss.elastic.co/t/s3-input-plugin-behind-proxy/32272>\
**Category:** Logstash\
**Created:** [October 15, 2015, 1:17pm UTC](https://discuss.elastic.co/t/s3-input-plugin-behind-proxy/32272 "2015-10-15T13:17:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![scaarup](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scaarup/32/4615_2.png) [@scaarup](https://discuss.elastic.co/u/scaarup)\
**Post date:** [October 15, 2015, 1:17pm UTC](https://discuss.elastic.co/t/s3-input-plugin-behind-proxy/32272/1 "2015-10-15T13:17:10Z")

</div>

Has anybody gotten the s3 input plugin working behind a HTTP proxy?

All I get is the below?

```
{:timestamp=>"2015-10-15T15:06:03.343000+0200", :message=>"A plugin had an unrecoverable error. Will restart this plugin.\n Plugin: <LogStash::Inputs::S3 access_key_id=>\"XXX\", secret_access_key=>\"XXX\", aws_credentials_file=>\"/etc/logstash/aws\", bucket=>\"xxx\", region=>\"eu-west-1\", type=>\"s3\", proxy_uri=>\"http://updater:xxx@192.168.0.200:3128\", debug=>true, codec=><LogStash::Codecs::Plain charset=>\"UTF-8\">, use_ssl=>true, delete=>false, interval=>60, temporary_directory=>\"/var/lib/logstash/logstash\">\n Error: Connection refused - Connection refused", :level=>:error}

```

My conf looks like this:

```
input {
       s3 {
               access_key_id => "XXX"
               secret_access_key => "XXX"
               aws_credentials_file => "/etc/logstash/aws"
               bucket => "xxx"
               region => "eu-west-1"
               type => "s3"
               proxy_uri => "http://updater:xxx@192.168.0.200:3128"
       }
}

```

There are no entries in my proxy-servers logfile, indicating, that logstash is not even trying to hit it...

---

<div class="post-metadata">

**Author:** ![conerj](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@conerj](https://discuss.elastic.co/u/conerj)\
**Post date:** [April 25, 2017, 6:32pm UTC](https://discuss.elastic.co/t/s3-input-plugin-behind-proxy/32272/2 "2017-04-25T18:32:16Z")

</div>

I have not been able to either.  
I'm using 1.5.4 and I used a proxy server and can see that logstash is still not honoring the proxy\_uri that I entered even though there is a github issue noting that it was supposedly closed around the time that you posted this:

> <https://github.com/logstash-plugins/logstash-input-s3/issues/30>

---

<div class="post-metadata">

**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\
**Post date:** [April 29, 2017, 10:43pm UTC](https://discuss.elastic.co/t/s3-input-plugin-behind-proxy/32272/3 "2017-04-29T22:43:03Z")

</div>

I put this in my elasticsearch.yml

```auto
cloud:
    aws:
        protocol: ${S3_PROTOCOL}
        proxy_host: ${S3_HTTPS_PROXY}
        proxy_port: ${S3_HTTPS_PROXY_PORT}

```

```auto
OUT=`curl -ks "http://$HOST:$PORT/_snapshot/s3_repo-$DATE" --data-binary @- --no-buffer -XPOST << _EOF_ 
{
  "type": "s3",
  "settings": {
        "access_key": "XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
        "secret_key": "XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
        "bucket": "abcdefg",
        "base_path": "blah-$DATE",
        "compress": true,
        "server_side_encryption": true,
        "max_retries": 10,
        "canned_acl": "private"
  }
}

```

works just fine for me in 2.4 and did the same for 5.2

---

<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:** [July 6, 2017, 4:26am UTC](https://discuss.elastic.co/t/s3-input-plugin-behind-proxy/32272/4 "2017-07-06T04:26:51Z")

</div>