Getting Started with External Catalogs

The how-to guides linked on this page illustrate how to link an external catalog with Immuta to ingest tags and add value to the Immuta modules: Secure and Discover.

Best practice: Use a single catalog; having more than one can lead to multiple truths and data leaks.

Requirement: A catalog with tags that correspond to your Immuta data sources

Configuration process

  1. When changes are made to the external catalog, refresh external tags.

Requirements:

  • A physical data dictionary with assets that correspond to your Immuta data sources

  • The Collibra global role Catalog or Catalog Author

Configuration process

  1. When changes are made to the external catalog, refresh external tags.

Requirements:

  • A catalog with assets that correspond to your Immuta data sources

  • The ability to create a registered app in the Azure portal

Configuration process

  1. When changes are made to the external catalog, refresh external tags.

Requirements:

Configuration process

  1. When changes are made to the external catalog, refresh external tags.

Requirements:

Configuration process

Once you register data sources, table and column tags from Databricks Unity Catalog will be ingested and applied to the corresponding data sources in Immuta.

Requirements:

  • A Snowflake user who can set the following permissions:

    1. GRANT IMPORTED PRIVILEGES ON DATABASE snowflake

    2. GRANT APPLY TAG ON ACCOUNT

  • Snowflake Enterprise Edition or higher

Configuration process

  1. When changes are made to the tags in Snowflake, refresh external tags.

Last updated

Copyright © 2014-2024 Immuta Inc. All rights reserved.