Compute Engine instances (original) (raw)


This page provides an overview of Compute Engine instances. A Compute Engine instance can be either a virtual machine (VM) or bare metal instance that is hosted on Google's infrastructure. You cancreate an instance orcreate a group of managed instances (MIG)by using the Google Cloud console, the Google Cloud CLI, or the Compute Engine API.

Introduction

The terms Compute Engine instance, compute instance or_instance_ are synonymous. Based on themachine typethat you specify, an instance can be either a bare metal instance or a virtual machine (VM) instance, as follows:

Synonymous terms are used interchangeably across the documentation and Google Cloud interfaces such as theGoogle Cloud console, thegcloud command-line tool, and the REST API.

Compute Engine instances can run thepublic images for Linux and Windows Server that Google provides as well as private custom images that you cancreate orimport from your existing systems. You can also deploy 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 number of 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 a Google Cloud console project, and a project can have one or more instances. When you create an instance in a project, you specify the zone, 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 that contains the operating system. You can add more disks to the instance when you create 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 with a subnet of a unique VPC network. For more information about VPCs, see Network overviewand VPC quotas.

Instances and containers

Compute Engine instances support a declarative method for launching your applications using containers. When creating an instance or an instance template, you can provide a Docker image name and launch configuration. Compute Engine takes care of the rest including supplying an up-to-date Container-Optimized OSimage with Docker installed and launching your container when the instance starts. For more information, seeDeploying containers on instances and MIGs.

To create and manage instances, you can use a variety of tools, including theGoogle Cloud console, the gcloud command-line tool, and the REST API. To configure applications 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:

Accessing your instances

After you configure access to your instances, you can use one of many options to connect to your Linux instancesor connect to your Windows instances.

Default time zone for compute instances

Regardless of the region where you create your instance, the default time for your instance is Coordinated Universal Time (UTC).

What's next

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 free