Looker (Google Cloud core) outbound access to external services using Private Service Connect

You can set up secure outbound connections (also known as southbound access) from Looker (Google Cloud core) to external services by using Private Service Connect. The following Codelabs guide you through configuring these connections so that your Looker (Google Cloud core) instance can securely interact with external resources while maintaining private network connectivity.

Any self-hosted or on-premise repository or service that Looker (Google Cloud core) connects to through southbound access must be configured with a publicly trusted SSL certificate.

• 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 Southbound HTTPS Internet NEG GitLab Self-Managed

  In this codelab, you will perform a southbound HTTPS connection to your GitLab self-managed environment by using an internal TCP proxy load balancer and internet network endpoint group (NEG) that is invoked from Looker (Google Cloud core) Private Service Connect as a service consumer.

Troubleshooting

For information about troubleshooting southbound connections, see the Troubleshooting southbound connections documentation.