You add a Key Management Server (KMS) to your vCenter Server system from the vSphere Client.
vCenter Server creates a KMS cluster when you add the first KMS instance. If you configure the KMS cluster on two or more vCenter Servers, make sure you use the same KMS cluster name.
Note: Do not deploy your KMS servers on the
vSAN cluster you plan to encrypt. If a failure occurs, hosts in the
vSAN cluster must communicate with the KMS.
- When you add the KMS, you are prompted to set this cluster as a default. You can later change the default cluster explicitly.
- After vCenter Server creates the first cluster, you can add KMS instances from the same vendor to the cluster, and configure all KMS instances to synchronize keys among them. Use the method documented by your KMS vendor.
- You can set up the cluster with only one KMS instance.
- If your environment supports KMS solutions from different vendors, you can add multiple KMS clusters.
Prerequisites
- Verify that the key server is in the vSphere Compatibility Matrixes and is KMIP 1.1 compliant.
- Verify that you have the required privileges:
- Connecting to a KMS by using only an IPv6 address is not supported.
- Connecting to a KMS through a proxy server that requires user name or password is not supported.