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.
- Ensure that you have specified the correct AWS region in your configuration. The region must match where your Amazon MSK cluster is located.
Invalid role ARN
Invalid role ARN. Please provide a valid role ARN.
- Ensure that you have specified the correct role ARN in your configuration.
- Ensure that the role has the required permissions to perform operations in your Amazon MSK cluster.
Invalid bootstrap server
Invalid bootstrap server details. Please provide a valid bootstrap server.
- Ensure that you have specified the correct bootstrap server in your configuration.
- Ensure that the IAM role has the required permissions to connect to Amazon MSK.
- If you're also using private network link, ensure that private network connectivity between Atlan and Amazon MSK is properly configured.
Internal server error
Internal server error. Please contact Atlan admin.
- There may be a connectivity issue between Atlan and your Amazon MSK cluster. Reach out to Atlan support.
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.