For one of our clients I need to connect to a database on Amazon Redshift. The IT Vendor who made the system is telling us to use SSL mode Required ( https://docs.aws.amazon.com/redshift/latest/mgmt/connecting-ssl-support.html#connect-using-ssl ). Using this setting in the ODBC connector from Amazon itself works fine but the CData connector only gives a true false dropdown. I've checked if this perhaps was one of those fields where you can overrule the drop down with manual input but that's not the case for this one. Is there any way to get this working in the CData connector or would our only option for now by create DSN and then use the ADO ODBC option the the ODX to connect with the DSN.
Solved
Amazon Redshift Connector SSL mode drop down missing options
+1Best answer by Christian Hauggaard
Hi
Can you please try to recreate the data source in the ODX with the same settings but a different name (i.e. not Recruitee)? Then try to execute the synchronize task followed by the transfer task
+5Hi
Have you tried using SSL mode to “Yes” rather than “required”? If so, what is the result of test connection?
Otherwise, like you mentioned you can use the below provider
+1Hi Christiaan,
Yes I've tried both but then I get the standard CData error message. It seems it expects one of the options as documented by Amazon ( disable, allow, prefer, require, verify-ca or verify-full ) as SSL mode and not true or false.
I'll use the ADO Odbc for now as the Amazon Odbc is already up and running.
+1The connection is now working and I can read and select the tables
but upon execution it now fails stating that it cannot find a path
Hi Hugo
Verify that the user account running ODX Service ( and TX ) has read/ write permissions on the folder mentioned in the error.
1 person likes this
+1Hi Syed,
The folder doesn't exist so I gave the user (local TXService) full control over the level in the path I could find but still the exact same error message.
+5Hi
Can you please try to recreate the data source in the ODX with the same settings but a different name (i.e. not Recruitee)? Then try to execute the synchronize task followed by the transfer task
+1Hi Christiaan, I've added a new connection with a different name so the DSN name and the datasource name are no longer the same and that seems to do it. Thanks!
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
