Data Lake Formation (DLF) is available in multiple regions. Each region has dedicated endpoints for accessing the DLF metadata API. Use the endpoint for the region where your data resides to minimize latency and avoid cross-region data transfer.
Choose an endpoint type
DLF provides two endpoint types:
| Endpoint type | Network path | Protocol support | When to use |
|---|---|---|---|
| VPC endpoint | Internal Alibaba Cloud network | HTTP and HTTPS | Default choice for compute engines running inside a Virtual Private Cloud (VPC) — lower latency, no public network exposure |
| OpenAPI public endpoint | Public internet | HTTPS only | Access from outside Alibaba Cloud, or when VPC access is not available |
OpenAPI public endpoints are disabled by default because they allow public network access. To enable one, an administrator must manually configure it: go to Data Catalog, open the target catalog, and on the Catalog Configuration tab, add or update theenable.openapiadvanced configuration and set its value totrue. You must also configure the OSS public endpoint before using an OpenAPI public endpoint.
For more information, see Public preview: Access DLF Paimon REST over the public network.
Paimon REST
VPC endpoints follow the pattern {region-id}-vpc.dlf.aliyuncs.com. OpenAPI public endpoints follow the pattern dlfnext.{region-id}.aliyuncs.com.
| Region | Region ID | VPC endpoint | OpenAPI public endpoint |
|---|---|---|---|
| China (Hangzhou) | cn-hangzhou | cn-hangzhou-vpc.dlf.aliyuncs.com | dlfnext.cn-hangzhou.aliyuncs.com |
| China (Beijing) | cn-beijing | cn-beijing-vpc.dlf.aliyuncs.com | dlfnext.cn-beijing.aliyuncs.com |
| China (Shanghai) | cn-shanghai | cn-shanghai-vpc.dlf.aliyuncs.com | dlfnext.cn-shanghai.aliyuncs.com |
| China (Shenzhen) | cn-shenzhen | cn-shenzhen-vpc.dlf.aliyuncs.com | dlfnext.cn-shenzhen.aliyuncs.com |
| China (Ulanqab) | cn-wulanchabu | cn-wulanchabu-vpc.dlf.aliyuncs.com | dlfnext.cn-wulanchabu.aliyuncs.com |
| China (Hong Kong) | cn-hongkong | cn-hongkong-vpc.dlf.aliyuncs.com | dlfnext.cn-hongkong.aliyuncs.com |
| Germany (Frankfurt) | eu-central-1 | eu-central-1-vpc.dlf.aliyuncs.com | dlfnext.eu-central-1.aliyuncs.com |
| Japan (Tokyo) | ap-northeast-1 | ap-northeast-1-vpc.dlf.aliyuncs.com | dlfnext.ap-northeast-1.aliyuncs.com |
| Singapore | ap-southeast-1 | ap-southeast-1-vpc.dlf.aliyuncs.com | dlfnext.ap-southeast-1.aliyuncs.com |
| Indonesia (Jakarta) | ap-southeast-5 | ap-southeast-5-vpc.dlf.aliyuncs.com | dlfnext.ap-southeast-5.aliyuncs.com |
| US (Silicon Valley) | us-west-1 | us-west-1-vpc.dlf.aliyuncs.com | dlfnext.us-west-1.aliyuncs.com |
| US (Virginia) | us-east-1 | us-east-1-vpc.dlf.aliyuncs.com | dlfnext.us-east-1.aliyuncs.com |
OpenAPI endpoint limitations
-
Naming limitations: Database and table names can contain only letters, digits, and specific symbols.
-
Performance: OpenAPI public endpoints have slightly higher latency than VPC endpoints.
Iceberg REST
All Iceberg REST endpoints are VPC-only. Each endpoint appends /iceberg to the base VPC domain: {region-id}-vpc.dlf.aliyuncs.com/iceberg.
| Region | Region ID | VPC endpoint |
|---|---|---|
| China (Hangzhou) | cn-hangzhou | cn-hangzhou-vpc.dlf.aliyuncs.com/iceberg |
| China (Beijing) | cn-beijing | cn-beijing-vpc.dlf.aliyuncs.com/iceberg |
| China (Shanghai) | cn-shanghai | cn-shanghai-vpc.dlf.aliyuncs.com/iceberg |
| China (Shenzhen) | cn-shenzhen | cn-shenzhen-vpc.dlf.aliyuncs.com/iceberg |
| China (Ulanqab) | cn-wulanchabu | cn-wulanchabu-vpc.dlf.aliyuncs.com/iceberg |
| China (Hong Kong) | cn-hongkong | cn-hongkong-vpc.dlf.aliyuncs.com/iceberg |
| Germany (Frankfurt) | eu-central-1 | eu-central-1-vpc.dlf.aliyuncs.com/iceberg |
| Japan (Tokyo) | ap-northeast-1 | ap-northeast-1-vpc.dlf.aliyuncs.com/iceberg |
| Singapore | ap-southeast-1 | ap-southeast-1-vpc.dlf.aliyuncs.com/iceberg |
| Indonesia (Jakarta) | ap-southeast-5 | ap-southeast-5-vpc.dlf.aliyuncs.com/iceberg |
| US (Silicon Valley) | us-west-1 | us-west-1-vpc.dlf.aliyuncs.com/iceberg |
| US (Virginia) | us-east-1 | us-east-1-vpc.dlf.aliyuncs.com/iceberg |