Connect Tablyne to Cassandra and ScyllaDB

Connect to Cassandra, ScyllaDB, Amazon Keyspaces or DataStax Astra with TLS, SSH tunnels, SigV4 or a Secure Connect Bundle.

Tablyne has one connection form for four providers. You pick the provider first, and the form shows only what that provider needs.

For self-managed Cassandra and ScyllaDB, enter one to sixteen hosts, separated by commas and without a port. The driver discovers the rest of the cluster. Then set the port, the user and password, an initial keyspace and the local datacenter. You can turn on TLS. Without a CA certificate, Tablyne checks the server against public roots and the host name. With a CA, it checks the certificate chain against that CA. The form can also read a cqlsh command and fill in the fields, and it lists the options it ignored. After connecting, Tablyne checks whether the server is really ScyllaDB and offers to switch the provider if you chose the wrong one.

For ScyllaDB Cloud, the form explains the host format, port 9142 with TLS, the cluster CA and the datacenter name.

For Amazon Keyspaces, enter the region. Leave the host empty to use the region’s public endpoint on port 9142, or enter a host for a VPC endpoint. You can sign in with SigV4 and an AWS profile, or with a service-specific credential. TLS is always on.

For DataStax Astra, choose the Secure Connect Bundle, the ZIP from the Astra dashboard, and enter the Astra token. Tablyne reads the bundle each time you connect and saves only its path.

SSH tunnels work for Cassandra and ScyllaDB. Each discovered node gets a local port through the same SSH connection, up to 64 nodes, and only nodes on the contact points’ network are accepted unless you allow others. Keyspaces and Astra do not use SSH.

You can mark a connection as production or read-only. Read-only is a safeguard in Tablyne that refuses writes and structure changes. For enforcement on the server, use a role without MODIFY permission.