Manage KMS using the CLI
This page describes how to manage the Key Management System (KMS) using the CLI.
Last updated
This page describes how to manage the Key Management System (KMS) using the CLI.
Last updated
Using the CLI, you can:
Command: weka security kms set
Use the following command line to add or update the Vault KMS configuration in the Weka system:
weka security kms set <type> <address> <key-identifier> [--token token] [--client-cert client-cert] [--client-key client-key] [--ca-cert ca-cert]
Parameters
Name
Type
Value
Limitations
Mandatory
Default
type
String
Type of the KMS
Either vault
or kmip
Yes
address
String
KMS server address
URL
for Vault, hostname:port
for KMIP
Yes
key-identifier
String
Key to be used for encryption-as-a-service in the KMS
Key name (for Vault) or a key UID (for KMIP)
Yes
token
String
API token to access Vault KMS
Must have:
read permissions to transit/keys/<master-key-name>
write permissions to transit/encrypt/<master-key-name>
and transit/decrypt/<masterkeyname>
permissions to /transit/rewrap
and auth/token/lookup
Must be supplied for vault
and must not be supplied for kmip
client-cert
String
Path to the client certificate PEM file
Must permit encrypt
and decrypt
permissions
Must be supplied for kmip
and must not be supplied for vault
client-key
String
Path to the client key PEM file
Must be supplied for kmip
and must not be supplied for vault
ca-cert
String
Path to the CA certificate PEM file
Optional for kmip
and must not be supplied for vault
Example:
Setting the Weka system with a Vault KMS:
weka security kms set vault https://vault-dns:8200 weka-key --token s.nRucA9Gtb3yNVmLUK221234
Setting the Weka system with a KMIP complaint KMS (e.g., SmartKey):
weka security kms set kmip amer.smartkey.io:5696 b2f81234-c0f6-4d63-b5b3-84a82e231234 --client-cert smartkey_cert.pem --client-key smartkey_key.pem
Command: weka security kms
Use this command to show the details of the configured KMS.
Command: weka security kms unset
Use this command to remove the KMS from the Weka system. It is only possible to remove a KMS configuration if no encrypted filesystems exist.
Note: To force remove a KMS even if encrypted filesystems exist, use the --allow-downgrade
attribute. In such cases, the encrypted filesystem keys are re-encrypted with local encryption and may be compromised.
Command: weka security kms rewrap
If the KMS key is compromised or requires rotation, the KMS admin can rotate the key in the KMS. In such cases, this command is used to re-encrypt the encrypted filesystem keys with the new KMS master key.
weka security kms rewrap [--new-key-uid new-key-uid]
Parameters
Name
Type
Value
Limitations
Mandatory
Default
new-key-uid
String
Unique identifier for the new key to be used to wrap filesystem keys
Must be supplied for kmip
and must not be supplied for vault
Note: Unlike in Vault KMS, re-wrapping a KMIP-based KMS requires generating a new key in the KMS, rather than rotating the same key. Hence, the old key should be preserved in the KMS in order to be able to decrypt old Snap2Obj snapshots.
Once the transit
secret engine is set up, a master key for use with the Weka system must be created.
Create a weka_policy.hcl
file with the following content:
This limits the capabilities so there is no permission to destroy the key, using this policy. This protection is important when creating an API token.
Create the policy using the following command:
Verify that thetoken
authentication method in Vault is enabled. This can be performed using the following command:
To enable the token authentication method use the following command:
Log into the KMS system using any of the identity methods supported by Vault. The identity should have permission to use the previously-set master key.
Create a token role for the identity using the following command:
Generate a token for the logged-in identity using the following command:
The method for obtaining a client certificate and key and set it via the KMS is different for each KMS. The certificate itself is generated using OpenSSL, with a UID obtained from the KMS.
Example:
See the specific KMS documentation to create a certificate and link it to the Weka cluster in the KMS with sufficient privileges (encrypt/decrypt).
The Weka system uses capabilities of the KMS to encrypt/decrypt the filesystem keys. This requires the configuration of Vault with the transit
secret engine.
For more information, refer to .
For more information, refer to .
Authentication from the Weka system to Vault relies on an API token. Since the Weka system must always be able to communicate with the KMS, a must be used.
For more information on obtaining an API token, refer to .
Note: The Weka system does not automatically renew the API token lease. It can be renewed using the . It is also possible to define a higher maximum token value (max_lease_ttl)
by changing the .
For example, for SmartKey KMS, follow similar instructions as suggested to create a client certificate and key, and assign a certificate for Weka within SmartKey.