Configuring SSL for Impala
Using Cloudera Manager
- Open the Cloudera Manager Admin Console and go to the Impala service.
- Click the Configuration tab.
- Select .
- Select .
- Edit the following SSL properties:
Impala SSL Properties Property Description Enable TLS/SSL for Impala Client Services Encrypt communication between clients (like ODBC, JDBC, and the Impala shell) and the Impala daemon using Transport Layer Security (TLS) (formerly known as Secure Socket Layer (SSL)). SSL/TLS Certificate for Clients Local path to the X509 certificate that will identify the Impala daemon to clients during SSL/TLS connections. This file must be in PEM format. SSL/TLS Private Key for Clients Local path to the private key that matches the certificate specified in the Certificate for Clients. This file must be in PEM format.
- Click Save Changes to commit the changes.
- Restart the Impala service.
For information on configuring SSL communication with the impala-shell interpreter, see Configuring SSL Communication for the Impala Shell.
Using the Command Line
To enable SSL for Impala network communication, add both of the following flags to the impalad startup options:
- --ssl_server_certificate: the full path to the server certificate, on the local filesystem.
- --ssl_private_key: the full path to the server private key, on the local filesystem.
If either of these flags are set, both must be set. In that case, Impala starts listening for Beeswax and HiveServer2 requests on SSL-secured ports only. (The port numbers stay the same; see Ports Used by Impala for details.)
Since Impala uses passphrase-less certificates in PEM format, you can reuse a host's existing Java keystore by converting it to the PEM format. For instructions, see Conversion from Java Keystore to OpenSSL.
Configuring SSL Communication for the Impala Shell
Typically, a client program has corresponding configuration properties in Cloudera Manager to verify that it is connecting to the right server. For example, with SSL enabled for Impala, you use the following options when starting the impala-shell interpreter:
- --ssl: enables SSL for impala-shell.
- --ca_cert: the local pathname pointing to the third-party CA certificate, or to a copy of the server certificate for self-signed server certificates.
If --ca_cert is not set, impala-shell enables SSL, but does not validate the server certificate. This is useful for connecting to a known-good Impala that is only running over SSL, when a copy of the certificate is not available (such as when debugging customer installations).
Using TLS/SSL with Business Intelligence Tools
You can use Kerberos authentication, TLS/SSL encryption, or both to secure connections from JDBC and ODBC applications to Impala. See Configuring Impala to Work with JDBC and Configuring Impala to Work with ODBC for details.
Currently, the Hive JDBC driver does not support connections that use both Kerberos authentication and SSL encryption. To use both of these security features with Impala through a JDBC application, use the Cloudera JDBC Connector as the JDBC driver.