Configure data encryption at rest in Azure HorizonDB

This article provides step-by-step instructions to configure data encryption at rest for an Azure HorizonDB cluster.

Important

Select either service-managed keys or customer-managed keys when you create the cluster. You can't change the encryption mode after cluster creation.

In this article, you learn how to create a new Azure HorizonDB cluster and configure its data encryption at rest options. For an existing cluster that uses customer-managed keys, you can:

  • Select a different user-assigned managed identity to access the customer-managed key.
  • Rotate the customer-managed key.

For more information about encryption architecture, requirements, rotation, and limitations, see Data encryption.

Prerequisites

To complete the steps in this article, you need:

  • An Azure subscription.
  • Permission to create and update Azure HorizonDB clusters.
  • For the CLI procedures, the HorizonDB Azure CLI extension. Install it by running az extension add --name horizondb.

Customer-managed key prerequisites

To use customer-managed keys, you also need:

  • An Azure Key Vault with soft delete and purge protection enabled.
  • A supported 4,096-bit RSA or RSA-HSM key.
  • A user-assigned managed identity with permission to access the customer-managed key, see Customer-managed key requirements.

Create an Azure HorizonDB cluster with service-managed keys

Use the Azure portal:

  1. When you create a new Azure HorizonDB cluster, configure data encryption at rest in the Security tab. For Data encryption key, select the Service-managed key option.

    Screenshot that shows how to select the service-managed encryption key during cluster provisioning.

Create an Azure HorizonDB cluster with customer-managed keys

Use the Azure portal:

  1. When you create a new Azure HorizonDB cluster, configure data encryption in the Security tab. For Data encryption key, select the Customer-managed key.

    Screenshot that shows how to select the customer-managed encryption key during cluster provisioning.

  2. In User-assigned managed identity, select Change identity.

    Screenshot that shows how to select the user-assigned managed identity to access the data encryption key for the data of the cluster location.

  3. From the list of user-assigned managed identities, select the one you want your Azure HorizonDB cluster to use to access the customer-managed key stored in an Azure Key Vault.

    Screenshot that shows how to select the user-assigned managed identity with which the cluster accesses the data encryption key.

  4. Select Add.

    Screenshot that shows the location of the Add button to assign the identity with which the cluster accesses the data encryption key.

  5. Select Select key.

    Screenshot that shows how to select a data encryption key.

  6. The key store that contains the customer-managed key must exist in the same subscription as the Azure HorizonDB cluster.

    Screenshot that shows how to select the subscription in which the key store should exist.

  7. In Key store type, select the type of key store in which you plan to store the customer-managed key. In this example, choose Key vault.

    Screenshot that shows how to select the type of store that keeps the data encryption key.

  8. Expand Key vault, and select the instance where the customer-managed key exists.

    Screenshot that shows how to select the key store that contains the customer-managed key.

  9. Expand Key, and select the key. Azure HorizonDB uses its versionless key URI, so you don't select a key version.

    Screenshot that shows how to select the data encryption key.

  10. Select Select.

    Screenshot that shows how to select the chosen key.

  11. Configure all other settings of the new Azure HorizonDB cluster and select Review + create.

    Screenshot that shows how to complete creation of the cluster.

Update customer-managed key settings

For an Azure HorizonDB cluster that uses customer-managed keys, you can change the key, the user-assigned managed identity used to access it, or both. You can't change the Azure HorizonDB cluster from customer-managed keys to service-managed keys.

Use the Azure portal:

  1. Select your Azure HorizonDB cluster.

  2. In the resource menu, under the Security section, select Data encryption.

    Screenshot that shows how to get to the Data encryption for an existing HorizonDB.

  3. To change the user-assigned managed identity that the Azure HorizonDB cluster uses to access the key store, expand the User-assigned managed identity list, and select any of the available identities. The list shows only the user-assigned managed identities assigned to the cluster. Although it's not required, to maintain regional resiliency, select user-assigned managed identities in the same region as your Azure HorizonDB cluster.

    Screenshot that shows how to select one of the user-assigned managed identities associated with the Azure HorizonDB cluster.

  4. If the user-assigned managed identity that you want to use to access the customer-managed key isn't assigned to your Azure HorizonDB cluster, and it doesn't exist as an Azure resource with its corresponding object in Microsoft Entra ID, create it by selecting Create.

    Screenshot that shows how to create a new user-assigned managed identity in Azure and Microsoft Entra ID, automatically assign it to your HorizonDB, and use it to access the data encryption key.

  5. In the Create User-Assigned Managed Identity panel, enter the details of the user-assigned managed identity that you want to create, and automatically assign it to your Azure HorizonDB cluster to access the customer-managed key.

    Screenshot that shows how to provide the details for the new user-assigned managed identity.

  6. If the user-assigned managed identity that you want to use to access the customer-managed key isn't assigned to your Azure HorizonDB cluster, but it exists as an Azure resource with its corresponding object in Microsoft Entra ID, assign it by selecting Select.

    Screenshot that shows how to select an existing user-assigned managed identity in Azure and Microsoft Entra ID, automatically assign it to your HorizonDB, and use it to access the data encryption key.

  7. From the list of user-assigned managed identities, select the one you want your Azure HorizonDB cluster to use to access the customer-managed key stored in an Azure Key Vault.

    Screenshot that shows how to select an existing user-assigned managed identity to assign it to your HorizonDB, and use it to access the data encryption key.

  8. Select Add.

    Screenshot that shows how to add the selected user-assigned managed identity.

  9. If your account has permission to read keys from the key store, choose Select a key under Key selection method, and then select Select key.

    Screenshot that shows how to select a data encryption key.

  10. Subscription displays the subscription containing the Azure HorizonDB cluster. The key store that contains the customer-managed key must exist in the same subscription as the Azure HorizonDB cluster.

    Screenshot that shows how to select the subscription in which the key store should exist.

  11. In Key store type, select the type of key store in which you plan to store the customer-managed key. In this example, choose Key vault.

    Screenshot that shows how to select the type of store that keeps the data encryption key.

  12. Expand Key vault, and select the instance where the customer-managed key exists.

    Screenshot that shows how to select the key store that contains the customer-managed key.

  13. Expand Key, and select the key. Azure HorizonDB uses its versionless key URI, so you don't select a key version.

    Screenshot that shows how to select the data encryption key.

  14. Select Select.

    Screenshot that shows how to select the chosen key.

  15. When you're satisfied with the changes, select Save.

    Screenshot that shows how to save the changes made to data encryption configuration.