If an Elastic Compute Service (ECS) instance is in a state in which the instance cannot provide services, such as the Stopped state, you must start the instance before you can use it. This topic describes how to start an instance in the ECS console.
Prerequisites
The instance that you want to start meets one of the following requirements:
The instance is in the Stopped state.
The instance is a pay-as-you-go instance that is in the Expired state due to an overdue payment. The overdue payment is settled, but the instance cannot be automatically reactivated.
Background information
When you complete the overdue payment for a pay-as-you-go instance, the instance is automatically reactivated. If the instance is not automatically reactivated, wait for 10 minutes and then check whether the instance is reactivated and enters the Running state. If the instance cannot be automatically reactivated, manually reactivate the instance.
After you reactivate a pay-as-you-go instance that was stopped due to an overdue payment, the instance starts running and resumes pay-as-you-go billing. Release the instances that are no longer needed to prevent unnecessary costs.
Start an instance in the ECS console
Go to ECS console - Instance.
In the top navigation bar, select the region and resource group of the resource that you want to manage.
Click the ID of the instance that you want to start to go to the instance details page, and click All Actions in the upper-right corner. In the pane that appears, search for and click Start.
In the Start Instance message, confirm the instance information and click Confirm.
After you start the instance, the status of the instance changes to Starting and then to Running. When the instance enters the Running state, the instance startup process is complete.
ImportantIf you cannot start an instance, the instance type may be understocked. In this case, you can change the instance type. For more information, see Change the instance type of a pay-as-you-go instance.
If you cannot start the instance after you change the instance type, use the instance health diagnostics feature to troubleshoot the issue.