How to change the vSAN key provider from an external KMS to the vSphere Native Key Provider (NKP)
search cancel

How to change the vSAN key provider from an external KMS to the vSphere Native Key Provider (NKP)

book

Article ID: 392250

calendar_today

Updated On:

Products

VMware vSAN VMware vSphere ESXi

Issue/Introduction

This article describes how to change the key provider of an encrypted vSAN cluster from an external KMS (standard key provider) to the vSphere Native Key Provider (NKP).

Use it when you’re retiring an external KMS, or when you want to remove the cluster’s dependency on one. The change is a shallow rekey: vSAN generates a new KEK and host key, and the data isn’t rewritten. With “Wipe residual data” unchecked, it doesn’t affect data availability.

Environment

VMware vSAN (All Versions)

 

Resolution

1. Configure the Native Key Provider and back it up by following Configure a vSphere Native Key Provider. Store the backup file and its password outside the encrypted cluster.

2. Select the vCenter Server instance › Configure › Security › Key Providers, select the Native Key Provider, and click SET AS DEFAULT.

3. Select the vSAN cluster › Configure › vSAN › Services › Data-at-rest encryption › EDIT.

4. Change the key provider from the external KMS to the Native Key Provider, and click APPLY. If the “Wipe residual data” option is not checked, this operation does not affect data availability. Changing the key provider is a shallow rekey: vSAN generates a new KEK and host key, and the data is not rewritten.

5. On each host, confirm that the key provider ID now shows the Native Key Provider:

esxcli vsan encryption info get

6. Keep the external KMS running until every host has been validated and nothing else uses it, such as VM encryption.