# Elasticsearch stack requirement

**URL:** <https://discuss.elastic.co/t/elasticsearch-stack-requirement/168245>\
**Category:** Elasticsearch\
**Created:** [February 13, 2019, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-stack-requirement/168245 "2019-02-13T14:51:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![devsecops-reetika](https://avatars.discourse-cdn.com/v4/letter/d/c0e974/32.png) [@devsecops-reetika](https://discuss.elastic.co/u/devsecops-reetika)\
**Post date:** [February 13, 2019, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-stack-requirement/168245/1 "2019-02-13T14:51:55Z")

</div>

Hi everyone,

I have currently running ELK stack on aws cloud. Currently I am facing performance issue with same and highwater mark.

I want to redeploy cluster , currently we have daily 400 GB data generated and we have to keep near to 30 days of data on Elasticsearch.

Please suggest how many master and data nodes and shards and replica I should consider? As I am new to ELk, watching watches help me understand basics but for production how should I proceed and gather information, to deploy cluster from scratch.

---

<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:** [March 13, 2019, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-stack-requirement/168245/2 "2019-03-13T14:51:56Z")

</div>

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