Connecting to Google’s Public and Private Cloud Services
Google offers two forms of private connectivity to Google Cloud. One is connectivity to the private RFC1918 space to access a customer built Virtual Private Cloud (VPC). The second provides access to Google Public route hosted applications.
Megaport supports both Private and Public options to access specific Google Cloud offerings. The Private space can be access by provisioning Partner Interconnect. Public access is supported via Direct Peering.
When connecting to Google Cloud Platform (GCP) via Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP. Through Partner Interconnect, a customer can access VMs (Virtual Machines) built within a projects VPC.
Examples of Services Offered
Cloud Spanner, Google Cloud BigQuery, Google Cloud Bigtable, Google Cloud Dataproc, Google Cloud Datastore, Google Cloud Pub/Sub, and Google Cloud Storage.
Benefits of connecting to Google Cloud Platform with Megaport using Partner Interconnect:
- Provides direct access to internal (RFC1918) network addresses
- Enables simplified hybrid cloud deployment
- Does not require the use and management of hardware VPN devices
- Provides dedicated bandwidth from 240+ Megaport locations with the ability to scale between 50Mbps – 10Gbps
- Enables you to connect automatically, workloads across any regions
access to any Google Cloud Region by interconnecting through a single location through Google’s backbone network.
For more details on provisioning Partner Interconnect with Megaport, please visit our dedicated article.
Direct Peering with Google is achieved by exchanging BGP routes between Google and the customer network.
When connecting to GCP Direct Peering with Megaport, the VXC forms a Layer 2 connection between the customer’s Megaport and Mega-IX or AMS-IX.
Examples of Services Offered:
G-Suite applications, Search, Youtube, Marketplace
Direct Peering Requirements:
- Publicly routable ASN
- Publicly routable address space (at least one /24 of IPv4 and/or one /48 of IPv6 space)
NOTE: Not all customers will meet Google’s Direct Peering requirements. The user is not required to have 24/7 NOC but must meet the remaining requirements outlined by Google.
Megaport – Google IX Peering Locations:
MegaIX: Ashburn, Dallas, Los Angeles, Seattle, Singapore, Sofia, Sydney
AMS-IX: Chicago, New York, Bay Area
For more details on provisioning Direct Peering with Megaport, please visit our dedicated article.