-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AccessDeniedException for kafka connector running on kafka connect cluster in kubernetes #151
Comments
GetSchemaVersion does not support resource based policies yet. Can you check this and modify permissions to use "*" resource for schema versions ? https://docs.aws.amazon.com/glue/latest/dg/schema-registry-gs.html
|
Hi! I tried using |
I would suggest reaching out to AWS Support. That way the details like AWSAccountId can be shared. It will also help the service teams debug. |
Hi, @antontreushchenko and @mohitpali we are still facing the same issue. Is this solved or can we have some guide on how to fix this permission issue? |
Hello, also facing this issue. I have granted
but am still seeing |
Related: #68 |
Hi i have a problem that i cant solve. I have a kafka connect cluster, and a connector that uses a glue schema registry. When I run my connector locally everything works fine, but when I do it in a kubernetes cluster I get this error:
Caused by: software.amazon.awssdk.services.glue.model.AccessDeniedException: User: arn:aws:sts::***:assumed-role/aws-***/*** is not authorized to perform: glue:GetSchemaVersion because no identity-based policy allows the glue:GetSchemaVersion action (Service: Glue, Status Code: 400, Request ID: ***, Extended Request ID: null)
Here are the connector settings:
My irsa. Not used in connector. Used to grant access:
In the error the role is not
irsa
butinstance profile
The text was updated successfully, but these errors were encountered: