Looker (Google Cloud core) enabled for Private Service Connect documentation

To create and set up a private IP Looker (Google Cloud core) instance with Private Service Connect enabled, use the following documentation in the order presented here:

1. Looker (Google Cloud core) networking options
2. Use Private Service Connect with Looker (Google Cloud core)
3. Create OAuth authorization credentials for a Looker (Google Cloud core) instance
4. Create a Looker (Google Cloud core) Private Service Connect instance
5. Set up northbound access to a Looker (Google Cloud core) instance using Private Service Connect (if you are accessing your Looker (Google Cloud core) instance from on-premises using hybrid networking)

What's next?

• Connecting Looker (Google Cloud core) to your database
• Prepare a Looker (Google Cloud core) instance for users
• Authentication methods for Looker (Google Cloud core)

• Codelab: Looker (Google Cloud core) PSC Southbound HTTPS Internet NEG SMTP

  In this codelab, you will create a southbound connection to Looker (Google Cloud core)'s SMTP service using an internal TCP proxy load balancer and internet network endpoint group (NEG) with the FQDN notifications-pa.googleapis.com invoked from a Looker (Google Cloud core) PSC as a Service Consumer.

• Codelab: Looker (Google Cloud core) PSC Southbound access to Cloud SQL PSC

  In this codelab, you will perform a southbound connection to Cloud SQL deployed with Private Service Connect as a Service Producer.

• Codelab: Looker (Google Cloud core) PSC Southbound SSH Internet NEG

  In this codelab, you will perform a southbound SSH connection to GitHub using an internal TCP proxy load balancer and internet network endpoint group (NEG) invoked from Looker (Google Cloud core) PSC as a Service Consumer.

• Codelab: Looker (Google Cloud core) PSC Southbound HTTPS Internet NEG

  In this codelab, you will perform a southbound HTTPS connection to GitHub using an internal TCP proxy load balancer and internet network endpoint group (NEG) invoked from a Looker (Google Cloud core) PSC as a Service Consumer.

• Codelab: Looker (Google Cloud core) PSC Southbound Hybrid NEG to on-premises

  In this codelab, you will perform a southbound connection to an on-premises Postgres database over H-VPN using an internal TCP proxy load balancer and hybrid network endpoint group (NEG) invoked from a Looker (Google Cloud core) PSC as a Service Consumer.

• Codelab: Looker (Google Cloud core) PSC Northbound Regional External L7 ALB

  In this codelab, you will create an L7 regional application load balancer and Private Service Connect backend to gain northbound access to Looker (Google Cloud core). Northbound access to Looker (Google Cloud core) requires that the Consumer VPC be allowlisted to the Looker (Google Cloud core) PSC instance.