Collibra Data Lineage service instances are cloud-hosted endpoints that process and store technical lineage metadata. When Edge synchronizes technical lineage, it connects to these service instances to transmit metadata and retrieve lineage information.
To allow Edge to synchronize technical lineage, your network must permit outbound traffic to the Collibra Data Lineage service instances.
Configuration requirements
Follow these requirements when configuring your firewall and network settings to ensure reliable connectivity to Collibra Data Lineage service instances.
- Uses the HTTPS protocol by default and uses port 443.
- Always use DNS names in your network configurations. IP addresses are dynamic and subject to change. If your firewall requires an IP address, use a utility like nslookup to find the current mapping.
- You must allow all service instances within your geographic location. For example, for data in Europe, you must allow
techlin-eu-central-1.collibra.com (AWS)andtechlin-europe-west1.collibra.com (GCP). - We highly recommend allowing the
techlin-us-east-1.collibra.cominstance. Edge uses this as a secondary endpoint for license verification if your primary regional instance is unreachable.
Service instance DNS names
When Edge synchronizes technical lineage, it automatically connects to the instance matching your cloud provider and geographic location.
| Region | DNS name |
|---|---|
| aws-ca | techlin-ca-central-1.collibra.com |
| aws-eu | techlin-eu-central-1.collibra.com |
| aws-me | techlin-me-central-1.collibra.com |
| aws-sg | techlin-ap-southeast-1.collibra.com |
| aws-us | techlin-us-east-1.collibra.com |
| gcp-au | techlin-australia-southeast1.collibra.com |
| gcp-ca | techlin-northamerica-northeast1.collibra.com |
| gcp-eu | techlin-europe-west1.collibra.com |
| gcp-sg | techlin-asia-southeast1.collibra.com |
| gcp-uk | techlin-europe-west2.collibra.com |
| gcp-us | techlin-us-east1.collibra.com |
In October 2024, we completed a migration to the DNS names shown in this table. If Edge is unable to retrieve the API key using these DNS names, it tries the old DNS names.