Transparent Data Encryption
Encrypt GridGain 9 data at rest with transparent data encryption (TDE), using a Java keystore or AWS KMS key encryption key provider.
Overview
Transparent data encryption (TDE) allows users to encrypt their data at rest.
When Ignite persistence is turned on, all data in the cluster will be encrypted, including:
Data on disk
RAFT log
Meta storage
If you enable cluster encryption, the cluster will generate a data encryption key and will use this key to encrypt/decrypt the data. This key is held in the internal memory and cannot be accessed by users. When the cluster needs save it to disk (for example, when the node goes down), it is encrypted by using the user-provided key — the key encryption key.
The key encryption key provider must be specified in the cluster configuration.
Key Generation Example
A keystore with a key can be created by using keytool:
user:~/tmp:[]$ keytool -genseckey \
-alias ignite.key \
-keystore ./ignite_keystore.jks \
-storetype PKCS12 \
-keyalg aes \
-storepass mypassw0rd \
-keysize 256
user:~/tmp:[]$ keytool \
-storepass mypassw0rd \
-storetype PKCS12 \
-keystore ./ignite_keystore.jks \
-list
Keystore type: PKCS12
Keystore provider: SunJSSE
Your keystore contains 1 entry
ignite.key, 12.01.2020, SecretKeyEntry,The generated keystore can be provided to the cluster as
Configuration
GridGain 9 supports two types of encryption providers: Java keystore (.jks or .p12 files) and AWS KMS.
Keystore Configuration
To enable encryption in the cluster, specify the path to your keystore in the cluster configuration by using the CLI tool.
enabled
false
Determines if data encryption is enabled on the cluster.
activeProvider
The name of the currently used provider.
providers.keyStoreType
PKCS12
Type of the keystore.
providers.name
Name of the provider. This name is used in the activeProvider field.
providers.password
Password for opening the keystore and extracting the active key.
providers.path
The path to the keystore file.
providers.activeKeyName
Name or alias for the active key.
providers.cipher
AES/CBC/PKCS5Padding
The algorithm used to encrypt DEK keys. Once set, this value cannot be changed for the provider. Supported algorithms: - AES - Chacha20 Supported modes: - CBC - GCM - CTR - OFB - ECB - CFB8 Supported paddings: - NoPadding - PKCS5Padding - ISO10126Padding
AWS KMS Configuration
The following example shows how to configure AWS KMS provider.
You also need to set the following properties for each node:
aws.accessKeyIdaws.secretAccessKeyaws.region
This can be done via environment variables, credentials file, or any other method that the AWS SDK supports. For more details, refer to the AWS documentation.
Key Rotation
You may need to change the encryption key at the end of your key's validity period, or if the currently used key is compromised.
To change the key, first create a new provider with a different key in the cluster configuration. The example below is in the JSON format.
Then, change the currently used provider to a provider with the new key.
This page is: Copyright © 2026 MariaDB. All rights reserved.
Last updated
Was this helpful?

