DEMO: Adding a Subnet to an Existing VPC
Start course
1h 1m

This course has been designed to teach you how to manage networking and compute resources on Google Cloud Platform. The content in this course will help prepare you for the Associate Cloud Engineer exam.

The topics covered within this course include:

  • Adding subnets to a VPC
  • Expanding existing subnets
  • Reserving static addresses via the console and Cloud Shell
  • Managing, configuring, and connecting to VM instances
  • Adding GPUs and installing CUDA libraries
  • Creating and deploying from snapshots and images
  • Working with instance groups

Learning Objectives

  • Learn how to manage networking and compute resources on Google Cloud Platform
  • Prepare for the Google Associate Cloud Engineer Exam

Intended Audience

  • Those who are preparing for the Associate Cloud Engineer exam
  • Those looking to learn more about managing GCP networking and compute features


To get the most from this course, you should have some exposure to GCP resources, such as VCPs, VM Instances, Cloud Console, and Cloud Shell. However, this is not essential.



Hi, everyone, welcome to this demonstration. In this demonstration, I'm going to show you how to add a subnet to an existing VPC.

When you create a subnet, you need to specify a name, a region, and at least a primary IP address range for the subnet. To complete this process, what you need to do is browse to the VPC networks page in Google Cloud Platform Console. From here, we need to click an existing VPC network. What this will do is show the network details page.

To add the subnet, click Add subnet and then provide a name for the subnet, and choose a region to deploy to. 

From here, specify the primary IP range for the subnet. For this exercise, I'll add a subnet with a range of As you can see here, we could enable Private Google Access for the subnet right now, if we wanted to. We can also leave it disabled for now and change it later. I'm not going to bother enabling it for this exercise, so we'll just leave it alone. We would typically enable this option in order to allow any VMs on this network to connect to Google APIs and services, without giving those VMs external IP addresses.

If I needed a way to record network flows sent to and from the VM instances on this subnet, I could enable VPC flow logs right here for the subnet. VPC flow logs are generally used for network monitoring, forensics, and real-time security analysis. Since this is a lab, I'm not terribly worried about any of these things, so I'll leave this option alone. Clicking Add down here, adds the newly configured subnet, and then what we'll do here is refresh, and you can see my new subnet is now listed.

Join me in the next lesson, where we'll discuss the expansion of CIDR block subnets.

About the Author
Learning Paths

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.