Shared VPC concept in GCP - Step-by-Step Execution

Process Flow - Shared VPC concept

Host Project Created

↓

Create VPC Network in Host

↓

Attach Service Projects

↓

Grant IAM Roles to Service Projects

↓

Service Projects Use Shared VPC Resources

↓

Resources Communicate Across Projects

↓

End

This flow shows how a host project creates a VPC network, attaches service projects, grants permissions, and enables resource sharing across projects.

Execution Sample

GCP

1. Create host project
2. Create VPC network in host
3. Attach service project
4. Grant IAM roles
5. Deploy VM in service project using shared VPC

Steps to set up a Shared VPC where service projects use the host project's network.

Process Table

Step	Action	Result	Notes
1	Create host project	Host project created	This project will own the VPC network
2	Create VPC network in host	VPC network created	Network is isolated in host project
3	Attach service project	Service project linked	Service project can use host's network
4	Grant IAM roles	Service project granted network user role	Allows service project to create resources in shared VPC
5	Deploy VM in service project	VM uses shared VPC network	VM gets IP from host project's network
6	VM communicates with other resources	Network traffic flows	Cross-project communication enabled
7	End	Setup complete	Shared VPC is operational

💡 All steps completed; Shared VPC setup allows service projects to use host project's network resources.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
Host Project	None	Created	Created	Created	Created	Created	Created
VPC Network	None	None	Created	Created	Created	Created	Created
Service Project	None	None	None	Attached	Attached	Attached	Attached
IAM Roles	None	None	None	None	Granted	Granted	Granted
VM Instance	None	None	None	None	None	Deployed	Deployed

Key Moments - 3 Insights

Why can't service projects create their own VPC networks in a Shared VPC setup?

Service projects do not create their own VPCs; they use the host project's VPC network. This is shown in execution_table rows 2 and 3 where the VPC is created only in the host project and service projects are attached to it.

How does a VM in a service project get an IP address from the host project's network?

Because the service project has the 'network user' IAM role granted (row 4), it can deploy resources like VMs that use the host project's VPC network, as seen in row 5.

Can resources in service projects communicate with each other across projects?

Yes, once the Shared VPC is set up and VMs are deployed (rows 5 and 6), network traffic flows across projects using the shared network.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the service project linked to the host project?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Action' column for 'Attach service project' in execution_table.

According to variable_tracker, when is the VM instance deployed?

A After Step 3

B After Step 4

C After Step 5

D At Start

💡 Hint

Look at the 'VM Instance' row and see when it changes from 'None' to 'Deployed'.

If the IAM roles were not granted, what would happen at Step 5 in execution_table?

A VM deployment would fail due to lack of permissions

B VM would deploy successfully

C Service project would be detached

D Host project would be deleted

💡 Hint

Refer to Step 4 and Step 5 in execution_table about IAM roles and VM deployment.

Concept Snapshot

Shared VPC lets multiple projects use one VPC network.
Host project owns the network.
Service projects attach to host and get permissions.
Resources in service projects use host's network.
Enables centralized network management across projects.

Full Transcript

Shared VPC is a Google Cloud concept where one project, called the host project, owns a Virtual Private Cloud (VPC) network. Other projects, called service projects, attach to this host project to use its network resources. The setup involves creating the host project, creating a VPC network inside it, attaching service projects, granting them network user roles, and then deploying resources like virtual machines in the service projects that use the shared network. This allows resources across projects to communicate securely and centrally managed. The execution table shows each step from creating projects to deploying VMs, and the variable tracker shows how key variables change over time. Key moments clarify common confusions about network ownership, permissions, and communication. The visual quiz tests understanding of the setup steps and permissions.