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.
Link an Alation external catalog
Requirement: A catalog with tags that correspond to your Immuta data sources
Configuration process
When changes are made to the external catalog, refresh external tags.
Link a Collibra external catalog
Requirements:
A physical data dictionary with assets that correspond to your Immuta data sources
The Collibra global role
CatalogorCatalog Author
Configuration process
When changes are made to the external catalog, refresh external tags.
Link a Microsoft Purview external catalog
Requirements:
A catalog with tags that correspond to your Immuta data sources
The ability to create a registered app in the Azure portal
Configuration process
When changes are made to the external catalog, refresh external tags.
Link a custom REST catalog
Requirements:
A catalog with tags that correspond to your Immuta data sources
Configuration process
When changes are made to the external catalog, refresh external tags.
Link Databricks Unity Catalog for tag ingestion
Requirements:
Fewer than 2,500 Databricks Unity Catalog data sources registered in Immuta
Databricks privileges listed on the Configure a Databricks Unity Catalog integration page
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.
Link Snowflake for tag ingestion
Requirements:
A Snowflake user who can set the following permissions:
GRANT IMPORTED PRIVILEGES ON DATABASE snowflakeGRANT APPLY TAG ON ACCOUNT
Snowflake Enterprise Edition or higher
Configuration process
Configure Snowflake tag ingestion in Immuta.
When changes are made to the tags in Snowflake, refresh external tags
Last updated