MaxCompute charges for each project based on storage, computing, and download operations. This topic describes the billable items, billing methods, and fee composition of MaxCompute, and explains how to select a billing method.
Billable items and billing methods
The following table describes the billable items and billing methods of MaxCompute.
Billing method | Description |
| |
MaxCompute supports pay-as-you-go and subscription billing methods. The two billing methods are independent of each other. After you activate and purchase a computing resource, you must associate it with a project before you can use it.
| |
For data downloaded over the Internet or across regions, MaxCompute charges based on the amount of data downloaded. Note Data import into MaxCompute is free of charge. | |
MaxCompute storage fees include storage billing and backup storage billing. After you enable zone-disaster recovery for storage, the storage fees for the project are calculated based on the storage disaster recovery billing rules. The billing method for backup storage remains unchanged. |
Fee composition
The following figure shows the billable items of MaxCompute.
Billing method selection
If you are a new user, you can start with the pay-as-you-go billing method. Because you consume fewer resources when you first start using MaxCompute, purchasing reserved compute units (CUs) can lead to idle resources. The pay-as-you-go method is more cost-effective in this case.
Data transfer fee description
Internet download fees
Data downloaded from an Internet Endpoint is charged on a pay-as-you-go basis. For more information about Internet Endpoints, see Endpoint.
Shared resource group
Each project has a limit on the number of free concurrent data transmissions. If this limit is exceeded, an error is reported. For more information about the concurrency limit, see Limits on free Data Transmission Service resources.
MaxCompute does not guarantee the available capacity of this shared pool or the throughput that you can achieve.
The shared resource group for Data Transmission Service does not support a queuing policy. If resources are insufficient, an error is returned.
Dedicated resource groups are currently available in the China (Hangzhou), China (Shanghai), China (Beijing), and China (Shenzhen) regions.