Understand Databricks networking costs
Data transfer and connectivity refer to moving data into and out of Databricks environments. Networking charges for serverless products only apply to customers using Databricks serverless compute; customers using classic compute manage and pay related networking costs directly to AWS. Networking charges for performance-intensive products apply to all customers, regardless of compute type.
In-region storage access from serverless uses S3 gateway endpoints and is not charged by Databricks.
Identify billable connections
Connection 3 in the diagram below shows Databricks serverless workloads, which run in the Databricks-managed cloud account and access your data or services. You are charged for the associated data transfer and connectivity costs.
Connection 1 in the diagram shows inbound client connections (users and applications). For performance-intensive products (Lakebase, Delta Sharing Network Gateway, Zerobus, and Files API), Databricks charges for cross-region and public-internet egress back to the client. Client ingress and same-region egress are not charged. All other client access to Databricks, such as UI and API requests, is not charged. This charge is separate from any serverless networking charges and applies regardless of whether you use serverless or classic compute.
To understand your usage, see Billable usage system table reference.
Types of connectivity charges
Databricks charges for the following types of connectivity:
Connection type | Description | Billed | Timeline |
|---|---|---|---|
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 | Billing |
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 | Expected in the future |
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 | Billing |
Data Transfer (/GB) | Data transfer 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 | Billing |
For detailed pricing information, see Data transfer and connectivity.
A GB is treated as 2^30 bytes.
Cost management best practices
For practical guidance on optimizing Databricks costs while maintaining performance, see Best practices for cost optimization.