This page describes pricing for Storage Transfer Service.
Service | Price* (USD) |
|---|---|
Agentless transfers | No charges |
Agent-based transfers to or from file systems | $0.0125 / 1 gibibyte |
Agent-based transfers from S3-compatible storage | No charges |
Agent-based transfers from HDFS | No charges |
Transfers from S3 over managed private network within Canada | $0.03 / 1 gibibyte |
Transfers from S3 over managed private network within North America | $0.03 / 1 gibibyte |
Transfers from S3 over managed private network within EU | $0.04 / 1 gibibyte |
Transfers from S3 over managed private network within APAC | $0.08 / 1 gibibyte |
* You will be charged this fee in addition to charges associated with network usage and operations performed by the service at source and destinations on your behalf.
The following sections provide detailed information about the pricing for different transfer scenarios.
You are charged for data stored on Cloud Storage as documented in Cloud Storage pricing.
External cloud providers' costs may apply while you use Storage Transfer Service.
The following charges may apply when you use Storage Transfer Service, regardless of the source:
The following charges may apply when you use Storage Transfer Service to transfer data from an external provider to Cloud Storage, in addition to the charges specified in Common charges:
Note: Storage Transfer Service provides optimization to avoid copying data if the source data and destination data match, reducing your outbound data transfer charges. You can change this by setting overwriteObjectsAlreadyExistingInSink to True. For information on changing this default, see TransferOptions.
The following charges apply when you use Storage Transfer Service to transfer data between Cloud Storage buckets, in addition to the charges specified in Common charges:
The following table summarizes the billable charges for data transferred to, from, or between file systems:
Service | Price (USD) |
|---|---|
Storage Transfer Service agent-assisted transfers | $0.0125 / 1 gibibyte |
Storage Transfer Service generates charges only for bytes transferred to the destination successfully. If Storage Transfer Service retries an object transfer that failed, the initial bytes moved on the failed request are not billed. Similarly, if you start an incremental transfer, you are not billed for files that haven't changed from the previous transfer, because Storage Transfer Service doesn't re-transfer the file.
Do the following to view the cost of a single transfer:
Note: Cloud Storage pricing and non-transfer charges are applied when you use Transfer for on-premises.
Non-transfer charges
While transferring data, Storage Transfer Service uses Google Cloud resources. Using those resources generates billable operations on your behalf for Cloud Storage. An operation is an action that makes changes to or retrieves information about buckets and objects in Cloud Storage. For more information, see Cloud Storage operations pricing.
The following table summarizes the billable operations that occur during a Storage Transfer Service transfer operation:
Operation type | How the operation is generated |
|---|---|
Cloud Storage Class A operations | When writing objects during a transfer, the number of operations depends on the size of the file. Small to medium files incur one operation per file. Larger files can incur more than one operation per file due to use of multipart upload to achieve faster transfers. When listing objects during a transfer, the number of operations depends on the source directory structure and the number of objects already in the destination bucket. Additional operations may be required for certain transfer configurations, such as delete-unique-at-sink or manifest-based uploads. These are billed to the Cloud Storage project for your destination Cloud Storage bucket. |
Cloud Storage Class B operations | For manifest-based uploads, 1 operation is incurred per file in the manifest. These are billed to the Cloud Storage project for your destination Cloud Storage bucket. |
Files that are restarted mid-upload due to a modification on your premises will not incur an extra cost from Storage Transfer Service. They may incur an extra Cloud Storage cost, as the files with changes may be treated as additional files within Cloud Storage. However, we expect that this scenario is rare enough that it doesn't meaningfully influence cost.
Note: The scenario above describes approximate resource consumption, which may vary based on your environment. It also refers to current pricing for Cloud Storage, and may change after this writing. For cost-concious users, we recommend that you perform a small transfer job with a sample of your data before beginning your production transfer jobs. This will enable you to gauge your non-transfer costs in your environment.
For more information about Google Cloud resource pricing, see: