Upgrades a pay-as-you-go ApsaraMQ for Kafka instance.
Operation description
Before you call this operation, make sure that you understand the billing method and pricing of pay-as-you-go Message Queue for Apache Kafka instances. For more information, see Billing .
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 |
---|---|---|---|---|
alikafka:UpgradePostPayOrder | Write |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
InstanceId | string | Yes | The instance ID. | alikafka_post-cn-mp919o4v**** |
DiskSize | integer | No | The disk size. Unit: GB.
Note
When you create an ApsaraMQ for Kafka V3 serverless instance, you do not need to configure this parameter.
| 500 |
RegionId | string | Yes | The region ID of the instance. | cn-hangzhou |
IoMaxSpec | string | No | The traffic specification of the instance. We recommend that you configure this parameter.
Note
When you create an ApsaraMQ for Kafka V3 serverless instance, you do not need to configure this parameter.
| alikafka.hw.6xlarge |
IoMax | integer | No | The maximum traffic for the instance. We recommend that you do not configure this parameter.
Note
When you create an ApsaraMQ for Kafka V3 serverless instance, you do not need to configure this parameter.
| 60 |
SpecType | string | No | The instance edition. Valid values for this parameter if you set PaidType to 1:
Valid values for this parameter if you set PaidType to 3:
For more information, see Billing . | professional |
PartitionNum | integer | No | The number of partitions. We recommend that you configure this parameter.
Note
When you create an ApsaraMQ for Kafka V3 serverless instance, you do not need to configure this parameter.
| 80 |
TopicQuota | integer | No | The number of topics. We recommend that you do not configure this parameter.
Note
When you create an ApsaraMQ for Kafka V3 serverless instance, you do not need to configure this parameter.
| 80 |
EipModel | boolean | No | Specifies whether to enable Internet access for the instance. Valid values:
| false |
EipMax | integer | No | The Internet traffic for the instance.
Note
| 0 |
ServerlessConfig | object | No | The parameters configured for the Serverless instance. When you create an ApsaraMQ for Kafka V3 serverless instance, you must configure these parameters. | |
ReservedPublishCapacity | long | No | The traffic reserved for message publishing. Unit: MB/s. Valid values: 1 to 31457280. You can specify only integers for this parameter. | 50 |
ReservedSubscribeCapacity | long | No | The traffic reserved for message subscription. Unit: MB/s. Valid values: 1 to 31457280. You can specify only integers for this parameter. | 50 |
Response parameters
Examples
Sample success responses
JSON
format
{
"Code": 200,
"Message": "operation success.",
"RequestId": "ABA4A7FD-E10F-45C7-9774-A5236015A***",
"Success": true
}
Error codes
HTTP status code | Error code | Error message |
---|---|---|
400 | BIZ.LIMIT.PUBNETWORK | EipMax is invalid. |
400 | BIZ.LIMIT.QUOTA.DOWN | Invalid.%s |
400 | BIZ.LIMIT.QUOTA.DOWN.1 | Invalid.%s |
400 | BIZ.LIMIT.QUOTA.DOWN.2 | Invalid.%s |
400 | BIZ_FIELD_CHECK_INVALID | %s. Please check and try again later. |
400 | Invalid.Partition.%s | Invalid.%s |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
2024-04-11 | The Error code has changed | see changesets | ||||||||
| ||||||||||
2024-03-20 | The Error code has changed | see changesets | ||||||||
| ||||||||||
2024-02-26 | The Error code has changed. The request parameters of the API has changed | see changesets | ||||||||
| ||||||||||
2022-08-31 | The Error code has changed | see changesets | ||||||||
|