Configuring TLS/SSL for Impala
Impala supports TLS/SSL network encryption, between Impala and client programs, and between the Impala-related daemons running on different nodes in the cluster. This feature is important when you also use other features such as Kerberos authentication or Sentry authorization, where credentials are being transmitted back and forth.
Using the Command Line
To enable SSL for when client applications connect to Impala, 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.
In Impala 2.3 and higher, Impala can also use SSL for its own internal communication between the
To enable this additional SSL encryption, set the
--ssl_private_key flags in the startup options for
impalad, catalogd, and statestored,
and also add the
--ssl_client_ca_certificate flag for all three of those daemons.
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 using the
openssl toolkit to convert it to the PEM format.
Configuring TLS/SSL Communication for the Impala Shell
With SSL enabled for Impala, use the following options when starting the impala-shell interpreter:
--ssl: enables TLS/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.
--ca_cert is not set, impala-shell enables TLS/SSL, but does not validate the server
certificate. This is useful for connecting to a known-good Impala that is only running over TLS/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.
Prior to Impala 2.5, the Hive JDBC driver did not support connections that use both Kerberos authentication and SSL encryption. If your cluster is running an older release that has this restriction, use an alternative JDBC driver that supports both of these security features.
Specifying TLS/SSL Minimum Allowed Version and Ciphers
Depending on your cluster configuration and the security practices in your organization, you might need to restrict the allowed versions of TLS/SSL used by Impala. Older TLS/SSL versions might have vulnerabilities or lack certain features. In Impala 2.10, you can use startup options for the impalad, catalogd, and statestored daemons to specify a minimum allowed version of TLS/SSL.
Specify one of the following values for the
tlsv1: Allow any TLS version of 1.0 or higher. This setting is the default when TLS/SSL is enabled.
tlsv1.1: Allow any TLS version of 1.1 or higher.
tlsv1.2: Allow any TLS version of 1.2 or higher.
Along with specifying the version, you can also specify the allowed set of TLS ciphers
by using the
--ssl_cipher_list configuration setting. The argument to
this option is a list of keywords, separated by colons, commas, or spaces, and
optionally including other notation. For example:
By default, the cipher list is empty, and Impala uses the default cipher list for the underlying platform. See the output of man ciphers for the full set of keywords and notation allowed in the argument string.