Connecting Sisense to Amazon DocumentDB via generic JDBC [Linux] | Knowledge Base Docs

Ihor Yokhym · 2026-05-26T06:58:19.146403Z

Introduction: Learn how to successfully connect Sisense to Amazon DocumentDB using a generic JDBC connection. This guide applies to Sisense Linux editions (both Cloud and On-Premises deployment models) and resolves common TLS-related connection reset errors.Step-by-Step Guide: Step 1: Whitelist the Sisense InstanceBefore modifying any configurations in Sisense, verify that your Sisense instance IP address or network range is properly whitelisted in your AWS DocumentDB cluster's security groups. The default connection port is 27017.Step 2: Download the driverGet the JDBC Driver for Amazon DocumentDB from the Amazon website and Github:AWS DocumentDB: DocumentationAWS DocumentDB: Driver GithubStep 3: Register the connector in Sisense2.1 Go to Admin > Server & Hardware > System Management > Configuration.2.2 Scroll to the bottom and click Manage Connectors.2.3 In the left pane, click +JDBC Connector and fill in:Connector ID: [YOUR_NAME]Display Name: [YOUR_NAME]Class Name: software.amazon.documentdb.jdbc.DocumentDbDriverUpload JAR File: upload jar fileClick Create.Step 4: Use the Generic JDBC Connection StringBecause of architectural differences, connecting via the native Sisense MongoDB connector can result in errors. Instead, connect using the generic AWS DocumentDB JDBC driver syntax.JDBC Connection String Templatejdbc:documentdb://<hostname>:<port>/<database-name>?<options>Step 5: Configure TLS Settings and Resolve Socket ExceptionsAccording to official AWS DocumentDB JDBC Driver documentation, the driver’s default behavior is tls=true.If your DocumentDB configuration expects plain text, a protocol mismatch occurs: the JDBC driver attempts an encrypted SSL handshake with a database node expecting unencrypted packets. DocumentDB will abruptly drop the network socket, resulting in the following error:java.net.SocketException: Connection resetTo fix this, modify your connection string based on your database environment:For Non-TLS Environments: Explicitly turn off TLS encryption by adding tls=false and completely removing the tlsAllowInvalidHostnames flag.For TLS Environments: Ensure both tls=true and tlsAllowInvalidHostnames=true are active.Code Type: JDBC Connection String Example (TLS Disabled)jdbc:documentdb://<a target="_blank" rel="noopener noreferrer nofollow" href="http://my-cluster.cluster-xyz.us-east-1.docdb.amazonaws.com:27017/my_database?tls=false"><u>my-cluster.cluster-xyz.us-east-1.docdb.amazonaws.com:27017/my_database?tls=false</u></a>[Screenshot: Generic JDBC connection setup window in the Sisense Data tab] Description: The image above illustrates where to input the customized DocumentDB JDBC connection string and credential details within the Sisense Data Connector UI.Conclusion: Successfully connecting Sisense to Amazon DocumentDB requires leveraging the generic JDBC driver framework rather than the native MongoDB connector. The most common pitfall is a TLS mismatch; explicitly declaring tls=false in your connection parameters will bypass the java.net.SocketException when working with unencrypted database nodes.References/Related Content Sisense Documentation: Deploy Custom JDBC connectorAWS DocumentDB: DocumentationAWS DocumentDB: Driver Github

MoreDiscussions

Connecting Sisense to Amazon DocumentDB via generic JDBC [Linux] | Knowledge Base Docs | Sisense Community