Before you can synchronize Sigma metadata or generate technical lineage (in preview) in Collibra, ensure that the following prerequisites are met so that your Sigma site and Sigma API connection are configured correctly.
These tasks, which are performed both in Sigma and Collibra, enable secure, automated metadata ingestion.
In your Sigma environment
- You have a valid Sigma API Token or Service Account JSON Key with API access permissions.
- The Sigma user or service account must have access to the workspaces, dashboards, and datasets that you want to synchronize.
- You have identified the Sigma domains or workspace IDs from which you want to ingest. Optional filtering is available in the synchronization capability.
For complete information, refer to the Sigma API documentation.
In your Collibra environment
You can set up the Sigma integration in one of two environments:
- An Edge site installed in your infrastructure.
- A Collibra Cloud site (managed environment).
Available vaults
You can use a vault (such as HashiCorp Vault) to securely store your Sigma connection credentials and tokens when creating your Edge connection.
- Vaults are supported only for Edge sites.
- Collibra Cloud sites do not use external vaults for credential storage.
Environment
- You have created and installed an Edge site, or have been granted access to a Collibra Cloud site.
- The Edge site status must be Healthy in Collibra Console.
- If using an outbound proxy, ensure the configuration allows HTTPS traffic to api.sigmacomputing.com.
Network and proxy configuration
The following endpoints must be reachable from the Edge host:
- https://api.sigmacomputing.com
- https://app.sigmacomputing.com
Ensure that your Edge site can make the outbound connections outlined in the Network requirements section of the topic System requirements of an Edge site.
Collibra permissions
- You have a global role with the Catalog global permission, for example, Catalog Author.
- You have a global role that has the Manage Edge sites global permission.
- You have a global role that has the View Edge connections and capabilities global permission.
- You have a resource role with the Configure external system resource permission, for example, Owner.