federate-lakehouse-catalog

Configures Google Cloud Lakehouse federated catalogs connecting to Databricks Unity or AWS Glue.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Yashyasik/zexca-api --skill federate-lakehouse-catalog-yashyasik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: federate-lakehouse-catalog
Source: https://github.com/Yashyasik/zexca-api/tree/main/.gemini/skills/federate-lakehouse-catalog
Command: npx skills add https://github.com/Yashyasik/zexca-api --skill federate-lakehouse-catalog-yashyasik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up cross-cloud data federation between Google Cloud and remote Iceberg REST catalogs like Databricks Unity or AWS Glue involves complex IAM, secret management, and region-pairing steps that are error-prone when done manually. ## Core Features & Use Cases - Databricks Unity Federation: Creates regional Secret Manager secrets and BigLake federated catalogs pointing to Databricks Unity Catalog with proper service account permissions. - AWS Glue Federation: Guides creation of AWS IAM roles with placeholder trust policies, scoped Glue/S3 permissions, and catalog creation using the AWS Account ID as the warehouse. - Validation & Troubleshooting: Verifies federation by listing namespaces via the bq CLI and provides region-pairing guidance to minimize cross-cloud latency. - Use Case: A data engineer wants to query S3 data cataloged in AWS Glue directly from BigQuery without migrating the data; this Skill walks through IAM setup, catalog creation, and query validation. ## Quick Start Ask the assistant to federate your lakehouse catalog to Databricks Unity or AWS Glue so you can query remote data from BigQuery.

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 Databricks Unity Catalog data from BigQuery?▼

Create a BigLake federated catalog of type unity using gcloud alpha biglake iceberg catalogs create, storing your Databricks OAuth credentials in a regional Secret Manager secret. Grant the catalog's service account secretAccessor access, then query tables via BigQuery in the same region.

How to connect AWS Glue Data Catalog to Google Cloud BigQuery?▼

Create an AWS IAM role with a placeholder trust policy, attach Glue and S3 read permissions, then create a BigLake federated catalog with --glue-warehouse set to your 12-digit AWS Account ID. Update the trust policy with the catalog's biglake-service-account-id and enable background refresh.

Which GCP region should I pair with my AWS region for lakehouse federation?▼

Choose GCP regions with low-latency dedicated connections to your AWS region. For example, AWS us-east-1 pairs with GCP us-east4, us-west-2 with us-west1, eu-west-2 with europe-west2, and eu-central-1 with europe-west3.

Why does my federated catalog fail to refresh metadata from AWS Glue?▼

Refresh failures usually occur because the AWS IAM trust policy still contains placeholder values instead of the catalog's biglake-service-account-id, or the Glue and S3 permissions are not scoped correctly. Verify the trust policy and IAM permissions, then enable the refresh interval.

Can this skill run Databricks SQL queries or manage Databricks clusters?▼

No. This skill only sets up federated catalogs so GCP engines can query remote data. It does not execute SQL directly against Databricks SQL warehouses or manage Databricks clusters, AWS Glue jobs, or other remote infrastructure.