Skip to main content

Documentation Index

Fetch the complete documentation index at: https://cubed3-docs-cub-2416-update-semantic-snowflake-semantic-vie.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

  • VPC Peering requires Cube to be hosted in single-tenant infrastructure. Let the Cube team know your Cube Cloud tenant name (e.g. example.cubecloud.dev) and what region the single-tenant 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, either through the GCP Web Console or an infrastructure-as-code tool. To send a VPC peering request through the Google Cloud Console, follow the instructions here, 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. 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.