Changing DB Instance Specifications
Function
This API is used to change DB instance specifications.
- Before calling an API, you need to understand the API in Authentication.
Services will be interrupted for 5 to 10 minutes when you change DB instance specifications. Exercise caution when performing this operation.
Constraints
- The new DB instance specifications must be different from the original DB instance specifications.
- The instance specifications can be modified only for DB instances in the Available status.
- The specifications of a DB instance can be changed only to the specifications of the same DB instance type. (For example, the specifications of a single DB instance cannot be changed to those of primary/standby DB instances.)
- When you change the instance specifications of an RDS for MySQL DB instance using local disks, the storage space after the change cannot be less than that of the original DB instance.
URI
- URI format
- Parameter description
Table 1 Parameter description Name
Mandatory
Description
project_id
Yes
Project ID of a tenant in a region.
For details about how to obtain the project ID, see Obtaining a Project ID.
instance_id
Yes
Specifies the DB instance ID.
Request
Name |
Mandatory |
Type |
Description |
---|---|---|---|
resize_flavor |
Yes |
Object |
For details, see Table 3. |
Name |
Mandatory |
Type |
Description |
---|---|---|---|
spec_code |
Yes |
String |
Specifies the resource specification code. Use rds.mysql.m1.xlarge as an example. rds indicates the RDS product, mysql indicates the DB engine, and m1.xlarge indicates the high memory performance specifications. The parameter containing rr indicates the read replica specifications. The parameter not containing rr indicates the single or primary/standby DB instance specifications. |
is_auto_pay |
No |
Boolean |
Specifies whether the order will be automatically paid when the specifications of yearly/monthly DB instances are changed.
|
Example Request
- Change the specifications of an RDS for MySQL DB instance to rds.mysql.m1.xlarge.
POST https://{endpoint}/v3/0483b6b16e954cb88930a360d2c4e663/instances/dsfae23fsfdsae3435in01/action { "resize_flavor": { "spec_code": "rds.mysql.m1.xlarge", "is_auto_pay": true } }
- Change the specifications of an RDS for PostgreSQL DB instance to rds.pg.c2.medium.ha.
{ "resize_flavor": { "spec_code": "rds.pg.c2.medium.ha", "is_auto_pay": true } }
- Change the specifications of an RDS for SQL Server DB instance to rds.mssql.2014.se.s3.large.2.
{ "resize_flavor": { "spec_code": "rds.mssql.2014.se.s3.large.2", "is_auto_pay": true } }
Response
- Pay-per-use
- Normal response
Table 4 Parameter description Name
Type
Description
job_id
String
Indicates the job ID.
- Example normal response
{ "job_id": "2b414788a6004883a02390e2eb0ea227" }
- Abnormal response
For details, see Abnormal Request Results.
- Normal response
- Yearly/Monthly
- Normal response
Table 5 Parameter description Name
Type
Description
order_id
String
Indicates the order ID.
- Example normal response
{ "order_id": "CS2009151216NO2U1" }
- Abnormal response
For details, see Abnormal Request Results.
- Normal response
Status Code
- Normal
- Abnormal
For details, see Status Codes.
Error Code
For details, see Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot