Quotas and limits

To reduce the risk of abuse, Google Cloud enforces limits on the usage of Google Cloud services. New Google Cloud customers using Migrate for Compute Engine should familiarize themselves with the limits that are applicable to their migration.

Migrate for Compute Engine uses the following Google Cloud resources which are subject to limits:

Google Cloud Resource How used in Migrate for Compute Engine
Compute instances Needed to support migrated VMs, Migrate for Compute Engine Manager, Cloud Extensions, and worker nodes.
Persistent disks When deploying Cloud Extensions, ensure that you have SSD (solid-state disk) Persistent Disk quota set high enough to support the number of Cloud Extensions you intend to create. For more, see Cloud Extensions Overview.
External IP addresses The migration process creates Compute Engine VMs, and can create IP addresses for access over the public Internet (such as for inbound access from your corporate data center).
Cloud Storage While you are migrating, Migrate for Compute Engine uses Cloud Storage to hold data that is used by your applications on Compute Engine VMs.
VPC networks Migrate for Compute Engine uses Virtual Private Cloud (VPC) for secure access to Google Cloud during migration. Ensure that your quotas for networks, subnets, IP addresses, and more will support your migration.

The number of worker nodes is equal to the number of VMs that are in Detach phase.

Viewing your current quota usage


The quotas page on the Google Cloud Console shows your project's current quotas and their usage.

Requesting increases to your quotas

See the Compute Engine documentation for instructions on how to request a quota increase.