You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel like we only tested the easy path with MSK (at least from our documentation). We didn’t test our the complex part, for example the public access has the most complex config of network, security groups, server setting and ACL rules. It’s not well documented.
The only feature that I am aware but unsupported now is "ssh tunnel", which allow clients outside AWS to connect to MSK through a jumpserver.
Leaving it aside, I am unaware of other lacking features for Kafka source. A difference between MSK and self-hosted Kafka is AWS IAM auth, which has recently been supported.
In general, I don't agree with the idea that "we only tested the easy path with MSK".
quote from @twocode:
The current MSK documentation: https://docs.risingwave.com/docs/current/connector-amazon-msk/
The text was updated successfully, but these errors were encountered: