Google Compute Engine lets you create and run virtual machines on Google infrastructure. Compute Engine offers scale, performance, and value that allows you to easily launch large compute clusters on Google's infrastructure. There are no upfront investments and you can run thousands of virtual CPUs on a system that has been designed to be fast, and to offer strong consistency of performance.

You can create virtual machines running different operating systems, including multiple flavors of Linux (Debian, Ubuntu, Suse, Red Hat, CoreOS) and Windows Server!

Follow along this lab to learn about how to create virtual machine instances of various machine types.

What you'll learn

What you'll need

How will you use this tutorial?

Read it through only Read it and complete the exercises

How would rate your experience with Google Cloud Platform?

Novice Intermediate Proficient

Codelab-at-a-conference setup

The instructor will be sharing with you temporary accounts with existing projects that are already setup so you do not need to worry about enabling billing or any cost associated with running this codelab. Note that all these accounts will be disabled soon after the codelab is over.

Once you have received a temporary username / password to login from the instructor, log into Google Cloud Console:

One you log in, Agree and Continue to the Terms of Service:

You will now be taken to the project selection screen. Dismiss the free trial popup (1) and select the precreated project (2). If your screen does not look like this, please inform a codelab proctor.

Note the project ID you were assigned ( "webcrew16-tok-7015" in the screenshot above). It will be referred to later in this codelab as PROJECT_ID.

Certain Compute Engine resources live in regions or zones. A region is a specific geographical location where you can run your resources. Each region has one or more zones. For example, the us-central1 region denotes a region in the Central United States that has zones us-central1-a, us-central1-b, us-central1-c, and us-central1-f.

Virtual machine Instances and persistent disks live in a zone, and these are referred to as zonal resources. For example, to attach a persistent disk to a virtual machine instance, both resources must be in the same zone.

In this section, you'll learn how to create a new Google Compute Engine virtual machine instance from the Cloud Console.

Login into Google Cloud Console

Navigate to the the Google Cloud Console from another browser tab/window, to Use the login credential given to you by the lab proctor.

Compute Engine

In the Google Developer Console, click the Menu icon on the top left of the screen:

Then navigate to Compute Engine > VM Instances

This may take a minute to initialize for the first time. Once initialized, you should see the following if the project has no virtual machine instances:

Create a new instance

To create a new instance, click Create instance

There are many parameters you can configure when creating a new instance. Let's use the following:





Learn more about zones in Regions & Zones documentation.

Note: remember the zone that you selected, you'll need it later.

Machine Type

1 vCPU (n1-standard-1)

This is a 1-CPU, 3.75GB RAM instance.

There are a number of machine types, ranging from micro instance types to 32-core/208GB RAM instance types. Learn more about this and custom machine types in the Machine Types documentation.

Note: A new project has a default resource quota, which may limit the number of CPU cores. You can request more for your projects.

Boot Disk

New 10 GB standard persistent disk

Image: Debian GNU/Linux 8 (jessie)

There are a number of images to choose from, including: Debian, Ubuntu, CoreOS as well as premium images such as Red Hat Enterprise Linux and Windows Server. See Operating System documentation for more detail.

Note: You may optionally choose SSD Persistent Disk as well.


Check Allow HTTP traffic

Check this option so that we can access a webserver that we will install later.

Note: This will automatically create firewall rule to allow HTTP traffic on port 80.

Your screen should look like this:

Click on Create to create the new virtual machine instance!

Once finished, you should see the new virtual machine in the VM Instances page. Note down the External IP of the machine on the VM instances page - you will need this later

To SSH into the virtual machine, click on SSH on the right hand side.

Once ssh'ed, install Node.js and Git

curl -sL | sudo -E bash -
sudo apt-get install -y nodejs git

Now let's run an sample application. First, clone the source code:

git clone
cd nodejs-docs-samples/appengine/hello-world/standard

Now, install the dependencies with npm:

npm install

Finally, start the Node application listening on port 80

sudo PORT=80 npm start

Awesome! Let's see the web page!

Use the External IP of the virtual machine instance that you noted down before, and in a new browser window/tab, browse to http://EXTERNAL_IP/, you should see the default page.

Rather than using the Google Cloud Console to create a virtual machine instance, you can also use the command line tool called gcloud.

We'll use Google Cloud Shell, a command line environment running in the Cloud. This Debian-based virtual machine is loaded with all the development tools you'll need (gcloud, git and others) and offers a persistent 5GB home directory.

Open the Google Cloud Shell by clicking on the Screen Shot 2015-06-08 at 5.30.32 PM.pngicon on the top right of the screen:


Once opened, you can create a new virtual machine instance from the command line by using gcloud (feel free to use another zone closer to you) :

$ gcloud compute instances create gcelab2 --zone us-central1-c
Created [...gcelab2].
gcelab2  us-central1-c  n1-standard-1             10.240.X.X  X.X.X.X        RUNNING

The instance was created with some default values:

Run gcloud compute instances create --help to see all the defaults.

Finally, you can SSH into your instance using gcloud as well (make sure you adjust your zone if you've used something else when creating the instance, or omit the --zone flag if you've set the option globally):

$ gcloud compute ssh gcelab2 --zone us-central1-c
Warning: Permanently added 'compute.745019997240233037' (ECDSA) to the list of known hosts.

Disconnect from SSH by existing from the remote shell:

username@gcelab2:~$ exit

In the previous section, you learned that there are a number of predefined machine types that you can choose for your virtual machine. However, if predefined machine types do not meet your needs, you can create an instance with custom virtualized hardware settings. Specifically, you can create an instance with a custom number of vCPUs and amount of memory, effectively using a custom machine type.

Create another virtual machine instance using the Google Cloud Console, and choose a custom machine type by clicking Customize:

Then, you use the sliders to pick the exact number of cores and memory to use:

Create a virtual machine instance with 2 vCPU and 5 GB of RAM.

It's time to shut down those VM instances to save on cost and to be an overall good cloud citizen. You can either decide to delete the instances or simply stop them :

If you decide to delete the VM instances (after all they're really easy to recreate), then remember that this will also delete the VM boot disks. If you'd like persistent disks, check out the Disks and Snapshots sections of the compute engine console :

Google Compute Engine is the foundation to Google Cloud Platform's Infrastructure-as-a-Service. You can easily map your existing server infrastructure, load balancers, and network topology to Google Cloud Platform.

What we've covered

Next Steps