All Products
Search

This Product

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

    Document Center

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

    Last Updated:Nov 28, 2025

    This topic describes how to change the billing method of an ApsaraDB RDS for MySQL 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 about the scenarios of serverless RDS instances, see Overview of serverless ApsaraDB RDS for MySQL instances.

    Note

    You cannot directly change the billing method from serverless to subscription. If you need to change the billing method from serverless to subscription, you can first change the billing method from serverless to pay-as-you-go based on this topic and then to subscription. For more information, see Change the billing method of an ApsaraDB RDS for MySQL instance from pay-as-you-go to subscription.

    Prerequisites

    Your RDS instance must meet the following requirements:

    • 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.

    • The Secure Sockets Layer (SSL) encryption feature is disabled for the RDS instance.

    Note

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

    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 original RDS instance is 4, make sure that the number of CPU cores of the RDS instance after the billing method change is greater than or equal to 4. For example, you can select the mysql.n2.large.1 instance type that provides 4 CPU cores and 8 GB of memory.

    Limits

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

    Impacts

    If you change the billing method of your RDS instance from serverless to pay-as-you-go, 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.

    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 Basic Information page of the Configuration Information section, click Change To Pay-As-You-Go.

    3. On the Change from Serverless to Pay-as-you-go page, configure the Instance Type and Switching Time parameters.

    4. Click Confirm Order. 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

    Q: After I change the billing method from serverless to pay-as-you-go, why do I see a new purchase order in Expenses And Costs > Orders?

    A: 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

    API

    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.

    • Set the DBInstanceClass parameter to the instance type to which you want to use. For more information, see Instance types for standard primary ApsaraDB RDS for MySQL instances (original x86 architecture).

    • 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.