Shared VPC in Google Cloud

Shared VPC allows an organization to connect resources from multiple projects to a common Virtual Private Cloud (VPC) network so that they can communicate with each other securely and efficiently using internal IPs from that network.

Unlike VPC peering, Shared VPC connects projects within the same organization.

But when we have VPC Peering, why do we use Shared VPC? 🤔

There are a lot of benefits of using share VPC over VPC Peering:

• You don’t have to deal with the complexity and overhead of VPC network peering between VPCs in different projects.
• It simplifies hybrid cloud network links to on-premise environments as it only needs to be created in the Shared VPC and can be then used by multiple VPCs.
• You can manage all the networking routes, firewalls, and subnet at one central location, and can be handled by a dedicated team of network engineers.

Overview of a Shared VPC in simple language: 😎

When you use Shared VPC, you designate a project as a host project and attach one or more other service projects to it.

In the above diagram, A Shared VPC Admin for the organization has created a host project and attached two service projects to it.