A sub-rede especificada ao criar um endpoint é uma sub-rede
normal. O endereço IP atribuído ao endpoint
é um endereço IP interno regional.
Se você usa a VPC compartilhada, pode criar o endpoint
o projeto host ou um projeto de serviço.
Por padrão, os endpoints podem ser acessados apenas por clientes que estão no mesmo
e a mesma rede VPC, ou VPC compartilhada
rede) como endpoint. Para informações sobre como disponibilizar endpoints em outras regiões, consulte Acesso global.
Arquitetura
Os endpoints do Private Service Connect que têm um
endpoint regional para um anexo de serviço criado
pelo Google para direcionar o tráfego ao endpoint do serviço regional.
Os clientes na mesma região do endpoint podem enviar tráfego para ele. Também
é possível acessar o endpoint a partir de redes
conectadas na
mesma região. Para acessar o endpoint de outras regiões, configure o
acesso global.
Figura 1.
Um endpoint permite que os consumidores de serviço enviem tráfego da rede VPC
do consumidor para endpoints de serviços regionais para APIs do Google
compatíveis por meio de um anexo de serviço gerenciado pelo Google. (clique para ampliar)
Acesso global
Ao criar um endpoint, é possível configurar o acesso global. O acesso global permite
que clientes em outras regiões acessem o endpoint. O endpoint também pode ser acessado nas redes conectadas.
Figura 2.
Um endpoint com acesso global ativado pode ser acessado por clientes em
outra região, inclusive por clientes em redes conectadas (clique para ampliar).
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2024-12-06 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)."]]
