Skip to main content
This guide covers releasing (terminating) a Baidu Cloud BCC (Baidu Cloud Compute) instance. Releasing an instance permanently removes it and stops billing. Attached Cloud Disk Service (CDS) volumes and snapshots must be deleted separately.
Complete the pre-termination checklist before proceeding. Releasing an instance is irreversible.

Option 1: Baidu Cloud Console

1

Open the BCC console

Sign in to the Baidu Cloud Console and navigate to Cloud Server BCC → Instance List.
2

Select the correct region

Use the region selector at the top to choose the region where your instance is running.
3

Select your instance

Find the BCC instance running OpenClaw. Confirm the correct instance by checking its public IP against what appeared on the watchboard.
4

Stop the instance first (if running)

An instance must be in the Stopped state before it can be released. If the instance is running, click More → Stop and wait for the status to change to Stopped.
5

Release the instance

With the instance stopped, click More → Release. Review the confirmation dialog and click OK to confirm.
Official Baidu Cloud documentation:

Option 2: BCE CLI

The Baidu Cloud Engine CLI (bcecli) handles authentication internally using your Access Key ID and Secret Access Key, so you don’t need to compute the API signatures manually. Install and configure:
pip install bcecli
bce configure  # Enter your AccessKeyId, SecretAccessKey, and default region
Stop and release the instance:
# Stop the instance first (must be Stopped before release)
bce bcc stop-instance --instance-id i-XXXXXXXX

# Release (permanently terminate) the instance
bce bcc release-instance --instance-id i-XXXXXXXX
Replace i-XXXXXXXX with your BCC instance ID and bj with your region code in the CLI config. See the BCE CLI BCC command reference for the full list of options.
The raw Baidu Cloud BCC REST API uses the BCE Signature Algorithm (bce-auth-v1), which requires HMAC-SHA256 signing that is not practical to do manually with curl. Use the BCE CLI or the BCE Python SDK (pip install bce-python-sdk) for scripted access.

Post-termination cleanup

Delete CDS data disks

Attached Cloud Disk Service volumes are not deleted when the instance is released. In the BCC console, navigate to Cloud Disk Service → Disk List, filter by Status = “Available”, and delete the disks you no longer need.

Delete snapshots

In the BCC console, navigate to Cloud Disk Service → Snapshot List and delete any snapshots created from this instance.

Release Elastic IPs (EIP)

Elastic IPs that were associated with the instance are not released automatically. In the console, navigate to Elastic IP → EIP List and release any EIPs no longer in use.

Rotate credentials

After releasing the instance, rotate everything the agent had access to. See the post-termination checklist for the full list.