[[["易于理解","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-08-20。"],[[["\u003cp\u003eApp Engine standard environment services can connect directly to a Shared VPC network using Serverless VPC Access, enabling access to resources like Compute Engine VMs and Memorystore instances with internal IP addresses.\u003c/p\u003e\n"],["\u003cp\u003eServerless VPC Access incurs a monthly charge, and is not compatible with the URL Fetch service, requiring the use of sockets instead.\u003c/p\u003e\n"],["\u003cp\u003eConnectors for Serverless VPC Access can be configured either in each service project for isolation and independent management, or in the host project for centralized management and IP address conservation.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring connectors in service projects offers advantages such as dedicated bandwidth, easier chargebacks, enhanced security, and team independence.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring connectors in the host project offers advantages such as centralized network management, IP address space conservation, reduced maintenance, and potential cost savings during idle time.\u003c/p\u003e\n"]]],[],null,["# Connecting to a Shared VPC network\n\nIf your organization uses [Shared VPC](/vpc/docs/shared-vpc), you can\nconnect App Engine standard environment services directly to your Shared VPC network\nby using [Serverless VPC Access](/vpc/docs/serverless-vpc-access).\nThis allows a standard environment service to access resources in your\nShared VPC network, such as Compute Engine VM instances,\nMemorystore instances, and any other resources with an internal IP\naddress.\n\nServerless VPC Access connectors incur a monthly charge. For more information, see Serverless VPC Access\n[pricing](/vpc/pricing#serverless-vpc-pricing).\n\nIf your organization does not use Shared VPC, see\n[Connect to a VPC network](/appengine/docs/legacy/standard/go111/connecting-vpc).\n\n\u003cbr /\u003e\n\n| **Note:** Serverless VPC Access is not compatible with the URL Fetch service. To use Serverless VPC Access, disable the URL Fetch default by [using sockets](/appengine/docs/legacy/standard/go111/sockets), and discontinue any explicit use of the [`urlfetch`](/appengine/docs/legacy/standard/go111/urlfetch/reference) package.\n\nComparison of configuration methods\n-----------------------------------\n\nFor Shared VPC, Serverless VPC Access connectors can be\nconfigured in two different ways. You can either set up connectors in each\nservice project that has standard environment resources that need access\nto your network, or you can set up shared connectors in the host project. There\nare advantages to each method. \n\n### Service projects\n\nAdvantages of creating connectors in the service projects:\n\n- **Isolation:** Each connector has dedicated bandwidth and is unaffected by bandwidth use of connectors in other service projects. This is good if you have a service that experiences spikes in traffic, or if you need to ensure that each service project is unaffected by connector use of other service projects.\n- **Chargebacks:** Charges incurred by connectors are associated with the service project containing the connector. This enables easier chargebacks.\n- **Security:** Allows you to follow the \"principle of least privilege.\" Connectors must be granted access to the resources in your Shared VPC network that they need to reach. By creating a connector in the service project, you can limit what the services in the project can access by using firewall rules.\n- **Team independence:** Reduces dependency on the host project administrator. Teams can create and manage the connectors associated with their service project. A user with the Compute Engine [Security Admin](/compute/docs/access/iam#compute.securityAdmin) role or a custom [Identity and Access Management (IAM)](/iam) role with the [`compute.firewalls.create`](/compute/docs/reference/rest/v1/firewalls/insert#iam-permissions) permission enabled for the host project must still manage firewall rules for the connector.\n\nTo set up connectors in service projects, see\n[Configure connectors in service projects](/appengine/docs/legacy/standard/go111/shared-vpc-service-projects).\n\n### Host project\n\nAdvantages of creating connectors in the host project:\n\n- **Centralized network management:** Aligns with the Shared VPC model of centralizing network configuration resources in the host project.\n- **IP address space:** Preserves more of your IP address space. Connectors require an IP address for each instance, so having fewer connectors (and fewer instances in each connector) uses fewer IP addresses. This is good if you are concerned about running out of IP addresses.\n- **Maintenance:** Reduces maintenance, because each connector you create may be used by multiple service projects. This is good if you are concerned about maintenance overhead.\n- **Cost for idle time:** Can reduce the amount of connector idle time and associated cost. Connectors incur costs even when they are not serving traffic (see [pricing](/vpc/pricing#serverless-vpc-pricing)). Having fewer connectors may reduce the amount of resource you pay for when not serving traffic, depending on your connector type and number of instances. This is often cost effective if your use case involves a large number of services, and the services are used infrequently.\n\nTo set up connectors in the host project, see\n[Configure connectors in the host project](/appengine/docs/legacy/standard/go111/shared-vpc-host-project)."]]
