Private Service Connect 엔드포인트를 통한 Vertex AI 서비스 액세스
컬렉션을 사용해 정리하기
내 환경설정을 기준으로 콘텐츠를 저장하고 분류하세요.
일부 Vertex AI 서비스 프로듀서는 Private Service Connect 엔드포인트를 통해 서비스에 연결해야 합니다.
이러한 서비스는 Vertex AI 액세스 방법 테이블에 나와 있습니다. 서비스 소비자의 온프레미스, 멀티 클라우드, VPC 워크로드에서 Google 관리형 Vertex AI 서비스로의 단방향 통신을 지원합니다. 클라이언트는 내부 IP 주소를 사용하여 엔드포인트에 연결합니다. Private Service Connect는 네트워크 주소 변환(NAT)을 수행하여 요청을 서비스에 라우팅합니다.
서비스 소비자는 자체 내부 IP 주소를 사용하여 VPC 네트워크를 벗어나거나 소비자 엔드포인트를 만들어 외부 IP 주소를 사용하지 않고도 이러한 Vertex AI 서비스에 액세스할 수 있습니다.
엔드포인트는 Private Service Connect 전달 규칙을 사용하여 또 다른 VPC 네트워크의 서비스에 연결됩니다.
비공개 연결의 서비스 프로듀서 측에는 서비스 리소스가 프로비저닝되는 VPC 네트워크가 있습니다. 이 네트워크는 사용자 전용으로 구축되고 사용자의 리소스만 포함합니다.
다음 다이어그램은 공유 VPC 배포의 일부로 서비스 프로젝트(serviceproject)에서 Vector Search API가 사용 설정되고 관리되는 벡터 검색 아키텍처를 보여줍니다. 벡터 검색 Compute Engine 리소스는 서비스 프로듀서의 VPC 네트워크에 Google 관리 Infrastructure as a Service(IaaS)로 배포됩니다.
[[["이해하기 쉬움","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,["# About accessing Vertex AI services through Private Service Connect endpoints\n\nSome Vertex AI service producers require you to connect to their\nservices through\n[Private Service Connect endpoints](/vpc/docs/private-service-connect#endpoints).\nThese services\nare listed in the\n[Vertex AI access methods](/vertex-ai/docs/general/netsec-overview#access-methods)\ntable. They support unidirectional communication\nfrom a service consumer's on-premises, multicloud, and VPC workloads to\nGoogle-managed Vertex AI services. Clients connect to the endpoint\nby using internal IP addresses. Private Service Connect performs\nnetwork address translation (NAT) to route requests to the service.\n\nService consumers can use their own internal IP addresses to access these\nVertex AI services without leaving their VPC networks\nor using external IP addresses by creating a consumer endpoint.\nThe endpoint connects to services in another VPC network using a\nPrivate Service Connect forwarding rule.\n\nOn the service producer's side of the private connection, there is a\nVPC network where your service resources are provisioned. This\nnetwork is created exclusively for you and contains only your resources.\n\nThe following diagram shows a Vector Search architecture in which the\nVector Search API is enabled and managed in a service project\n(`serviceproject`) as part of a [Shared VPC](/vpc/docs/shared-vpc)\ndeployment. The Vector Search Compute Engine resources\nare deployed as a Google-managed Infrastructure-as-a-Service (IaaS) in the\nservice producer's VPC network.\n\nPrivate Service Connect endpoints are deployed in the service\nconsumer's VPC network (`hostproject`) for index query, in\naddition to\n[Private Service Connect endpoints for Google APIs](/vertex-ai/docs/general/googleapi-access-methods#psc)\nfor private index creation.\n\nFor more information, see\n[Private Service Connect endpoints](/vpc/docs/private-service-connect#endpoints).\n\nBefore you configure Private Service Connect endpoints, learn about\naccess\n[considerations](/vpc/docs/about-accessing-vpc-hosted-services-endpoints#limitations).\n\nPrivate Service Connect endpoint deployment options\n---------------------------------------------------\n\nA Private Service Connect service attachment is generated from the\nproducer service (such as Vertex AI). As a consumer, you can gain\naccess to the service producer by deploying a consumer endpoint in one or more\nVPC networks.\n\nDeployment considerations\n-------------------------\n\nThe following sections discuss considerations for communication from your\non-premises, multicloud, and VPC workloads to Google-managed\nVertex AI services.\n\n### Private Service Connect backends\n\nGoogle does not support using\n[Private Service Connect backends](/vpc/docs/access-apis-managed-services-private-service-connect-backends)\nwith Vertex AI online prediction endpoints.\n\n### IP advertisement\n\n- When you use Private Service Connect to connect to services in\n another VPC network, you choose an IP address from a [regular\n subnet](/vpc/docs/subnets#purpose) in your VPC network.\n\n- By default, the Cloud Router will advertise regular VPC\n subnets unless custom advertisement mode is configured. For more\n information, see [Custom advertisement\n mode](/network-connectivity/docs/router/concepts/advertised-routes#overview-am-custom).\n\n- The IP address for the consumer endpoint must be in the same region as the\n service producer's service attachment. For more information, see [Service\n attachments](/vpc/docs/private-service-connect#service-attachments) and\n [Access published services through\n endpoints](/vpc/docs/configure-private-service-connect-services).\n\n### Firewall rules\n\nYou must update the firewall rules for the VPC\nnetwork that connects your on-premises and multicloud environments\nto Google Cloud to allow egress traffic to the\nPrivate Service Connect endpoint subnet. For more information, see\n[Firewall rules](/vpc/docs/manage-security-private-service-connect-consumers#firewall-rules)."]]
