Changes the billing method of an instance. You can call this operation to switch the billing method from pay-as-you-go to subscription for Server Load Balancer (SLB) instances, elastic IP addresses (EIPs), and NAT gateways, and switch the billing method from subscription to pay-as-you-go for SLB instances and EIPs.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
bss:ModifyInstance | WRITE |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
ProductType | string | No | The type of the service to which the instance belongs. | rds |
SubscriptionType | string | Yes | The billing method of the instance. Valid values:
Note
After the call is successful, the billing method of the instance is switched.
| Subscription |
Period | integer | No | The subscription duration. Unit: months. This parameter is required if you switch the billing method to subscription. Valid values:
| 6 |
ProductCode | string | Yes | The code of the service to which the instance belongs. | rds |
InstanceId | string | Yes | The ID of the instance. | rm-kasjgfjshgf |
Response parameters
Examples
Sample success responses
JSON
format
{
"Code": "Success",
"Message": "Successful!",
"RequestId": "6000EE23-274B-4E07-A697-FF2E999520A4",
"Success": true,
"Data": {
"OrderId": "202657601410661"
}
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | NotApplicable | This API is not applicable for caller. | - |
400 | NotAuthorized | This API is not authorized for caller. | - |
400 | InvalidOwner | The specified owner doesn't belong to caller. | Invalid user identity. |
405 | SYSTEM.SALE_VALIDATE_NO_SPECIFIC_CODE_FAILED | - | |
405 | ORDER.INST_HAS_UNPAID_ORDER | - | |
405 | COMMODITY.INVALID_COMPONENT | - | |
405 | ORDER.QUANTITY_INVALID | - | |
500 | InternalError | The request processing has failed due to some unknown error. | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
2022-12-26 | The Error code has changed | see changesets | ||||||||
|