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.
Hello, and welcome back. In this brief demonstration, we are going to walk through the process of enabling Private Google access for one of our VPC networks. So on the screen here, you can see I'm logged in to my portal, and I'm logged in as an admin, and I'm at my dashboard. To enable Private Google access for a VPC network, what I'm going to do first is, browse to the hamburger here and go down to VPC networks.
Now, if we scroll down in this list of networks, what we're going to do is see this test network, with this default sub-net? This is the network that we're going to enable Private Google access on. Now, to do that what I'm going to do is select my default subnet here, and we'll see that we have Private Google access is turned off at the moment. Now, before we enable Private Google access, we wanna make sure that we have the default internet gateway defined as the next hop, at least in this example for the default route.
So what we'll do is we'll select routes here, and then what we see here, we have our test network listed in our list of routes here. Now, what we could do is just filter our table. So for our test network, we can see we have a couple of different routes here. We have one default local route to the 192.168.0.0 sub-net, and then we have our default route to the internet which is what we're looking for. So we do have a default route here with our destination IP of 0.0.0.0.
Now, since we already talked about the default route to the internet, with a range of 0.0.0.0/0, as being sufficient for routing to Google APIs and services in the context of Private Google access, we're good here. So what we'll do to enable Private Google access for our sub-net on this network, we'll go ahead and select the network, and then what we'll do is we'll select our sub-net here. We can see we have Private Google access off, we can edit it, we can then enable Private Google access and save it.
And there you have it. We've now configured a default route that works with Private Google access, and we've gone ahead and enabled Private Google access for the default sub-net in our test network.
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.