> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coral.inc/llms.txt
> Use this file to discover all available pages before exploring further.

# Terminate on Baidu Cloud

> How to permanently release a BCC instance running OpenClaw on Baidu Cloud (Baidu AI Cloud)

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.

<Warning>
  Complete the [pre-termination checklist](/security/terminate-instance#pre-termination-checklist) before proceeding. Releasing an instance is irreversible.
</Warning>

***

## Option 1: Baidu Cloud Console

<Steps>
  <Step title="Open the BCC console">
    Sign in to the [Baidu Cloud Console](https://console.bce.baidu.com/bcc/) and navigate to **Cloud Server BCC → Instance List**.
  </Step>

  <Step title="Select the correct region">
    Use the region selector at the top to choose the region where your instance is running.
  </Step>

  <Step title="Select your instance">
    Find the BCC instance running OpenClaw. Confirm the correct instance by checking its public IP against what appeared on the watchboard.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Release the instance">
    With the instance stopped, click **More → Release**. Review the confirmation dialog and click **OK** to confirm.
  </Step>
</Steps>

**Official Baidu Cloud documentation:**

* [Stop an Instance](https://intl.cloud.baidu.com/en/doc/BCC/s/7jwvynngs-intl-en)
* [Batch Stop Instances](https://intl.cloud.baidu.com/en/doc/BCC/s/Akyb07kw0-intl-en)

***

## Option 2: BCE CLI

The [Baidu Cloud Engine CLI (bcecli)](https://cloud.baidu.com/doc/CLI/s/Kjwvz23ms) 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:

```bash theme={null}
pip install bcecli
bce configure  # Enter your AccessKeyId, SecretAccessKey, and default region
```

Stop and release the instance:

```bash theme={null}
# 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](https://cloud.baidu.com/doc/CLI/s/Kjwvz23ms) for the full list of options.

<Note>
  The raw Baidu Cloud BCC REST API uses the [BCE Signature Algorithm (bce-auth-v1)](https://cloud.baidu.com/doc/Reference/s/njwvz1yfu), which requires HMAC-SHA256 signing that is not practical to do manually with curl. Use the BCE CLI or the [BCE Python SDK](https://github.com/baidubce/bce-sdk-python) (`pip install bce-python-sdk`) for scripted access.
</Note>

***

## 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](/security/terminate-instance#post-termination-checklist) for the full list.