# ELK stack on a standalone machine?

**URL:** <https://discuss.elastic.co/t/elk-stack-on-a-standalone-machine/366603>\
**Category:** Elasticsearch\
**Created:** [September 16, 2024, 6:44am UTC](https://discuss.elastic.co/t/elk-stack-on-a-standalone-machine/366603 "2024-09-16T06:44:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![karankamat\_21](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@karankamat\_21](https://discuss.elastic.co/u/karankamat_21)\
**Post date:** [September 16, 2024, 6:44am UTC](https://discuss.elastic.co/t/elk-stack-on-a-standalone-machine/366603/1 "2024-09-16T06:44:06Z")

</div>

Hello,  
Is it a good practice to run ELK stack on a standalone machine?

My concerns:

1. The search dataset I'm trying to load is huge
2. Minimum requirement to run Elastic Search, Logstash, Kibana, Elastic Agent

Suggestions are always welcomed!

---

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [September 17, 2024, 4:55am UTC](https://discuss.elastic.co/t/elk-stack-on-a-standalone-machine/366603/2 "2024-09-17T04:55:02Z")

</div>

Hi,

While it is possible to run the Elastic Stack on a standalone machine (depending on the amount of data of course), it is definitely not a good practice. We only do this on our test system reduce the costs but even then it can be a problem. Some of the issues you will see:

- Only one instance can be installed over the package manager, the other 2 need to be installed and updated manually if you follow the recommendations of a 3 node setup
- if you use a single node cluser, you loose the resiliency granted by replica shards
- Failover not possible
- contention for resources from the different services (CPU, Memory, Disk IO, ...)
- ...

> [@karankamat\_21](#):
>
> The search dataset I'm trying to load is huge

The size of the dataset itself is not the issue - once loaded it just takes space on the disk. The question is: How much Ingest and Search traffic does the server need to serve? How important is availability to you?

In the end, you need to test it yourself, if a single, standalone machine is sufficient for you. If you still want to do this, checkout the recommendations for [small clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-small-clusters.html)

Best regards  
Wolfram