[[["易于理解","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-05。"],[],[],null,["# Options for connecting to multiple VPC networks\n\nThis page describes how Virtual Private Cloud (VPC) networks can access VLAN\nattachments for Dedicated Interconnect or Partner Interconnect\nthat are located in a different VPC network. Both\nShared VPC and VPC Network Peering support this functionality.\n\nFor VPC networks that don't use Shared VPC\nor VPC Network Peering, you must create additional VLAN attachments:\n\n- [Create VLAN attachments for Dedicated Interconnect](/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments)\n- [Create VLAN attachments for Partner Interconnect](/network-connectivity/docs/interconnect/how-to/partner/creating-vlan-attachments)\n- [Use Dedicated Interconnect connections in other projects](/network-connectivity/docs/interconnect/how-to/dedicated/using-interconnects-other-projects)\n\n| **Note:** If you don't use a Shared VPC network, you can create multiple VLAN attachments and Cloud Routers for other projects and networks. However, this method is less cost efficient than using a Shared VPC network.\n\nUse Cloud Interconnect with Shared VPC\n--------------------------------------\n\nTo share your VLAN attachment in a project with other VPC\nnetworks, you can use Shared VPC. Using Shared VPC is\npreferable if you need to create many projects and would like to prevent\nindividual project owners from managing their connectivity back to your\non-premises network.\n\nIn this scenario, the host project contains a common Shared VPC network\nthat VMs in service projects can use. Because VMs in service projects use this\nnetwork, [Service Project Admins](/vpc/docs/shared-vpc#svc_proj_admins) don't\nneed to create other VLAN attachments or Cloud Routers in the service\nprojects.\n\nYou must create VLAN attachments and Cloud Routers for a Cloud Interconnect\nconnection *only* in the Shared VPC host project. The combination of a\nVLAN attachment and its associated Cloud Router are unique to a given\nShared VPC network.\n\nService Project Admins can create VMs in subnets that exist in a host\nproject's Shared VPC network based on the permissions that they have to\nthe host project. VMs that use the Shared VPC network can use the\ncustom dynamic routes for VLAN attachments available to that network.\n\nFor more information about setting up a Shared VPC network, see\nthe [Shared VPC overview](/vpc/docs/shared-vpc) and\n[Provisioning Shared VPC](/vpc/docs/provisioning-shared-vpc).\n\nUse Cloud Interconnect with VPC Network Peering\n-----------------------------------------------\n\nIf you have only a few projects (two to three) or if you need to connect\nVPC networks between different organizations, you can use\nVPC Network Peering. With VPC Network Peering, you land VLAN attachments\nin one VPC network and then peer that network with one or more\nother VPC networks that you want to have access to your\non-premises network.\n\nWe recommend using Shared VPC over using VPC Network Peering\nbecause Shared VPC is easier to configure and scale.\n\nFor information about VPC Network Peering, see the\n[VPC Network Peering overview](/vpc/docs/vpc-peering).\n\nWhat's next\n-----------\n\n- To learn more about Cloud Interconnect options, see the\n [Cloud Interconnect overview](/network-connectivity/docs/interconnect/concepts/overview).\n\n- To help you solve common issues that you might encounter when using\n Cloud Interconnect, see\n [Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting)."]]
