federate-lakehouse-catalog

Federate remote Iceberg REST catalogs into Google Cloud BigLake for cross-cloud querying.

2|1|Updated May 25, 2026
One-click install
npx skills add https://github.com/interflownex/All-in-One --skill federate-lakehouse-catalog-interflownex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: federate-lakehouse-catalog
Source: https://github.com/interflownex/All-in-One/tree/main/.gemini/skills/federate-lakehouse-catalog
Command: npx skills add https://github.com/interflownex/All-in-One --skill federate-lakehouse-catalog-interflownex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the complexity of cross-cloud data access by enabling BigQuery to query remote Iceberg catalogs like Databricks Unity and AWS Glue without moving the underlying data.

Core Features & Use Cases

  • Cross-Cloud Federation: Seamlessly link Databricks Unity Catalog or AWS Glue to Google Cloud BigLake.
  • Unified Analytics: Query remote data residing in AWS or Databricks directly from BigQuery or Spark engines.
  • Use Case: A data analyst needs to join e-commerce transaction data stored in AWS Glue with customer profile data in BigQuery to generate a unified report without performing expensive ETL migrations.

Quick Start

Use the federate-lakehouse-catalog skill to connect my AWS Glue data catalog to BigQuery in the us-east4 region.

Frequently Asked Questions about federate-lakehouse-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query remote Iceberg tables in BigQuery without moving data?

Query remote Iceberg tables in BigQuery by federating remote REST catalogs into Google Cloud BigLake. This cross-cloud federation connects catalogs like Databricks Unity Catalog or AWS Glue directly, enabling unified analytics without expensive ETL migrations.

Can I connect AWS Glue or Databricks Unity Catalog to BigQuery?

Yes, you can connect AWS Glue or Databricks Unity Catalog to BigQuery. The federation process links these remote Iceberg REST catalogs to Google Cloud BigLake, allowing BigQuery and Spark engines to query cross-cloud data seamlessly.

What credentials do I need to federate remote Iceberg catalogs into BigLake?

Federating remote Iceberg catalogs into BigLake requires configuring cloud-specific credentials, IAM roles, and regional secret management. These secure configurations establish low-latency data access across multiple cloud providers.

Does cross-cloud BigLake federation support querying data from multiple cloud providers?

Yes, BigLake federation supports querying remote data across multiple cloud providers. It integrates with Databricks Unity Catalog and AWS Glue, allowing BigQuery to access remote data residing in AWS or Databricks directly.

How does BigQuery federation with Iceberg catalogs handle cross-cloud data access?

BigQuery federation with Iceberg catalogs handles cross-cloud data access by linking remote REST catalogs to BigLake. This mechanism queries remote data in AWS or Databricks directly from BigQuery, eliminating the need to move underlying data.