The requirements necessitate a private, cross-project service-to-service connection with explicit authorization—a capability perfectly addressed by Private Service Connect (PSC).
Internal Load Balancer: Ensures the service is isolated from the internet (Layer 7 Load Balancer for HTTP/S ML endpoint).
Private Service Connect (PSC): Allows a service (the model endpoint, exposed via the internal load balancer) in one VPC/project (producer) to be securely consumed by other VPCs/projects (consumers) using an internal IP address.
Defined List of Projects: PSC enables Explicit authorization, allowing the producer to define the allowed list of consumers that can establish a connection, directly meeting the granular restriction requirement.
Extracts:
"Private Service Connect provides... Explicit authorization. Private Service Connect provides an authorization model that gives consumers and producers granular control." (Source 2.4)
"Private Service Connect backends let Google Cloud load balancers send traffic through Private Service Connect to reach published services... Placing a load balancer in front of a managed service provides the consumer with more visibility and control..." (Source 2.4)
"Publish services by using Private Service Connect... Select the internal load balancer that hosts the service that you want to publish." (Source 2.3)
