Menu

Azure Databricks + Snowflake Catalog Federation Over Private Link: The Two-Hostname Trap
πŸ“°

Azure Databricks + Snowflake Catalog Federation Over Private Link: The Two-Hostname Trap

DEV Community: azureΒ·Bhargav BhattΒ·12 days ago
#zU9IWPQ9
#devtoazure#devto#dev#snowflake#databricks
Reading 0:00
15s threshold

The Problem

You've got Azure Databricks and Snowflake in the same region. Your security team mandates no public internet egress from the compute plane. You set up Private Link. You create the connection in Databricks. You run a federated query.

It fails.

Not with a permission error. Not with a schema mismatch. With a DNS resolution failure β€” NXDOMAIN β€” on a hostname that should resolve.

The root cause: you used the same hostname in two places that require different ones.

This article walks through the exact network topology, the DDL, and the failure mode so you can set this up in one pass instead of three.

The Architecture in One Diagram

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Your Azure VNet β”‚ β”‚ β”‚ β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”‚ β”‚ Azure Databricks (two planes) β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”‚ β”‚ β”‚ β”‚ Control Plane β”‚ β”‚ Compute Plane (Serverless / β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ (managed by MSFT) β”‚ │…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.