Switch your RDS PostgreSQL Serverless instance to pay-as-you-go billing for stable workloads or manual scaling control.
Scenarios
Switch to pay-as-you-go if your workload is stable or you want manual control over instance type changes.
For applicable Serverless scenarios, see Introduction to RDS PostgreSQL Serverless instances.
Prerequisites
The instance must meet the following conditions:
-
Engine: RDS PostgreSQL
-
Edition: Basic Edition or High-availability Edition
-
Billing method: Serverless
-
Status: Running
You can view this information on the instance details page in the RDS console.
Limits
You can switch between Serverless and pay-as-you-go only once every 24 hours.
To switch back to Serverless later, the instance must use an ESSD PL1 cloud disk. Only ESSD PL1 instances support pay-as-you-go to Serverless conversion. If your instance uses a different ESSD type, change the disk type to ESSD PL1 first.
Impacts
This change triggers an instance switchover. Ensure your application supports automatic reconnection. Impacts of an instance switchover.
Notes
Select an instance type with vCPUs greater than or equal to the RCU upper limit of the original instance. For example, if the RCU upper limit is 4, select pg.n4m.4c.2m (4 vCPUs, 16 GB) or higher.
Billing
This switch is free of charge. For pay-as-you-go pricing details, see Product billing.
Procedure
-
Go to the RDS instance list, select a region in the top navigation bar, and click the target instance ID.
-
On the Basic Information page, go to the Configuration Information section and click Convert to Pay-As-You-Go.
-
On the purchase page, configure parameters such as Instance Type and Switching Time based on your business requirements.
-
Select the terms of service, click Confirm Order, confirm the changes in the dialog box, and click Pay.
NoteDuring the conversion, the instance status changes to Upgrading/Downgrading. After the conversion is complete, the instance status changes back to Running.
FAQ
Q: After I change the billing method of an instance from Serverless to pay-as-you-go, why is the order displayed as a new purchase in Billing and Costs > Orders > My Orders?
A: The system creates a new pay-as-you-go instance and switches over from the original, so the order is recorded as a new purchase.
Related APIs
|
API |
Description |
|
When you change the billing method of a Serverless instance to pay-as-you-go:
|