Create and run commands

Console

1. Go to ECS console - ECS Cloud Assistant.

2. In the top navigation bar, select the region and resource group of the resource that you want to manage.

3. In the upper-right corner of the ECS Cloud Assistant page, click Create/Run Command.

4. In the Command Information section, configure the following settings:

   • Command: You can enable Use Parameters.

     The Base64-encoded command content cannot exceed 18 KB when you select Run and Save, or 24 KB when you select Run.

     • Custom parameters: Define custom parameters using the {{parameter}} format and assign values to them manually. This format supports dynamic values and parameter reuse.

     • Built-in parameters: Cloud Assistant provides built-in parameters, such as {{ACS::RegionId}} (region ID) and {{ACS::InstanceId}} (instance ID), which are automatically replaced at runtime and do not require you to assign values.

     #!/bin/bash
     # Example
     # {{name}} is a custom parameter. You must assign a value after you write the command content.
     echo {{name}}
     
     # {{ACS::RegionId}} is a built-in parameter that does not require a value.
     echo {{ACS::RegionId}}

   • Execution Plan:

     • Perform Only Dry Run: Validates the command and its parameters without executing it. This check includes request parameters, the instance execution environment, and the Cloud Assistant Agent status.

     • Timing execution:

       • Run at Fixed Interval: Runs the command at a fixed interval based on a rate expression.

         The interval, which must be between 60 seconds and 7 days, must be longer than the task's configured timeout.

       • Run on Clock-based Schedule: Schedules the command using a cron expression, which is ideal for complex, recurring tasks.

   • Username: Defaults to root (Linux) or System (Windows). To follow the principle of least privilege, run commands as a non-root user.

   • Execution Path: The working directory on the instance where the command runs. The default is /root on Linux and C:\Windows\system32 on Windows. To ensure the script runs from a specific directory, add a cd command at the beginning of your script.

   • Timeout Period: The default is 60 seconds. You can set the timeout to a value from 10 to 86,400 seconds (24 hours).

   • Task Stop Scope:

     • Command Process: Stops the script process when you stop the task.

     • Command Process Tree: Stops the process tree (the script process and all its child processes) when you stop the task.

5. In the Select Instances or Select Managed Instances area, select the instances on which to run the command.

   You can select up to 100 instances.

6. Click Run and Save or Run to start the task.

CLI