# Minimal hardware requirement for Kibana

**URL:** <https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772>\
**Category:** Kibana\
**Created:** [June 16, 2015, 8:58am UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772 "2015-06-16T08:58:58Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![mal](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@mal](https://discuss.elastic.co/u/mal)\
**Post date:** [June 16, 2015, 8:58am UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/1 "2015-06-16T08:58:58Z")

</div>

Hello,

what are the minimal hardware requirements for running Kibana on a server?

Background:  
For different departments we've to create separate Dashboards.  
We use Shield for authorization.  
We separate data by creating different aliases, so the departments couldn't read the data from the other department.  
We also want to separate the dashboards - this is done by defining different '.kibana'-Index for each kibana instance. (f.exe '.kibana-dep1', '.kibana-dep2',...).  
Every Kibana instances runs on a different port (5601, 5602, ....)

So know we want to know the hardware footprint of running multiple Kibana instances.

thanx & best regards  
Malu

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 16, 2015, 10:17am UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/2 "2015-06-16T10:17:31Z")

</div>

It doesn't need much, most of the resource use will be in ES.

---

<div class="post-metadata">

**Author:** ![mal](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@mal](https://discuss.elastic.co/u/mal)\
**Post date:** [June 16, 2015, 11:20am UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/3 "2015-06-16T11:20:49Z")

</div>

Yes, I know ;/  
But I didn't found any recommendations as for [elasticsearch](https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html).

We're in a very restrictive environment, where we've have to calculate the exact requirements.  
We're planning for 100 departments - so we've to calculate the costs.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 16, 2015, 10:11pm UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/4 "2015-06-16T22:11:36Z")

</div>

We don't have that sort of info, but when I start my KB4 instance it uses ~90M of RAM.  
You really want to test this yourself.

---

<div class="post-metadata">

**Author:** ![mal](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@mal](https://discuss.elastic.co/u/mal)\
**Post date:** [June 19, 2015, 1:46pm UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/5 "2015-06-19T13:46:38Z")

</div>

Okay - that\_s what I also have find out.  
Thanx for your information

---

<div class="post-metadata">

**Author:** ![julienb](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@julienb](https://discuss.elastic.co/u/julienb)\
**Post date:** [September 8, 2015, 8:10am UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/6 "2015-09-08T08:10:10Z")

</div>

Hello Malu,

I have also installed 2 different instances of Kibana4 on the same server in order to seperate the dashboards.  
However, I have an issue to separate data using aliases. In fact, as every alias is stored in the same cluster, even if you create different aliases, they can all be accessible through kibana using the right index-pattern right ? Or did you find a way to prevent the user to create the index-pattern he wants ?  
Thanks

Julien

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 8, 2015, 8:11am UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/7 "2015-09-08T08:11:08Z")

</div>

Please raise this in your own thread.

---

<div class="post-metadata">

**Author:** ![mal](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@mal](https://discuss.elastic.co/u/mal)\
**Post date:** [September 8, 2015, 9:43am UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/8 "2015-09-08T09:43:03Z")

</div>

Hello Julien,

no, we didn't have find another solution. We've installed two instances of Kibana.  
We're experimenting with a proxy-server between kibana and elastic search who separates the Dashboards by patterns.

Even Shield won't help us solve the problem. So we've to manage authentication by our selves.

best regards  
Malu

---

<div class="post-metadata">

**Author:** ![julienb](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@julienb](https://discuss.elastic.co/u/julienb)\
**Post date:** [September 10, 2015, 8:20am UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/9 "2015-09-10T08:20:57Z")

</div>

Thanks for your answer.  
I will stay in this config for now !

---

<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:** [July 6, 2017, 2:13pm UTC](https://discuss.elastic.co/t/minimal-hardware-requirement-for-kibana/2772/10 "2017-07-06T14:13:30Z")

</div>


