How does Network Connectivity Center differ from VPC peering?

VPC peering creates direct connections between two VPC networks but is non-transitive — if VPC-A peers with VPC-B and VPC-B peers with VPC-C, A and C cannot communicate through B. Network Connectivity Center provides transitive routing through a hub, so all spokes can reach each other automatically. It also provides centralized management, supports hybrid spokes (VPN, Interconnect), and scales better than maintaining a full mesh of peering connections.

Can Network Connectivity Center connect to on-premises networks?

Yes. Hybrid spokes connect on-premises networks via Cloud VPN tunnels, Cloud Interconnect VLAN attachments, or third-party Router appliance instances running in GCE. Routes learned from on-premises BGP sessions are automatically distributed to all other spokes in the hub, enabling on-premises to reach any connected VPC or other on-premises site through the hub.

GCP Network Connectivity Hub Builder

NetworkingGCP

Build Network Connectivity Center hub and spoke configurations for multi-region and hybrid connectivity.

Network Connectivity Center Configuration

Build Network Connectivity Center hub and spoke configurations for multi-region and hybrid connectivity.

Required Fields

hub.namehub.routingVpcsspokes

{
  "hub": {
    "name": "projects/my-project/locations/global/hubs/global-connectivity-hub",
    "description": "Global Network Connectivity Center hub for multi-region mesh",
    "routingVpcs": [
      {
        "uri": "projects/my-project/global/networks/prod-vpc"
      }
    ]
  },
  "spokes": [
    {
      "name": "projects/my-project/locations/us-central1/spokes/us-central1-spoke",
      "hub": "projects/my-project/locations/global/hubs/global-connectivity-hub",
      "linkedVpnTunnels": {
        "uris": [
          "projects/my-project/regions/us-central1/vpnTunnels/tunnel-to-onprem-1",
          "projects/my-project/regions/us-central1/vpnTunnels/tunnel-to-onprem-2"
        ],
        "siteToSiteDataTransfer": true
      },
      "labels": {
        "env": "production",
        "region": "us-central1"
      }
    },
    {
      "name": "projects/my-project/locations/europe-west1/spokes/europe-west1-spoke",
      "hub": "projects/my-project/locations/global/hubs/global-connectivity-hub",
      "linkedInterconnectAttachments": {
        "uris": [
          "projects/my-project/regions/europe-west1/interconnectAttachments/attach-eu-1"
        ],
        "siteToSiteDataTransfer": true
      },
      "labels": {
        "env": "production",
        "region": "europe-west1"
      }
    }
  ]
}

Generated Output

Output will appear here...

About This Tool

Network Connectivity Center is Google Cloud's hub-and-spoke architecture for connecting VPC networks, on-premises sites, and remote branches through a centralized management plane. It supports hybrid spokes (Cloud VPN, Cloud Interconnect, Router appliances) and VPC spokes for network-to-network connectivity. This builder helps you design hub topologies, configure spoke attachments, set up route exchange policies, and generate the Terraform or gcloud configurations needed for deployment.

When to Use This Tool

•Designing a hub-and-spoke network topology that connects multiple VPCs with centralized route management and transitive routing
•Configuring hybrid spokes to connect on-premises data centers through Cloud Interconnect and branch offices through Cloud VPN to a central hub
•Building a multi-region network mesh using VPC spokes that enables transitive connectivity between project VPCs without full mesh peering
•Setting up route advertisement filters to control which prefixes are exchanged between spokes

Frequently Asked Questions

How does Network Connectivity Center differ from VPC peering?: VPC peering creates direct connections between two VPC networks but is non-transitive — if VPC-A peers with VPC-B and VPC-B peers with VPC-C, A and C cannot communicate through B. Network Connectivity Center provides transitive routing through a hub, so all spokes can reach each other automatically. It also provides centralized management, supports hybrid spokes (VPN, Interconnect), and scales better than maintaining a full mesh of peering connections.
Can Network Connectivity Center connect to on-premises networks?: Yes. Hybrid spokes connect on-premises networks via Cloud VPN tunnels, Cloud Interconnect VLAN attachments, or third-party Router appliance instances running in GCE. Routes learned from on-premises BGP sessions are automatically distributed to all other spokes in the hub, enabling on-premises to reach any connected VPC or other on-premises site through the hub.

Related Learning Guides

VPC Network Design Patterns28 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.

GCP Network Connectivity Hub Builder

NetworkingGCP

Build Network Connectivity Center hub and spoke configurations for multi-region and hybrid connectivity.

Network Connectivity Center Configuration

Build Network Connectivity Center hub and spoke configurations for multi-region and hybrid connectivity.

Required Fields

hub.namehub.routingVpcsspokes

Generated Output

Output will appear here...

About This Tool

When to Use This Tool

•Designing a hub-and-spoke network topology that connects multiple VPCs with centralized route management and transitive routing
•Configuring hybrid spokes to connect on-premises data centers through Cloud Interconnect and branch offices through Cloud VPN to a central hub
•Building a multi-region network mesh using VPC spokes that enables transitive connectivity between project VPCs without full mesh peering
•Setting up route advertisement filters to control which prefixes are exchanged between spokes

Frequently Asked Questions

How does Network Connectivity Center differ from VPC peering?: VPC peering creates direct connections between two VPC networks but is non-transitive — if VPC-A peers with VPC-B and VPC-B peers with VPC-C, A and C cannot communicate through B. Network Connectivity Center provides transitive routing through a hub, so all spokes can reach each other automatically. It also provides centralized management, supports hybrid spokes (VPN, Interconnect), and scales better than maintaining a full mesh of peering connections.
Can Network Connectivity Center connect to on-premises networks?: Yes. Hybrid spokes connect on-premises networks via Cloud VPN tunnels, Cloud Interconnect VLAN attachments, or third-party Router appliance instances running in GCE. Routes learned from on-premises BGP sessions are automatically distributed to all other spokes in the hub, enabling on-premises to reach any connected VPC or other on-premises site through the hub.

Related Learning Guides

VPC Network Design Patterns28 min read