Ends in
00
hrs
00
mins
00
secs
SHOP NOW

💝 48-Hour Valentine's Sale Extension! Get 30% OFF Any Reviewer. Use coupon code: VDAYSALE2026 & 5% OFF Store Credits/Gift Cards

Back to Course

GCP PlayCloud Labs

0% Complete
0/0 Steps
  1. GCP PlayCloud Labs
  2. Guided Lab: How to Launch a GCP Compute Engine Linux Instance
  3. Guided Lab: Creating a VM Using Instance Templates
  4. Guided Lab: Creating and Managing Instance Groups in Compute Engine
  5. Guided Lab: Creating a Spot VM Instance
  6. Guided Lab: Configuring Shielded VM Options
  7. Guided Lab: Exploring Instance Metadata in Google Cloud
  8. Guided Lab: Vertically Scaling a VM Instance
  9. Guided Lab: Setting up a Web Server on a VM Instance
  10. Guided Lab: Using Startup Scripts in GCP VM Instances
  11. Guided Lab: Creating a Custom Image from a VM Instance with Web Server in Google Cloud
  12. Guided Lab: Creating VM Snapshots and Restoring a VM from a Snapshot
  13. Guided Lab: Setting Up and Managing a Database on a VM Instance
  14. Guided Lab: Installing WordPress on an Ubuntu VM Instance with LEMP Stack
  15. Guided Lab: Deploying a LAMP Stack on a Compute Engine VM
  16. Guided Lab: Reserving or Promoting a Static IP Address for a VM Instance
  17. Guided Lab: SSH Access to GCP VM Instance from Local Machine using SSH Key Pair
  18. Guided Lab: Guarding Your VM with Deletion Protection
  19. Guided Lab: Setting Up a Linux Bastion Host on GCP
  20. Guided Lab: Creating a Cloud Storage Bucket
  21. Guided Lab: Uploading, Organizing, and Managing Objects in Cloud Storage
  22. Guided Lab: Exploring Google Cloud Storage Classes
  23. Guided Lab: Hosting a Static Website in Google Cloud Storage Bucket
  24. Guided Lab: Protecting Data on Cloud Storage Bucket Against Accidental Delete and Overwrite Using Object Versioning
  25. Guided Lab: Using Cloud Storage Lifecycle Rules to Automate Object Management
  26. Guided Lab: Managing Cloud Storage Buckets via SSH Commands
  27. Guided Lab: Creating a Cloud SQL Instance
  28. Guided Lab: Running SQL Commands in Cloud SQL Studio
  29. Guided Lab: Creating and Restoring Cloud SQL Backups
  30. Guided Lab: Integrating Cloud SQL Database instance with a VM instance
  31. Guided Lab: Connecting Cloud SQL Database with MySQL Workbench (Local)
  32. Guided Lab: Guarding Your Cloud SQL Instances with Deletion Protection
  33. Guided Lab: Creating a Cloud NAT Gateway
  34. Guided Lab: Creating a Google Kubernetes Engine (GKE) Cluster
  35. Guided Lab: Connecting to a Kubernetes Engine Cluster
  36. Guided Lab: Deploying a Simple Web Application on GKE
  37. Guided Lab: Creating a Custom Virtual Private Cloud (VPC)
  38. Guided Lab: Establishing VPC Peering for Secure Cross‑Network Communication
  39. Guided Lab: Configuring Firewall Rules to Secure and Access a VM
  40. Guided Lab: Creating an Application Load Balancer
  41. Guided Lab: Creating a Network Load Balancer
Lesson 38 of 41
In Progress

Guided Lab: Establishing VPC Peering for Secure Cross‑Network Communication

Description

Google Cloud VPC Network Peering enables direct communication between two Virtual Private Cloud (VPC) networks, allowing resources in each network to interact seamlessly. These peered networks can reside within the same project, across different projects in the same organization, or even between projects belonging to separate organizations.

In this guided lab, you will learn how to establish VPC Network Peering between two Virtual Private Cloud (VPC) networks in Google Cloud. This exercise demonstrates how to enable private communication across networks without using external IP addresses or VPNs.

Prerequisites

To ensure the successful completion of this lab, we highly recommend taking the following guided labs to gain the necessary understanding:

Objectives

In this lab, you will:

  • Create two VPC networks.
  • Set up VPC peering between the two networks.
  • Launch VM instances in each VPC.
  • Test connectivity between the VM instances.

Lab Steps

Create VPC Networks

1. In the Console, go to VPC network > VPC networks.

2. Create a new VPC network named vpc-network-1 with a custom subnet (e.g., 10.0.0.0/24).

  • Under Subnets, add a new subnet named vpc-network-1-subnet
  • Region: us-central1
  • IP Stack: IPv4
  • IPv4 range: 10.0.0.0/24


  • Under Firewall rules, select all IPv4 firewall rules


  • Leave other configurations at their default values.
  • Click Create.

3. Create another VPC network named vpc-network-2 with a different custom subnet (e.g., 10.1.0.0/24).

  • Under Subnets, add a new subnet named vpc-network-2-subnet
  • Region: us-central1
  • IP Stack: IPv4
  • IPv4 range: 10.1.0.0/24


  • Under Firewall rules, select all IPv4 firewall rules


  • Leave other configurations at their default values.
  • Click Create.
Set Up VPC Peering

1. In the Console, go to VPC network > VPC network peering.

2. Click Create connection > Continue

3. Configure the peering from vpc-network-1 to vpc-network-2

  • Peering connection name: peer-1-to-2.
  • Your VPC Network: vpc-network-1
  • Peered VPC network:
    • In project …
    • VPC network name: vpc-network-2
  • Leave other configurations at their default values.
  • Click Create.

4. Configure the peering from vpc-network-2 to vpc-network-1

  • Peering connection name: peer-2-to-1.
  • Your VPC Network: vpc-network-2
  • Peered VPC network:
    • In project …
    • VPC network name: vpc-network-1
  • Leave other configurations at their default values.
  • Click Create.
Create VM Instances

1. Go to Compute Engine > VM instances.

2. Create a VM instance named vm-instance-1 in vpc-network-1.

  • Machine type: e2-micro
  • Under Networking > Network interfaces
    • Edit the Network interface from default to vpc-network-1
  • Leave other configurations at their default values.
  • Click Create.

3. Create another VM instance named vm-instance-2 in vpc-network-2.

  • Machine type: e2-micro
  • Under Networking > Network interfaces
    • Edit the Network interface from default to vpc-network-2
  • Leave other configurations at their default values.
  • Click Create.
Test Connectivity

1. In the Console, click SSH for vm-instance-1 to open a browser SSH session.

2. Ping the internal IP address of vm-instance-2 to test connectivity.

From the shell, run:

ping <internal-ip-of-vm-instance-2>

This output indicates successful communication between the two VM instances over the peered VPC networks.

Congratulations! You have successfully created two VPC networks, established peering between them, launched VM instances, and verified connectivity. This setup is foundational for building secure and scalable cloud network architectures.

Skip to content