GCP Private Service Connect and other GCP Private Access methods

1. How to connect to VPNs
2. GCP Private Service Connect and other GCP Private Access methods
3. Use GCP Cloud DNS from AWS
4. Use AWS Route53 from GCP

This is the second story in the above posts.

In a previous blog post, I introduced how to connect VPNs between AWS and GCP. However, just because it is VPN-linked, the traffic that was going on the NAT Gateway does not immediately move to the VPN. I have only made a foundation for network communication based on IP. In fact, changing an existing route to a VPN requires additional work.

If you don’t use NAT Gateway when you use googleapis.com , you can even save money.

• First, in order to access the GCP Managed Service (BigQuery, Pub/Sub, etc.) through VPN in AWS mentioned in the first scenario, two tasks are required.

1. Configures Private Service Connect (PSC) to access GCP Managed Service with Private IP
2. Set up Private DNS Zone for googleapis.com and register records for PSC IP

First of all, I will briefly introduce how to access Google Managed Google Services (APIs) privately from a GCP VPC, including GCP Private Service Connect.

GCP Private Access options for Google APIs

1. Private Google Access