AWS MSK Connect

Hello,

Yes, MSK Connect when associated with an MSK cluster it runs in the same VPC as the cluster.

Moreover, as for why MSK Connect is not establishing a connection with the source database even though both sit in the same VPC you will have to refer the CloudWatch logs for it. The logs must state a reason for failure of connection or the error that was encountered, if any.

• Logging for MSK Connect: https://docs.aws.amazon.com/msk/latest/developerguide/msk-connect-logging.html

The below AWS documentations guide how to setup a Debezium MySQL connector plugin with a MySQL-compatible database that runs in a VPC. You can take this as a reference and consult your configuration.

• Debezium source connector with configuration provider: https://docs.aws.amazon.com/msk/latest/developerguide/mkc-debeziumsource-connector-example.html
• https://aws.amazon.com/blogs/aws/introducing-amazon-msk-connect-stream-data-to-and-from-your-apache-kafka-clusters-using-managed-connectors/

For a deeper analysis into the issue and gain more insights tailored to your architecture and use case here, I request you to please reach out to AWS Premium Support team via a support case. The team is better equipped to handle such requests and should be able to guide you better, as per your cluster's and connector's configuration.

Hope the above information and documentation helps!