# How to deploy Kibana with preconfigured index pattern

**URL:** https://discuss.elastic.co/t/how-to-deploy-kibana-with-preconfigured-index-pattern/161555
**Category:** Beats
**Tags:** filebeat
**Created:** [December 19, 2018, 4:25pm UTC](https://discuss.elastic.co/t/how-to-deploy-kibana-with-preconfigured-index-pattern/161555 "2018-12-19T16:25:15Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![RussellBateman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/russellbateman/32/34928_2.png) [@RussellBateman](https://discuss.elastic.co/u/RussellBateman)
#### Post date: [January 4, 2019, 2:12pm UTC](https://discuss.elastic.co/t/how-to-deploy-kibana-with-preconfigured-index-pattern/161555/7 "2019-01-04T14:12:27Z")

</div>

I explored some of these solutions and went another way which I've detailed in another discussion:

> [@Certificates between Filebeat and Kibana for Filebeat to do setup.dashboards.enabled: true](https://discuss.elastic.co/t/certificates-between-filebeat-and-kibana-for-filebeat-to-do-setup-dashboards-enabled-true/161904/4):
>
> Well, back from the holidays, this is what I now think. I hope this comment helps someone else. Especially since our multiple Filebeat containers are running potentially (very likely) on different hosts, we don't want to use filebeat.yml to install dashboards in Kibana. Instead, we'll do it in our greater, ELK container. Right now, for instance, we're using the saved-object API in Kibana to preinstall our index pattern ("filebeat-\*") and we'll find a similar solution for any dashboard we choose…

---

_[View the full topic](https://discuss.elastic.co/t/how-to-deploy-kibana-with-preconfigured-index-pattern/161555)._
