All Products
Search
Document Center

ApsaraDB RDS:Change the billing method from serverless to pay-as-you-go

Last Updated:Mar 22, 2024

This topic describes how to change the billing method of an ApsaraDB RDS for PostgreSQL instance from serverless to pay-as-you-go.

Scenarios

If your workloads slightly fluctuate or you want to manually change instance specifications, you can change the billing method of your RDS instance from serverless to pay-as-you-go.

For more information, see Overview.

Prerequisites

Your RDS instance must meet the following requirements:

  • The RDS instance runs PostgreSQL.

  • The RDS instance runs RDS Basic Edition or RDS High-availability Edition.

  • The RDS instance uses the serverless billing method.

  • The RDS instance is in the Running state.

Note

You can log on to the ApsaraDB RDS console and view the preceding information on the instance details page.

Limits

You can change the billing method between pay-as-you-go and serverless. The change can be performed only once within 24 hours.

Impacts

If you change the billing method of your RDS instance from serverless to pay-as-you-go to, an instance switchover occurs during the change. Make sure that your application is configured to automatically reconnect to the RDS instance. To automatically reconnect to an RDS instance, you must complete the required configurations in your application. For more information about the impacts of an instance switchover, see Impacts of an instance switchover.

Usage notes

We recommend that the number of CPU cores of your RDS instance be greater than or equal to the maximum number of RDS Capacity Units (RCUs). For example, if the maximum number of RCUs of the serverless RDS instance is 4, make sure that the number of the CPU cores of the pay-as-you-go RDS instance to which you want to change is greater than or equal to 4. Example: pg.n4m.4c.2m. The pg.n4m.4c.2m instance type indicates that the pay-as-you-go RDS instance provides 4 CPU cores and 16 GB of memory.

Billing rules

You are not charged for the change operation. For more information about the billing rules of a pay-as-you-go RDS instance, see Billing overview.

Procedure

  1. Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which your RDS instance resides. Then, find the RDS instance and click the ID of the RDS instance.

  2. In the Configuration Information section of the Basic Information page, click Change to Pay-As-You-Go.

  3. On the ApsaraDB RDS buy page, configure the Instance Type and Switching Time parameters.

  4. Read and select Terms of Service and click Pay Now. In the dialog box that appears, confirm the settings and click OK to complete the payment.

    Note

    During the change, the status of your RDS instance changes to Upgrading/Downgrading. After the change is complete, the status of the RDS instance changes to Running.

FAQ

After I change the billing method of my RDS instance from serverless to pay-as-you-go, why is a new purchase order displayed on the Orders for Services tab that is displayed after I choose Expenses > User Center in the top navigation bar and click Orders in the left-side navigation pane?

The billing method of your RDS instance is changed by creating a pay-as-you-go RDS instance. During the change, a new purchase order is displayed. After the change, your RDS instance automatically changes to a pay-as-you-go RDS instance.

Related operations

Operation

Description

ModifyDBInstanceSpec

Changes the billing method from serverless to pay-as-you-go.

  • Make sure that the billing method of the original instance is serverless, and the PayType parameter is set to Postpaid.

  • Make sure that the DBInstanceClass parameter is configured to the new instance type. For more information, see Instance types for primary ApsaraDB RDS for PostgreSQL instances.

  • Make sure that other parameters, such as DBInstanceStorage, are not specified or are configured with the same values as the original instance. You cannot change the values of the parameters.