To collect metadata from a data source and add it into Collibra via an Edge or Collibra Cloud site, Edge or Collibra Cloud need to be able to communicate with the data source. This is managed via a connection. Once a connection is established, it can be used by some of the Collibra capabilities to, for example, register the metadata or collect sample data.
You want to add the metadata of a Snowflake data source in Collibra and create technical lineage for it. By defining a JDBC connection between Edge and your Snowflake data source, you establish a secure line of communication between Collibra and your data source. This line of communication is then used to register the metadata and create technical lineage for it in your Collibra platform.
Multiple connection types are available. The connection type that you need to use depends on what you want to achieve. The following table contains the available connection types and the associated capabilities.
| Connection type | Description | Supported for Edge sites? | Supported for Collibra Cloud sites? |
|---|---|---|---|
| AWS (Amazon Web Services) |
Used for the integration and protection of Amazon S3 data sources and Amazon SageMaker AI models. |
 Yes
|
Yes
|
| Azure |
Used for the integration of Azure Data Lake Storage (ADLS) data sources, Azure AI Foundry models and agents, and Microsoft Azure AI models. |
Yes
|
Yes
|
| Databricks |
Used for the integration of Databricks Unity Catalog. |
Yes
|
Yes
|
| dbt |
Used for the integration of |
Yes
|
 No |
| GCP (Google Cloud Platform) |
Used for the integration and protection of Google Cloud Storage and Dataplex data sources. |
Yes
|
Yes
|
|
Allows workflows to communicate with other HTTP systems, such as external REST APIs. |
Yes
|
Yes
|
|
Used to connect to Informatica Intelligent Cloud Services. |
Yes
|
No |
|
|
Used to connect to JDBC data sources, for example, Snowflake, Salesforce, and PostgreSQL. In most cases, you need to create a connection for each database you want to register. Some data sources, however, allow you to use a single connection to register multiple databases. You can find this information in the Supports registration of multiple databases? in Overview of connectors. Show associated capabilities
|
Yes
|
Yes, limited depending on the capability. For more information, go to available capabilities.
|
| Looker |
Used to connect to Looker. |
Yes
|
No |
|
Used to connect to Matillion. |
Yes
|
No |
|
| Microsoft SSRS-PBRS |
Used to connect to SSRS-PBRS. |
Yes
|
No |
| MicroStrategy |
Used to connect to MicroStrategy. |
Yes
|
No |
| MLflow |
Used to connect to MLflow. |
Yes
|
Yes
|
| Power BI |
Used to connect to Power BI. |
Yes
|
Yes
|
| SAP AI Core |
Used to connect to SAP AI Core. |
Yes
|
Yes
|
|
Used to connect to SAP Analytics Cloud. Show associated capabilities
|
Yes
|
Yes
|
|
| Shared Storage connection |
Used to access files from a shared folder. |
Yes
|
No |
| Tableau |
Used to connect to Tableau Server or Tableau Online. |
Yes
|
Yes
|
| Technical Lineage Admin |
Used to connect to the Collibra Data Lineage service instances, to run any of the following technical lineage admin options:
|
Yes
|
Yes
|