Create a KMS configuration using AWS KMS

Encryption at rest uses a master key to encrypt and decrypt universe keys. The master key details are stored in YugabyteDB Anywhere in key management service (KMS) configurations. You enable encryption at rest for a universe by assigning the universe a KMS configuration. The master key designated in the configuration is then used for generating the universe keys used for encrypting the universe data.

Encryption at rest in YugabyteDB Anywhere supports the use of Amazon Web Services (AWS) KMS.

The master key resource policy should include the following key policy permissions:

  • kms:Encrypt
  • kms:Decrypt
  • kms:GenerateDataKeyWithoutPlaintext
  • kms:DescribeKey
  • kms:DisableKey
  • kms:ScheduleKeyDeletion
  • kms:CreateAlias
  • kms:DeleteAlias
  • kms:UpdateAlias

Note

To support master key rotation, after upgrading YBA from a version prior to 2.17.3, add the kms:Encrypt permission to any existing keys that are used by any AWS KMS configurations, if not already present.

The AWS user associated with a KMS configuration requires the following minimum Identity and Access Management (IAM) KMS-related permissions:

  • kms:CreateKey
  • kms:ListAliases
  • kms:ListKeys
  • kms:CreateAlias
  • kms:DeleteAlias
  • kms:UpdateAlias
  • kms:TagResource

Create a KMS configuration

You can create a KMS configuration that uses AWS KMS, as follows:

  1. Use the YugabyteDB Anywhere UI to navigate to Configs > Security > Encryption At Rest to access the list of existing configurations.

  2. Click Create New Config.

  3. Enter the following configuration details in the form:

    • Configuration Name — Enter a meaningful name for your configuration.
    • KMS Provider — Select AWS KMS.
    • Use IAM Profile — Specify whether or not to use an IAM profile attached to an Amazon Elastic Compute Cloud (EC2) instance running YugabyteDB. For more information, see Using instance profiles.
    • Access Key Id — Enter the identifier for the access key.
    • Secret Key Id — Enter the identifier for the secret key.
    • Region — Select the AWS region where the customer master key (CMK) that was used for generating the universe keys is to be located. This setting does not need to match the region where the encrypted universe resides on AWS.
    • Customer Master Key ID — Enter the identifier for the CMK. If an identifier is not entered, a CMK ID will be auto-generated.
    • AWS KMS Endpoint — Specify the KMS endpoint to ensure that the encryption traffic is routed across your internal links without crossing into an external network.

  4. Optionally, click Upload CMK Policy to select a custom policy file. The following is the default policy:

      {
      "Version": "2012-10-17",
      "Id": "key-default-1",
      "Statement": [
          {
              "Sid": "Enable IAM User Permissions",
              "Effect": "Allow",
              "Principal": {
                  "AWS": "arn:aws:iam::<AWS_ACCOUNT_ID>:root"
              },
              "Action": "kms:*",
              "Resource": "*"
          },
          {
              "Sid": "Allow access for Key Administrators",
              "Effect": "Allow",
              "Principal": {
                  "AWS": "arn:aws:iam::<AWS_ACCOUNT_ID>:[user|role]{1}/[<USER_NAME>|<ROLE_NAME>]{1}"
              },
              "Action": "kms:*",
              "Resource": "*"
          }
      ]
  }

  5. Click Save.

    Your new configuration should appear in the list of configurations. A saved KMS configuration can only be deleted if it is not in use by any existing universes.

  6. Optionally, to confirm that the information is correct, click Show details. Note that sensitive configuration values are displayed partially masked.