Documentation
Deployment
Cube Cloud
VPC
GCP

Connecting with a VPC on GCP

Work with your Cube sales or customer success team to initiate this process.

  • VPC Peering requires Cube to be hosted in dedicated infrastructure. Let the Cube team know your Cube Cloud tenant name (e.g. example.cubecloud.dev) and what region the dedicated infrastructure should be hosted in. For best performance, select one of the "Supported Regions" listed below.
  • Cube will provision the dedicated VPC and provide the following information you can use to create the peering request:

Setup

VPC Peering

After receiving the information above, create a VPC peering request (opens in a new tab), either through the GCP Web Console (opens in a new tab) or an infrastructure-as-code tool. To send a VPC peering request through the Google Cloud Console, follow the instructions here (opens in a new tab), with the following amendments:

  • In Step 6, use the project name XXXXX, and the project ID and network name(s) provided by Cube.
  • In Step 7, ensure Import custom routes and Export custom routes are selected so that the necessary routes are created.

Supported Regions

We support all general-purpose regions. Cube Store is currently located only in US Central 1 and Europe West 2 so pre-aggregations performance might depend on geographical proximity to it.

Notes

Cloud SQL

Google Cloud SQL databases can only be peered to a VPC within the same GCP project (opens in a new tab). To work around this limitation, we recommend that customers provision a micro VM in their Google Cloud account to run the Cloud SQL Auth Proxy (opens in a new tab).

VPC PeeringAzure