Using VPC Network Peering
In this lab, you configure VPC Network Peering between two networks. Then, you verify private communication between two VMs in those networks as illustrated in this diagram:
VPC Network Peering allows you to build SaaS (Software-as-a-Service) ecosystems on Google Cloud Platform (GCP), making services available privately across different VPC networks within and across organizations, allowing workloads to communicate in private RFC 1918 space.
VPC Network Peering gives you several advantages over using external IP addresses or VPNs to connect networks, including:
Network Latency: Public IP networking suffers higher latency than private networking.
Network Security: Service owners have no need to expose their services to the public Internet and deal with the associated risks.
Network Cost: GCP charges egress bandwidth pricing for networks using external IPs to communicate even if the traffic is within the same zone. If however, the networks are peered they can use internal IPs to communicate and save on those egress costs. Regular network pricing still applies to all traffic.
In this lab, you perform the following tasks:
Explore connectivity between non-peered VPC networks
Configure VPC Network Peering
Verify private communication between peered VPC networks
Delete VPC Network Peering
- Temporary Access
- Bite Sized