StartInstance - Deploy an instance
Before you can use an ApsaraMQ for Kafka instance to send and receive messages, you must purchase and deploy it.
API
The rate limit for this operation is 2 queries per second (QPS) per user.
Debugging
You can call this operation directly in OpenAPI Explorer. OpenAPI Explorer simplifies the process by automatically calculating signatures and generating SDK code examples.
Authorization
The following table describes the authorization information for this operation. You can add the action in the Action element of a RAM policy statement to grant a RAM user or RAM role permissions to call this operation.
Operation: The specific permission.
Access level: The access level of the operation. Valid values: Write, Read, and List.
Resource type: The resource type that the operation supports. The following rules apply:
Required resource types are highlighted.
For operations that do not support resource-level authorization, the value is
All resources.
Condition key: The condition keys that the cloud service defines.
Associated operation: Other permissions required for the operation to succeed. To ensure this operation succeeds, you must also grant the permissions for the associated operations.
Actions | Access level | Resource type | Condition key | Associated operation |
alikafka:StartInstance | Write | All resources * |
| None |
Request parameters
Parameter | Type | Required | Description | Example |
InstanceId | string | Yes | The ID of the instance. | alikafka_post-cn-v0h1fgs2**** |
RegionId | string | Yes | The ID of the region where the instance is deployed. | cn-hangzhou |
VpcId | string | Yes | The ID of the virtual private cloud (VPC) in which the instance is deployed. | vpc-bp1r4eg3yrxmygv**** |
VSwitchId | string | Yes | The ID of the vSwitch to which the instance is deployed. | vsw-bp1j3sg5979fstnpl**** |
DeployModule | string | Yes | The deployment mode of the instance. This parameter is required for reserved instances but is optional for serverless instances and ApsaraMQ for Confluent instances. Valid values:
The deployment mode must be consistent with the instance type. For a VPC-only instance, set this parameter to vpc. For an Internet and VPC instance, set this parameter to eip. | vpc |
ZoneId | string | No | The ID of the zone in which the instance is deployed.
Note If resources in the specified zone are insufficient, the instance may be deployed in another zone. | cn-hangzhou-k |
IsEipInner | boolean | No | Specifies whether to enable access over the internet. Valid values:
The value of this parameter must be consistent with the instance type. For example, if the instance is a VPC-only instance, you must set this parameter to false. | false |
IsSetUserAndPassword | boolean | No | Specifies whether to set a new username and password. Valid values:
This parameter is applicable only to Internet and VPC instances. | false |
Username | string | No | The username.
Default value: | username |
Password | string | No | The password.
| password |
Name | string | No | The name of the instance. Note The instance name must be unique within the region. | newInstanceName |
CrossZone | boolean | No | Specifies whether to deploy the instance across zones.
Default value: true. | false |
SecurityGroup | string | No | The ID of the security group for the instance. If you do not specify this parameter, ApsaraMQ for Kafka automatically configures a security group for your instance. To specify a security group, you must first create one. For more information, see Create a security group. | sg-bp13wfx7kz9pko**** |
ServiceVersion | string | No | The version of the ApsaraMQ for Kafka instance to be deployed.
Default values:
| reserved instance: 2.2.0 serverless instance: 3.3.1 ApsaraMQ for Confluent instance: 7.4.0 |
Config | string | No | The initial configurations for the ApsaraMQ for Kafka instance. The configurations must be a valid JSON string. If you omit this parameter, no initial configurations are set. Note
The Config parameter supports the following configurations:
| {"kafka.log.retention.hours":"33"} |
KMSKeyId | string | No | The ID of a key for cloud disk encryption in the same region. You can view the key ID in the Key Management Service (KMS) console or create a new key. For more information, see Create a CMK. If you specify this parameter, cloud disk encryption is enabled for the instance. This setting cannot be changed after deployment. When you call this operation, the system checks if the Note You cannot specify a | 0d24xxxx-da7b-4786-b981-9a164dxxxxxx |
Notifier | string | No | The alert contact. | Mr. Wang |
UserPhoneNum | string | No | The mobile phone number of the alert contact. | 1581234**** |
SelectedZones | string | No | A two-dimensional array that specifies the candidate primary and secondary zones for deployment. Both custom codes (for example,
| [[\"zonel\"],[\"zonek\"]] |
IsForceSelectedZones | boolean | No | Specifies whether to force deployment in the selected zones. | false |
VSwitchIds | array | No | A list of vSwitch IDs for instance deployment. This parameter is required for reserved instances and serverless instances. ApsaraMQ for Confluent instances also support this parameter. For ApsaraMQ for Confluent instances, you must specify at least one of | |
string | No | The ID of the vSwitch. | ["vsw-bp1j3sg5979fstnpl****", "vsw-2ze8rwvzn7yi3r88****"] |
Response parameters
Parameter | Type | Description | Example |
object | |||
Code | integer | The response code. A value of 200 indicates that the request was successful. | 200 |
Message | string | The response message. | operation success. |
RequestId | string | The ID of the request. | ABA4A7FD-E10F-45C7-9774-A5236015**** |
Success | boolean | Indicates whether the call was successful. | true |
Examples
Sample success response
JSON format
{
"Code": 200,
"Message": "operation success.",
"RequestId": "ABA4A7FD-E10F-45C7-9774-A5236015****",
"Success": true
}Error codes
For a list of common error codes, see Common error codes.
Change history
Date | Change summary | Actions |
August 15, 2024 | Updated the API description. | |
February 27, 2024 | Changed the request parameters. | |
October 9, 2023 | Changed the request parameters. |