33 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.

Everything IP- and firewall-related for dbt - dbt Cloud's IP restrictions feature, and storage-side firewalls for dbt Core buckets.

What identity Atlan presents to your AWS account for AWS Glue, which values are tenant-specific, and exactly what to request from support in a single ticket.

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 Amazon Redshift cluster or Serverless workgroup - public IP allowlisting, the AWS private network link, and the self-deployed agent.

Pick how Atlan proves its identity to AWS Glue - IAM access keys, a cross-account IAM role, or the self-deployed agent.

Compare the two ways Atlan can read your dbt metadata - the dbt Cloud API with a token, or dbt output files in a cloud storage bucket for dbt Core.

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.

Allow Atlan's fixed source IPs through your security group so crawlers and miners can connect to publicly accessible Amazon Redshift clusters and workgroups.

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.

Learn how Atlan reads your AWS Glue Data Catalog - the traffic path, the two ways of proving identity, and the two-key door that makes role-based access safe.

Learn the three traffic paths between your dbt setup and Atlan - the dbt Cloud API pull, the storage-bucket read, and your own upload pipeline.

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.

Learn how Redshift-managed VPC endpoints work, who builds which half, and the three traffic paths between Atlan and Amazon Redshift.

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 a private Amazon Redshift cluster over a Redshift-managed VPC endpoint, so traffic never crosses the public internet.

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.

Amazon Redshift Serverless, DC2 clusters, multiple clusters, cross-region and cross-cloud tenants, external (Glue/Spectrum) schemas, and sources reachable only from inside your network.

Symptom-first troubleshooting for Amazon Redshift connectivity - timeouts, IAM policy scope, role trust, DNS, password failures, Serverless quirks, and sudden breakage.