หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
Important
Lakebase Autoscaling is the latest version of Lakebase, with autoscaling compute, scale-to-zero, branching, and instant restore. For supported regions, see Region availability. If you are a Lakebase Provisioned user, see Lakebase Provisioned.
Configuring Private Link for Lakebase Autoscaling keeps all traffic off the public internet. The endpoints you need depend on how your applications connect to Lakebase:
- Inbound Private Link is required. It covers Azure Databricks REST API calls and workspace traffic.
- Inbound Private Link for performance-intensive services (Service Direct Private Link, port 5432) is required if your applications connect using a Postgres client (such as psql, a Postgres driver, or an ORM) or if you use the Tables editor or SQL Editor in the Lakebase App. If your applications connect only through the Data API, you do not need this endpoint.
Lakebase Autoscaling routes these two traffic types through separate network paths, each with its own endpoint. Postgres client connections, the Tables editor, and the SQL Editor use a dedicated high-performance regional ingress with a hostname in the form *.database.<region>.cloud.databricks.com.
Private Link endpoints
| Endpoint | Traffic type | Port | Notes |
|---|---|---|---|
| Inbound Private Link | Azure Databricks REST API and workspace connectivity | 443 | Standard Azure Databricks workspace-level Private Link. |
| Inbound Private Link for performance-intensive services | Postgres database connections, Tables editor, and SQL Editor | 5432 | Covers the high-performance regional ingress used by Lakebase Autoscaling. Required for Postgres clients, drivers, and tools connecting directly to the database endpoint. Also required for the Tables editor and SQL Editor in the Lakebase App. |
Troubleshoot Private Link connectivity
If the Tables editor or SQL Editor in the Lakebase App displays a "Failed to fetch" or "Unknown error" message, the workspace likely has inbound Private Link configured but is missing inbound Private Link for performance-intensive services.
The Tables editor and SQL Editor route their database traffic through the same high-performance regional ingress as Postgres clients. Both Private Link endpoints are required for the Tables editor and SQL Editor to function correctly.
To resolve this, configure inbound Private Link for performance-intensive services. See Configure inbound Private Link for performance-intensive services.