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 permissions required for Private Google Access for on-prem hosts! There isn’t a whole lot to cover here but I just wanted to make sure I included a blurb here regarding permissions that are necessary for implementing private Google access for on-prem hosts if for nothing else than for the sake of completeness.
Since the implementation of Private Google Access for on-prem hosts will require you to create subnets, updates subnets, and sometimes assign IP addresses, you’ll need an account that’s a Project Owner, an Editor, or an account that is an IAM member that has the Network Admin role assigned to it in order to perform the necessary configuration tasks when implementing Private Google Access.
I should point out that these permissions requirements apply to both the implementation of Private Google Access as well Private Google Access for on-prem hosts.
Join me in the next lesson, where we will touch on other types of private access options.
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.