# Using two kibana for HA(active-active) - Pointing to the same Elastic cluster

**URL:** <https://discuss.elastic.co/t/using-two-kibana-for-ha-active-active-pointing-to-the-same-elastic-cluster/304283>\
**Category:** Kibana\
**Created:** [May 9, 2022, 5:58pm UTC](https://discuss.elastic.co/t/using-two-kibana-for-ha-active-active-pointing-to-the-same-elastic-cluster/304283 "2022-05-09T17:58:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonatiao](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@jonatiao](https://discuss.elastic.co/u/jonatiao)\
**Post date:** [May 9, 2022, 5:58pm UTC](https://discuss.elastic.co/t/using-two-kibana-for-ha-active-active-pointing-to-the-same-elastic-cluster/304283/1 "2022-05-09T17:58:21Z")

</div>

Hello,

Is it possible to have two kibana, in different VMs, in an active-active state responding the the same address via LB?

Browser([kibana.mydomain.com](http://kibana.mydomain.com)) -\> LB -\> kibana1,kibana2

If yes, what are the configurations we need for the load balancer.  
Do we need sticky sessions and cookie control in the LB or kibana will be, somehow, able to control the browser session?

What about SSL. Do I need to configure the LB to support a bridged SSL? Like:

Browser([https://kibana.mydomain.com](https://kibana.mydomain.com)) -\>(SSL1) LB (SSL2) -\> ([https://kibana.intern](https://kibana.intern))kibana1,kibana2([https://kibana2.intern](https://kibana2.intern))

thx!

---

<div class="post-metadata">

**Author:** ![LizaD](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lizad/32/51074_2.png) [@LizaD](https://discuss.elastic.co/u/LizaD)\
**Post date:** [May 9, 2022, 6:23pm UTC](https://discuss.elastic.co/t/using-two-kibana-for-ha-active-active-pointing-to-the-same-elastic-cluster/304283/2 "2022-05-09T18:23:57Z")

</div>

Hi @jonatiao , welcome to our community!

Here are some documentation that may help you provision this setup:

> **[Use Kibana in a production environment | Kibana Guide \[8.2\] | Elastic](https://www.elastic.co/guide/en/kibana/current/production.html)**
>
> Consider the production components that are used to generate reports.

> **[Configure Kibana | Kibana Guide \[8.2\] | Elastic](https://www.elastic.co/guide/en/kibana/8.2/settings.html)**
>
> A reference of the reporting settings administrators configure in kibana.yml.

---

<div class="post-metadata">

**Author:** ![jonatiao](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@jonatiao](https://discuss.elastic.co/u/jonatiao)\
**Post date:** [May 9, 2022, 8:21pm UTC](https://discuss.elastic.co/t/using-two-kibana-for-ha-active-active-pointing-to-the-same-elastic-cluster/304283/3 "2022-05-09T20:21:23Z")

</div>

Hello Liza,

Thx for your answer. : )  
I had already read those docs but the latter don't answer my questions. Or maybe I got it all wrong, if so, could you please be more specific on which part of the docs it is said how I do(or do not) need to configure my LB?

thx a lot!

---

<div class="post-metadata">

**Author:** ![LizaD](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lizad/32/51074_2.png) [@LizaD](https://discuss.elastic.co/u/LizaD)\
**Post date:** [May 9, 2022, 8:50pm UTC](https://discuss.elastic.co/t/using-two-kibana-for-ha-active-active-pointing-to-the-same-elastic-cluster/304283/4 "2022-05-09T20:50:36Z")

</div>

Our docs show the settings for our products, not sure it would give specifics on how to provision a load balancer, I have not set this up, but let me see if someone in our ops team can answer your question: cc: @jbudz can you help here?

---

<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:** [June 6, 2022, 8:50pm UTC](https://discuss.elastic.co/t/using-two-kibana-for-ha-active-active-pointing-to-the-same-elastic-cluster/304283/5 "2022-06-06T20:50:38Z")

</div>

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