# Elasticsearch installation and configuration

**URL:** <https://discuss.elastic.co/t/elasticsearch-installation-and-configuration/81510>\
**Category:** Elasticsearch\
**Created:** [April 6, 2017, 4:33pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-and-configuration/81510 "2017-04-06T16:33:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![john99](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@john99](https://discuss.elastic.co/u/john99)\
**Post date:** [April 6, 2017, 4:33pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-and-configuration/81510/1 "2017-04-06T16:33:43Z")

</div>

Hello Experts,

I am Planning to install Elasticsearch in my environment PROD,

can you suggest me with Pre-Req? Also do we need license version ?

How to make it has how automation for installation /upgrade?

---

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [April 6, 2017, 5:29pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-and-configuration/81510/2 "2017-04-06T17:29:38Z")

</div>

Hello,

You don't need any licence for elasticsearch "alone".

About automation, there are a ton of good tutorial to work with Chef, Ansible etc... Search on elastic Github:

> **[elastic/ansible-elasticsearch](https://github.com/elastic/ansible-elasticsearch)**
>
> ansible-elasticsearch - Ansible playbook for Elasticsearch

  

> **[elastic/cookbook-elasticsearch](https://github.com/elastic/cookbook-elasticsearch)**
>
> cookbook-elasticsearch - Chef cookbook for Elasticsearch

---

<div class="post-metadata">

**Author:** ![john99](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@john99](https://discuss.elastic.co/u/john99)\
**Post date:** [April 6, 2017, 5:34pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-and-configuration/81510/3 "2017-04-06T17:34:33Z")

</div>

Thanks for you response, do you recommend to have X-pack for it even if it is alone ELASTIC SEARCH setup? we are setting up 5.3.0, what your suggestions for me?

---

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [April 7, 2017, 9:16am UTC](https://discuss.elastic.co/t/elasticsearch-installation-and-configuration/81510/4 "2017-04-07T09:16:22Z")

</div>

It depends what you need, read documentation and product presentation, you should understand what it's good for you or not.

---

<div class="post-metadata">

**Author:** ![StivOstenberg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stivostenberg/32/4681_2.png) [@StivOstenberg](https://discuss.elastic.co/u/StivOstenberg)\
**Post date:** [April 25, 2017, 6:01pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-and-configuration/81510/5 "2017-04-25T18:01:29Z")

</div>

Been struggling with the Ansible Playbook. Have run into problems with JAVA\_HOME (seems to be using 1.7 at install time, had to fix that) and quite a few errors related to permissions on the host. I overcame these by sprinkling "become: true" wherever I ran into permission problems. Will try an end to end run again, to check, but not impressed by the ease of use of the Playbook, though it looks quite simple.  
I am not installing on localhost, running it against an AWS instance. My goal is a functioning ELK stack, but it is proving quite difficult.

---

<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:** [May 23, 2017, 6:02pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-and-configuration/81510/6 "2017-05-23T18:02:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
