Compute Engine instances Stay organized with collections Save and categorize content based on your preferences.
Introduction
The termsCompute Engine instance,compute instance orinstance are synonymous. Based on themachine typethat you specify, an instance can be either a bare metal instanceor a virtual machine (VM) instance, as follows:
- If the name of its machine type ends in
-metal, an instance is abare metal instance, which does not have a hypervisor installed. - Otherwise, an instance is a VM instance. The termsvirtual machine instance,VM instance, andVM are synonymous.
Synonymous terms are used interchangeablyacross the documentation and Google Cloud interfaces such as theGoogle Cloud console, thegcloud command-line tool,and theREST API.
Compute Engine instances can run thepublic images for Linux and Windows Server that Googleprovides as well as private custom images that you cancreate orimport from your existing systems.You can alsodeploy Docker containers,which are automatically launched on instances running theContainer-Optimized OS public image.
You can choose the machine properties of your instances, such as the numberof virtual CPUs and the amount of memory, by using a set ofpredefined machine typesor by creating your owncustom machine types.
Instances and projects
Each instance belongs to aGoogle Cloud console project, and a project can haveone or more instances. When you create an instance in a project, you specify thezone, operating system, and machine type of that instance.When you delete an instance, it is removed from the project.
Instances and storage options
By default, each Compute Engine instance has a small boot disk thatcontains the operating system. You can add more disks to the instance when youcreate it, and you can add disks to an instance while the instance is running.For more information about disks in Compute Engine, seeChoose a disk type.
Instances and networks
Each network interface of a Compute Engine instance is associated witha subnet of a unique VPC network. For more information aboutVPCs, seeNetwork overviewandVPC quotas.
Instances and containers
Compute Engine instances support a declarative method for launchingyour applications usingcontainers. When creating an instance oran instance template, you can provide a Docker image name and launchconfiguration. Compute Engine takes care of the rest includingsupplying an up-to-dateContainer-Optimized OSimage with Docker installed and launching your container when the instance starts. For more information, seeDeploying containers on instances and MIGs.
Tools to manage instances
To create and manage instances, you can use a variety of tools, including theGoogle Cloud console, thegcloud command-linetool, and theREST API. To configureapplications on your instances,connect to the instanceusing Secure Shell (SSH) for Linux instances or Remote Desktop Protocol (RDP)for Windows Server instances.
Managing access to your instances
You can manage access to your instances using one of the following methods:
- Linux instances:
- Managing instance access using OS Login, which allows you to associate SSH keys with your Google Account or Google Workspace account and manage admin or non-admin access to your instance through IAM roles.
- Manage your SSH keys in project or instance metadata, which uses public SSH keys stored in Compute Engine metadata to grant access to the instance. You can use SSH keys stored in project metadata to access all instances in a project. You can use SSH keys stored in instance metadata to access individual instances.
- If youconnect to your instances using the Google Cloud CLI or SSH from the console, Compute Engine automatically generates SSH keys for you.
- Windows Server instances:
- Generate credentials for Windows instances, which associates a password with a Windows user. Windows instances use this information to authenticate access to the instance.
Accessing your instances
After you configure access to your instances, you can use one of many optionstoconnect to your Linux instancesorconnect to your Windows instances.
Default time zone for compute instances
Regardless of theregion where you create yourinstance, the default time for your instance is Coordinated Universal Time (UTC).
What's next
If you are new to Compute Engine, seeCreate a Linux instance in Compute Engineto learn how to create an instance using the Google Cloud console.
For a more detailed guide to create an instance, seeCreate and start an instance instance.
For more information about the features of Compute Engineinstances, see the following:
Learn how tocreate a MIG from an existing instance.
Try it for yourself
If you're new to Google Cloud, create an account to evaluate how Compute Engine performs in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
Try Compute Engine freeExcept as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-15 UTC.