# Hardware requirements for elasticssearch

**URL:** <https://discuss.elastic.co/t/hardware-requirements-for-elasticssearch/359059>\
**Category:** Elasticsearch\
**Created:** [May 8, 2024, 12:21pm UTC](https://discuss.elastic.co/t/hardware-requirements-for-elasticssearch/359059 "2024-05-08T12:21:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Muhammad\_Shahyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muhammad_shahyan/32/134309_2.png) [@Muhammad\_Shahyan](https://discuss.elastic.co/u/Muhammad_Shahyan)\
**Post date:** [May 8, 2024, 12:21pm UTC](https://discuss.elastic.co/t/hardware-requirements-for-elasticssearch/359059/1 "2024-05-08T12:21:14Z")

</div>

what are the minimum hardware requirements for high availability elk cluster.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 8, 2024, 12:27pm UTC](https://discuss.elastic.co/t/hardware-requirements-for-elasticssearch/359059/2 "2024-05-08T12:27:34Z")

</div>

You need [a minimum of 3 nodes](https://www.elastic.co/guide/en/elasticsearch/reference/8.13/high-availability-cluster-small-clusters.html). The size and configuration will depend on your use case and expected data volumes.

---

<div class="post-metadata">

**Author:** ![riahc3](https://avatars.discourse-cdn.com/v4/letter/r/d6d6ee/32.png) [@riahc3](https://discuss.elastic.co/u/riahc3)\
**Post date:** [May 8, 2024, 1:02pm UTC](https://discuss.elastic.co/t/hardware-requirements-for-elasticssearch/359059/3 "2024-05-08T13:02:42Z")

</div>

At least 32GB RAM and 4 cores, per node. Forget about anything else in 2024.

---

<div class="post-metadata">

**Author:** ![Muhammad\_Shahyan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muhammad_shahyan/32/134309_2.png) [@Muhammad\_Shahyan](https://discuss.elastic.co/u/Muhammad_Shahyan)\
**Post date:** [May 9, 2024, 6:19am UTC](https://discuss.elastic.co/t/hardware-requirements-for-elasticssearch/359059/4 "2024-05-09T06:19:46Z")

</div>

i am going to setup ELK for an enterprise application  
daily logs: 2GB  
retention period: 6 months

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 9, 2024, 6:51am UTC](https://discuss.elastic.co/t/hardware-requirements-for-elasticssearch/359059/5 "2024-05-09T06:51:28Z")

</div>

Lets assume your data takes up the same amount of space on disk as the raw size. This ratio will depend on your mappings , levels of enrichment and index settings. You can find a discussion around this [in this old blog post](https://www.elastic.co/blog/sizing-hot-warm-architectures-for-logging-and-metrics-in-the-elasticsearch-service-on-elastic-cloud). As you want high availability you will need a replica shard, which means you will add 4GB of indexed data per day. With 6 months retention period this results in approximately 700GB - 750GB of indexed data in the cluster. With 3 nodes that is 250GB per node, which is not a lot for Elasticsearch. I would expect 8GB or 16GB of RAM to be sufficient for this together with 2-4 CPU cores.