arjun180 commented on issue #1263: URL: https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-959545732
I think the error on the Kafka Connect pod is confusing. It says `Not authorized to perform sts:AssumeRoleWithWebIdentity` - which means the AWS role being used on the Kafka Connect pod is unable to assume the role to carry out the operations. However, we did more two more things. - Logged onto the Kafka Connect pod to check the env variables : ``` AWS_DEFAULT_REGION=<region> AWS_WEB_IDENTITY_TOKEN_FILE=/eks.amazonaws.com/serviceaccount/token AWS_REGION=<region> AWS_ROLE_ARN=arn:aws:iam::xxxxxxxxxxxx:role/my-kafka-sa ``` - Checked the trust relationship for the AWS role above : `"Action": "sts:AssumeRoleWithWebIdentity",` I was wondering what exactly happens when a Kafka Connect pod is spun up - does it not use the AWS credentials within the pod. The error seems to suggest it does not. @scholzj @oscerd -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
