Stay organized with collections Save and categorize content based on your preferences.
Linux Windows
Bulk creation of virtual machine (VM) instances lets you create a large number of VMs that are identical and independent from each other. When you create VMs in bulk, you can do the following:
Minimize consumption of API rate limits. Requests for creating VMs in bulk consume API rate limits as if you were creating a single VM.
Distribute VM creation across multiple zones in a region. For regional requests, Compute Engine determines the zone to create the VMs in based on the zones that have available hardware, taking into consideration the available capacity in each zone, as well as any of your reservations.
Compute Engine doesn't manage VMs that you create in bulk. To create a group of managed VMs, use managed instance groups.
Creating VMs in bulk versus batching API requestsCreating VMs in bulk is different from batching API requests with the instances.insert method. The following table compares these two ways of creating multiple VMs:
The following list describes the limitations that apply when creating VMs in bulk:
Customer supplied encryption keys. You can't create VMs that have disks that are protected by customer-supplied encryption keys (CSEK). The disks must use Google-default or customer-managed encryption keys.
Boot disks from snapshots. You can't use a snapshot to create the boot disks for the VMs. Instead, use a custom image when you create VMs in bulk.
Global DNS. If you are using global DNS, there might be name conflicts because the fully qualified domain name (FQDN) doesn't contain the zone. To avoid this, use zonal DNS. If you cannot switch to zonal DNS, avoid using the same name pattern across different regions. For more information, see Types of internal DNS names.
Machine images. You cannot create VMs from machine images.
Number of VMs. You can create up to 5,000 VMs with each call. Also, you can create a maximum of 8,000 instances simultaneously at any time. This simultaneous operation limit is shared between instances.insert and instances.bulkInsert.
Sole-tenant nodes. You cannot create VMs that use sole-tenant node affinity labels.
VM properties. All VM properties, except their names and custom hostnames, must be identical. You cannot use VM properties that are mutually exclusive between VMs, which include but are not limited to static external IP addresses and static internal IP addresses.
Compute Engine logs information about the bulk VM creation to the Admin Activity audit log when you make the API call and when the API call completes.
Compute Engine also creates separate audit logs for each VM. You can find the audit log for a single VM by matching the value of protoPayload.resourceName with the VM name generated by the naming pattern that you specify with the request.
There are no additional charges for using bulk VM creation. As with creating single VMs, billing begins when you create the VMs.
You are not billed for any VMs that Compute Engine fails to create.
What's nextExcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-07 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["Bulk VM creation allows for the creation of numerous identical and independent virtual machines with a single API request, effectively minimizing API rate limit consumption."],["When creating VMs in bulk, Compute Engine can automatically distribute the VMs across multiple zones within a region, optimizing for resource availability and honoring any existing reservations."],["Unlike batching API requests, bulk VM creation offers automatic zone selection, upfront validation of requests, optional automatic VM name generation, and the possibility of automatic rollback if VM creation fails."],["There are limitations to bulk VM creation, such as not supporting customer-supplied encryption keys, boot disks from snapshots, machine images, sole-tenant nodes, and requiring most VM properties to be identical."],["Using bulk VM creation does not incur additional charges, and billing only starts upon successful VM creation; additionally, audit logs are provided for both the bulk operation and individual VMs."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4