이 페이지에서는 Cloud Run 서비스 또는 작업에서 공유 VPC 네트워크로 이그레스(아웃바운드) 트래픽을 전송하여 Compute Engine VM 인스턴스, Memorystore 인스턴스, 내부 IP 주소가 있는 모든 기타 리소스에 대한 액세스를 허용하는 방법을 설명합니다.
중앙 집중식 네트워크 관리: 호스트 프로젝트에서 네트워크 구성 리소스를 중앙 집중화하는 공유 VPC 모델과 일치합니다.
IP 주소 공간: IP 주소 공간을 더 많이 보존합니다. 커넥터는 인스턴스마다 IP 주소가 필요하므로 커넥터가 적고 각 커넥터의 인스턴스 수가 적을수록 IP 주소가 더 적게 사용됩니다. 이 방법은 IP 주소 부족이 우려되는 경우에 유용합니다.
유지보수: 생성한 각 커넥터가 여러 서비스 프로젝트에서 사용될 수 있으므로 유지보수가 줄어듭니다. 이 방식은 유지보수 오버헤드가 우려되는 경우에 유용합니다.
유휴 시간 비용: 커넥터 유휴 시간 및 관련 비용을 줄일 수 있습니다. 커넥터는 트래픽을 처리하지 않는 경우에도 비용이 발생합니다(가격 책정 참조). 커넥터 수가 적으면 커넥터 유형 및 인스턴스 수에 따라 트래픽을 제공하지 않을 때 비용을 지불하는 리소스 양이 줄어들 수 있습니다. 이 방법은 많은 서비스가 포함되며 서비스가 자주 사용되지 않는 사용 사례에 비용 효율적입니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Connect to a Shared VPC network\n\nThis page describes how to send egress (outbound) traffic from a Cloud Run\nservice or job to a [Shared VPC](/vpc/docs/shared-vpc) network, allowing\naccess to Compute Engine VM instances, Memorystore instances, and any\nother resources with an internal IP address.\n\nIf your organization does not use Shared VPC, see\n[Send traffic to a standard VPC network](/run/docs/configuring/connecting-vpc).\n\nComparison of configuration methods\n-----------------------------------\n\nConnecting to a Shared VPC network can be configured in different ways:\n\n#### Direct VPC egress\n\nYou can use Direct VPC egress to send traffic to a Shared VPC network\nwithout the need for Serverless VPC Access connectors. To set up egress\n(outbound) traffic without a connector, see\n[Direct VPC egress with a Shared VPC network](/run/docs/configuring/shared-vpc-direct-vpc).\n\n#### Serverless VPC Access connectors\n\nIf you need to use Serverless VPC Access connectors, you can set them\nup in [Shared VPC](/vpc/docs/shared-vpc) service projects that have\nCloud Run resources needing access to your network, or you can\nset up shared connectors in the Shared VPC host project. There are\nadvantages to each method. \n\n### Service projects\n\nAdvantages of creating connectors in the Shared VPC 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](/run/docs/configuring/shared-vpc-service-projects).\n\n### Host project\n\nAdvantages of creating connectors in the Shared VPC 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 can 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 can reduce the amount of resources 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](/run/docs/configuring/shared-vpc-host-project).\n| **Tip:** For a side-by-side comparison, see [Compare Direct VPC egress and VPC connectors](/run/docs/configuring/connecting-vpc)."]]
