federate-lakehouse-catalog

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

1|Updated Aug 30, 2026
One-click install
npx skills add https://github.com/FeexSystems/3WM-SONIK-LABS --skill federate-lakehouse-catalog-feexsystems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: federate-lakehouse-catalog
Source: https://github.com/FeexSystems/3WM-SONIK-LABS/tree/main/.gemini/skills/federate-lakehouse-catalog
Command: npx skills add https://github.com/FeexSystems/3WM-SONIK-LABS --skill federate-lakehouse-catalog-feexsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Querying data stored in remote catalogs like Databricks Unity or AWS Glue from Google Cloud engines normally requires complex cross-cloud setup involving secrets, IAM roles, and trust policies. This Skill guides the entire federation workflow so you can query remote Iceberg data directly from BigQuery or Spark without moving it. ## Core Features & Use Cases - Databricks Unity Federation: Creates regional Secret Manager credentials and a federated BigLake Iceberg catalog pointing to a Unity Catalog instance. - AWS Glue Federation: Walks through IAM role creation with placeholder trust policies, scoped Glue/S3 permissions, catalog creation, and trust policy updates using the Google service account ID. - Region Pairing Guidance: Recommends optimal GCP regions paired with AWS regions to minimize cross-cloud query latency. - Validation & Troubleshooting: Verifies the federation by listing namespaces via the bq CLI and proposes meaningful analytical queries on the discovered data. - Use Case: A data team keeps tables in AWS Glue but wants analysts to query them in BigQuery. This Skill sets up the federated catalog, configures IAM trust, and validates that BigQuery can list and query the remote tables. ## Quick Start Ask the assistant to federate your lakehouse catalog to Databricks Unity or AWS Glue so you can query that 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 data from BigQuery?▼

Create a federated BigLake Iceberg catalog pointing to your Databricks Unity Catalog using gcloud alpha biglake iceberg catalogs create. Store your Databricks OAuth client ID and secret in a regional Secret Manager secret, then grant the catalog's service account secret accessor rights.

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

Create an AWS IAM role with a placeholder trust policy, attach Glue and S3 read permissions, then create a federated BigLake catalog with your AWS account ID as the glue-warehouse. Finally update the trust policy with the catalog's Google service account ID.

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

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

Why does my federated catalog return permission errors?▼

For AWS Glue, verify the IAM trust policy references the correct biglake-service-account-id in the aud and sub conditions. For Databricks, confirm the secret exists in the same region as the catalog and the service account has roles/secretmanager.secretAccessor.

Can I use this for running Databricks SQL queries directly?▼

No. This Skill only sets up federated catalogs so GCP engines like BigQuery can query remote Iceberg data. It does not support direct remote database SQL execution or managing Databricks clusters and AWS Glue jobs.