Data Transfer & Connectivity
Customers using Databricks Serverless products may incur data transfer costs when they move data between different regions or availability zones within the same cloud, move data out of a cloud, or require public or private connectivity from their VPCs. Additionally, in certain high-throughput scenarios egress to client users and applications may also result in data egress charges. Please refer to the links below to see detailed information about data transfer pricing by cloud and type of data transfer.
Data Transfer & Connectivity FAQ
There are two ways customers may incur Databricks data transfer costs - Data transfer from Databricks Serverless products to your resources, and, in certain high-throughput use cases, data egress from Databricks back to client users and applications. Please refer to product documentation (AWS, Azure) for details.
| Connection type | Description | Billed |
|---|---|---|
| Private Connectivity (/GB) | Charges for per GB data processed. Databricks private connectivity allows you to connect to cloud resources without using a public IP. | Yes |
| Private Connectivity (/hour) | Charges for per hour private endpoint fees. Databricks private connectivity allows you to connect to cloud resources without using a public IP. | Yes* |
| Public Connectivity (/GB) | Charges for per GB data processed. Databricks public connectivity allows you to connect to cloud resources or the internet using public IP addresses. | Yes |
| Data Egress (/GB) | Data egress includes in-region data transfer between availability zones or from IPv4 address, data transfer to a different region, and data transfer to the internet or other clouds. | Yes |
* Please note that inbound and outbound data processed charges for Azure Private Link are waived indefinitely.
Pay as you go with a 14-day free trial or contact us for committed-use discounts or custom requirements.