# Kibana connecting to AWS ES via a proxy

**URL:** https://discuss.elastic.co/t/kibana-connecting-to-aws-es-via-a-proxy/70695
**Category:** Kibana
**Created:** [January 5, 2017, 3:20pm UTC](https://discuss.elastic.co/t/kibana-connecting-to-aws-es-via-a-proxy/70695 "2017-01-05T15:20:24Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Neil\_Briscoe](https://avatars.discourse-cdn.com/v4/letter/n/13edae/32.png) [@Neil\_Briscoe](https://discuss.elastic.co/u/Neil_Briscoe)
#### Post date: [January 5, 2017, 3:20pm UTC](https://discuss.elastic.co/t/kibana-connecting-to-aws-es-via-a-proxy/70695/1 "2017-01-05T15:20:25Z")

</div>

Hi all,

I am trying to connect to my Kibana box to the AWS ES service I have through a proxy. Currently, the kibana.yml config is:

server.port: 5601  
server.host: "0.0.0.0"  
elasticsearch\_url: "[http://search-xxxxx.eu-west-1.es.amazonaws.com:80](http://search-xxxxx.eu-west-1.es.amazonaws.com:80)"

Therefore, this box sits behind a proxy, and the elasticsearch\_url is over HTTP/80, and I want to push it through it.

I have managed to find the logstash\_output\_plugin to push logs to AWS ES via a proxy - all works fine.

I have tried using **export http\_proxy="x.x.x.x:3128"** from the CLI, in rc.local and in /etc/environment but it appears that kibana is either not using these env settings, or ignoring.

Any ideas?

---

<div class="post-metadata">

### Author: ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)
#### Post date: [January 5, 2017, 9:03pm UTC](https://discuss.elastic.co/t/kibana-connecting-to-aws-es-via-a-proxy/70695/2 "2017-01-05T21:03:15Z")

</div>

> elasticsearch\_url: "[http://search-xxxxx.eu-west-1.es.amazonaws.com:80](http://search-xxxxx.eu-west-1.es.amazonaws.com:80)"

That's not a valid config setting according to the Kibana documentation on Server Properties. I think you want `elasticsearch.url` (use a dot not an underscore).

See [Configuring Kibana | Kibana User Guide [5.1] | Elastic](https://www.elastic.co/guide/en/kibana/5.1/settings.html)

---

<div class="post-metadata">

### Author: ![Neil\_Briscoe](https://avatars.discourse-cdn.com/v4/letter/n/13edae/32.png) [@Neil\_Briscoe](https://discuss.elastic.co/u/Neil_Briscoe)
#### Post date: [January 5, 2017, 9:25pm UTC](https://discuss.elastic.co/t/kibana-connecting-to-aws-es-via-a-proxy/70695/3 "2017-01-05T21:25:11Z")

</div>

Thanks Tim.

I am using kibana 4.5.0, which works perfectly fine when _not_ going through a proxy, so I know the configuration is valid at this version.

My design does not permit the server with kibana on to have direct access to the internet to access AWS ES - i.e. has to go through a proxy.

---

<div class="post-metadata">

### Author: ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)
#### Post date: [January 5, 2017, 9:48pm UTC](https://discuss.elastic.co/t/kibana-connecting-to-aws-es-via-a-proxy/70695/4 "2017-01-05T21:48:44Z")

</div>

Documentation for Kibana 4.5.x Server Properties is here: [Setting Kibana Server Properties | Kibana User Guide [4.5] | Elastic](https://www.elastic.co/guide/en/kibana/4.5/kibana-server-properties.html) and in that version as well, the config option for setting the URL to Elasticsearch is `elasticsearch.url` not `elasticsearch_url`.

Sorry, when I read your original post, I forgot to reply about this part:

> I have tried using export http\_proxy="x.x.x.x:3128" from the CLI, in rc.local and in /etc/environment but it appears that kibana is either not using these env settings, or ignoring.

Applications need to be built to honor that environment variable, and the HTTP client that Kibana uses internally doesn't look for that environment variable.

I think you might be encountering a problem similar to this open issue: [HTTP\_PROXY support for connections towards Elasticsearch · Issue #5211 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/5211)

---

<div class="post-metadata">

### Author: ![Neil\_Briscoe](https://avatars.discourse-cdn.com/v4/letter/n/13edae/32.png) [@Neil\_Briscoe](https://discuss.elastic.co/u/Neil_Briscoe)
#### Post date: [January 5, 2017, 10:04pm UTC](https://discuss.elastic.co/t/kibana-connecting-to-aws-es-via-a-proxy/70695/5 "2017-01-05T22:04:07Z")

</div>

Perfect - that is the exact thing I was hoping you'd say!

Doesn't help me solve my issue, but now I know that it cannot be done and should think of alternative methods.

Current thinking is via a (source) NAT iptables box so it can route to AWS ES without a proxy, but not exposed directly to the internet.

Thanks again.

---

<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 2, 2017, 10:04pm UTC](https://discuss.elastic.co/t/kibana-connecting-to-aws-es-via-a-proxy/70695/6 "2017-02-02T22:04:55Z")

</div>

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