Shared VPC versus VPC Network Peering

1. Shared VPC versus VPC Network Peering

Let's compare both of these configurations to help you decide which one is appropriate for a given situation. If you want to configure private communication between VPC networks in different organizations, you must use VPC network peering shared VPC only works within the same organization. If you want to configure private communication between VPC networks in the same project, you must use VPC network peering. The VPC networks can be in the same project, but it's not required. Shared VPC only works across projects. In our opinion, the biggest difference between the two configurations is the network administration models. Shared VPC is a centralized approach to multi project networking because security and network policy occurs in a single designated VPC network. In contrast, VPC network peering is a decentralized approach. Each VPC network is controlled by administrator groups in that VPC networks organization. Each VPC network can maintain its own global firewall and routing tables. For more information about the limits of VM instances per VPC network, see per network on the quotas and limits page of the Google Cloud documentation. Now that we've compared both of these configurations to share VPC networks across Google cloud projects, lets look at one last use case. In Google Cloud you can peer with a shared VPC network. Here you can see an example of a shared VPC network called network SVPC. Network SVPC is in host project P One. Service projects P3 and P4 can attach VM instances to network SVPC, which enables private communication between VMs 1, 2, and 4. If we establish a peering session between Network A and network SVPC, all VM instances will have private internal IP connectivity. Each VPC network has firewall rules that define which traffic is allowed or denied between the networks. You can also set up VPC network peering between two shared VPC networks.

2. Let's practice!

Create Your Free Account

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.