[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-01。"],[],[],null,["# VPC networks management in service perimeters\n\nThis document provides an overview of how you can manage VPC networks and VPC Service Controls.\n\nYou can create separate perimeters for each of the VPC\nnetworks in your host project instead of creating a single perimeter for the entire\nhost project. For example, if your host project contains separate VPC networks\nfor development, test, and production environments, you can create separate perimeters\nfor the development, test, and production networks.\n\nYou can also allow access from a VPC network that is not inside your\nperimeter to resources inside your perimeter by specifying an ingress rule.\n\nThe following diagram shows an example of a VPC networks host project and how\nyou can apply a different perimeter policy for each VPC network:\n\n- **VPC networks host project**. The host project contains VPC network 1 and VPC network 2, each containing virtual machines VM A and VM B respectively.\n- **Service perimeters**. The service perimeters SP1 and SP2 contain BigQuery and Cloud Storage resources. As VPC network 1 is added to perimeter SP1, VPC network 1 can access resources in perimeter SP1 but cannot access resources in perimeter SP2. As VPC network 2 is added to perimeter SP2, VPC network 2 can access resources in perimeter SP2 but cannot access resources in perimeter SP1.\n\nManage VPC networks in a service perimeter\n------------------------------------------\n\nYou can perform the following tasks to manage VPC networks in a perimeter:\n\n- Add a single VPC network to a perimeter instead of adding an entire host project to the perimeter.\n- Remove a VPC network from a perimeter.\n- Allow a VPC network to access resources inside a perimeter by specifying an ingress policy.\n- Migrate from a single perimeter setup to a multiple perimeter setup and use dry-run mode to test the migration.\n\nLimitations\n-----------\n\nThe following are the limitations when you manage VPC networks in service perimeters:\n\n- You cannot add VPC networks that exists in an another organization to your service perimeter or specify them as an ingress source. To specify an VPC network that exists in an another organization as an ingress source, you must have the ([`roles/compute.networkViewer`](/compute/docs/access/iam#compute.networkViewer)) role.\n- If you delete a VPC network protected by a perimeter and then recreate a VPC network with the same name, the service perimeter does not protect the VPC network that you recreate. We recommend that you don't recreate a VPC network with the same name. To resolve this issue, create a VPC network with a different name and add it to the perimeter.\n- The limit for the number of VPC networks that you can have under an organization is 500.\n- If a VPC network has a custom subnet mode but if no subnets exist, then that VPC network cannot be added independently to VPC Service Controls. To add a VPC network to a perimeter, the VPC network must contain at least one subnet.\n\nWhat's next\n-----------\n\n- Learn about [rules to add VPC networks to service perimeters](/vpc-service-controls/docs/vpc-networks-rules)."]]
