An enterprise organization is deploying workloads in a Shared VPC network on Google Cloud. The infrastructure team must establish secure, private connectivity from compute instances in a service project to a third-party managed database service hosted in another Google Cloud tenant project. The third-party provider uses an internal IP address range that overlaps with the organization's subnet ranges, preventing the use of standard VPC Network Peering. Which network configuration should the Cloud Architect implement to meet these requirements?
- Create a Private Service Connect endpoint in the consumer Shared VPC that targets the published Service Attachment of the managed database provider.Answer
- BEstablish a VPC Network Peering connection between the Shared VPC and the third-party provider VPC network while disabling custom route export.
- CProvision a Dedicated Interconnect connection directly between the consumer project and the third-party provider project.
- DConfigure a VPC Service Controls perimeter around the consumer Shared VPC and grant the third-party service account IAM access.
Answer
Create a Private Service Connect endpoint in the consumer Shared VPC that targets the published Service Attachment of the managed database provider.
Private Service Connect endpoints allow consumers to access services published in another VPC using a private IP address allocated from the consumer's own local VPC subnet. Because traffic is translated through the endpoint and Service Attachment, overlapping IP ranges between the consumer and producer VPC networks do not block communication.
Step-by-Step Solution
Key Concept
Private Service Connect Endpoint for Cross-Tenant VPC Access