Switch the billing method of an ApsaraDB RDS for PostgreSQL serverless instance to pay-as-you-go for fixed-spec resource control.
Use cases
Switch from serverless to pay-as-you-go when:
Your workloads are stable and do not fluctuate significantly.
You want to manually control changes to the instance type.
For details on when to use serverless instances, see Introduction to ApsaraDB RDS for PostgreSQL serverless instances.
Prerequisites
Engine: ApsaraDB RDS for PostgreSQL
Edition: Basic Edition or High-availability Edition
Billing method: Serverless
Status: Running
Verify these details on the instance details page in the ApsaraDB RDS console.
Impacts
This operation causes an instance switchover. Make sure that your application has an automatic reconnection mechanism. For details on switchover impacts, see Impacts of an instance switchover.
Limitations
You can switch the billing method between pay-as-you-go and serverless only once every 24 hours.
To switch an instance back from pay-as-you-go to serverless, the instance must use PL1 ESSDs. If the instance uses a different enterprise SSD (ESSD) type, convert the disk type to PL1 ESSD first.
Billing
This operation is free of charge. After the conversion, standard pay-as-you-go billing applies. For pricing details, see Product Billing.
Procedure
When selecting an instance type for the conversion, choose a type with CPU cores greater than or equal to the RDS Capacity Unit (RCU) limit of the current instance. For example, if the RCU limit is 4, select an instance type with 4 or more CPU cores, such as pg.n4m.4c.2m (4 cores, 16 GB).
Go to the RDS Instances page. In the upper-left corner, select the region where the instance resides. Click the instance ID.
On the Basic Information page, in the Configuration Information section, click Change To Pay-As-You-Go.
On the buy page, configure the Instance Type and Switching Time parameters.
Read the Terms of Service and click Confirm Order. In the dialog box that appears, confirm the settings and click OK to complete the payment.
During the conversion, the instance status changes to Upgrading/Downgrading. After the conversion completes, the instance status changes to Running.
FAQ
After switching from serverless to pay-as-you-go, why does a new purchase order appear under Expenses and Costs > Orders > My Orders?
The conversion creates a new pay-as-you-go instance and performs a switchover from the original instance to the new one. This is why a new purchase order appears.
API reference
| API | Description |
|---|---|
| Modify an RDS instance | Switches the billing method from serverless to pay-as-you-go. |
To call this API:
Set the PayType parameter to Postpaid (pay-as-you-go). The original instance must use the serverless billing method.
Set the DBInstanceClass parameter to the target instance type. This parameter corresponds to the instance type shown in the console. For available types, see Instance types for primary ApsaraDB RDS for PostgreSQL instances.
Leave other parameters, such as storage space, blank or set them to the same values as the original instance. These parameters cannot be modified during the conversion.