Elastic Compute Service
Elastic Compute Service
Elastic Compute Service
Document
Elastic Compute Service
What's New
Announcement
OpenAPI related
Pricing and quotas are related
About products and plugins
Feature discontinuation
Overview
Billing
Billable items
Billing methods
Billing methods change
Getting Started
User Guide
Instances
Instance types
X86 Computing
Elastic Bare Metal Server
Heterogeneous Computing
Select instance billing method
Spot instance
Elastic Scheduled Instance
Offsetting Resources
Reserved Instances
Buying ECS instances
Logging in to an instance
Logging in to a Linux instance
Managing instance status
Modifying instance types
Using instance user data and metadata
Instance metadata
Images
Public images
veLinux images
Custom images
Importing custom images
Creating custom images
Image detection
End of life (EOL) of image
Elastic Block Storage
Basic volume operations
Partitioning and formatting a volume
Extending a volume
EBS Agent
Snapshots
Basic snapshot operations
Auto snapshot policies
DataInsights
Network
Network interface and IP address
IP Address
IPv4 address
Security group
Security
Passwords and key pairs
Deployment and scaling
Monitoring
Monitoring metrics
Event monitoring
Local volume event O&M
Method 1: Solve the local volume failure by replacing the faulty volume
O&M
Cloud assistant
Managing agents
Process choreography
Common operation and maintenance tasks
Batch operations on instances
Batch operations on EBS Volumes
Batch operations on images
Temporary upgrade of bandwidth
Managing application updates
orchestration plan
Patch management
Managing patch plans
Managing patch baselines
IAM
Tags and projects
Best Practices
AI applications
OpenClaw (formerly Moltbot)
Quickly deploying OpenClaw via application templates
Quickly deploying OpenClaw via marketplace images
Manually deploying OpenClaw
Self-service website creation
Building environments
Building a Web environment (Windows)
Building applications
Building FTP site
Deploying databases
Building game servers
Building websites
Building a WordPress blog
Building multiple websites
Manage software sources for Linux instances
AIGC practices
Performance test
Network performance test
Instance configuration
Setting up AD Domain Services on Windows OS
Windows Multi - User Login
Changing screen resolution
Instance data
Uploading or downloading files
Data restoration
ECS instance local time synchronization
Volume
Monitoring
Security
Images
Kernel fine-tuning
O&M
Troubleshooting
Remote log in issue
Linux operating system issue
Windows operating system issue
SSH log in issue
Operating system issue
veLinux operating system issue
Linux operating system issue
Windows operating system issue
Instance status issue
Instance unable to start issue
High instance load issue
GPU instances issue
Network connection issue
Network configuration issue
Storage classes issue
EBS Volume issue
Local Disk issue
Logs and monitoring issue
Third - party software issue
API Reference
Regions and availability zones
Instances
Images
HPC clusters
Key pairs
Tags
Volumes
Reserved storage capacity
Snapshot
Auto snapshot policy
Monitoring
Deployment sets
Launch templates
Cloud assistant
Patch management
SDK reference
CLI Reference
FAQ
Dedicated Host DDH
What's New
Billing
User Guide
Manage Dedicated Host
Manage Dedicated Host Cluster
Manage ECS instances
Monitoring and O&M
API reference
proprietary host
- Documentation
Elastic Compute ServiceElastic Compute ServiceUser GuideO&MProcess choreographyCommon operation and maintenance tasksManaging application updatesCreating OpenClaw (Linux) system reinstallation tasks
Copy page
Download PDFManaging application updates
Creating OpenClaw (Linux) system reinstallation tasks
Copy pageDownload PDFCreating OpenClaw (Linux) system reinstallation tasks
You can use the application update feature of Orchestration to reinstall the operating system of your ECS instance with the latest image that includes the newest application version. No additional purchase or reconfiguration is required, significantly reducing deployment time and costs.
tip
Currently, only the following regions are supported: China (Beijing), China (Shanghai), China (Guangzhou), Asia Pacific (Johor), and Asia Pacific (Jakarta). Learn more.
Applicable scenarios
ECS instance | Scenarios | Description |
ECS instance | Scenarios | Description |
ECS instance with OpenClaw already deployed | Update to latest version | Follow Volcano Engine version updates without repurchasing or reconfiguring the instance. Simply reinstall the operating system of your existing instance to the latest version to use the latest OpenClaw capabilities supported by Volcano Engine on your original ECS instance. |
| Restore to the initial state | For any ECS instance that needs to be restored to its initial OpenClaw state, you can reset the operating system to its initial state using this method. |
ECS instance without OpenClaw deployed | Deploy OpenClaw on an existing ECS instance | Reinstall the operating system to convert an existing ECS instance without a preinstalled OpenClaw application into an ECS instance with a preinstalled OpenClaw application. No additional purchase or configuration is required, significantly reducing deployment time and costs. |
Usage notes
Operating system reinstallation is a high-risk operation. Read and fully understand the following usage notes before proceeding:
warning
- The application update feature reinstalls the operating system using a brand-new application image, and the operation is irreversible. Proceed with caution.
- Reinstalling the operating system restores the system volume to its initial state (all data on the system volume, including saved configurations and logs, is cleared and cannot be recovered). We recommend that you back up your system volume data in advance. To back up OpenClaw context data, follow the OpenClaw data backup and recovery guide.
Prerequisites
- Cloud assistant Agent has been installed on the instance for which you want to reinstall the operating system.
- To configure the model and complete notification channel integration in the application update task, obtain the following information based on the notification channel to be integrated:
tip
You can also configure the following information after creating and executing the application update task. For details, see the advanced configuration section in the procedure.
- Required informationNotification channelsDescriptionRequired informationNotification channelsDescriptionModel API KeyFeishu integration, DingTalk integration, WeCom integration
- If you do not use the Coding Plan, obtain the ID of the ModelArk model you want to use. For more information, see Activate the ModelArk service and obtain the configuration.
- If you use the Coding Plan, obtain the name of the supported model. Currently supported: . Currently, the doubao-seed-code, glm-4.7, deepseek-v3.2, kimi-k2-thinking, and kimi-k2.5 models are supported.
AppId and AppSecretFeishu integration- App Id: The App ID of the target Feishu bot.
- App Secret: The key of the target Feishu bot.
tip- You can log in to the Feishu Open Platform and view the App ID and App Secret of the application in the "Basic Info > Credentials & Basic Info" section of the application details page. Learn more.
- Take note that the App ID and App Secret are important identity credentials for calling Feishu Open Platform APIs. Keep them secure and avoid disclosure.
Client ID and Client SecretDingTalk integration- Client ID: The client ID of the target DingTalk application.
- Client Secret: The Client Secret of the target DingTalk application.
tip- You can log in to the DingTalk application console and obtain the Client ID and Client Secret in the "Basic Info > Credentials & Basic Info" section of the target application details page. Learn more.
- Caution: The Client ID and Client Secret are important identity credentials for accessing the DingTalk application. Keep them secure to prevent disclosure.
Token andEncoding-AESKeyWeCom integration- Token: The token of the target WeCom bot.
- Encoding-AESKey: The encryption key of the target WeCom bot.
tip- Log in to the WeCom official website using an account with enterprise administrator permissions. Click the "Details" button next to the target bot to obtain its Token and EncodingAESKey on the details page. Learn more.
- Caution: The Token and EncodingAESKey are important identity credentials for accessing the WeCom bot. Keep them secure to prevent disclosure.
Procedure
- Log in to the ECS console.
- In the left-side navigation pane, click "Maintenance & Monitoring > Orchestration".
- In the top menu bar, select the region and project of your business.
- On the "CloudOps Orchestration" page, click the "Common O&M tasks" tab and select "App update".
- Click the "Create task" button and configure the parameters described in the following table.
- ParameterDescriptionParameterDescriptionApplication configurationApplication templateThe OpenClaw application deployed by the user. The default value is "OpenClaw" and cannot be modified.Task templateThe preset standardized O&M process template. Select "Reinstall operating system".Login credentialsReset passwordConfigure the instance login password.warning
- Instances after batch operating system reinstallation will share the same new login credentials you configured. Keep your password secure. You can also reset the login password separately for the target instance.
- We recommend that you increase password complexity to improve security.
Confirm passwordRe-enter the instance login password for confirmation.Select instancesSelect instancesSelect the instance for which you want to reinstall the operating system.tipIf the target ECS instance is preconfigured with OpenClaw, use the filter "Application template: OpenClaw" for faster searching. Otherwise, clear the filter to select your instance.Advanced configuration (optional)tipThe model and notification channel integration parameters in this section can also be configured after the task is executed. For details, refer to: Model configurationAfter you configure the model on the ModelArk platform, OpenClaw will use this model for inference after your ECS instance starts. Configure the relevant parameters based on the notification channel you want to integrate.- Lark: For details, see Configure the model and integrate a Feishu application during ECS instance purchase.
- WeCom: For details, see Configure the model and integrate a WeCom bot during ECS instance purchase.
- DingTalk: For details, see Configure the model and integrate a DingTalk application during ECS instance purchase.
Message channel integrationFeishu integrationEnter the App Id and App Secret of the Feishu bot. For details, see Prerequisites.WeCom integrationEnter the Token and EncodingAESKey of the WeCom bot. For details, see Prerequisites.DingTalk integrationEnter the Client ID and Client Secret of the DingTalk application. For details, see Prerequisites.Relevant informationAssociated projectYou can add the application update task to the project and manage it in a centralized manner by project dimension, which helps maintain resource independence and ensure data security. Learn more.tip- After you select a project, new instances that meet the conditions automatically match the application update task.
- The project displayed here is the one you selected in Step 3. You can change the project in the top menu bar.
TagOptional. Used to select the scope of instances the application update task applies to based on tags. Click the "Add tag" button, and then select or enter the tag key and its corresponding tag value.tip- Up to 20 tags can be added.
- A tag is a key-value pair used to identify cloud resources. Tags help you categorize resources based on different dimensions, such as purpose, owner, or environment. This allows you to search and aggregate your resources. Learn more.
- Click "Create".
- After you confirm that the information to be updated is correct, click the "Confirm" button to start reinstalling the system.
Expected results
- Reinstallation succeeded
- The reinstallation completes, and the instance starts automatically in approximately 3 to 5 minutes. Its status is updated to Running synchronously.
- Reinstallation failed
- The instance will enter an abnormal state and fail to start. All original data on the system volume will be cleared and cannot be recovered. Submit a ticket to obtain technical support.
Last updated: 2026.06.02 15:52:00
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
