Changes the billing method of the specified Lindorm instance.
Operation description
You can call this operation to change the billing method of an instance to subscription or pay-as-you-go.
Before you call this operation, make sure that you fully understand the billing methods and pricing of Lindorm. Published on only international site (alibabacloud.com).
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 |
---|---|---|---|---|
lindorm:ModifyInstancePayType | update |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
InstanceId | string | Yes | The ID of the instance. | ld-bp1z3506imz2f**** |
Duration | integer | Yes | The subscription duration of the instance. The parameter is required if the instance is an subscription instance.
| 1 |
PricingCycle | string | Yes | The unit of the subscription duration for the instance. Valid values:
| Month |
PayType | string | Yes | The billing method of the instance. Valid values:
| POSTPAY |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "587BCA54-50DA-4885-ADE9-80A848339151",
"OrderId": 211662251220224,
"InstanceId": "ld-bp1z3506imz2f****",
"AccessDeniedDetail": "{\"AuthAction\":\"xxx\",\"AuthPrincipalDisplayName\":\"222\",\"AuthPrincipalOwnerId\":\"111\",\"AuthPrincipalType\":\"SubUser\",,\"NoPermissionType\":\"ImplicitDeny\",\"PolicyType\":\"AccountLevelIdentityBasedPolicy\",\"EncodedDiagnosticMessage\":\"xxxxxx\"}"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | Instance.IsDeleted | The instance is deleted. | The specified instance is already deleted. |
400 | Instance.IsNotAvailable | The instance is unavailable. | The specified instance is unavailable. |
403 | API.Forbidden | The API operation is forbidden in this environment. | This operation is not supported in the current environment. |
403 | Lindorm.Errorcode.OperationDenied | You are not authorized to operate on the specified resource. | You are not authorized to manage the specified resource. |
403 | Lindorm.Errorcode.ServiceLinkedRoleNoPermission | No permission to create service linked role. | You are not authorized to create the service-linked role. |
404 | Lindorm.Errorcode.InstanceNotFound | The instance is not found. | The specified instance does not exist. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-09-18 | The Error code has changed. The response structure of the API has changed | View Change Details |