- Newest
- Most votes
- Most comments
You can use most connectors with MSK Connect, as long as they do not need to actively listen themselves. In the case of the MQ connector, this should work for you. The issue is most likely connected to the networking setup and the ability of the connector to find your MQ instances. Since networking can be very dependent on your environment it is difficult to be specific, and you may be able to get more details by sharing the logs and specifics with the AWS support team. However, some common challenges include name resolution, and making sure your host names are resolvable from the connector's perspective.
Thank you for your response. I don't believe it is a networking issue as i tried the reachability analyzer from the VPC end point where the IBM MQ is installed and the AWS Kafka Connect ENI and it is reachable. I also enabled the cloudwatch log monitoring and don't see any errors in the logs. So i am not sure if there is an issue with the connector configuration and if the properties specified are correct as i don't see I also don't see any message saying connectivity is established.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago