Delete a MIG

---

This document describes how to delete a managed 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, then set up authentication. Authentication is the process by which your identity is verified 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, then initialize it by running the following command:

     gcloud init

     Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud 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, then initialize it by running the following command:

  gcloud init

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

Delete a MIG

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

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

Note: You cannot delete an instance group if it is being used by a load balancer's backend service. Remove the backend service before deleting the instance group.

When you delete a managed instance group and its instances by using the Google Cloud console or the gcloud CLI, any attached autoscaler is automatically deleted. However, if you use the REST, you must first issue a separate request to delete any attached autoscaler with the autoscalers.delete method or regionAutoscalers.delete method. If you happen to delete the managed instance group first, you can still delete the attached autoscaler using REST.

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

Permissions required for this task

To perform this task, you must have the following permissions:

• compute.instanceGroupManagers.delete on the managed instance group

Console

1. In the Google Cloud console, go to the Instance groups page.

   Go to Instance groups

2. Select one or more groups on the list that you want to delete.

3. Click Delete to delete the group and all of the VMs in the managed instance group.

gcloud

Use the delete command.

gcloud compute instance-groups managed delete INSTANCE_GROUP_NAME \
    --zone ZONE

REST

Call the delete method for a zonal or regional MIG resource. If the MIG has an attached autoscaler, you must first delete the autoscaler using the autoscalers.delete method or regionAutoscalers.delete method.

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

If the instance group is a regional managed instance group, replace zones/ZONE with regions/REGION.

What's next

• Learn about Getting, listing, and deleting instance templates