Encryption: Data in Transit Client to Node¶
If you are working on a new cluster skip steps 1 & 2.
/etc/scylla/scylla.yamlto modify the
Available options are:
enabled (default - false)
certificate - A PEM format certificate, either self-signed, or provided by a certificate authority (CA).
keyfile - The corresponding PEM format key for the certificate
truststore - Optional path to a PEM format certificate store holding the trusted CA certificates. If not provided, Scylla will attempt to use the system truststore to authenticate certificates.
If using a self-signed certificate, the “truststore” parameter need to be set to a PEM format container with the private authority.
client_encryption_options: enabled: true certificate: /etc/scylla/db.crt keyfile: /etc/scylla/db.key truststore: <optional path to PEM encoded trust store>
Note: parameters (enabled, certificate, keyfile) must be indented 4 spaces from the header (
To validate that encrypted connection to the node is enabled, check the logs using
journalctl _COMM=scylla. You should see the following
message: storage_service - Enabling encrypted CQL connections between client and node.
Client side validation steps
6. In order for cqlsh to work in client to node encryption SSL mode, you need to generate cqlshrc file:
Example: [authentication] username = myusername password = mypassword [cql] ; Substitute for the version of Cassandra you are connecting to. version = 3.3.1 [connection] hostname = 127.0.0.1 port = 9042 factory = cqlshlib.ssl.ssl_transport_factory [ssl] certfile = /etc/scylla/db.crt ; Note: If validate = true then the certificate name must match the machine's hostname validate = true ; If using client authentication (require_client_auth = true in cassandra.yaml) you'll also need to point to your userkey and usercert. ; SSL client authentication is only supported via cqlsh on C* 2.1 and greater. ; This is disabled by default on all Instaclustr-managed clusters. userkey = /etc/scylla/db.key usercert = /etc/scylla/db.crt
Copy the following created files (db.key, db.crt, cadb.key, cadb.pem) to your client/s, from which you run cassandra-stress
To run cassandra-stress with SSL, each client running cassandra-stress needs to have a java key store file (.jks). This file can be made using the
cadb.pemfile and must be present on every client that runs cassandra-stress.
Generate the Java keystore for the node certs
openssl pkcs12 -export -out keystore.p12 -inkey /home/scylla/server_files/db.key -in /home/scylla/server_files/db.crt keytool -importkeystore -destkeystore keystore.jks -srcstoretype PKCS12 -srckeystore keystore.p12
Generate the Java truststore for the trust provider
openssl pkcs12 -export -out truststore.p12 -inkey /home/scylla/server_files/cadb.key -in /home/scylla/server_files/cadb.pem keytool -importkeystore -destkeystore truststore.jks -srcstoretype PKCS12 -srckeystore truststore.p12
Download and install the Java security providers:
Note: make sure you have the latest version from this location.
Run Cassandra stress with the parameters below:
cassandra-stress write n=1000000 cl=ONE -node 10.240.0.48 -transport keystore=keystore.jks keystore-password=[password] truststore=truststore.jks truststore-password=[password] -mode native cql3 -pop -rate threads=50
Note: when running cassandra-stress you may encounter an exception, if some nodes are still not in client to node SSL encrypted mode, yet the cassandra-stress will continue to run and connect only to the nodes it can.
Note2: This procedure works as-is for v1.7 or higher. When using Scylla v1.6.x you will need a dummy keystore in the default (conf/.keystore) location with password “cassandra” to run. The contents is irrelevant. Also, it only pertains to cassandra-stress. It has no impact/relation to using the normal java driver connection or cqlsh.
Enable encryption on the client application.