Manages a VM instance resource within GCE. For more information see the official documentation and API.

Example Usage

resource "google_compute_instance" "default" {
  name         = "test"
  machine_type = "n1-standard-1"
  zone         = "us-central1-a"

  tags = ["foo", "bar"]

  disk {
    image = "debian-cloud/debian-8"

  // Local SSD disk
  disk {
    type    = "local-ssd"
    scratch = true

  network_interface {
    network = "default"
    access_config {
      // Ephemeral IP

  metadata {
    foo = "bar"

  metadata_startup_script = "echo hi > /test.txt"

  service_account {
    scopes = ["userinfo-email", "compute-ro", "storage-ro"]

Argument Reference

The following arguments are supported:

  • disk - (Required) Disks to attach to the instance. This can be specified multiple times for multiple disks. Structure is documented below.

  • machine_type - (Required) The machine type to create.To create a custom machine type, value should be set as specified here

  • name - (Required) A unique name for the resource, required by GCE. Changing this forces a new resource to be created.

  • zone - (Required) The zone that the machine should be created in.

  • can_ip_forward - (Optional) Whether to allow sending and receiving of packets with non-matching source or destination IPs. This defaults to false.

  • description - (Optional) A brief description of this resource.

  • metadata - (Optional) Metadata key/value pairs to make available from within the instance.

  • metadata_startup_script - (Optional) An alternative to using the startup-script metadata key, except this one forces the instance to be recreated (thus re-running the script) if it is changed. This replaces the startup-script metadata key on the created instance and thus the two mechanisms are not allowed to be used simultaneously.

  • network_interface - (Required) Networks to attach to the instance. This can be specified multiple times for multiple networks, but GCE is currently limited to just 1. Structure is documented below.

  • network - (DEPRECATED, Required) Networks to attach to the instance. This can be specified multiple times for multiple networks. Structure is documented below.

  • project - (Optional) The project in which the resource belongs. If it is not provided, the provider project is used.

  • scheduling - (Optional) The scheduling strategy to use. More details about this configuration option are detailed below.

  • service_account - (Optional) Service account to attach to the instance. Structure is documented below.

  • tags - (Optional) Tags to attach to the instance.

The disk block supports: (Note that either disk or image is required, unless the type is "local-ssd", in which case scratch must be true).

  • disk - The name of the existing disk (such as those managed by google_compute_disk) to attach.

  • image - The image from which to initialize this disk. Either the full URL, a contraction of the form "project/name", an image family, or just a name (in which case the current project is used).

  • auto_delete - (Optional) Whether or not the disk should be auto-deleted. This defaults to true. Leave true for local SSDs.

  • type - (Optional) The GCE disk type, e.g. pd-standard, pd-ssd, or local-ssd.

  • scratch - (Optional) Whether the disk is a scratch disk as opposed to a persistent disk (required for local-ssd).

  • size - (Optional) The size of the image in gigabytes. If not specified, it will inherit the size of its base image. Do not specify for local SSDs as their size is fixed.

  • device_name - (Optional) Name with which attached disk will be accessible under /dev/disk/by-id/

The network_interface block supports:

  • network - (Optional) The name of the network to attach this interface to. Either network or subnetwork must be provided.

  • subnetwork - (Optional) the name of the subnetwork to attach this interface to. The subnetwork must exist in the same region this instance will be created in. Either network or subnetwork must be provided.

  • address - (Optional) The private IP address to assign to the instance. If empty, the address will be automatically assigned.

  • access_config - (Optional) Access configurations, i.e. IPs via which this instance can be accessed via the Internet. Omit to ensure that the instance is not accessible from the Internet (this means that ssh provisioners will not work unless you are running Terraform can send traffic to the instance's network (e.g. via tunnel or because it is running on another cloud instance on that network). This block can be repeated multiple times. Structure documented below.

The access_config block supports:

  • nat_ip - (Optional) The IP address that will be 1:1 mapped to the instance's network ip. If not given, one will be generated.

The service_account block supports:

  • email - (Optional) The service account e-mail address. If not given, the default Google Compute Engine service account is used.

  • scopes - (Required) A list of service scopes. Both OAuth2 URLs and gcloud short names are supported.

(DEPRECATED) The network block supports:

  • source - (Required) The name of the network to attach this interface to.

  • address - (Optional) The IP address of a reserved IP address to assign to this interface.

The scheduling block supports:

  • preemptible - (Optional) Is the instance preemptible.

  • on_host_maintenance - (Optional) Describes maintenance behavior for the instance. Can be MIGRATE or TERMINATE, for more info, read here

  • automatic_restart - (Optional) Specifies if the instance should be restarted if it was terminated by Compute Engine (not a user).

Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

  • metadata_fingerprint - The unique fingerprint of the metadata.

  • self_link - The URI of the created resource.

  • tags_fingerprint - The unique fingerprint of the tags.

  • network_interface.0.address - The internal ip address of the instance, either manually or dynamically assigned.

  • network_interface.0.access_config.0.assigned_nat_ip - If the instance has an access config, either the given external ip (in the nat_ip field) or the ephemeral (generated) ip (if you didn't provide one).