KMS management

Efficiently manage and safeguard WEKA system keys through strategic KMS configurations and best practices. Optimize security and operational resilience.

When establishing an encrypted filesystem within the WEKA system, the usage of a Key Management System (KMS) is imperative to ensure the secure management of encryption keys. The WEKA system relies on the KMS for encrypting filesystem keys, and during system startup, it employs the KMS to decrypt these keys, leveraging its in-memory capabilities for data encryption and decryption operations.

The Snap-To-Object feature, employed for taking snapshots, includes the storage of the encrypted filesystem key along with the encrypted data. Subsequently, when promoting such a snapshot to a different filesystem or recovering from a disaster within the WEKA cluster, the KMS decrypts the filesystem key. Therefore, the presence of the same KMS data is crucial for these operations. To enhance security, the WEKA system refrains from saving any information that could reconstruct KMS encryption keys, relying solely on the KMS configuration. This necessitates careful consideration of the following:

  • Disaster recovery strategy: Loss of the KMS configuration may result in the loss of encrypted data. It is imperative to establish a robust Disaster Recovery (DR) strategy when deploying the KMS in a production environment.

  • High availability: The KMS must be available during system startup, when creating a new filesystem, and periodically during key rotations. Therefore, maintaining high availability for the KMS is strongly recommended.

The WEKA system supports the following KMS types:

KMS integration best practices

The KMS is the sole entity holding the key to decrypt WEKA system filesystem keys. Adhering to the following best practices is crucial for non-disruptive operations:

  • DR setup for KMS: Implement backup/replication for the KMS to mitigate data loss risks.

  • High availability for KMS: Maintain high availability for the KMS, represented by a single address in the WEKA system.

  • Access to KMS: Provide access to the KMS from the WEKA backend servers.

  • Verification of KMS methods: Verify and understand the methods employed by the KMS for securing, unsealing, and reconstructing lost keys. Different KMS solutions have distinct methods; for instance, Vault unsealing methods can enable auto unsealing using a trusted service.

For additional best practices recommended by HashiCorp when using Vault, refer to the Production Hardening documentation.

Snapshot considerations: Taking a Snap-To-Object ensures that the (encrypted) filesystem keys are backed up to the object store, serving as a crucial safeguard in the event of total corruption of the WEKA system configuration.

Related topics

Manage KMS using the GUI

Manage KMS using the CLI

Last updated