# How to access a public S3 bucket through corporate firewall

**URL:** <https://community.dremio.com/t/how-to-access-a-public-s3-bucket-through-corporate-firewall/304>\
**Category:** Uncategorized\
**Created:** [September 21, 2017, 3:17pm UTC](https://community.dremio.com/t/how-to-access-a-public-s3-bucket-through-corporate-firewall/304 "2017-09-21T15:17:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![david.lee](https://avatars.discourse-cdn.com/v4/letter/d/ed655f/32.png) [@david.lee](https://community.dremio.com/u/david.lee)\
**Post date:** [September 21, 2017, 3:17pm UTC](https://community.dremio.com/t/how-to-access-a-public-s3-bucket-through-corporate-firewall/304/1 "2017-09-21T15:17:31Z")

</div>

Tried testing the [samples.dremio.com](http://samples.dremio.com) public bucket…

It shows up in Sources, but it comes up empty. The error message is below…

How do I add a HTTP\_PROXY setting into the Dremio configuration to get through the corporate firewall?

Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to [samples.dremio.com.s3.amazonaws.com:80](http://samples.dremio.com.s3.amazonaws.com:80) [[samples.dremio.com.s3.amazonaws.com/52.218.193.138](http://samples.dremio.com.s3.amazonaws.com/52.218.193.138)] failed: connect timed out  
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150) ~[httpclient-4.5.2.jar:4.5.2]  
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) ~[httpclient-4.5.2.jar:4.5.2]  
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0\_121]

---

<div class="post-metadata">

**Author:** ![jduong](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/jduong/32/21_2.png) [@jduong](https://community.dremio.com/u/jduong)\
**Post date:** [September 21, 2017, 3:36pm UTC](https://community.dremio.com/t/how-to-access-a-public-s3-bucket-through-corporate-firewall/304/2 "2017-09-21T15:36:06Z")

</div>

Hello @david.lee,

Dremio can be configured to run with additional JVM flags. You can use this property to set the http.proxyHost and http.proxyPort options.

From your installation, go to /conf and edit the dremio-env file.

At the bottom of this file is a DREMIO\_JAVA\_EXTRA\_OPTS variable which is commented out with the # character at the front. Uncomment this, and add -Dhttp.proxyHost=[your proxy host] and -Dhttp.proxyPort=[your proxy port]

---

<div class="post-metadata">

**Author:** ![david.lee](https://avatars.discourse-cdn.com/v4/letter/d/ed655f/32.png) [@david.lee](https://community.dremio.com/u/david.lee)\
**Post date:** [September 21, 2017, 3:57pm UTC](https://community.dremio.com/t/how-to-access-a-public-s3-bucket-through-corporate-firewall/304/3 "2017-09-21T15:57:10Z")

</div>

Ok this worked after some tweeking…

DREMIO\_JAVA\_EXTRA\_OPTS="-Dhttp.proxyHost=[proxy host] -Dhttp.proxyPort=[port]"

---

<div class="post-metadata">

**Author:** ![jduong](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/jduong/32/21_2.png) [@jduong](https://community.dremio.com/u/jduong)\
**Post date:** [September 21, 2017, 5:49pm UTC](https://community.dremio.com/t/how-to-access-a-public-s3-bucket-through-corporate-firewall/304/4 "2017-09-21T17:49:49Z")

</div>

Perfect! Thanks for the update.

---

<div class="post-metadata">

**Author:** ![vardominator](https://avatars.discourse-cdn.com/v4/letter/v/839c29/32.png) [@vardominator](https://community.dremio.com/u/vardominator)\
**Post date:** [July 26, 2018, 5:16pm UTC](https://community.dremio.com/t/how-to-access-a-public-s3-bucket-through-corporate-firewall/304/5 "2018-07-26T17:16:57Z")

</div>

I did exactly what @david.lee suggested, but I am seeing the following error:

Unable to execute HTTP request: Connect to [samples.dremio.com.s3.amazonaws.com:80](http://samples.dremio.com.s3.amazonaws.com:80) [[samples.dremio.com.s3.amazonaws.com/52.218.244.242](http://samples.dremio.com.s3.amazonaws.com/52.218.244.242)] failed: Connection refused: connect

@jduong could this be caused by something other than the proxy?