# Multiple clusters on EKS

**URL:** <https://discuss.elastic.co/t/multiple-clusters-on-eks/381519>\
**Category:** Elasticsearch\
**Created:** [September 2, 2025, 12:44pm UTC](https://discuss.elastic.co/t/multiple-clusters-on-eks/381519 "2025-09-02T12:44:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![searchwithme](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/searchwithme/32/137075_2.png) [@searchwithme](https://discuss.elastic.co/u/searchwithme)\
**Post date:** [September 2, 2025, 12:44pm UTC](https://discuss.elastic.co/t/multiple-clusters-on-eks/381519/1 "2025-09-02T12:44:08Z")

</div>

Does this mean I can spin up multiple elasticsearch clusters on the same EKS?

If that is the case, can I use 1 ERU (64 GB RAM) across 2 clusters if they are under 32 GB RAM each?

> **[Install ECK | Elastic Docs](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install#:~:text=ECK%20relies%20on,allowed%20to%20work)**
>
> Elastic Cloud on Kubernetes (ECK) is a Kubernetes operator that helps you deploy and manage Elastic applications on Kubernetes, including Elasticsearch,...

Also, I do not see any documentation on setting up Elasticsearch clusters (multiple) on same EKS. Please share references

---

<div class="post-metadata">

**Author:** ![Rafa\_Silva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rafa_silva/32/147814_2.png) [@Rafa\_Silva](https://discuss.elastic.co/u/Rafa_Silva)\
**Post date:** [March 1, 2026, 9:36pm UTC](https://discuss.elastic.co/t/multiple-clusters-on-eks/381519/2 "2026-03-01T21:36:15Z")

</div>

Yes you can run multiple Elasticsearch clusters on the same EKS when using ECK. Each Elasticsearch resource created by ECK is an independent cluster, and running several of them in the same Kubernetes cluster is fully supported.  
Regarding ERUs: licensing is calculated based on the total Elasticsearch memory allocated, not per cluster. What matters is the aggregate memory footprint of all Elasticsearch pods under the license.  
So if you deploy:  
• Cluster A → 32 GB  
• Cluster B → 32 GB  
You are consuming 64 GB total.  
If the combined allocated memory stays within 64 GB, you are within a single 64 GB ERU. There is no “per-cluster” ERU split it’s the total memory that counts.  
From an architecture standpoint, just ensure Kubernetes capacity (CPU, RAM, storage) supports the aggregated workload