Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to delete the an AlloyDB primary instance or
a read pool instance from an AlloyDB cluster.
Points to remember when you delete an AlloyDB instance:
When you delete an AlloyDB instance, it does not automatically delete the data in the storage layer.
After you delete the AlloyDB primary instance, you continue to incur the cost of the AlloyDB storage.
If you create the primary instance in the same cluster from which you deleted the primary instance, the data becomes readily available and accessible from the primary instance, without any need to restore.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThis guide details the process for deleting an AlloyDB primary instance or a read pool instance from an AlloyDB cluster.\u003c/p\u003e\n"],["\u003cp\u003eDeleting an AlloyDB instance does not remove the data from the storage layer, and storage costs will persist after deletion of the primary instance.\u003c/p\u003e\n"],["\u003cp\u003eIf a deleted primary instance is recreated in the same cluster, its data will be immediately available without needing restoration.\u003c/p\u003e\n"],["\u003cp\u003eYou cannot delete an AlloyDB primary instance if there are any read pool instances within that cluster.\u003c/p\u003e\n"],["\u003cp\u003eTo delete an instance, you must have appropriate IAM roles such as \u003ccode\u003eroles/alloydb.admin\u003c/code\u003e, \u003ccode\u003eroles/owner\u003c/code\u003e, or \u003ccode\u003eroles/editor\u003c/code\u003e, and you can perform this action using the Google Cloud console or the gcloud CLI.\u003c/p\u003e\n"]]],[],null,["# Delete an instance\n\nThis page describes how to delete the an AlloyDB primary instance or\na read pool instance from an AlloyDB cluster.\n\nPoints to remember when you delete an AlloyDB instance:\n\n- When you delete an AlloyDB instance, it does not automatically delete the data in the storage layer.\n- After you delete the AlloyDB primary instance, you continue to incur the cost of the AlloyDB storage.\n- If you create the primary instance in the same cluster from which you deleted the primary instance, the data becomes readily available and accessible from the primary instance, without any need to restore.\n\n| **Note:** You cannot delete the primary instance if the cluster contains any read pool instances.\n\n\nBefore you begin\n----------------\n\n- The Google Cloud project you are using must have been [enabled to access AlloyDB](/alloydb/docs/project-enable-access).\n- You must have one of these IAM roles in the Google Cloud project you are using:\n - `roles/alloydb.admin` (the AlloyDB Admin predefined IAM role)\n - `roles/owner` (the Owner basic IAM role)\n - `roles/editor` (the Editor basic IAM role)\n\n If you don't have any of these roles, contact your Organization Administrator to request\n access.\n\n\u003cbr /\u003e\n\nProcedure\n---------\n\n### Console\n\n1. In the Google Cloud console, go to the **Clusters** page.\n\n [Go to Clusters](https://console.cloud.google.com/alloydb/clusters)\n2. Click a cluster in the **Resource Name** column.\n3. In the **Overview** page, go to the **Instances in your cluster** section, choose the instance that you want to delete, and click **Delete**.\n4. In the dialog that appears, enter the instance's ID, and click **Delete**.\n\n### gcloud\n\nTo use the gcloud CLI, you can\n[install and initialize](/sdk/docs/install) the Google Cloud CLI, or you\ncan use [Cloud Shell](/shell/docs/using-cloud-shell).\n\nUse the `instances delete` command to delete an instance. \n\n```\ngcloud alloydb instances delete INSTANCE_ID \\\n --region=REGION_ID \\\n --cluster=CLUSTER_ID \\\n --project=PROJECT_ID\n```\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: The ID of the instance.\n- \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e: The region where the instance is placed.\n- \u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e: The ID of the cluster where the instance is placed.\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: The ID of the project where the cluster is placed."]]