# Why X-Pack required to install with Elasticsearch & Kibana

**URL:** <https://discuss.elastic.co/t/why-x-pack-required-to-install-with-elasticsearch-kibana/56231>\
**Category:** Kibana\
**Created:** [July 24, 2016, 9:43am UTC](https://discuss.elastic.co/t/why-x-pack-required-to-install-with-elasticsearch-kibana/56231 "2016-07-24T09:43:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gupta.yuvraj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gupta.yuvraj/32/7550_2.png) [@gupta.yuvraj](https://discuss.elastic.co/u/gupta.yuvraj)\
**Post date:** [July 24, 2016, 9:43am UTC](https://discuss.elastic.co/t/why-x-pack-required-to-install-with-elasticsearch-kibana/56231/1 "2016-07-24T09:43:10Z")

</div>

Why do we need to install X-Pack separately for Elasticsearch & Kibana. Can't we provide a single installation which will install the components with Elastisearch & Kibana?

Also, what is the need of having X-Pack installation for Elasticsearch and Kibana? Is there any specific functionality for which it is required to install in both?

---

<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:** [July 24, 2016, 10:29am UTC](https://discuss.elastic.co/t/why-x-pack-required-to-install-with-elasticsearch-kibana/56231/2 "2016-07-24T10:29:26Z")

</div>

> [@gupta.yuvraj](#):
>
> Can't we provide a single installation which will install the components with Elastisearch & Kibana?

They are separate apps requiring separate commands, calling separate binaries.

> [@gupta.yuvraj](#):
>
> Also, what is the need of having X-Pack installation for Elasticsearch and Kibana? Is there any specific functionality for which it is required to install in both?

One is a datastore, one is the visualisation layer. These are separate.

---

<div class="post-metadata">

**Author:** ![gupta.yuvraj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gupta.yuvraj/32/7550_2.png) [@gupta.yuvraj](https://discuss.elastic.co/u/gupta.yuvraj)\
**Post date:** [July 24, 2016, 10:39am UTC](https://discuss.elastic.co/t/why-x-pack-required-to-install-with-elasticsearch-kibana/56231/3 "2016-07-24T10:39:18Z")

</div>

Hi @warkolm

Thanks for your reply.

Can we segregate the apps on the basis of the separate binaries for Elasticsearch & Kibana?

For Example:- Can we say if we install X-Pack for Elasticsearch we will get Shield for securing ES Cluster, Marvel for monitoring ES Cluster, Graph for providing relationships among ES Index entities?

Can we also say if we install X-Pack for Kibana we will get Shield for securing UI, Graph to provide visualizations on the relationships, New Management Dashboard to manage X-Pack Settings, Upload to CSV option and Reporting features?

---

<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:** [July 24, 2016, 10:43am UTC](https://discuss.elastic.co/t/why-x-pack-required-to-install-with-elasticsearch-kibana/56231/4 "2016-07-24T10:43:54Z")

</div>

I'm not sure what you mean.

You've already pointed out the installs are separate. But you need to install x-pack for both ES and KB.

---

<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, 1:40pm UTC](https://discuss.elastic.co/t/why-x-pack-required-to-install-with-elasticsearch-kibana/56231/5 "2017-07-06T13:40:42Z")

</div>