17 docs tagged with "privatelink"

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.

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

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.

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.

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.

Keep traffic between your GCP-hosted Atlan tenant and your Cloud SQL for PostgreSQL instance entirely on Google's internal network with Private Service Connect.

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

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.

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

Keep Atlan's BigQuery API traffic off the public internet with Google Private Service Connect - Atlan builds the private endpoint; you paste one DNS name.

Let Atlan's SaaS reach your AlloyDB for PostgreSQL privately over Google's internal network - no public IP, nothing deployed on your side beyond a service attachment.