Top / Google Cloud Platform / Google Compute Engine / Instance From Machine Image

Google Compute Engine Instance From Machine Image

This page shows how to write Terraform for Compute Engine Instance From Machine Image and write them securely.

terraform-logo

Review your .tf file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

google_compute_instance_from_machine_image (Terraform)

The Instance From Machine Image in Compute Engine can be configured in Terraform with the resource name google_compute_instance_from_machine_image. The following sections describe 4 examples of how to use the resource and its parameters.

Example Usage from GitHub

ui-vm.tf#L1
resource "google_compute_instance_from_machine_image" "tpl" {
  provider = google-beta
  name     = "mvcdotnet-vm"
  zone     = "us-central1-a"

  source_machine_image = "projects/clean-circle-322216/global/machineImages/mvcdotnet-vm-image"
ui-vm.tf#L1
resource "google_compute_instance_from_machine_image" "tpl" {
  provider = google-beta
  name     = "mvcdotnet-vm-image"
  zone     = "us-central1-a"

  source_machine_image = "projects/clean-circle-322216/global/machineImages/mvcdotnet-vm-image"
vm.tf#L1
resource "google_compute_instance_from_machine_image" "tpl" {
  provider = google-beta
  name     = "reactvm"
  zone     = "us-central1-a"

  source_machine_image = "projects/clean-circle-322216/global/machineImages/react-v1"
reactvm.tf#L1
resource "google_compute_instance_from_machine_image" "tpl" {
  provider = google-beta
  name     = "reactvm"
  zone     = "us-central1-a"

  source_machine_image = "projects/clean-circle-322216/global/machineImages/react-v1"

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

The following arguments are supported:

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

  • source_machine_image - (Required) Name or self link of a machine image to create the instance based on.

  • zone - (Optional) The zone that the machine should be created in. If not set, the provider zone is used.

In addition to these, most* arguments from google_compute_instance are supported as a way to override the properties in the machine image. All exported attributes from google_compute_instance are likewise exported here.

Warning: *Due to API limitations, disk overrides are currently disabled. This includes the "boot_disk", "attached_disk", and "scratch_disk" fields.

All exported attributes from google_compute_instance are exported here. See https://www.terraform.io/docs/providers/google/r/compute_instance.html#attributes-reference for details.

>> from Terraform Registry

Explanation in Terraform Registry

Manages a VM instance resource within GCE. For more information see the official documentation and API. This resource is specifically to create a compute instance from a given source_machine_image. To create an instance without a machine image, use the google_compute_instance resource.

>> from Terraform Registry

Tips: Best Practices for The Other Google Compute Engine Resources

In addition to the google_compute_disk, Google Compute Engine has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.

risk-label

google_compute_disk

Ensure the encryption key for your GCE disk is stored securely

It is better to store the encryption key for your GCE disk securely. Secret Manager could be used instead.

risk-label

google_compute_firewall

Ensure your VPC firewall blocks unwanted outbound traffic

It is better to block unwanted outbound traffic not to expose resources in the VPC to unwanted attacks.

risk-label

google_compute_instance

Ensure appropriate service account is assigned to your GCE instance

It is better to create a custom service account for the instance and assign it.

risk-label

google_compute_project_metadata

Ensure OS login for your GCE instances is enabled at project level

It is better to enable OS login for your GCE instances. Enabling OS login ensures that SSH keys used to connect to instances are mapped with IAM users, allowing centralized and automated SSH key management.

risk-label

google_compute_ssl_policy

Ensure to use modern TLS protocols

It's better to adopt TLS v1.2+ instead of outdated TLS protocols.

risk-label

google_compute_subnetwork

Ensure VPC flow logging is enabled

It is better to enable VPC flow logging. VPC flow logging allows us to audit traffic in your network.

Review your Google Compute Engine settings

In addition to the above, there are other security points you should be aware of making sure that your .tf files are protected in Shisho Cloud.

The Other Related Google Compute Engine Resources

Frequently asked questions

What is Google Compute Engine Instance From Machine Image?

Google Compute Engine Instance From Machine Image is a resource for Compute Engine of Google Cloud Platform. Settings can be wrote in Terraform.

Where can I find the example code for the Google Compute Engine Instance From Machine Image?

For Terraform, the bagulmahendra/gcpterraform, bagulmahendra/gcpterraform and bagulmahendra/gcpterraform source code examples are useful. See the Terraform Example section for further details.

security-icon

Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.

Table of Contents