#eks-pod-identity

KEDA kept our SQS workers at zero replicas while the queue filled: operator identity and AWS auth

A new KEDA ScaledObject was meant to scale workers from zero on SQS queue depth. The queue reached 40,000 messages and the Deployment stayed at zero. The KEDA operator, not the worker, needed permission to read the queue. How we found it in the ScaledObject status and fixed it with EKS Pod Identity.