Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to remove a private services access allocated range
that you have been using for an AlloyDB.
When you create an AlloyDB cluster or instance in a region that
doesn't yet have any clusters or instances, AlloyDB creates a
subnet in that region in a Google-owned and managed project, which is called a tenant
project. The subnet is connected to your network using the private service
connection VPC Network Peering.
If you decide to remove all an AlloyDB resources associated with
an allocated range, as well as the allocated range, follow the
steps in this document to ensure that your network resources are cleaned up.
[[["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 removing a private services access allocated range used by AlloyDB resources.\u003c/p\u003e\n"],["\u003cp\u003eRemoving an allocated range requires first deleting all associated AlloyDB resources.\u003c/p\u003e\n"],["\u003cp\u003eAfter deleting AlloyDB resources, the allocated range must be removed from the private service connection.\u003c/p\u003e\n"],["\u003cp\u003eFinally, users must contact support to have subnets created by private services access in the tenant project deleted.\u003c/p\u003e\n"],["\u003cp\u003eThis operation requires proper IAM roles and permissions to access the allocated range.\u003c/p\u003e\n"]]],[],null,["# Remove a private services access allocated range\n\nThis page describes how to remove a private services access allocated range\nthat you have been using for an AlloyDB.\n\nWhen you create an AlloyDB cluster or instance in a region that\ndoesn't yet have any clusters or instances, AlloyDB creates a\nsubnet in that region in a Google-owned and managed project, which is called a *tenant\nproject*. The subnet is connected to your network using the private service\nconnection VPC Network Peering.\n\nIf you decide to remove all an AlloyDB resources associated with\nan allocated range, as well as the allocated range, follow the\nsteps in this document to ensure that your network resources are cleaned up.\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- To increase the IP address range, you also must have these IAM permissions:\n - `compute.networks.list`\n - `compute.addresses.create`\n - `compute.addresses.list`\n - `servicenetworking.services.addPeering`\n\n\u003cbr /\u003e\n\nRemove an allocated range\n-------------------------\n\nTo remove an allocated range associated with your an AlloyDB\nresources, follow these steps:\n\n1. [Delete all AlloyDB resources](/alloydb/docs/instance-delete) that are using the allocated range.\n2. [Remove the allocated range from the private service connection](/vpc/docs/configure-private-services-access#modifying-connection).\n3. [Delete the allocated range](/vpc/docs/configure-private-services-access#deleting-allocation).\n4. Contact [Support](/support) and ask them to delete the subnets that private services access created on the tenant project."]]
