This lab walks you through GCP VPC Peering.
In this lab, you will create two VPCs, and two VPC Peering connections to connect both VPCs.
Region: us-central1 , us-east1
Duration: 60 minutes
Before understanding VPC Peering, you must possess knowledge of VPCs which is a virtual version of a physical network. It is a global resource.
In the real world, there might be a chance when your company needs connectivity with several other VPCs, either on-cloud or on-premise, VPC Peering is the solution.
It provides private connectivity among two VPCs regardless of the same project/organization or not.
Private Connectivity means traffic stays within Google Network and not public.
It is a secure solution as nothing is going public on the Internet.
You are able to save egress costs as nothing is traveling outside.
Both VPCs in the Peering connection remain administratively separate which means both are managed by their administrators. Configuration is done in each VPC separately.
A VPC can peer with up to 25 VPCs but only direct peering is possible no transitive peering is possible which simply means if VPC A is connected with VPC B and VPC B is connected with VPC C that doesn't mean VPC A is connected with VPC C.
Creating a VPC with Subnet in us-central1 Region.
Creating a VPC with Subnet in us-east1 Region.
Creating a VPC Peering from us-central to us-east.
Creating a VPC Peering from us-east to us-central.