Google Cloud Private Service Connect limitations and considerations

Learn more about the Google Cloud Private Service Connect limits and considerations that apply to Reltio Private Link.

This topic summarizes the key limits and ownership boundaries for using Google Cloud Private Service Connect with Reltio Private Link.

Limitations and considerations

The following table lists the Private Service Connect (PSC) limitations and considerations that apply to Reltio Private Link.


Area	Details
Regional scope	PSC operates within a single region and does not route traffic globally across all access points.
Endpoint relationship	One PSC endpoint connects to one service attachment.
Service attachment reuse	One service attachment can serve multiple PSC endpoints.
Region alignment	Reltio-managed internal HTTPS load balancing and the PSC service attachment must align by region.
Public access	Public access remains unchanged for customers who don't use Private Link.
Environment hostname	The same Reltio environment hostname is used for both public and private access.

The following table summarizes ownership boundaries between Reltio and your organization.


Owner	Responsibility
Reltio	Adds the customer Google Cloud project under accepted projects for the service attachment. Publishes the PSC service attachment and provides the service attachment URL.
Customer	Creates and manages the PSC endpoint in their Google Cloud VPC. Configures firewall rules, routing, private DNS, and the A record for the Reltio environment hostname. Maintains the private endpoint lifecycle, including updates and decommissioning.

For more information about generic PSC concepts, see Private Service Connect in the Google Cloud documentation.