# Delivering and Deploying ELK in production environment

**URL:** <https://discuss.elastic.co/t/delivering-and-deploying-elk-in-production-environment/34390>\
**Category:** Elasticsearch\
**Created:** [November 12, 2015, 9:42am UTC](https://discuss.elastic.co/t/delivering-and-deploying-elk-in-production-environment/34390 "2015-11-12T09:42:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Keerthana\_Kannan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keerthana_kannan/32/71091_2.png) [@Keerthana\_Kannan](https://discuss.elastic.co/u/Keerthana_Kannan)\
**Post date:** [November 12, 2015, 9:42am UTC](https://discuss.elastic.co/t/delivering-and-deploying-elk-in-production-environment/34390/1 "2015-11-12T09:42:28Z")

</div>

Hi  
I am new to ELK. I need help on the format of the deliverables.

Our customer has ELK nodes setup and sanity testing is also completed with respect to log ingestion.  
The requirement is to design and develop a analytics application consisting of some dashboards, reports, pivots, and etc. Obviously it will contain searches and views. We can create these in our local development environment.

How can we export or build a deliverable that can be shipped and deployed at customer site? Is there a defined methodology or procedure to build deliverables that can be deployed or do we have to create them in production nodes?

We were working earlier on Splunk and we used to create apps containing configurations for the searches and views and deliver to the customer in the form of tar files.

Thanks,  
Keerthana

---

<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:** [November 18, 2015, 2:18am UTC](https://discuss.elastic.co/t/delivering-and-deploying-elk-in-production-environment/34390/2 "2015-11-18T02:18:44Z")

</div>

We don't have anything like a packaged app, you can use puppet to automate things though.

---

<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 5, 2017, 11:37pm UTC](https://discuss.elastic.co/t/delivering-and-deploying-elk-in-production-environment/34390/3 "2017-07-05T23:37:49Z")

</div>

Closed on July 5, 2017, 11:37pm UTC