Changing the Billing Mode from Pay-per-Use to Yearly/Monthly
This section describes how to change the billing mode of a GeminiDB Influx instance from pay-per-use to yearly/monthly. If you want to use a pay-per-use instance for a long time, change its billing mode to yearly/monthly to reduce costs.
Precautions
- Only when the status of a pay-per-use instance is Available, its billing mode can be changed to yearly/monthly.
Changing the Billing Mode of a Single Instance
- Log in to the management console.
- In the service list, choose Databases > GeminiDB.
- On the Instances page, locate the instance whose billing mode you want to change and click Change to Yearly/Monthly in the Operation column.
Figure 1 Changing from pay-per-use to yearly/monthly
- On the displayed page, select the renewal duration in month. The minimum duration is one month.
Confirm the settings and click Pay Now.
- Select a payment method and click Pay.
- View the results on the Instances page.
In the upper right corner of the instance list, click to refresh the list. The instance status will become Available after the change is successful. The billing mode changes to Yearly/Monthly.
Changing the Billing Mode of Multiple Instance in Batches
- Log in to the management console.
- In the service list, choose Databases > GeminiDB.
- On the Instances page, select the instances whose billing mode you want to change and click Change to Yearly/Monthly above the instance list. In displayed dialog box, click Yes.
Figure 2 Changing the billing mode of multiple instances
- On the displayed page, select how many months you want to renew the instance for. The minimum duration is one month.
Confirm the settings and click Pay Now.
- Select a payment method and click Pay.
- View the results on the Instances page.
In the upper right corner of the instance list, click to refresh the list. The instance status will become Available after the change is successful. The billing mode becomes to Yearly/Monthly.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.