Stopping Instances (Batch Stop)
Prerequisites
The instance must be in the Running status.
Elastic Baremetal Compute (EBC) instances do not support forced shutdown.
Forced stopping is equivalent to turning off the power and may result in the loss of unsaved data in the instance's OS disk.
Background
When you need to stop an instance, you can perform the stop operation. Stopping an instance is similar to shutting down a local computer.
Note
- When an instance is stopped, related services will no longer be accessible. Please proceed cautiously.
- Stopped instances will still be retained and continue to be charged. For postpaid BCC instances, you may select no charge for stopped instances. Refer to [No Charge for Stopped Postpaid Instances](BCC/Operation guide/Instance/Postpay Instance No Charge for Stopped Instances.md).
- You can stop an instance using specific OS commands (e.g., shutdown operation for Windows or shutdown command for Linux) or through the console.
Operation steps
- Sign in to BCC Console and enter the Instance List page.
-
Choose different methods to stop instances based on your specific needs.
- To stop a single instance: Select the instance you wish to stop and click More - Instance Status - Stop in the right-side operation bar, as shown in the figure below. Alternatively, select the instance and click Stop at the top menu.
- To stop multiple instances: Check the boxes for the instances to be stopped and click Stop at the top, as shown in the figure below.
- In the pop-up Stop dialog box, confirm the instance information, set the stop mode, and click OK button, as shown in the following figure.
Note: For no charge for stopped instances, refer to [No Charge for Stopped Postpaid Instances](BCC/Operation guide/Instance/Postpay Instance No Charge for Stopped Instances.md).
- After successful stoppage, the instance status will change to Stopped.
Stop an instance via API
You can stop specified instances through [Stop Instance API](BCC/API Reference/Instance Related Interfaces/Stop an instance.md).