# Setting up elasticsearch and kibana behind a single AWS application load balancer (on http)

**URL:** <https://discuss.elastic.co/t/setting-up-elasticsearch-and-kibana-behind-a-single-aws-application-load-balancer-on-http/243541>\
**Category:** Kibana\
**Created:** [August 3, 2020, 10:49am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-and-kibana-behind-a-single-aws-application-load-balancer-on-http/243541 "2020-08-03T10:49:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deepak\_Atrey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepak_atrey/32/48115_2.png) [@Deepak\_Atrey](https://discuss.elastic.co/u/Deepak_Atrey)\
**Post date:** [August 3, 2020, 10:49am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-and-kibana-behind-a-single-aws-application-load-balancer-on-http/243541/1 "2020-08-03T10:49:03Z")

</div>

Hi Experts,

I am setting up the elasticsearch and kibana on amazon ECS cluster. I am able to run the elasticsearch and kibana from official docker images (v7.8.1) on Ec2 nodes.

I have configured the elasticsearch target group behind an ALB and able to access elasticsearch from ALB dns name. Listner rule path is **"/\*"**

Further, I have configured an another target group for kibana and configured it behind the same ALB with different listner rule **(/app/kibana)**. However, when I am trying to access the kibana console from browser, then it shows a blank white screen (Not even kibana logo).

Both elasticsearch and kibana ecs containers are running on the same ec2 nodes in the ecs cluster.

Note: When I created a different ALB for kibana then I was able to access it, but my requirement is to get them working under the same ALB.

---

<div class="post-metadata">

**Author:** ![Deepak\_Atrey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepak_atrey/32/48115_2.png) [@Deepak\_Atrey](https://discuss.elastic.co/u/Deepak_Atrey)\
**Post date:** [August 6, 2020, 5:12am UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-and-kibana-behind-a-single-aws-application-load-balancer-on-http/243541/2 "2020-08-06T05:12:25Z")

</div>

Any help on the above issue would be appreciated. ?

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [August 12, 2020, 5:03pm UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-and-kibana-behind-a-single-aws-application-load-balancer-on-http/243541/3 "2020-08-12T17:03:24Z")

</div>

Are you only forwarding requests to `/app/kibana` to the Kibana port? There are lots of resources loaded from other paths, you can scope it to something else by using `server.basePath` in your `kibana.yml`: [https://www.elastic.co/guide/en/kibana/master/settings.html](https://www.elastic.co/guide/en/kibana/master/settings.html)

So you should to something like using `/kibanaRoot` as the base path, then forward everything below that in your AWS config and you can access kibana at `/kibanaRoot/app/kibana`.

Apologies if I got something wrong about the AWS parts here, I'm not really familiar to it.

---

<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:** [September 9, 2020, 5:03pm UTC](https://discuss.elastic.co/t/setting-up-elasticsearch-and-kibana-behind-a-single-aws-application-load-balancer-on-http/243541/4 "2020-09-09T17:03:47Z")

</div>

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