Auto Scaling:Automatically execute scripts on ECS instances

Procedure

Step 1: Grant OOS permissions to the RAM role

You must have the permissions to execute OOS templates. In this example, the ACS-ESS-LifeCycleRunCommand public template is used. The template defines the ECS and Auto Scaling resources that are required to perform O&M operations.

1. Log on to the RAM console.

2. Create a policy.

   1. In the left-side navigation pane, choose Permissions > Policies.

   2. On the Policies page, click Create Policy.

   3. On the Create Policy page, click the JSON tab, configure parameters as prompted, and then click OK.

      The following table describes the parameters that are used in this example. For parameters that are not described in the table, use the default settings.

      Parameter	Description
      Name	Enter ESSHookPolicyForRunCommand.
      Policy document	Enter the following content: { "Version": "1", "Statement": [ { "Action": [ "ecs:DescribeInvocationResults", "ecs:DescribeInvocations", "ecs:RunCommand" ], "Resource": "*", "Effect": "Allow" }, { "Action": [ "ess:CompleteLifecycleAction" ], "Resource": "*", "Effect": "Allow" } ] }

3. Grant the required permissions to the OOSServiceRole RAM role.

   1. In the left-side navigation pane, choose Identities > Roles.

   2. Find the RAM role OOSServiceRole and click Add Permissions in the Actions column.

      Grant the required permissions to OOSServiceRole.

   3. In the Add Permissions panel, configure parameters as prompted and click OK.

      The following table describes the parameters that are used in this example. For parameters that are not described in the table, use the default settings.

      Parameter	Description
      Authorized Scope	Select Alibaba Cloud Account.
      Select Policy	Select the following custom policy: ESSHookPolicyForRunCommand policy.

Step 2: Create a lifecycle hook and trigger a scale-out

To automatically execute scripts on an ECS instance during a scale-out, you must specify an OOS template as the notification method when you create a lifecycle hook.

1. Log on to the Auto Scaling console.

2. In the left-side navigation pane, click Scaling Groups.

3. In the top navigation bar, select the region where Auto Scaling is activated.

4. Find a scaling group and use one of the following methods to go to the scaling group details page:

   • Click the ID of the scaling group in the Scaling Group Name/ID column.

   • Click Details in the Actions column.

5. Create a lifecycle hook.

   1. In the upper part of the scaling group details page, click the Lifecycle Hook tab.

   2. Click Create Lifecycle Hook.

   3. Configure parameters of the lifecycle hook and click OK.

      The following table describes the parameters that are used in this example. For parameters that are not described in the table, use the default settings.

      Parameter	Description
      Name	Enter ESSHookForRunCommand.
      Scaling Activity	Select Scale-out Event.
      Timeout Period	Configure the Timeout Period parameter based on your business requirements. Unit: seconds. In this example, the Timeout Period parameter is set to 300. Note The timeout period is the period of time during which you can perform custom operations on ECS instances. If the timeout period is shorter than the period of time that is required to perform the custom operations, the operations may fail. We recommend that you estimate the period of time that is required to perform custom operations on ECS instances and configure the Timeout Period parameter based on your business requirements.
      Default Execution Policy	Select Continue.
      Send Notification When Lifecycle Hook Takes Effect	Specify a notification method or the action that you want Auto Scaling to perform after the lifecycle hook times out. In this example, perform the following operations: Select OOS Template. Select Public Templates. Select ACS-ESS-LifeCycleRunCommand. In the ACS-ESS-LifeCycleRunCommand public template, you must configure the following parameters: commandType: Select RunShellScript. commandContent: Enter the script that you want to execute on the ECS instance. In this example, a script is executed to automatically install Apache on the ECS instance. yum install -y httpd systemctl start httpd systemctl enable httpd OOSAssumeRole: Select OOSServiceRole. In Step 1: Grant OOS permissions to the RAM role, OOSServiceRole is granted the permissions on the ECS and Auto Scaling resources. OOS obtains the preceding permissions after it assumes the RAM role.

6. Trigger a scale-out.

   In this example, a scale-out is manually triggered by executing a scaling rule. You can also trigger scale-outs by using scheduled or event-triggered tasks.

   Note

   If scaling activities are triggered when you manually execute scaling rules, lifecycle hooks take effect. However, lifecycle hooks do not take effect when you manually add or remove ECS instances to or from a scaling group.

   1. In the upper part of the scaling group details page, click the Scaling Rules and Event-triggered Tasks tab.

   2. Click the Scaling Rules tab, and then click Create Scaling Rule in the upper-right corner.

   3. In the Create Scaling Rule dialog box, configure parameters of the scaling rule and click OK.

      The following table describes the parameters that are used in this example. For parameters that are not described in the table, use the default settings.

      Parameter	Description
      Rule Name	Enter Add1.
      Rule Type	Select Simple Scaling Rule.
      Operation	Set the value to Add 1 Instances.

   4. On the Scaling Rules page, find the Add1 scaling rule and click Execute in the Actions column.

   5. In the Execute Scaling Rule message, click OK.

   After the scaling rule is executed, Auto Scaling adds one ECS instance to the scaling group. However, the ECS instance enters the Pending Add state because of the ESSHookForRunCommand lifecycle hook that is in effect before the ECS instance is added. During the timeout period of the lifecycle hook, Auto Scaling notifies OOS to execute the O&M operations that are defined in the ACS-ESS-LifeCycleRunCommand public template.

7. Check whether Apache is installed on the ECS instance.

   1. In the upper part of the scaling group details page, click the Instances tab.

   2. Find the ECS instance and click its ID in the ECS Instance ID/Name column.

   3. In the left-side navigation pane, click ECS Cloud Assistant.

   4. In the upper-right corner of the page that appears, click Create or Run Command.

   5. Run the following command to check whether Apache is installed:

      For more information, see Use the immediate execution feature.

      systemctl status httpd

      • On the Command Execution Result tab, you can check the command execution result. If Apache is installed on the ECS instance and enters the Active state, the ACS-ESS-LifeCycleRunCommand public template takes effect.

      • If the ECS instance is created but Apache is not installed on the ECS instance, you can go to the OOS console to check the execution of the O&M operations. For more information, see Step 3 (Optional) View the OOS execution.

Step 3 (Optional) View the OOS execution

1. Log on to the OOS console.

2. In the left-side navigation pane, choose Automated Tasks > Task Execution Management.

3. Find the execution task by time and click Details in the Actions column.

4. On the execution details page, view information about the OOS execution.

   For example, in the Basic Information section, you can view the execution ID and status. In the Execution Result section, you can click a task node to view the execution details. For more information, see View the details of an execution.

   Note

   If an execution failed, the error message is displayed in the Execution Result section.

FAQ

References