AWS MSK Connect - Snowflake Plugin (Secrets)
Hi All, I have an MSK Cluster set with 1 broker per 3 AZ's on m5.large and looking to switch our ECS Containers I have running Kafka Connect to using MSK Kafka Connect.
I have a working ECS configuration that runs Kafka Connect with a Snowflake Connector. This user's private key, username, and password per the Snowflake Documentation. When I take the same working configuration and run it with MSK - I get the following error message:
2022-01-13T07:52:08.000-06:00 [Worker-0576cf5f4676783e1] [SF_KAFKA_CONNECTOR] Error Code: 0018 2022-01-13T07:52:08.000-06:00 [Worker-0576cf5f4676783e1] [SF_KAFKA_CONNECTOR] Detail: failed to decrypt private key. Please verify input private key and passphrase.
Since my password contains a special character e.g. ! and the private key contains / etc. I am assuming this might need to be escaped?
Appreciate helps.
Thanks Wayne
Hi there, does it work if you try with quotes or unencrypted private key without snowflake.private.key.passphrase as mentioned here https://docs.snowflake.com/en/user-guide/kafka-connector-install.html?
If it doesn't the best way forward would be to open a Support case so that internal logs can be looked at and proper guidance will be given. Without checking the internal logs it is hard to proceed or draw any conclusions, sorry.
Relevant questions
MSK Connect - Exposing Connector Specific Metrics
asked 5 months agoHow to connect Glue to MSK with IAM authentication?
asked 7 months agoKafka connect Regex Transform not working in the MSK Connect
asked 5 months agoAWS MSK IAM Authentication with MSK Connect
asked 5 months agoLambda MSK trigger not working
asked 2 years agoAWS MSK Connect - Snowflake Plugin (Secrets)
Accepted Answerasked 6 months agoUsing MSK as trigger to a Lambda with SASL/SCRAM Authentication
asked a month agoCan MSK Connect be made rack-aware?
asked 5 months agoConnect Amazon MSK cluster to on-premises web server?
Accepted Answerasked 3 years agoMSK connect connector deployment
asked 12 days ago
Thanks - I did raise an AWS support ticket after raising here and the issue was related to a special character in my Password for the secret that needed to be escaped. I appreciate your input.