Elastic Compute Service: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 content: You can enable Use Parameters.

     The Base64-encoded command payload cannot exceed 18 KB when select Run And Save, and 24 KB when select Run.

     • Custom parameters: Use the {{parameter}} format to define parameters and assign values manually to support dynamic values and reuse.

     • Built-in parameters: Cloud Assistant provides built-in parameters that are automatically replaced at runtime, such as {{ACS::RegionId}} (Region ID) and {{ACS::InstanceId}} (Instance ID).

     #!/bin/bash
     # Example
     # {{name}} is a custom parameter that you must assign a value to.
     echo {{name}}
     
     # {{ACS::RegionId}} is a built-in parameter that does not require a value to be assigned.
     echo {{ACS::RegionId}}

   • Execution Plan:

     • Perform Only Dry Run: The command is not executed. Only pre-check such as request parameters, the instance environment, and the Cloud Assistant Agent status.

     • Run on Schedule:

       • Run at Fixed Interval: Runs the command at a fixed interval defined by a rate expression.

         The interval must be between 60 seconds and 7 days, and must be longer than the command timeout.

       • Run on Clock-based Schedule: Use cron expression for flexible scheduling of complex tasks.

   • Username: Defaults to root (Linux) or System (Windows). For security, we recommend using a non-root user that follows the principle of least privilege.

   • Execution Path: The default script working directory is /root (Linux) and C:\Windows\system32 (Windows). To ensure execution in the intended path, using cd command at the start of the script.

   • Timeout: Defaults to 60 seconds. You can set the timeout to a value between 10 and 86,400 seconds (24 hours).

   • Task Stop Scope:

     • Command Process: Stops only the script process when the task is terminated.

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

5. In the Select Instance or Select Managed Instances section, select the target instances for the command.

   You can select up to 100 instances.

6. To start the task, click Run and Save or Run.

CLI