I got this working late last week. I did the shotgun approach with all the
values in both the distributor and connector.json and once it worked, I
started to remove things to see when it stop working.
On Sun, Apr 18, 2021 at 10:00 PM Ning Zhang wrote:
> if the source kafka cluster is SSL-enable
if the source kafka cluster is SSL-enabled, then the consumer of mm2 should be
configured to read from SSL-enabled cluster
if the target kafka cluster is SSL-enabled, then the producer of mm2 should be
configured to write to SSL-enabled cluster.
On 2021/04/16 03:23:21, Men Lim wrote:
> well th
well the 405 is due to a syntax error in the connector.json. after fixing
that, passing the -k switch, it started. but when looking at the
connect.log, mm2 is only talking in plaintext rather than SSL. After a
while it timed out because the port 9094 is ssl while mm2 is trying to use
plaintext.
I read thru the security_ssl page when I started this, it doesn't apply
much to me because I'm running this in AWS MSK, where I can't access the
broker. so my hands are tied there when it come to certificate.
however, this morning, I decided to work on creating a self sign cert for
the CURL comman
assume your target / destination kafka cluster is SSL enabled. If your MM2
wants to write to such cluster, you may have the following config in your MM2:
https://github.com/ning2008wisc/minikube-mm2-demo/blob/master/kafka-mm/values.yaml#L79-L80
on the broker (even client) side, you may refer to:
Hi Ning,
thanks for the response. This self sign cert stays on the ec2 instance,
specifically for the curl command and I don't have to share it with the
brokers correct?
thanks,
On Fri, Apr 9, 2021 at 7:55 AM Ning Zhang wrote:
> Hi Men,
>
> I used to deploy MM2 on EC2 with SSL and IIRC, pro
Hi Men,
I used to deploy MM2 on EC2 with SSL and IIRC, probably give a try of
self-signing certs and key for testing purpose:
https://linuxize.com/post/creating-a-self-signed-ssl-certificate/
On 2021/04/09 03:14:30, Men Lim wrote:
> Hi Ryanne,
>
> thanks for the reply. My kafka clusters are
Hi Ryanne,
thanks for the reply. My kafka clusters are on AWS, their serverless
platform, MSK. I'm stuck with using the default java cacerts unless I use
their AWS PCA which is pretty pricey.
I ran the CURL command yesterday with the -v and --tlsv1.2 flag and got the
following verbose message:
Yes it's possible. The most common issue in my experience is the location
of the trust store and key store being different or absent on some hosts.
You need to make sure that these locations are consistent across all hosts
in your Connect cluster, or use a ConfigProvider to provide the location
dyn
Hello. I was wondering if someone can help answer my question. I'm trying
to run MirrorMaker 2 in distributed mode using SSL. I have the distributor
running in SSL but when I can't get the curl REST api to do so. I saw that
kif-208 fixed this but I can't seem to implement it.
in my mm2-dist.pro
10 matches
Mail list logo
