1 Answer
- Newest
- Most votes
- Most comments
1
If you are using IAM authentication and your access policy blocks topic operations like WriteData and ReadData then you get org.apache.kafka.common.errors.TopicAuthorizationException.
Also, permission boundaries and service control policies also block user attempting to connect to the cluster without the required authorization.
If you're using non-IAM authentication, then ensure that you have topic level access control lists (ACLs) that block operations.
You can run below command to list the ACLs that are applied on a topic:
bin/kafka-acls.sh --bootstrap-server $BOOTSTRAP:PORT --command-config adminclient-configs.conf –-list –-topic testtopic
Please refer https://repost.aws/knowledge-center/msk-cluster-connection-issues for more details.
answered 10 months ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- How do I troubleshoot common issues when using my Amazon MSK cluster with SASL/SCRAM authentication?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago