# Getting an idea for resources required to locally deploy the ELK stack **URL:** \ **Category:** Elasticsearch\ **Created:** [June 10, 2022, 8:12am UTC](https://discuss.elastic.co/t/getting-an-idea-for-resources-required-to-locally-deploy-the-elk-stack/306853 "2022-06-10T08:12:56Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ahamza](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@ahamza](https://discuss.elastic.co/u/ahamza)\ **Post date:** [June 10, 2022, 8:12am UTC](https://discuss.elastic.co/t/getting-an-idea-for-resources-required-to-locally-deploy-the-elk-stack/306853/1 "2022-06-10T08:12:56Z")
Hey, I've recently started reading up on the ELK stack and I want to understand what sort of hardware requirements I would have to do an on-premise deployment. I have about 9.5GB + 3.5GB (~13GB total) of log data coming in from two sources, and the retention policy is for one year. I think we would have the default replication of 1, since the deployment for now is quite small scale. I went through [this post](https://discuss.elastic.co/t/elk-storing-data-and-reading-from-database/64073) and if I am understanding the sort of hardware needed, would this be okay? 30GB of storage for daily logs and queries, and about 16GB of RAM and 6 CPUs for 6 or so nodes? It would be a single server deployment. Is this a very optimistic estimation or can I go more conservative with the hardware requirements? Thanks for your patience. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 8, 2022, 8:13am UTC](https://discuss.elastic.co/t/getting-an-idea-for-resources-required-to-locally-deploy-the-elk-stack/306853/2 "2022-07-08T08:13:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.