swaminathanmanish commented on issue #11446: URL: https://github.com/apache/pinot/issues/11446#issuecomment-2089592328
> @swaminathanmanish the above link is not working, can you please share the workaround here? @xiangfu0 had suggested the following in that slack thread to the problem described in this issue - <<Can you check IAM Role Trust Relationship: Make sure that your EKS nodes (or the EKS service itself) can assume the IAM role arn:aws:iam::333870179331:role/pinot. If the trust relationship is not configured correctly, then your nodes won’t be able to assume this role. Also check the Annotations: You’ve annotated your service account with [eks.amazonaws.com/role-arn](http://eks.amazonaws.com/role-arn). Make sure that this service account is actually being used by your pod. You can check this by describing the pod or statefulset (kubectl describe pod <POD_NAME> -n pinot-new) and looking at the Service Account field >> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
