# AWS EKS Not enough hosts to serve request error

**URL:** <https://community.temporal.io/t/aws-eks-not-enough-hosts-to-serve-request-error/16675>\
**Category:** Server Deployment\
**Created:** [March 4, 2025, 7:02pm UTC](https://community.temporal.io/t/aws-eks-not-enough-hosts-to-serve-request-error/16675 "2025-03-04T19:02:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hari.narasimhamurthy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/hari.narasimhamurthy/32/6932_2.png) [@hari.narasimhamurthy](https://community.temporal.io/u/hari.narasimhamurthy)\
**Post date:** [March 4, 2025, 7:02pm UTC](https://community.temporal.io/t/aws-eks-not-enough-hosts-to-serve-request-error/16675/1 "2025-03-04T19:02:37Z")

</div>

We have created Temporal server 1.25.2 initial deployment on AWS EKS. I have run the 1.25.2 auto-setup image to setup the database. However, I have not been able to successfully start up Temporal server. The pods are restarting often, every 4-5 minutes with the error “error”:“cannot resolve Nexus endpoints partition owner: Not enough hosts to serve the request”. I see a bunch of ““lifecycle”:“Stopped”,“cause”:“ShuttingDown””, and eventually, all services are stopped with this message at the end “All services are stopped.”

We use AWS RDS database and in the I see repeated "ERROR: duplicate key value violates unique constraint "namespaces\_pkey" error. I am assuming the both are connected, but don’t have enough information to confirm.

We don’t have any running workflows or namespaces. This is the very first deployment. I have not found answers in my searches in the forum. Any help is greatly appreciated.

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [March 29, 2025, 3:10am UTC](https://community.temporal.io/t/aws-eks-not-enough-hosts-to-serve-request-error/16675/2 "2025-03-29T03:10:55Z")

</div>

Sounds like what was reported in issue [here](https://github.com/temporalio/temporal/issues/5097). Check if same fix mentioned there works for you as well.