Data Transfer Cost
Data transfer can be traffic coming into Zilliz Cloud, leaving Zilliz Cloud out into the internet, or in between two resources within Zilliz Cloud. Data transfer costs in Zilliz Cloud are billed based on the amount of data transferred.
The following table compares the different data transfer types.
Data Transfer Type | Description | Common Scenarios | Pricing |
---|---|---|---|
Public Internet Egress | The transfer of data from Zilliz Cloud to destinations over the public internet, such as external networks, client applications, or third-party services outside the cloud provider’s private network. | Returning search or query results to a client app hosted outside the cloud provider. | The most expensive. For detailed rates, see Zilliz Cloud Pricing Guide. |
Cross-region Transfer | The movement of data between different regions within the same cloud provider’s network, which may incur additional latency and costs compared to intra-region transfer. |
|
|
Intra-region Transfer | The transfer of data between within the same region of a cloud provider, typically incurring lower latency and cost than cross-region transfers. |
| Free |
Sources of data transfer cost
You will be billed for data transfer in the following scenarios:
-
Operations like search/query
-
Forwarding audit logs to cloud object storage
-
Zero downtime migration data sync
If the data transfer occurs within the same cloud region, the cost may be $0.
If you use a private endpoint to conduct operations like search or query, no data transfer cost will incur.
Cost calculation
Data Transfer Cost = Data Transfer Unit Price × Transferred Data Size
-
Data Transfer Unit Price: Determined by cluster cloud provider and region, data transfer type (public internet, cross-region, or intra-region). For detailed rates, see Zilliz Cloud Pricing Guide.
-
Transferred Data Size: Measured in GB and calculated based on the size of the data sent over the network.
Examples
The following are some examples to help you understand how storage costs are calculated.
Example 1: Public internet egress
Suppose your cluster is deployed in AWS us-east-1 (Virginia) and you return search results to clients via the public internet:
-
Transferred Data Size: 500 GB over one month
-
Transfer Type: Public Internet Egress
-
Unit Price: $0.09/GB (based on AWS us-east-1 public internet egress rate)
The data transfer cost is $0.09 × 500 = $45.00
.
Example 2: Cross-region transfer
Suppose your cluster is deployed in GCP us-west1 (Oregon) and you need to back up this cluster to 2 different regions, GCP us-central1 (Iowa) and GCP europe-west3 (Frankfurt):
-
Backup File Size: 20 GB
-
Transfer Type: Cross-region Transfer
-
Unit Price:
-
Data transfer from GCP us-west1 (Oregon) to GCP us-central1 (Iowa) is billed at the same-continent cross-region rate of $0.01/GB.
-
Data transfer from GCP us-west1 (Oregon) to GCP europe-west3 (Frankfurt) is billed at the different-continent cross-region rate of $0.08/GB.
-
The data transfer cost is $0.01 × 20 + $0.08 x 20 = $1.80
.
Example 3: Intra-region transfer
Suppose you have enabled audit logging for your cluster deployed in AWS us-east-1 (Virginia) and you need to forward the audit logs of this cluster to an AWS S3 bucket created in the same cloud region. The data transfer cost in this case will be $0 because intra-region data transfer is free of charge.