In this Course, we look at configuring Private Google access starting with an overview of what it is, before moving on to networking and DNS configuration as well as routing and firewalls. We'll then walk you through a guided demonstration of how to enable Private Google Access so that you get a practical understanding of the service.
We'll also look at Private Google Access for on-premises hosts, covering domain names, virtual IPs, networking and DNS configuration, and permissions. We'll wrap with Private Services Access and Serverless VPC Access.
Learning Objectives
- Learn about Private Google Access, its networking and DNS requirements, and how to configure routing and firewalls to use it
- Learn about Private Google Access for on-premises hosts, its requirements, its permissions, and how to use it
- Get a high-level overview of Private Services Access and Serverless VPC Access
Intended Audience
This Course is intended for those who wish to learn how to configure private Google access on the GCP platform.
Prerequisites
To get the most out of this Course, you should have a basic knowledge of GCP.
Welcome to private services access. While the main topic of this course is private Google Access and private Google Access for on-prem hosts, I thought it would be important, for completeness, to touch on the other two types of private access that are available. These other types of private access include private services access and serverless VPC access. In this lesson here, we will take a quick, high level look at what private services access is and what it offers.
There will be times when you have VM instances on a VPC network that need to access services that are hosted on another VPC network that you may or may not control. In some instances, these services will only have internal IP addresses associated with them.
Private services access is a private connection between your VPC network in Google cloud and another network. That other network can be a Google owned network, or a network owned by some other third-party. This connectivity is created through a VPC Network Peering connection.
Generally speaking, you use this private connection, or Private Services Access, to connect to specific Google services or third-party services without the need to assign an external IP address to your Google cloud resources or to the third-party resources. Private services access essentially allows access to such external services without the need for external IP addresses.
To learn more about Private Services Access, visit the URL that you see on your screen:
https://cloud.google.com/vpc/docs/configure-private-services-access
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.