Pasting my reply from the MapR community thread: So, I have found a temporary workaround for this. Heres what I did: For the client, I found out the password of /opt/mapr/conf/ssl_trustore via ssl-client.xml For both Datadog and Amazon S3, I found out the certs chain that they were using (i could do this easily in firefox). I then dowloaded these certs and added them to the mapr trustore i.e. /opt/mapr/conf/ssl_trustore e.g: keytool -import -alias s3 -file s3.cer -keystore /opt/mapr/conf/ssl_truststore -storepass <map_client_trustore_pass>) After doing this, the ssl handshake error that i was getting was resolved. I say this is a temporary fix because, lets say in future Amazon S3 change their root certificate issuer or they change their ssl certificate, then we ll need to do these steps again. Also, it is cumbersome to add these certs for EACH AND EVERY website that we are trying to access. So, I think the issue is that once we add mapr libs to flink classpath, MapR's keystore/truststore get used and that is what is causing the problem. Is this the expected behaviour? Would this be a bug on Flink side or mapr side or (worse) even on the base apache http client used by aws and datadog?
-- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/MapR-libraries-shading-issue-tp13988p14005.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
