Public hostnames for regional endpoints have the following format: SERVICE . REGION .rep. DOMAIN . We recommend using the public hostnames to specify the target service in your Private Service Connect endpoint configuration.

Note: The private hostname format is also supported: SERVICE . REGION .p.rep. DOMAIN .
The subnet that you specify when you create an endpoint is a regular subnet . The IP address assigned to the endpoint is a regional internal IP address.
By default, endpoints can be accessed only by clients that are in the same region and the same VPC network (or Shared VPC network) as the endpoint. For information about making endpoints available in other regions, see Global access .
For information about creating this configuration in a Shared VPC network, see Shared VPC .

Architecture

Private Service Connect endpoints that have a regional endpoint target point to a service attachment that has been created by Google to direct traffic to the regional service endpoint.

Clients in the same region as the endpoint can send traffic to the endpoint. You can also access the endpoint from connected networks in the same region. If you want to access the endpoint from other regions, configure global access .

Figure 1. An endpoint lets service consumers send traffic from the consumer's VPC network to regional service endpoints for supported Google APIs through a service attachment that is managed by Google (click to enlarge).

Global access

When you create an endpoint, you can configure global access. Global access lets clients in other regions access the endpoint. The endpoint is also accessible from connected networks .

Figure 2. An endpoint with global access enabled can be accessed by clients in another region, including by clients in connected networks (click to enlarge).

Supported regions and services

For a list of supported regions and services, see Regional service endpoints .

Shared VPC

Service Project Admins can create Private Service Connect endpoints in Shared VPC service projects that use IP addresses from Shared VPC networks .

In general, we recommend that you create forwarding rules and their corresponding address resources in the same Google Cloud project. Using the same project helps to avoid issues when a project is deleted.

If you're creating an endpoint in a service project and using a reserved static IP address in the configuration, use or create an address resource in the service project. The address resource can reference an IP address from a subnet in the host project, or from the service project, if it contains subnets.

We don't recommend using an address resource from a host project to create an endpoint in a service project.

You must use the gcloud CLI or the API to create an endpoint in a service project, and this configuration requires additional permissions .

For more information, see Create a regional Private Service Connect endpoint in a Shared VPC service project .

Pricing

For pricing information, see Virtual Private Cloud pricing .

Quotas

See the Number of Regional Endpoints per project per regionquota in Quotas and limits .

What's next

Create a Private Service Connect endpoint to access regional Google APIs .
Learn more about Private Service Connect .

About accessing regional endpoints through Private Service Connect endpoints Stay organized with collections Save and categorize content based on your preferences.

Features and compatibility

Specifications