Nama host publik untuk endpoint regional memiliki format berikut:
SERVICE.REGION.rep.DOMAIN.
Sebaiknya gunakan nama host publik untuk menentukan layanan target dalam konfigurasi endpoint Private Service Connect Anda.
Subnet yang Anda tentukan saat membuat endpoint adalah subnet
reguler. Alamat IP yang ditetapkan ke endpoint
adalah alamat IP internal regional.
Jika menggunakan VPC Bersama, Anda dapat membuat endpoint di project host atau project layanan.
Secara default, endpoint hanya dapat diakses oleh klien yang berada di region yang sama dan jaringan VPC yang sama (atau jaringan VPC Bersama) dengan endpoint. Untuk mengetahui informasi tentang cara menyediakan endpoint di region lain, lihat Akses global.
Arsitektur
Endpoint Private Service Connect yang memiliki target endpoint regional mengarah ke lampiran layanan yang telah dibuat oleh Google untuk mengarahkan traffic ke endpoint layanan regional.
Klien di region yang sama dengan endpoint dapat mengirim traffic ke endpoint. Anda
juga dapat mengakses endpoint dari jaringan
yang terhubung di
region yang sama. Jika Anda ingin mengakses endpoint dari region lain, konfigurasi
akses global.
Gambar 1.
Endpoint memungkinkan konsumen layanan mengirimkan traffic dari jaringan VPC konsumen ke endpoint layanan regional untuk Google API yang didukung melalui lampiran layanan yang dikelola oleh Google (klik untuk memperbesar).
Akses global
Saat membuat endpoint, Anda dapat mengonfigurasi akses global. Akses global memungkinkan klien di region lain mengakses endpoint. Endpoint juga dapat diakses
dari jaringan
yang terhubung.
Gambar 2.
Endpoint dengan akses global yang diaktifkan dapat diakses oleh klien di
region lain, termasuk oleh klien di jaringan yang terhubung (klik untuk memperbesar).
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 UTC."],[],[],null,["# About accessing regional endpoints through Private Service Connect endpoints\n============================================================================\n\nThis page provides an overview of using\n[Private Service Connect endpoints to access regional\nendpoints](/vpc/docs/access-regional-google-apis-endpoints) for\n[supported Google APIs in supported regions](/vpc/docs/regional-service-endpoints).\n\nConsider using regional endpoints if you want to ensure that in-transit data\nremains in a particular region.\n\nFor information about other Private Service Connect configurations,\nsee [Private Service Connect overview](/vpc/docs/private-service-connect).\n\nFeatures and compatibility\n--------------------------\n\nThis table summarizes the features that are supported by endpoints that are used\nto access regional endpoints for Google APIs.\n\n\n\u003cbr /\u003e\n\nSpecifications\n--------------\n\n- Public hostnames for regional endpoints have the following format:\n \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e`.`\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e`.rep.`\u003cvar translate=\"no\"\u003eDOMAIN\u003c/var\u003e.\n We recommend using the public hostnames to specify the target service in\n your Private Service Connect endpoint configuration.\n\n | **Note:** The private hostname format is also supported: \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e`.`\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e`.p.rep.`\u003cvar translate=\"no\"\u003eDOMAIN\u003c/var\u003e.\n- The subnet that you specify when you create a endpoint is a [regular\n subnet](/vpc/docs/subnets#purpose). The IP address assigned to the endpoint\n is a regional internal IP address.\n\n- If you're using Shared VPC, you can create the endpoint in either\n the host project or a service project.\n\n- By default, endpoints can be accessed only by clients that are in the same\n region and the same VPC network (or Shared VPC\n network) as the endpoint. For information about making endpoints available\n in other regions, see [Global access](#global-access).\n\nArchitecture\n------------\n\nPrivate Service Connect endpoints that have a\nregional endpoint target point to a service attachment that has been created\nby Google to direct traffic to the regional service endpoint.\n\nClients in the same region as the endpoint can send traffic to the endpoint. You\ncan also access the endpoint from [connected\nnetworks](/vpc/docs/access-regional-google-apis-endpoints#hybrid-access) in the\nsame region. If you want to access the endpoint from other regions, configure\n[global access](#global-access).\n[](/static/vpc/images/psc-endpoint-service-rep.svg) **Figure 1.**\nAn endpoint lets service consumers send traffic from the consumer's\nVPC network to regional service endpoints for supported\nGoogle APIs through a service attachment that is managed by Google (click\nto enlarge).\n\nGlobal access\n-------------\n\nWhen you create an endpoint, you can configure global access. Global access lets\nclients in other regions access the endpoint. The endpoint is also accessible\nfrom [connected\nnetworks](/vpc/docs/access-regional-google-apis-endpoints#hybrid-access).\n[](/static/vpc/images/psc-multi-region-rep.svg) **Figure 2.**\nAn endpoint with global access enabled can be accessed by clients in\nanother region, including by clients in connected networks (click to enlarge).\n\nSupported regions and services\n------------------------------\n\nFor a list of supported regions and services, see [Regional service\nendpoints](/vpc/docs/regional-service-endpoints).\n\nPricing\n-------\n\nFor pricing information, see\n[Virtual Private Cloud pricing](/vpc/pricing#psc-forwarding-rule-regional-end-apis).\n\nQuotas\n------\n\nSee the **Number of Regional Endpoints per project per region** quota in\n[Quotas and limits](/vpc/docs/quota#regional-per-project-regional-endpoints).\n\nWhat's next\n-----------\n\n- Create a Private Service Connect endpoint to [access regional\n Google APIs](/vpc/docs/access-regional-google-apis-endpoints).\n- Learn more about [Private Service Connect](/vpc/docs/private-service-connect)."]]
