# Instructions ot upgrade the ELK stack

**URL:** <https://discuss.elastic.co/t/instructions-ot-upgrade-the-elk-stack/41201>\
**Category:** Elasticsearch\
**Created:** [February 8, 2016, 4:05pm UTC](https://discuss.elastic.co/t/instructions-ot-upgrade-the-elk-stack/41201 "2016-02-08T16:05:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![yahoo](https://avatars.discourse-cdn.com/v4/letter/y/898d66/32.png) [@yahoo](https://discuss.elastic.co/u/yahoo)\
**Post date:** [February 8, 2016, 4:05pm UTC](https://discuss.elastic.co/t/instructions-ot-upgrade-the-elk-stack/41201/1 "2016-02-08T16:05:21Z")

</div>

I am trying to upgrade ELK stack (L 2.1.2, E 2.1.2, K 4.3.1) to (L 2.2.0, E 2.2.0, K 4.4.0) in a windows 10 environment.

I assembled the following instructions.  
Please, correct, suggest, advice, expand, or critique.

## Upgrading the ELK stack

Assuming a direct download upgrade. No roll over.

**Upgrade Logstash**  
Follow the instructions in  
[https://www.elastic.co/guide/en/logstash/current/\_upgrading\_using\_a\_direct\_download.html](https://www.elastic.co/guide/en/logstash/current/_upgrading_using_a_direct_download.html)  
However, keep the config file outside the logstash directory and point to it via  
`-f <configuration-file>`

**Upgrade Elasticsearch**  
Snapshots will keep the data  
[https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html)  
But will they keep the:  
1- templates

However, keep the config file outside the elasticsearch directory and point to it via  
`-Des.path.conf= <path to directory with the elasticsearch yml file>`

**Upgrade Kibana**  
How do we keep the  
1- dashboards, and visualizations (export/import ?),  
2- indices and field type specializations (such as strings specialized as urls),  
3- advanced settings (time zone, date format, meta fields,... ),  
4- data,  
5- configuration (yml),  
6- plugins.

**Script?**  
Finally, is there a script that will enable such upgrades?  
Elastic is active providing bug fixes and upgrades frequently.

---

<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:** [February 10, 2016, 1:44am UTC](https://discuss.elastic.co/t/instructions-ot-upgrade-the-elk-stack/41201/2 "2016-02-10T01:44:56Z")

</div>

Why not use packages?

Also, as long as you don't delete the data in ES then the templates will exist after the upgrade.  
For KB, most of that is stored in the `.kibana` index in ES, so see my previous comment.

---

<div class="post-metadata">

**Author:** ![yahoo](https://avatars.discourse-cdn.com/v4/letter/y/898d66/32.png) [@yahoo](https://discuss.elastic.co/u/yahoo)\
**Post date:** [February 10, 2016, 11:21pm UTC](https://discuss.elastic.co/t/instructions-ot-upgrade-the-elk-stack/41201/3 "2016-02-10T23:21:20Z")

</div>

What do you mean by "packages" ?

---

<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:** [February 11, 2016, 2:45am UTC](https://discuss.elastic.co/t/instructions-ot-upgrade-the-elk-stack/41201/4 "2016-02-11T02:45:28Z")

</div>

[https://www.elastic.co/guide/en/elasticsearch/reference/2.2/setup-repositories.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.2/setup-repositories.html)

---

<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:17pm UTC](https://discuss.elastic.co/t/instructions-ot-upgrade-the-elk-stack/41201/5 "2017-07-05T23:17:23Z")

</div>