Use Customer-managed encryption keys (CMEK) with Migrate to Virtual Machines

By default, Migrate to Virtual Machines encrypts customer content at rest. Migrate to Virtual Machines handles encryption for you without any additional actions on your part. This option is called Google default encryption.

If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in Cloud KMS with CMEK-integrated services including Migrate to Virtual Machines. Using Cloud KMS keys gives you control over their protection level, location, rotation schedule, usage and access permissions, and cryptographic boundaries. Using Cloud KMS also lets you track key usage, view audit logs, and control key life cycles. Instead of Google owning and managing the symmetric key encryption keys (KEKs) that protect your data, you control and manage these keys in Cloud KMS.

After you set up your resources with CMEKs, the experience of accessing your Migrate to Virtual Machines resources is similar to using Google default encryption. For more information about your encryption options, see Customer-managed encryption keys (CMEK).

Migrate to Virtual Machines uses CMEK to encrypt the following data:

The following sections describe these scenarios is more detail.

Use CMEK to encrypt data stored during a migration

To encrypt data stored during a migration or import using CMEK, you must provide a reference to a Cloud KMS key when creating a migration source or import resource respectively. For instructions on using CMEK to encrypt data during a migration from various migration sources, see the following topics:

Use CMEK to encrypt data on target VM instances and VM disks

To encrypt data on target VM instances and VM disks using CMEK, you must provide a reference to a Cloud KMS key in the target details. For instructions on setting CMEK in the target details, see setting CMEK for VM instances and setting CMEK for VM disks.

Use CMEK to encrypt data on target disks and machine images

To encrypt data on target disks and machine images using CMEK, you must provide a reference to a Cloud KMS key in the target details. For instructions on setting CMEK in the target details, see Import a virtual disk image to Compute Engine and Import a machine image to Compute Engine.