Configuring data at rest encryption
You can enable data at rest encryption using Cloudera Manager. However, you can enable it only for a fresh installation and once Kudu directories exist on the cluster you cannot disable the encryption.
Kudu supports data at rest encryption, specifically AES-128, AES-192 and AES-256 ciphers in CTR mode are supported to encrypt data.
When data is encrypted at rest, the following keys are used for encryption:
- File Key: The unique key used to encrypt a physical file
- Server Key: A server’s own key used to encrypt the File Key
- Cluster Key: A key that is used to encrypt the Server Key and stored in a third-party Key Management Service (KMS). Kudu supports Apache Ranger KMS and Apache Hadoop KMS. Both are API-compatible
If Kudu was started before encryption was enabled, all Kudu data directories, WAL directories, and metadata directories (usually the same as WAL directories) must be deleted. This will result in a completely clean slate, so if there is any data in Kudu, it must be backed up using the backup tool before doing so. For more information, see Kudu backup.
If you enabled data at encryption for a pre-existing cluster, restore the data you backed up before enabling encryption. For more information, see Kudu recovery.