Instance
Creates an instance resource in the specified project using the data included in the request.
Constructors
Properties
Controls for advanced machine-related behavior features.
Allows this instance to send and receive packets with non-matching destination or source IPs. This is required if you plan to use this instance to forward routes. For more information, see Enabling IP Forwarding .
Whether the resource should be protected against deletion.
An optional description of this resource. Provide this property when you create the resource.
Array of disks associated with this instance. Persistent disks must be created before you can assign them.
Enables display device for the instance.
Specifies whether the disks restored from source snapshots or source machine image should erase Windows specific VSS signature.
A list of the type and count of accelerator cards attached to the instance.
Specifies the hostname of the instance. The specified hostname must be RFC1035 compliant. If hostname is not specified, the default hostname is INSTANCE_NAME.c.PROJECT_ID.internal when using the global DNS, and INSTANCE_NAME.ZONE.c.PROJECT_ID.internal when using zonal DNS.
Encrypts suspended data for an instance with a customer-managed encryption key. If you are creating a new instance, this field will encrypt the local SSD and in-memory contents of the instance during the suspend operation. If you do not provide an encryption key when creating the instance, then the local SSD and in-memory contents will be encrypted using an automatically generated key during the suspend operation.
KeyRevocationActionType of the instance. Supported options are "STOP" and "NONE". The default value is "NONE" if it is not specified.
Full or partial URL of the machine type resource to use for this instance, in the format: zones/zone/machineTypes/machine-type. This is provided by the client when the instance is created. For example, the following is a valid partial url to a predefined machine type: zones/us-central1-f/machineTypes/n1-standard-1 To create a custom machine type, provide a URL to a machine type in the following format, where CPUS is 1 or an even number up to 32 (2, 4, 6, ... 24, etc), and MEMORY is the total memory for this instance. Memory must be a multiple of 256 MB and must be supplied in MB (e.g. 5 GB of memory is 5120 MB): zones/zone/machineTypes/custom-CPUS-MEMORY For example: zones/us-central1-f/machineTypes/custom-4-5120 For a full list of restrictions, read the Specifications for custom machine types.
The metadata key/value pairs assigned to this instance. This includes custom metadata and predefined keys.
Specifies a minimum CPU platform for the VM instance. Applicable values are the friendly names of CPU platforms, such as minCpuPlatform: "Intel Haswell" or minCpuPlatform: "Intel Sandy Bridge".
The name of the resource, provided by the client when initially creating the resource. The resource name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
An array of network configurations for this instance. These specify how interfaces are configured to interact with other network services, such as connecting to the internet. Multiple interfaces are supported per instance.
Input only. Input Only Additional params passed with the request, but not persisted as part of resource payload.
PostKeyRevocationActionType of the instance.
Total amount of preserved state for SUSPENDED instances. Read-only in the api.
The private IPv6 google access type for the VM. If not specified, use INHERIT_FROM_SUBNETWORK as default.
An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
Specifies the reservations that this instance can consume from.
Resource policies applied to this instance.
Sets the scheduling options for this instance.
Input Only Secure tags to apply to this instance. These can be later modified by the update method. Maximum number of secure tags allowed is 50.
A list of service accounts, with their specified scopes, authorized for this instance. Only one service account per VM instance is supported. Service accounts generate access tokens that can be accessed through the metadata server and used to authenticate applications on the instance. See Service Accounts for more information.
Mapping of user-defined keys to specifications for service integrations. Currently only a single key-value pair is supported.
Deprecating, please use shielded_instance_config.
Deprecating, please use shielded_instance_integrity_policy.
Specifies instance template to create the instance. This field is optional. It can be a full or partial URL. For example, the following are all valid URLs to an instance template: - https://www.googleapis.com/compute/v1/projects/project /global/instanceTemplates/instanceTemplate - projects/project/global/instanceTemplates/instanceTemplate - global/instanceTemplates/instanceTemplate
Source machine image
Source machine image encryption key when creating an instance from a machine image.
Tags to apply to this instance. Tags are used to identify valid sources or targets for network firewalls and are specified by the client during instance creation. The tags can be later modified by the setTags method. Each tag within the list must comply with RFC1035. Multiple tags can be specified via the 'tags.items' field.