This document describes how to delete amanaged instance group (MIG)that you no longer need so you can stop paying for the resources it uses.

Before you begin

• If you haven't already, set upauthentication. 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:

     gcloudinit

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

     Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update.
  2. Set a default region and zone.

  REST

  To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.

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

  gcloudinit

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

  Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update.

  For more information, seeAuthenticate for using REST in the Google Cloud authentication documentation.

Delete a MIG

When you delete a managed instance group, all VMs in the group aredeleted. If you want to keep any of the VMs,abandon the VMsfirst to remove those VMs from the group. Then, delete the managed instancegroup.

The disks in a MIG are deleted only if you had set the disk's auto-deleteproperty to true when defining the disks in the MIG's instance template. If adisk's auto-delete property is set to false, then you can manually clean up thedisks when you no longer need them.

When you delete a managed instance group and its instances by using theGoogle Cloud console or thegcloud CLI,any attached autoscaler is automatically deleted. However, if you use theREST, youmust first issue a separate request to delete any attached autoscaler with theautoscalers.delete methodorregionAutoscalers.delete method.If you happen to delete the managed instance group first, you can still deletethe attached autoscaler using REST.

For each disk, you can also override the auto-delete property to specify whetherthe disk should be deleted when its associated instance is deleted.

gcloud compute instance-groups managed deleteINSTANCE_GROUP_NAME \    --zoneZONE

DELETE https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME

What's next

• Learn aboutGetting, listing, and deleting instance templates