Supported regions and CCI capabilities

This section maps AWS regions to Google Cloud regions for querying remote data and outlines the Cross-Cloud Interconnect (CCI) capabilities.

Supported Cross-Cloud Interconnect capabilities

Lakehouse supports routing query data reads, background metadata refresh, or both privately over Cross-Cloud Interconnect depending on whether your network isolation and cost requirements apply to object storage reads, control-plane catalog endpoints, or end-to-end cross-cloud traffic:

  • Query transport (--service-directory-name): Routes query reads to remote object storage (Amazon S3 on Amazon Web Services (AWS) or Microsoft Azure Data Lake Storage Gen2 on Azure) to help reduce egress costs and provide predictable query throughput.
  • Background metadata refresh (--metadata-service-directory-name): Routes control-plane background metadata refresh and authentication requests from the Lakehouse runtime catalog privately to remote catalog AWS PrivateLink or Azure Private Link endpoints.
  • Supported catalogs and clouds:

    # disableFinding(CORRECTION_VARIABLE_CLOUD) #

    AWS Glue Data Catalog: AWS (Cross-Cloud Interconnect or Partner Cross-Cloud Interconnect).
    • Databricks Unity Catalog: AWS (Cross-Cloud Interconnect or Partner Cross-Cloud Interconnect) and Azure (Cross-Cloud Interconnect).
    • Snowflake Horizon Catalog: AWS (Cross-Cloud Interconnect or Partner Cross-Cloud Interconnect) and Azure (Cross-Cloud Interconnect).

For Azure deployments, create your federated catalog in the Google Cloud region closest to your Azure region and interconnect location. For supported Azure peering locations, see Choose locations for Cross-Cloud Interconnect for Azure.

Interconnect classifications

Lakehouse supports the following two types of Cross-Cloud Interconnect connections:

  • Partner Cross-Cloud Interconnect (Partner CCI): Provides pre-provisioned connectivity between Google Cloud and designated AWS regions through a supported partner. For more information, see the Partner Cross-Cloud Interconnect for AWS overview.
  • Cross-Cloud Interconnect (CCI): Provides a direct physical connection between the Google network and your cloud service provider. Cross-Cloud Interconnect is supported across all listed AWS and Azure regions. For more information, see the Cross-Cloud Interconnect overview.

Considerations

  • In the region mapping table, the Low Latency column indicates region pairs where the AWS region, the interconnect facility, and the closest Google Cloud region are in the same geographical metropolitan area.
  • If possible, choose a region pair with Low Latency or Partner CCI to ensure optimal performance when you federate large datasets across clouds.

AWS to Google Cloud region mapping

AWS Region Name AWS Region Metro Closest Google Cloud Region Name Closest Google Cloud Region Metro Partner CCI Low Latency Top 3 Alternative Google Cloud Regions
us-east-1 N. Virginia us-east4 Ashburn, VA ✓ ✓ us-east1, us-east5, us-central1
us-east-2 Ohio us-east5 Columbus, OH ✓ us-east4, us-east1, us-central1
us-west-1 N. California us-west2 Los Angeles, CA ✓ us-west4, us-west1, us-west3
us-west-2 Oregon us-west1 The Dalles, OR ✓ ✓ us-west3, us-west4, us-west2
ca-central-1 Montreal northamerica-northeast1 Montreal ✓ northamerica-northeast2, us-east4, us-east5
sa-east-1 São Paulo southamerica-east1 São Paulo ✓ southamerica-west1, us-east1, us-south1
eu-west-1 Ireland europe-west1 Belgium europe-west2, europe-west9, europe-west4
eu-west-2 London europe-west2 London ✓ ✓ europe-west1, europe-west9, europe-west4
eu-west-3 Paris europe-west9 Paris ✓ europe-west1, europe-west2, europe-west3
eu-central-1 Frankfurt europe-west3 Frankfurt ✓ ✓ europe-west4, europe-west1, europe-west6
eu-central-2 Zurich europe-west6 Zurich europe-west8, europe-west12, europe-west3
eu-north-1 Stockholm europe-north2 Stockholm ✓ ✓ europe-north1, europe-west4, europe-central2
eu-south-1 Milan europe-west8 Milan europe-west12, europe-west6, europe-west3
eu-south-2 Spain (Aragon) europe-southwest1 Madrid europe-west9, europe-west1, europe-west8
me-central-1 UAE me-central1 Doha me-central2, me-west1, asia-south1
me-south-1 Bahrain me-central2 Dammam me-central1, me-west1, asia-south1
af-south-1 Cape Town europe-southwest1 Madrid me-central2, me-west1, europe-west1
ap-east-1 Hong Kong asia-east2 Hong Kong ✓ asia-east1, asia-southeast3, asia-southeast1
ap-northeast-1 Tokyo asia-northeast1 Tokyo ✓ asia-northeast2, asia-northeast3, asia-east1
ap-northeast-2 Seoul asia-northeast3 Seoul ✓ asia-northeast2, asia-northeast1, asia-east1
ap-northeast-3 Osaka asia-northeast2 Osaka ✓ asia-northeast1, asia-northeast3, asia-east1
ap-south-1 Mumbai asia-south1 Mumbai ✓ asia-south2, me-central1, asia-southeast1
ap-south-2 Hyderabad asia-south2 Delhi asia-south1, asia-southeast1, me-central1
ap-southeast-1 Singapore asia-southeast1 Singapore ✓ ✓ asia-southeast2, asia-southeast3, asia-east1
ap-southeast-2 Sydney australia-southeast1 Sydney ✓ ✓ australia-southeast2, asia-southeast2, asia-southeast1
ap-southeast-3 Jakarta asia-southeast2 Jakarta ✓ asia-southeast1, asia-southeast3, australia-southeast1

What's next