Securing Spark Connections
Communication between Spark applications and transactional nodes, masters and workers, and intercommunication between Spark drivers and executors can be encrypted. Encryption must be configured individually on each node in the cluster.
Encryption between the Spark processes and DSE is configured by enabling
client-to-node encryption in
The location of the
Encryption between Spark applications, including between the Spark master and worker nodes, is configured by enabling Spark security in
Encryption between the Spark driver and executors in client applications is configured by enabling Spark security in the application configuration properties, or by default in
spark-daemon-defaults.conf in the Spark configuration directory.
The default location of the Spark configuration files depends on the type of installation:
dse.yamlconfiguration file. The location of this file depends on the type of installation:
Enable mutual authentication and encryption between Spark master and worker nodes in
When DSE authentication is enabled with
dse.yaml, Spark security is enabled regardless of these settings.
Enable mutual authentication by setting
Enable encryption by setting
spark_security_enabled: true spark_security_encryption_enabled: true
To enable encryption, you must also enable mutual authentication.
To encrypt communication between the Spark application and master, DSE inherits the
client to cluster connection encryptionoptions.
The Spark web UI by default uses client-to-cluster encryption settings to enable SSL security in the web interface. To enable SSL security separately from DSE client-to-cluster encryption, change the settings in
custom, then set the keystore settings in
The Spark web UI server automatically discards all cipher algorithms that end with a suffix
MD5. If you manually specify cipher suites for encryption, make sure the specified cipher suites are not ignored by the server and are supported by the web browsers used to access the Spark web UI. For example, two 256 bit cipher suites that are supported by both the server and current web browsers are
AlwaysOn SQLserver can optionally use SSL to encrypt client connections.
Restart the node to recognize the changes.
For each Spark application, set the following client encryption options to true in the
spark-defaults.conffile to enable encryption between the Spark driver and executors.
Enables or disables mutual authentication using a secret key. The default is
Enables or disables SASL encryption between a Spark driver and its executors. The default is
Enables or disables encryption for data stored by drivers directly on disk.
To enable encryption by default for all Spark applications, modify the options in the
spark-defaults.conffile in the Spark configuration directory. To encrypt data stored on the server by default, modify the options in the
Enables or disables encryption for data stored by executors and shuffle services directly on disk.