Stop or restart a Compute Engine instance

You can manually stop a Compute Engine instance when you longer use it, or to modify its properties—for example, to change its machine type, or remove any attached and mounted disks. After the instance stops, you can either restart it to resume your workload, or delete the instance if you no longer need it.

This document explains how to manually stop or restart an instance. To automate stopping or restarting an instance, see the following:

Limitations

When you stop a compute instance, the following limitations apply:

  • You can only stop or restart an instance if the instance state allows it.

  • You can only restart an instance if there are sufficient resources in the instance's zone.

  • You can't restart TPU instances.

Before you begin

  • If you haven't already, set up authentication. Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:

    Select the tab for how you plan to use the samples on this page:

    Console

    When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.

    gcloud

    1. Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:

      gcloud init

      If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

    2. Set a default region and zone.

    Go

    To use the Go samples on this page in a local development environment, install and initialize the gcloud CLI, and then set up Application Default Credentials with your user credentials.

    1. Install the Google Cloud CLI.

  • If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

  • If you're using a local shell, then create local authentication credentials for your user account:

    gcloud auth application-default login

    You don't need to do this if you're using Cloud Shell.

    If an authentication error is returned, and you are using an external identity provider (IdP), confirm that you have signed in to the gcloud CLI with your federated identity.

  • For more information, see Set up authentication for a local development environment.