E-MapReduce (EMR) supports the pay-as-you-go and subscription billing methods to meet your requirements in different scenarios. You can select a billing method based on your business requirements.
The following table describes the billing methods.
Item | Subscription | Pay-as-you-go |
Billing method | Subscription is a billing method that requires you to pay for resources before you can use them. You are charged for the resources based on the subscription duration. | Pay-as-you-go is a billing method that allows you to use resources before you pay for them. You are charged based on the actual usage of a cluster. |
Billing cycle | You are charged for the resources based on the subscription duration. The minimum subscription duration is 1 month, and the maximum subscription duration is 3 years. | You are charged for the resources per second, and bills are generated on an hourly basis at the top of every hour (UTC+8). |
Billable item | EMR service and Elastic Compute Service (ECS) instances.
| EMR service and ECS instances.
|
Billing method switching | Not supported. | You can change the billing method from pay-as-you-go to subscription. |
Scenario | The resource usage period can be estimated. This method allows you to reserve resources in advance and reduce costs based on discounted rates. | The demand computing resource fluctuates significantly. This billing method allows you to use and release resources on demand without the need to purchase a large number of resources in advance. |
EMR allows you to add pay-as-you-go node groups to a subscription cluster. In this case, you are charged based on both the subscription and pay-as-you-go billing methods. The hybrid billing methods are suitable for scenarios in which stable workloads are required and issues related to business computing loads need to be handled during specific peak hours. You can configure auto scaling rules to enable the system to dynamically adjust the number of on-demand resources based on your actual scenario. This helps balance cost optimization and performance assurance. For more information, see Configure auto scaling rules.