Troubleshooting Amazon MSK connectivity

What are the known limitations of the Amazon MSK connector?

Following are the known limitations of the Amazon MSK connector:

  • Atlan currently does not support upstream or downstream lineage for Amazon MSK assets.
  • Atlan currently only supports asset-level lineage between topics and consumer groups. Column-level lineage is currently not supported.
  • SASL/SCRAM and TLS authentication methods are currently not supported. Atlan currently only supports IAM role authentication.
  • Serverless deployment for Amazon MSK is currently not supported.
  • Atlan currently only supports Apache Kafka version 2.7.1 or higher for Amazon MSK.

How to debug test authentication and preflight check errors?

Invalid region

Invalid region. Please provide a valid region.

Invalid role ARN

Invalid role ARN. Please provide a valid role ARN.

Invalid bootstrap server

Invalid bootstrap server details. Please provide a valid bootstrap server.

Internal server error

Internal server error. Please contact Atlan admin.

Timeout exception

Caused by: org.apache.kafka.common.errors.TimeoutException: Error listing groups on <broker-address>:<broker-port> : Timed out waiting to send the call.

  • Ensure that the port is authorized in the inbound rule of the security group for your Amazon MSK cluster.
  • If you're also using private network link, ensure that private network connectivity between Atlan and Amazon MSK is properly configured.
  • Ensure that both your Amazon MSK cluster and Atlan tenant are hosted in the same AWS region.

Related articles

Was this article helpful?
0 out of 0 found this helpful