# Setting up Kibana behind AWS application load balancer

**URL:** <https://discuss.elastic.co/t/setting-up-kibana-behind-aws-application-load-balancer/214348>\
**Category:** Kibana\
**Created:** [January 9, 2020, 5:51am UTC](https://discuss.elastic.co/t/setting-up-kibana-behind-aws-application-load-balancer/214348 "2020-01-09T05:51:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amphagory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amphagory/32/46127_2.png) [@Amphagory](https://discuss.elastic.co/u/Amphagory)\
**Post date:** [January 9, 2020, 5:51am UTC](https://discuss.elastic.co/t/setting-up-kibana-behind-aws-application-load-balancer/214348/1 "2020-01-09T05:51:34Z")

</div>

I am having trouble setting up multiple Kibana 7.3.2 instances behind an AWS ALB.

Actually, I don't even get that far as the installation of Kibana is not going well. I follow the simple guide ([https://www.elastic.co/guide/en/kibana/current/rpm.html](https://www.elastic.co/guide/en/kibana/current/rpm.html)) to install Kibana on an EC2 instance running AWS linux 2.

I should be able to connect to this instance (http://public\_ip:5601), but I get connection refuse... I've seen tutorials and videos connect with just setting this up. No reverse proxy (nginx or httpd) needed... I guess I side rant as the goal it to set up an application load balance with the Kibana instance behind it.

I was wondering if you share your blog, experience, step by step guide if you have the same setup?

---

<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 9, 2020, 4:59pm UTC](https://discuss.elastic.co/t/setting-up-kibana-behind-aws-application-load-balancer/214348/2 "2020-01-09T16:59:55Z")

</div>

Is Kibana configured to listen on the public interface?

Check the documentation at:  
See: [Configure Kibana | Kibana Guide [8.11] | Elastic](https://www.elastic.co/guide/en/kibana/current/settings.html)

> The default host and port settings configure Kibana to run on `localhost:5601` . To change this behavior and allow remote users to connect, you’ll need to update your `kibana.yml`

Check your `server.host` setting. By default it is `localhost` which only allows local users to connect. You'll need to change that setting to have Kibana bind to the public interface

---

<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 6, 2020, 5:00pm UTC](https://discuss.elastic.co/t/setting-up-kibana-behind-aws-application-load-balancer/214348/3 "2020-02-06T17:00:03Z")

</div>

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