federate-lakehouse-catalog

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/Lathika-laa/Recipe_Box --skill federate-lakehouse-catalog-lathika-laa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: federate-lakehouse-catalog
Source: https://github.com/Lathika-laa/Recipe_Box/tree/main/.github/.gemini/skills/federate-lakehouse-catalog
Command: npx skills add https://github.com/Lathika-laa/Recipe_Box --skill federate-lakehouse-catalog-lathika-laa

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 credentials, IAM trust policies, and regional alignment. This Skill guides the entire federation workflow so remote Iceberg data becomes queryable from BigQuery and Spark without manual guesswork. ## Core Features & Use Cases - Databricks Unity Federation: Creates regional Secret Manager secrets for OAuth credentials and provisions a federated BigLake Iceberg catalog pointing to Unity. - AWS Glue Federation: Builds AWS IAM roles with placeholder trust policies, attaches scoped Glue and S3 permissions, and finalizes trust using the generated Google service account ID. - Region Pairing Guidance: Recommends optimal GCP regions paired with AWS regions to minimize cross-cloud query latency. - Use Case: A data team keeps tables in AWS Glue on S3 but wants analysts to query them in BigQuery; this Skill walks through IAM setup, catalog creation, and validation until queries return results. ## Quick Start Ask the assistant to federate your lakehouse catalog to Databricks Unity or AWS Glue so you can query that 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 data from BigQuery?▼

Create a federated BigLake Iceberg catalog of type unity using gcloud, storing your Databricks OAuth client ID and secret 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 federated BigLake catalog with your AWS account ID as the glue-warehouse. Update the trust policy with the generated Google service account ID and enable background refresh.

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

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

Why does my federated catalog validation fail after creation?▼

Common causes include the AWS trust policy not referencing the correct biglake-service-account-id, mismatched regions between the secret and catalog, or missing secretAccessor permissions. Verify each and consult the cross-cloud lakehouse troubleshooting documentation.

Can this skill run Databricks SQL queries or manage AWS Glue jobs?▼

No. It only sets up federated catalogs so remote metadata and data become queryable from GCP engines. Direct remote SQL execution, cluster management, and Glue job administration are explicitly out of scope.