Connect to SingleStoreDB Cloud using TLS/SSL
On this page
singlestore_ file, which SQL clients can use to connect to SingleStoreDB Cloud, will be updated as of October 20, 2023.
If your SQL client uses the
singlestore_ file and the
--ssl-mode=VERIFY_ flag to connect, and your SQL client can no longer connect to SingleStoreDB Cloud, please download and use the latest
To ensure a secure connection to SingleStoreDB Cloud, SQL clients must be properly configured to both require a secure connection and to verify the supplied server certificate.
These instructions describe how to configure the MySQL command-line client to connect to SingleStoreDB Cloud with a secure connection.
singlestore_certificate file and save it to your MySQL client machine.
When connecting to SingleStoreDB Cloud, be sure to include:
The host shown under the Endpoint from your workspace in the Cloud Portal.
--ssl-caoption, including the path to the
bundle. pem This can be done via command-line option, as in
--ssl-ca=/path/singlestore_, or by setting the appropriate option in the configuration files for the MySQL command-line client.
bundle. pem Include the
--ssl-mode=REQUIREDwhen using older versions of the MySQL client, even when the
--ssl-caoption is specified.
--ssl-mode=VERIFY_option to verify the certificate.
Test the connection to SingleStoreDB Cloud.
The MySQL client will abort with an error if a secure connection cannot be established. While this is most likely due to a misconfiguration, it can also be due to a would-be attacker manipulating the secure connection to SingleStoreDB Cloud.mysql -u admin -p -h <endpoint-host> -P 3306 \--default-auth=mysql_native_password \--ssl-ca=./singlestore_bundle.pem \--ssl-mode=VERIFY_CA
Verify that a secure connection has been established to SingleStoreDB Cloud via the
statuscommand.mysql -u admin -p -h <endpoint-host> -P 3306 \--default-auth=mysql_native_password \--ssl-ca=./singlestore_bundle.pem -e 'status' \--ssl-mode=VERIFY_CA
mysql Ver 14.14 Distrib 5.6.19, for osx10.9 (x86_64) using EditLine wrapper Connection id: 13 Current database: Current user: firstname.lastname@example.org SSL: Cipher in use is AES256-SHA Current pager: stdout Using outfile: '' Using delimiter: ; Server version: 5.5.8 MemSQL source distribution (compatible; MySQL Enterprise & MySQL Commercial) Protocol version: 10 Connection: xxx.xxx.xxx.xxx via TCP/IP Server characterset: utf8 Db characterset: utf8 Client characterset: utf8 Conn. characterset: utf8 TCP port: 3306
Last modified: October 18, 2023