Direct Peering

Google Cloud Hybrid Connectivity – IC, VPN & NCC

~ Last updated on : ~ jayendrapatil

Google Cloud Hybrid Connectivity

Google Cloud provides various network connectivity options to meet the needs, using either public networks, peering, or interconnect technologies.

🆕 Updated June 2026: This post covers major updates including Cross-Cloud Interconnect (multicloud connectivity), Cross-Site Interconnect (L2 site-to-site), Network Connectivity Center (hub-spoke orchestration), 400 Gbps Dedicated Interconnect circuits, Classic VPN BGP deprecation, HA VPN over Cloud Interconnect, MACsec encryption, and customizable VPN ciphers.

Google Cloud Hybrid Connectivity Options

Public Network Connectivity

Standard internet connection can be used to connect Google Cloud with the on-premises environment if it meets the bandwidth needs.

Cloud VPN

  • provides secure, private connectivity using IPSec
  • connects on-premises networks to VPC or two VPCs in GCP
  • traffic flows via the VPN tunnel but is still routed over the public internet
  • traffic is encrypted by one gateway and decrypted by the other
  • allows users to access private RFC1918 addresses on resources in the VPC from on-prem computers also using private RFC1918 addresses.
  • can be used with Private Google Access for on-premises hosts
  • provides guaranteed uptime of 99.99% using High Availability (HA) VPN
  • supports only site-to-site VPN
  • supports up to 3Gbps per tunnel with a maximum of 8 tunnels
  • supports static as well as dynamic routing using Cloud Router
  • supports IKEv1 or IKEv2 using a shared secret
  • supports IPv6 traffic exchange with dual-stack (IPv4/IPv6) HA VPN gateways
  • supports customizable cipher options allowing you to configure specific ciphers per your security requirements (GA)

Classic VPN vs HA VPN

  • Classic VPN provides a single external IP address and tunnels with 99.9% SLA
  • HA VPN uses redundant interfaces and provides 99.99% SLA
  • HA VPN supports IPv6/dual-stack; Classic VPN does not
  • HA VPN supports dynamic routing (BGP) and is the only VPN option for BGP
⚠️ Classic VPN BGP Deprecation (August 1, 2025): Dynamic routing (BGP) for Classic VPN tunnels is deprecated. You cannot create new Classic VPN tunnels using BGP. Existing BGP tunnels continue to function but without SLA. For workloads requiring BGP, you must migrate to HA VPN. Classic VPN with static routing remains supported.

Peering

  • Peering provides better connectivity to Google Cloud as compared to the public connection. However, the connectivity is still not RFC1918-to-RFC1918 private address connectivity.
  • Peering gets your network as close as possible to Google Cloud public IP addresses.
  • Google does not offer an SLA with Direct Peering or Carrier Peering. For customers requiring SLA, Google recommends Cloud Interconnect.
  • Google recommends using a Verified Peering Provider instead of Direct Peering.

Direct Peering

  • requires you to lease co-lo space and install and support routing equipment in a Google Point Of Presence (PoP).
  • supports BGP over a link to exchange network routes.
  • All traffic destined to Google rides over this new link, while traffic to other sites on the internet rides your regular internet connection.

Carrier Peering

  • preferred if installing equipment isn’t an option or would prefer to work with a service provider partner as an intermediary to peer with Google
  • connection to Google is via a new link connection installed to a partner carrier that is already connected to the Google network itself.
  • supports BGP or uses static routing over that link.
  • All traffic destined to Google rides over this new link.
  • Traffic to other sites on the internet rides your regular internet connection.

Interconnect

  • Interconnects are similar to peering in that the connections get your network as close as possible to the Google network.
  • Interconnects differ from peering as they provide connectivity using private address space into the Google VPC.
  • For RFC1918-to-RFC1918 private address connectivity, either a dedicated or partner interconnect is required.
  • Cloud Interconnect now offers four types: Dedicated Interconnect, Partner Interconnect, Cross-Cloud Interconnect, and Cross-Site Interconnect.
  • Traffic doesn’t traverse the public internet, resulting in fewer hops and points of failure.
  • Supports MACsec for link-layer encryption between your on-premises router and Google’s edge routers.
  • Supports HA VPN over Cloud Interconnect for IPsec encryption of VLAN attachment traffic.

Dedicated Interconnect

  • provides private, high-performance connectivity to Google Cloud
  • requires you to lease co-lo space and install and support routing equipment in a Google Point Of Presence (PoP).
  • supports 10 Gbps, 100 Gbps, and 400 Gbps circuits with up to 8 circuits per connection (max 3200 Gbps with 400G circuits)
  • gives the RFC1918-to-RFC1918 private address connectivity.
  • All traffic destined to the Google Cloud VPC rides over this new link.
  • Traffic to other sites on the internet rides the regular internet connection.
  • Single Interconnect connection does not offer HA and GCP recommends redundancy using 2 (99.9%) or 4 (99.99%) interconnect connections so that if one connection fails, the other connection can continue to serve traffic
  • supports IPv6 traffic with dual-stack (IPv4 and IPv6) VLAN attachments
  • supports VLAN attachment MTU of 1440, 1460, 1500, or 8896 bytes (jumbo frames)
  • supports MACsec encryption for securing traffic between on-premises router and Google’s edge routers
  • supports connection groups (Interconnect groups and Attachment groups) for reliability monitoring and SLA eligibility tracking
  • supports application awareness for traffic differentiation using DSCP for prioritizing business-critical traffic
  • offers fixed port pricing for predictable monthly billing of outbound data transfers

Partner Interconnect

  • provides private, high-performance connectivity to Google Cloud
  • preferred if bandwidth requirements are below 10 Gbps or installing equipment isn’t an option or would prefer to work with a service provider partner as an intermediary
  • similar to carrier peering in that you connect to a partner service provider that is directly connected to Google.
  • supports BGP or use static routing over that link.
  • requires provisioning a VLAN attachment over the physical link
  • gives the RFC1918-to-RFC1918 private address connectivity.
  • supports VLAN attachment capacities from 50 Mbps to 50 Gbps
  • All traffic destined to your Google VPC rides over this new link.
  • Traffic to other sites on the internet rides your regular internet connection.
  • supports IPv6 traffic with dual-stack VLAN attachments
  • supports HA VPN over Cloud Interconnect for encrypting traffic

Cross-Cloud Interconnect

  • provides dedicated, private connectivity between Google Cloud and another cloud service provider (multicloud connectivity)
  • establishes a direct physical connection between Google’s network and another cloud provider’s network
  • supports connectivity to AWS, Microsoft Azure, Oracle Cloud Infrastructure (OCI), and Alibaba Cloud
  • available in 10 Gbps and 100 Gbps circuit sizes
  • provides private RFC1918-to-RFC1918 connectivity across clouds
  • backed by Google Cloud SLA (99.9% or 99.99% depending on redundancy)
  • Partner Cross-Cloud Interconnect is available for AWS and OCI for on-demand, managed cross-cloud connectivity without provisioning dedicated physical connections
  • supports application awareness for traffic differentiation
  • supports HA VPN over Cloud Interconnect for encryption
  • Google and AWS announced a managed, private, on-demand cross-cloud connectivity collaboration in 2026

Cross-Site Interconnect (GA 2025)

  • provides transparent, on-demand Layer 2 connectivity between your on-premises network sites using Google’s global infrastructure
  • simplifies, augments, and improves reliability for WAN connectivity between your data centers
  • leverages Google’s global network for high-performance and high-bandwidth site-to-site connectivity
  • requires colocation in Google-supported facilities
  • supports cross-site network MTU of 9,000 bytes
  • ideal for disaster recovery, data replication, and site-to-site backup use cases

HA VPN over Cloud Interconnect

  • allows deploying HA VPN tunnels over Dedicated Interconnect or Partner Interconnect VLAN attachments
  • encrypts traffic that traverses Cloud Interconnect connections using IPsec
  • helps meet regulatory and security requirements for data encryption in transit
  • supported for both Dedicated Interconnect and Partner Interconnect
  • provides both the private connectivity of Cloud Interconnect and the encryption of VPN

MACsec for Cloud Interconnect

  • provides link-layer encryption (IEEE 802.1AE) between your on-premises router and Google’s edge routers
  • secures traffic on the physical connection without the overhead of IPsec tunneling
  • supported on Dedicated Interconnect circuits
  • provides configurable fail-open behavior (traffic passes unencrypted if MACsec fails) or fail-close (traffic is blocked)
  • requires MACsec-capable on-premises router

Network Connectivity Center (NCC)

  • a hub-and-spoke orchestration framework that simplifies network connectivity
  • provides centralized management of connectivity between VPC networks, on-premises networks, and other clouds
  • supports VPC spokes for inter-VPC connectivity (up to 250 VPC spokes per hub)
  • supports hybrid spokes using Cloud VPN, Cloud Interconnect, or Router appliance
  • enables site-to-site data transfer using Google’s global network as part of your WAN
  • provides full mesh transitivity between all spokes connected to a hub
  • supports spoke groups for preset connectivity topologies (mesh, star, etc.)
  • integrates with Cross-Cloud Interconnect for multicloud hub-spoke architectures

Google Cloud Hybrid Connectivity Decision Tree

Google Cloud Hybrid Connectivity Decision Tree

Google Cloud Hybrid Connectivity

Google Cloud Hybrid Connectivity Comparison

Option Connectivity Bandwidth SLA Private RFC1918
Cloud VPN (HA) Over public internet (encrypted) Up to 3 Gbps/tunnel 99.99% Yes
Direct Peering Direct to Google PoP 10 Gbps per link No SLA No
Carrier Peering Via partner to Google Varies by partner No SLA No
Dedicated Interconnect Direct physical to Google 10/100/400 Gbps (up to 3200 Gbps) 99.9%/99.99% Yes
Partner Interconnect Via partner to Google 50 Mbps–50 Gbps 99.9%/99.99% Yes
Cross-Cloud Interconnect Google to other cloud provider 10/100 Gbps 99.9%/99.99% Yes
Cross-Site Interconnect Between on-prem sites via Google 10/100 Gbps Yes L2 transparent

Google Cloud Hybrid Connectivity Certification Tips

  • HA VPN is the recommended option for encrypted connectivity over public internet; Classic VPN BGP is deprecated
  • For private RFC1918 connectivity, Dedicated or Partner Interconnect is required (peering does NOT provide private addressing)
  • Cross-Cloud Interconnect is the recommended option for multicloud private connectivity (Google ↔ AWS/Azure/OCI)
  • Network Connectivity Center enables hub-spoke topologies and site-to-site data transfer across Google’s backbone
  • MACsec provides link-layer encryption; HA VPN over Interconnect provides IPsec encryption for Interconnect traffic
  • Dedicated Interconnect requires colocation in Google PoP; Partner Interconnect does not
  • Minimum 2 connections in different edge availability domains for 99.9%; 4 connections for 99.99% SLA

Google Cloud Data Transfer Services Overview

~ Last updated on : ~ jayendrapatil

Google Cloud Data Transfer Services

Google Cloud Data Transfer services provide various options in terms of network and transfer tools to help transfer data from on-premises to Google Cloud network.

📋 Last Updated: June 2026 — Updated with gcloud storage CLI (gsutil replacement), Storage Transfer Service event-driven transfers, Cross-Cloud Interconnect, Transfer Appliance data export, BigQuery Data Transfer Service new sources, Classic VPN dynamic routing deprecation, and Network Connectivity Center.

Network Services

Cloud VPN

  • Provides network connectivity with Google Cloud between on-premises network and Google Cloud, or from Google Cloud to another cloud provider.
  • Cloud VPN still routes the traffic through the Internet.
  • Cloud VPN is quick to set up (as compared to Interconnect)
  • Each Cloud VPN tunnel can support up to 3 Gbps total for ingress and egress, but available bandwidth depends on the connectivity. Bandwidth can be increased by adding more tunnels.
  • Choose Cloud VPN to encrypt traffic to Google Cloud, or with lower throughput solution, or experimenting with migrating the workloads to Google Cloud
  • HA VPN is the recommended VPN configuration offering a 99.99% SLA when configured with tunnels on both interfaces per Google best practices.
  • Classic VPN provides a 99.9% SLA. Note: Classic VPN dynamic routing (BGP) was deprecated on August 1, 2025. HA VPN must be used for BGP-based VPN connectivity.
  • HA VPN over Cloud Interconnect allows encrypting traffic traversing Dedicated or Partner Interconnect connections for additional security and compliance.
  • Cloud VPN supports customizable cipher options (Public Preview as of June 2025) allowing configuration of ciphers per security requirements.
  • Cloud Interconnect offers a direct connection to Google Cloud through Google or one of the Cloud Interconnect service providers.
  • Cloud Interconnect service prevents data from going on the public internet and can provide a more consistent throughput for large data transfers
  • For enterprise-grade connection to Google Cloud that has higher throughput requirements, choose Dedicated Interconnect (10 Gbps to 100 Gbps) or Partner Interconnect (50 Mbps to 50 Gbps)
  • Cloud Interconnect provides access to all Google Cloud products and services from your on-premises network except Google Workspace.
  • Cloud Interconnect also allows access to supported APIs and services by using Private Google Access from on-premises hosts.
  • Cross-Cloud Interconnect enables dedicated, private connectivity between Google Cloud and another cloud service provider (AWS, Azure, Oracle Cloud Infrastructure, Alibaba Cloud). This eliminates the need for traffic to traverse the public internet for multicloud architectures.
  • Partner Cross-Cloud Interconnect (available for AWS) provides an on-demand method for cross-cloud transport without manually setting up networking components.
  • Cross-Site Interconnect (GA 2025) is a transparent, on-demand Layer 2 connectivity solution leveraging Google’s global infrastructure for high-bandwidth connectivity between on-premises sites.
  • Direct Peering provides access to the Google network with fewer network hops than with a public internet connection
  • By using Direct Peering, internet traffic is exchanged between the customer network and Google’s Edge Points of Presence (PoPs), which means the data does not use the public internet.
  • Google does not offer a Service Level Agreement (SLA) with Direct Peering.
  • For SLA-backed connectivity, Cloud Interconnect (Dedicated or Partner) is recommended over Direct Peering.

Network Connectivity Center

  • Network Connectivity Center (NCC) is an orchestration framework that simplifies network connectivity using a hub-and-spoke model.
  • Supports three types of spokes: VPC spokes, Producer VPC spokes, and Hybrid spokes (HA VPN tunnels, Cloud Interconnect VLAN attachments, Router appliance VMs).
  • Enables site-to-cloud connectivity (external networks to Google Cloud) and site-to-site connectivity (using Google Cloud as enterprise WAN).
  • Supports up to 250 VPC spokes per hub and provides transitivity between workload VPCs.
  • Useful for managing complex multicloud and hybrid network topologies centrally.

Google Cloud Networking Services Decision Tree

Google Cloud Hybrid Connectivity

Transfer Services

gcloud storage (formerly gsutil)

⚠️ gsutil Deprecation Notice: gsutil is no longer the recommended CLI for Cloud Storage. Google recommends using gcloud storage commands in the Google Cloud CLI instead. gsutil does not support newer Cloud Storage features such as soft delete and managed folders. gcloud storage commands require less manual optimization and provide faster transfer rates.
  • gcloud storage (replacement for gsutil) is the standard tool for small- to medium-sized transfers (less than 1 TB) over a typical enterprise-scale network, from a private data center to Google Cloud.
  • gcloud storage provides all the basic features needed to manage Cloud Storage instances, including copying data to and from the local file system and Cloud Storage.
  • gcloud storage can also move, rename, and remove objects and perform real-time incremental syncs (similar to rsync) to a Cloud Storage bucket.
  • gcloud storage is especially useful in the following scenarios:
    • As-needed transfers or during command-line sessions by your users.
    • Transferring only a few files or very large files, or both.
    • Consuming the output of a program (streaming output to Cloud Storage).
    • Watching a directory with a moderate number of files and syncing any updates with very low latencies.
  • gcloud storage provides the following features:
    • Parallel multi-threaded transfers for increased transfer speeds.
    • Composite transfers for a single large file, breaking them into smaller chunks to increase transfer speed. Chunks are transferred and validated in parallel. Once the chunks arrive at Google, they are combined (composited) to form a single object.
    • Uses faster CRC32C hashing algorithm for data integrity checking (improved over gsutil’s crcmod).
  • Migration: Replace gsutil commands with equivalent gcloud storage commands. For example: gsutil cp → gcloud storage cp, gsutil rsync → gcloud storage rsync.
  • Storage Transfer Service is a fully managed, highly scalable service to automate transfers into Cloud Storage from multiple sources.
  • Supported Sources:
    • Amazon S3
    • S3-compatible storage (requires agents)
    • Microsoft Azure Blob Storage and Azure Data Lake Storage Gen2
    • Cloud Storage (bucket-to-bucket)
    • Publicly accessible HTTP/HTTPS URLs
    • On-premises file systems (POSIX-compliant, requires agents)
    • Hadoop Distributed File System (HDFS, requires agents)
  • Storage Transfer Service for Cloud-to-Cloud transfers:
    • Supports transfers from S3, Azure Blob Storage, and Cloud Storage without agents.
    • Supports daily copies of any modified objects.
  • Storage Transfer Service for on-premises data:
    • Is designed for large-scale transfers (up to petabytes of data, billions of files).
    • Supports full copies or incremental copies.
    • Can be set up by installing on-premises software (known as agents) onto computers in the data center.
  • Has a simple, managed graphical user interface; even non-technically savvy users (after setup) can use it to move data.
  • Provides robust error-reporting and a record of all files and objects that are moved.
  • Supports executing recurring transfers on a schedule.
  • Event-Driven Transfers (2025-2026):
    • Listens to event notifications to automatically transfer new or updated objects.
    • Supported for AWS S3 (via S3 Event Notifications to Amazon SQS).
    • Supported for Azure Blob Storage and Data Lake Storage Gen2 (via Azure Event Grid to Azure Storage Queues) — available since January 2026.
    • Supported for Cloud Storage (via Pub/Sub notifications).
  • Private Network Transfers (December 2025): Transfer data from AWS S3 or Azure Blob Storage to Cloud Storage over a private network connection using Cross-Cloud Interconnect or Partner Interconnect, optimizing costs and compliance.
  • Google-Managed Private Network for S3: Transfer from S3 over a Google-managed private network, eliminating AWS egress fees with a flat per-GiB rate.
  • AWS GovCloud Support (2026): Supports transfers from S3 buckets in us-gov-east-1 and us-gov-west-1 regions.
  • Organization Policy Constraints (February 2026): Custom organization policy constraints to control Storage Transfer Service usage (e.g., restrict sources or destinations).
  • Encrypts data in transit, supports VPC Service Controls, and uses checksums for data integrity.

Transfer Appliance

  • Transfer Appliance is an excellent option for performing large-scale transfers, especially when a fast network connection is unavailable, it’s too costly to acquire more bandwidth, or it’s a one-time transfer.
  • Expected turnaround time for a network appliance to be shipped, loaded with the data, shipped back, and rehydrated on Google Cloud is approximately 50 days.
  • Consider Transfer Appliance if the online transfer timeframe is calculated to be substantially more than this timeframe.
  • Transfer Appliance requires the ability to receive and ship back the Google-owned hardware.
  • Transfer Appliance is available only in certain countries.
  • Data Export (GA in US): Transfer Appliance now supports exporting data from Cloud Storage to the appliance, which is then shipped to you. This enables large-scale data egress from Google Cloud when network transfer is impractical.
  • gcloud CLI Support (Alpha): gcloud alpha transfer appliances commands allow viewing in-progress results, working with draft orders, and cloning existing orders.
  • Data is encrypted during upload, transit, after upload to Cloud Storage, and during download for data export.

BigQuery Data Transfer Service

  • BigQuery Data Transfer Service automates data movement into BigQuery on a scheduled, managed basis.
  • After a data transfer is configured, the BigQuery Data Transfer Service automatically loads data into BigQuery on a regular basis.
  • BigQuery Data Transfer Service can also initiate data backfills to recover from any outages or gaps.
  • BigQuery Data Transfer Service can only sink data to BigQuery and cannot be used to transfer data out of BigQuery.
  • Also supports dataset copies and scheduled queries within BigQuery.
  • BigQuery Data Transfer Service supports loading data from the following data sources:
    • Google SaaS Applications:
      • Google Ads
      • Google Ad Manager
      • Campaign Manager
      • Search Ads 360
      • Google Merchant Center
      • Google Play
      • YouTube Channel reports
      • YouTube Content Owner reports
      • Google Analytics 4 (GA4) — provides 12 daily partitioned tables reflecting UI reports
    • Cloud Storage — supports incremental and truncated write preferences
    • External cloud storage providers:
      • Amazon S3 (supports cross-cloud transfer)
    • Data warehouses:
      • Teradata
      • Amazon Redshift
    • Third-party connectors (2025):
      • Salesforce Sales Cloud
      • Salesforce Marketing Cloud (SFMC)
      • Facebook Ads
      • Adobe Analytics

Transfer Data vs Speed Comparison

Data Migration Speeds

Choosing the Right Transfer Method

Method Best For Data Size Network Requirement
gcloud storage Ad-hoc, small transfers < 1 TB Standard internet
Storage Transfer Service Recurring, large cloud-to-cloud or on-premises transfers TB to PB scale Available network (supports private network)
Transfer Appliance One-time massive transfers, limited bandwidth Hundreds of TB to PB Minimal (physical shipping)
BigQuery Data Transfer Service SaaS data ingestion into BigQuery Varies Standard internet

GCP Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • GCP services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • GCP exam questions are not updated to keep up the pace with GCP updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. A company wants to connect cloud applications to an Oracle database in its data center. Requirements are a maximum of 9 Gbps of data and a Service Level Agreement (SLA) of 99%. Which option best suits the requirements?
    1. Implement a high-throughput Cloud VPN connection
    2. Cloud Router with VPN
    3. Dedicated Interconnect
    4. Partner Interconnect
  2. An organization wishes to automate data movement from Software as a Service (SaaS) applications such as Google Ads and Google Ad Manager on a scheduled, managed basis. This data is further needed for analytics and generate reports. How can the process be automated?
    1. Use Storage Transfer Service to move the data to Cloud Storage
    2. Use Storage Transfer Service to move the data to BigQuery
    3. Use BigQuery Data Transfer Service to move the data to BigQuery
    4. Use Transfer Appliance to move the data to Cloud Storage
  3. Your company’s migration team needs to transfer 1PB of data to Google Cloud. The network speed between the on-premises data center and Google Cloud is 100Mbps. The migration activity has a timeframe of 6 months. What is the efficient way to transfer the data?
    1. Use BigQuery Data Transfer Service to transfer the data to Cloud Storage
    2. Expose the data as a public URL and Storage Transfer Service to transfer it
    3. Use Transfer Appliance to transfer the data to Cloud Storage
    4. Use gcloud storage command to transfer the data to Cloud Storage
  4. Your company uses Google Analytics for tracking. You need to export the session and hit data from a Google Analytics 360 reporting view on a scheduled basis into BigQuery for analysis. How can the data be exported?
    1. Configure a scheduler in Google Analytics to convert the Google Analytics data to JSON format, then import directly into BigQuery using bq command line.
    2. Use gcloud storage to export the Google Analytics data to Cloud Storage, then import into BigQuery and schedule it using Cron.
    3. Import data to BigQuery directly from Google Analytics using Cron
    4. Use BigQuery Data Transfer Service to import the data from Google Analytics
  5. A company needs to automatically transfer new files from an AWS S3 bucket to Cloud Storage as soon as they are created, with minimal latency. What is the most efficient approach?
    1. Schedule Storage Transfer Service to run every 15 minutes
    2. Use a Lambda function to call the Cloud Storage API on each new object
    3. Configure Storage Transfer Service event-driven transfers using S3 Event Notifications and Amazon SQS
    4. Use gsutil rsync with a cron job
  6. An organization wants to establish private, high-bandwidth connectivity between their Google Cloud environment and their AWS infrastructure for a multicloud application. Which service should they use?
    1. Cloud VPN with HA configuration
    2. Partner Interconnect
    3. Cross-Cloud Interconnect
    4. Direct Peering
  7. A company needs to transfer 500 TB of data from Azure Blob Storage to Cloud Storage while keeping all traffic off the public internet and maintaining dedicated bandwidth. What combination should they use?
    1. Storage Transfer Service over public internet
    2. Storage Transfer Service with private network transfer over Cross-Cloud Interconnect
    3. Transfer Appliance
    4. gcloud storage cp command
  8. Your organization wants to centrally manage connectivity between multiple VPC networks, on-premises sites, and other cloud providers using a hub-and-spoke model. Which Google Cloud service should you use?
    1. Cloud Router
    2. VPC Network Peering
    3. Shared VPC
    4. Network Connectivity Center

References