Virtual Machine on Google Cloud

The Google Cloud Virtual Machine template scaffolds a Pulumi project that provisions a Compute Engine instance and the supporting Compute Engine network. The instance boots an HTTP server on port 80 from a small init script, so the project deploys end to end out of the box. Use it as a starting point for a web application, backend service, or database VM.

Using this template

To use this template to deploy your own virtual machine, make sure you’ve installed Pulumi and configured your Google Cloud credentials, then create a new project using the template in the language of your choice:

$ mkdir my-virtual-machine && cd my-virtual-machine
$ pulumi new vm-gcp-typescript

Alternatively, you can create and configure a new project with this template (vm-gcp-typescript) in Pulumi Cloud.

$ mkdir my-virtual-machine && cd my-virtual-machine
$ pulumi new vm-gcp-python

Alternatively, you can create and configure a new project with this template (vm-gcp-python) in Pulumi Cloud.

$ mkdir my-virtual-machine && cd my-virtual-machine
$ pulumi new vm-gcp-go

Alternatively, you can create and configure a new project with this template (vm-gcp-go) in Pulumi Cloud.

$ mkdir my-virtual-machine && cd my-virtual-machine
$ pulumi new vm-gcp-csharp

Alternatively, you can create and configure a new project with this template (vm-gcp-csharp) in Pulumi Cloud.

$ mkdir my-virtual-machine && cd my-virtual-machine
$ pulumi new vm-gcp-yaml

Alternatively, you can create and configure a new project with this template (vm-gcp-yaml) in Pulumi Cloud.

Follow the prompts to complete the new-project wizard. When it’s done, you’ll have a complete Pulumi project that’s ready to deploy and configured with the most common settings. Feel free to inspect the code in index.js index.ts __main__.py main.go Program.cs Program.fs Program.vb App.java Pulumi.yaml for a closer look.

Deploying the project

The template requires no additional configuration. Once the new project is created, you can deploy it immediately with pulumi up:

$ pulumi up

When the deployment completes, Pulumi exports the following stack output values:

ip

The IP address of the virtual machine.

hostname

The provider-assigned hostname of the virtual machine.

url

The fully-qualified HTTP URL of the HTTP server running on the virtual machine.

Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed url, for example, can be used from the command line to open the newly deployed website in your favorite web browser:

$ open $(pulumi stack output url)

Customizing the project

Projects created with the Virtual Machine template expose the following configuration settings:

machineType

The Compute Engine machine type to use for the VM. Defaults to e2-micro.

osImage

The OS image type to use for the VM. Defaults to debian-11.

instanceTag

The tag to apply to the VM instance. Defaults to webserver.

servicePort

The HTTP service port to expose on the VM. Defaults to 80.

All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with pulumi config set:

Cleaning up

You can cleanly destroy the stack and all of its infrastructure with pulumi destroy:

$ pulumi destroy

Learn more

• Browse other architecture templates in the Templates gallery.
• Explore the Google Cloud provider API docs in the Pulumi Registry.
• Walk through Pulumi from the ground up in Pulumi Tutorials.
• Read the latest Google Cloud posts on the Pulumi blog.