You need to enable JavaScript to run this app.
Elastic Compute Service

Elastic Compute Service

Copy page
Download PDF
Process choreography
Overview of Orchestration
Copy page
Download PDF
Overview of Orchestration
Orchestration is a process-based automated O&M service for cloud products. It allows you to orchestrate task workflows based on your business requirements for auto-execution. You can also centrally manage these tasks and view their execution progress and results.​
Application scenarios​
Orchestration is often used in relatively complex cloud product O&M scenarios. It can orchestrate multiple operations into a single process for unified execution, addressing the inefficiency and fragmentation issues of manual execution.​
Concepts​
​
Concept​
Description​
Step​
The basic actions that can be executed with the orchestration feature, which are generally operations and O&M on cloud products, such as ECS instance creation, starting, and stop actions, and calling cloud assistant. You can orchestrate multiple steps into a complete workflow. You can view details of currently supported steps in Summary of orchestration steps.​
Role​
A role is a type of identity in the IAM system. Its permissions are defined by the attached policy. For more information about roles, see Role management. The orchestration service will assume the role you select to obtain permissions to access the resources under your account. You can create roles with permissions to execute orchestration tasks. For detailed operations, refer to Preparations.​
Alert trigger​
An alert trigger is an automated response mechanism designed for metric anomalies or risks. When the metrics or status of a monitored object reaches a predefined exception threshold or meets risk conditions, an alert is generated, which then triggers predefined follow-up operations to enable automated O&M.​
Event triggers​
An event trigger is an automated response mechanism designed for specific events. When a specific event occurs, the system automatically initiates predefined operations to enable automated O&M. Specific events can be detected risks in GPU operation or pending responses for instance redeployment triggered by disk anomalies.​
​
Procedure​
Use preset steps to create an orchestration task​
By combining various preset steps, you can achieve process-based automated O&M. The following table describes the procedure.​
​
Method for initiating O&M orchestration​
Procedure and description​
Proactive O&M orchestration​
O&M orchestration is proactively initiated and executed based on preset rules or detection results, independent of triggers from external events or alerts. Its core lies in "proactive prevention and proactive O&M."​
  • Grant read and write permissions on ECS instances to your account.​
  1. Create a custom template or view steps to orchestrate an O&M task (optional)​
  • If the current preset public templates do not meet your business requirements, you can create a custom template.​
  • Understand the purpose, input and output parameters, and other relevant aspects of each step of your task. This helps you accurately and appropriately plan the steps when you create an orchestration task.​
  • Add preset steps to create a task. This enables process-based automated O&M.​
  • Learn about task information and the execution status of each step of the task.​
Passive O&M orchestration​
O&M orchestration is passively triggered and executed when external (CloudMonitor) events or alerts meet specific conditions. Its core lies in "on-demand responsive and automated O&M".​
  • Grant read and write permissions on ECS instances to your account.​
  • Understand the purpose, input and output parameters, and other relevant aspects of each step in your plan. This helps you accurately and appropriately plan the steps when you create an orchestration plan.​
  • Add preset steps to predefine the O&M orchestration workflow for a specific alert policy or event rule.​
  • Associate event or alert triggers with your orchestration plan. This allows preset operations in the plan to start under specific conditions, thereby enabling automated O&M.​
​
Create orchestration tasks for common batch operations​
You can perform the following steps to create orchestration tasks for common batch operations on instances, volumes, and images.​
​
Procedure​
Description​
  1. Preparations (optional)​
When using O&M Orchestration for the first time, you need to prepare read and write permissions for Elastic Compute Service (ECS) resources for your Account.​
  1. Create tasks​
  • Create tasks for batch volume operations: Perform batch O&M operations on multiple volumes, including volume scaling, snapshot creation, and volume specification modifications, to enhance O&M efficiency.​
  • Create temporary bandwidth upgrade tasks: Batch-create temporary bandwidth upgrade tasks for multiple subscription instances to handle traffic peaks, ensure business stability, and lower bandwidth costs.​
  1. View tasks​
View the execution results and status of batch tasks, as well as the overview, log, and workflow for each task.​
​
​
Last updated: 2026.06.18 17:49:52