Skip to main content

GCP Compute Instance

A GCP Compute Instance is a virtual machine running on Google Cloud’s Compute Engine. It provides configurable CPU, memory, storage and networking resources, and can host any workload that runs on a Linux or Windows server. Instances are created from machine images or custom boot disks, can be attached to multiple disks and network interfaces, and are managed through the Compute Engine API, the gcloud CLI or the Cloud Console. For full details see the official documentation: https://cloud.google.com/compute/docs/instances

Terrafrom Mappings:

  • google_compute_instance.name

Supported Methods​

  • GET: Get GCP Compute Instance by "gcp-compute-instance-name"
  • LIST: List all GCP Compute Instance items
  • SEARCH

ip​

Every compute instance is assigned at least one internal IP address and may have one or more external (public) IP addresses. These addresses are tracked as separate IP resources, so Overmind links them to the instance to show inbound/outbound exposure and potential network-level risk.

gcp-compute-disk​

Boot disks and any additional persistent disks attached to the instance are represented by the gcp-compute-disk type. Linking allows you to trace data-at-rest dependencies, check encryption settings, and see which disks would be affected if the instance were modified or deleted.

gcp-compute-subnetwork​

An instance’s primary network interface must reside in a specific subnetwork. The link surfaces routing, firewall rules and CIDR details inherited from the subnetwork, helping you verify isolation boundaries before deployment.

gcp-compute-network​

Subnetworks themselves live inside a VPC network. By linking the instance directly to its parent network, Overmind presents a complete view of peering relationships, shared VPC configurations and any network-wide policies that could impact the instance’s security or connectivity.