21 docs tagged with "networking"

Add Atlan's addresses to your Databricks workspace IP access list (or a corporate firewall in the path) so crawlers and miners can connect.

Learn about the network identities Atlan presents to your data sources—public egress IPs, private CIDR ranges, and endpoint identities for AWS, Azure, and GCP tenants.

Compare the three ways Atlan can reach your Snowflake account—public IP allowlisting, Private Link, and the self-deployed agent—and pick the right one before you touch any cloud configuration.

Learn how Atlan supports private network connectivity to data sources in different AWS regions and across cloud providers.

Troubleshoot Databricks connectivity, covering network and private-link issues, authentication, permissions, extraction, and metadata questions.

Understand the three connectivity paths between Atlan and Databricks—public, Private Link, and site-to-site VPN—and what determines which one applies to your workspace.

A plain-language explanation of what a private link to Databricks is, who builds which half, and the three traffic paths between Atlan and Databricks.

Learn what a private link is, who is responsible for each part of the setup, and the three traffic paths between Atlan and Snowflake.

Definitions of the connectivity and identity terms used across Atlan's connector setup guides—endpoints, endpoint services, CIDR ranges, service principals, tenant settings, and more.

Connect Atlan to Google Cloud data sources using Private Service Connect: Google APIs PSC for BigQuery and GCS, or published-service PSC for VPC databases.

Classic AWS PrivateLink for Atlan: publish a VPC endpoint service backed by an NLB; covers AWS databases, on-premises sources, and multi-account hubs.

Share individual AWS databases with Atlan over PrivateLink using VPC resource gateways—no NLB, endpoint service, or target-group maintenance.

At-scale AWS private connectivity: one VPC Lattice service-network share reaches many databases across VPCs and accounts, with real hostnames for RDS IAM auth.

Azure Private Link for Atlan: direct private endpoints into PaaS services, or IaaS sources behind a Standard SKU ILB and Private Link Service.

A decision guide for connecting Atlan to your data sources privately, without crossing the public internet—which pattern fits your cloud and source.

Understand how AWS PrivateLink ensures all metadata traffic between Atlan and AWS SageMaker Unified Studio stays within the AWS private network.

For all details, see [Databricks documentation](https://docs.databricks.com/administration-guide/cloud-configurations/aws/privatelink.html).

Connect Atlan to an AWS-hosted Databricks workspace over AWS PrivateLink, so traffic never crosses the public internet.

Set up AWS PrivateLink between your Snowflake account and your Atlan tenant, including cross-region configurations.

Connect Atlan to an Azure Databricks workspace over Azure Private Link, including the endpoint approval handshake and the NSG rule.

Multiple workspaces, extra hostnames and custom ports, cross-cloud and cross-region setups, site-to-site VPNs, and the reversed traffic of lakehouse and MCP integrations.