GCP KMS

To set up Akeyless KMS Integration with GCP KMS, follow these steps:

1. Create a new GCP Target in the Akeyless Platform. You can do it either from the Akeyless CLI or in the Akeyless Console. Make sure you have a GCP Keyring to target.

👍

Note

Remember to give the GCP Target the cloud KMS admin permissions to manage the keyring.

2. Create a Classic Key in the Akeyless Platform. You can do it either from the Akeyless CLI or in the Akeyless console. Alternatively, You can also use an existing Classic Key if it fits the target's accepted algorithm types.

GCP supports the following algorithm types: AES256GCM, RSA2048, RSA3072, RSA4096, EC256, EC384.

👍

Note

Any classic key will be protected using the Akeyless DFC key (you can select a DFC key with Zero-Knowledge Encryption).

3. Associate the key with the GCP Target. When you attach a key, a copy of the key material is securely transferred to the GCP Keyring KMS in accordance with its key import specification.

If you are using the CLI in order to associate the key and the target, please note to use all of the GCP mandatory parameters as described in the CLI Reference:

• project-id: A project ID of the GCP KMS (from the keyring created in the first step).
• location-id: A location ID of the GCP KMS (from the keyring created in the first step).
• keyring-name: A keyring name of the GCP KMS (from the keyring created in the first step).
• purpose: A purpose of the key in GCP KMS.
• kms-algorithm: An algorithm of the key in GCP KMS.

The value of the --purpose parameter depends on the key type:

• For AES keys, possible values are: ENCRYPT_DECRYPT,MAC

• For RSA keys, possible values are: ASYMMETRIC_SIGN, ASYMMETRIC_DECRYPT

• For EC keys, possible values is: ASYMMETRIC_SIGN

The value of the --kms-algorithm parameter depends on the key type, key size, and the selected purpose: