GCP PlayCloud Labs
-
GCP PlayCloud Labs
-
Guided Lab: How to Launch a GCP Compute Engine Linux Instance
-
Guided Lab: Creating a VM Using Instance Templates
-
Guided Lab: Creating and Managing Instance Groups in Compute Engine
-
Guided Lab: Creating a Spot VM Instance
-
Guided Lab: Configuring Shielded VM Options
-
Guided Lab: Exploring Instance Metadata in Google Cloud
-
Guided Lab: Vertically Scaling a VM Instance
-
Guided Lab: Setting up a Web Server on a VM Instance
-
Guided Lab: Using Startup Scripts in GCP VM Instances
-
Guided Lab: Creating a Custom Image from a VM Instance with Web Server in Google Cloud
-
Guided Lab: Creating VM Snapshots and Restoring a VM from a Snapshot
-
Guided Lab: Setting Up and Managing a Database on a VM Instance
-
Guided Lab: Installing WordPress on an Ubuntu VM Instance with LEMP Stack
-
Guided Lab: Deploying a LAMP Stack on a Compute Engine VM
-
Guided Lab: Reserving or Promoting a Static IP Address for a VM Instance
-
Guided Lab: SSH Access to GCP VM Instance from Local Machine using SSH Key Pair
-
Guided Lab: Guarding Your VM with Deletion Protection
-
Guided Lab: Setting Up a Linux Bastion Host on GCP
-
Guided Lab: Creating a Cloud Storage Bucket
-
Guided Lab: Uploading, Organizing, and Managing Objects in Cloud Storage
-
Guided Lab: Exploring Google Cloud Storage Classes
-
Guided Lab: Hosting a Static Website in Google Cloud Storage Bucket
-
Guided Lab: Protecting Data on Cloud Storage Bucket Against Accidental Delete and Overwrite Using Object Versioning
-
Guided Lab: Using Cloud Storage Lifecycle Rules to Automate Object Management
-
Guided Lab: Managing Cloud Storage Buckets via SSH Commands
-
Guided Lab: Creating a Cloud SQL Instance
-
Guided Lab: Running SQL Commands in Cloud SQL Studio
-
Guided Lab: Creating and Restoring Cloud SQL Backups
-
Guided Lab: Integrating Cloud SQL Database instance with a VM instance
-
Guided Lab: Connecting Cloud SQL Database with MySQL Workbench (Local)
-
Guided Lab: Guarding Your Cloud SQL Instances with Deletion Protection
-
Guided Lab: Creating a Cloud NAT Gateway
-
Guided Lab: Creating a Google Kubernetes Engine (GKE) Cluster
-
Guided Lab: Connecting to a Kubernetes Engine Cluster
-
Guided Lab: Deploying a Simple Web Application on GKE
-
Guided Lab: Creating a Custom Virtual Private Cloud (VPC)
-
Guided Lab: Establishing VPC Peering for Secure Cross‑Network Communication
-
Guided Lab: Configuring Firewall Rules to Secure and Access a VM
-
Guided Lab: Creating an Application Load Balancer
-
Guided Lab: Creating a Network Load Balancer
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:
- Guided Lab: How to Launch a GCP Compute Engine Linux Instance
- Guided Lab: Creating a Custom Virtual Private Cloud (VPC)
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.



