StartInstances - Elastic Compute Service - Alibaba Cloud Documentation Center

Starts Elastic Compute Service (ECS) instances that are in the Stopped state. After the operation is called, the instances enter the Starting state.

Operation description

Usage notes

Take note of the following items:

The instances to be started must be in the Stopped (Stopped) state.
If the response contains {"OperationLocks": {"LockReason" : "security"}} when you query the information of an instance, the instance is locked for security reasons. No operations are allowed on the instance.
You can use BatchOptimization to specify the batch operation mode and restart multiple instances at a time.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
DryRun	boolean	No	The region ID of the ECS instance. You can call the DescribeRegions operation to query the most recent region list.	false
RegionId	string	Yes	The batch operation mode. Valid values: AllTogether: starts all ECS instances at the same time. If all ECS instances are started, a success message is returned. If an ECS instance fails to be started, all the specified instances fail to be started and an error message is returned. SuccessFirst: separately starts each ECS instance. The response contains the operation results of each ECS instance. Default value: AllTogether.	cn-hangzhou
BatchOptimization	string	No	The IDs of the ECS instances. You can specify up to 100 ECS instance IDs.	AllTogether
InstanceId	array	Yes	The ID of instance N. Valid values of N: 1 to 100.
	string	Yes	The ID of the request.	i-bp67acfmxazb4p****

Response parameters

Parameter	Type	Description	Example
	object
RequestId	string	The information about the ECS instance, such as the status of each instance before and after the operation is called and the operation results.	473469C7-AA6F-4DC5-B3DB-A3DC0DE3****
InstanceResponses	array<object>	The status of the instances before and after the operation is called and the operation results.
	object
Code	string	The error code returned for the operation on the instance. The status code 200 indicates that the request was successful. For more information, see the "Error codes" section of this topic.	200
Message	string	The error message returned for the operation on the instance. The status code 200 indicates that the request was successful. For more information, see the "Error codes" section of this topic.	success
InstanceId	string	The ID of the instance.	i-bp67acfmxazb4p****
CurrentStatus	string	The status of the instance after the operation is called.	Starting
PreviousStatus	string	The status of the instance before the operation is called.	Stopped

Examples

Sample success responses

JSONformat

{
  "RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3****",
  "InstanceResponses": {
    "InstanceResponse": [
      {
        "Code": "200",
        "Message": "success",
        "InstanceId": "i-bp67acfmxazb4p****",
        "CurrentStatus": "Starting",
        "PreviousStatus": "Stopped"
      }
    ]
  }
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidParameter.KMSKeyId.CMKNotEnabled	The CMK needs to be added ECS tag	-
400	InvalidParameter.KMSKeyId.CMKNotEnabled	The CMK needs to be enabled.	The customer master key (CMK) is not enabled when KMSKeyId is specified for an encrypted disk. You can call the DescribeKey operation of KMS to query information about the specified CMK.
400	InvalidParameter.KMSKeyId.KMSUnauthorized	ECS service account have no right to access your KMS.	-
400	DRYRUN.SUCCESS	This request is a dryrun request with successful result.	The request is checked and determined as valid.
400	Invalid.PrivatePoolOptions.NoStock	The PrivatePool has been used up.	-
403	InvalidInstanceId.NotFound	InstanceId should not be null.	-
403	InvalidParameter.TooManyInstanceIds	Instance ids cannot be more than 100.	-
403	Abs.InvalidInstanceIds.MalFormed	The specified instanceIds is not valid.	-
403	InstanceExpired	%s	-
403	InstanceLockedForSecurity	%s	-
403	InstanceExpiredOrInArrears	%s	-
403	IncorrectInstanceStatus	%s	The instance is in a state that does not support the current operation.
403	InvalidInstance.NotFoundSystemDisk	%s	-
403	OperationDenied.NoStock	The requested resource is sold out in the specified zone; try other types of resources or other regions and zones.	The requested resources are insufficient.
403	OperationDenied.SpotPriceLowerThanPublicPrice	The spot instance price is lower than public price.	Your user-defined maximum hourly price of a preemptible instance is lower than the current market price.
403	OperationDenied.SpotPriceLowerThanPublicPrice	%s	-
403	InsufficientBalance	Your account does not have enough balance.	Your account balance is insufficient. Add funds to your account and try again.
403	InstanceNotReady	The specified instance is not ready for use.	The resource is in a state that does not support the current operation. Try again later and check whether the instance state supports the operation.
403	OperationDenied.HostRepairing	%s	-
404	InvalidInstanceId.NotFound	%s	The specified instance does not exist. Check whether the InstanceId parameter is valid.
404	InvalidInstanceIds.NotFound	The specified InstanceIds does not exist.	The specified InstanceId parameter does not exist. You can call the DescribeInstances operation to query the state of the instance.
404	InvalidInstanceId.NotFound	The specified InstanceId does not exist.	The specified instance does not exist.
409	InvalidOperation.Conflict	Request was denied due to conflict with a previous request, please try again later.	-
500	InternalError	The request processing has failed due to some unknown error.	An internal error has occurred. Try again later.

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation

No change history