Bulk propagate ECS instance tags with OOS - Resource Management

Use a CloudOps Orchestration Service (OOS) public template to propagate tags from Elastic Compute Service (ECS) instances to their associated disks, elastic network interfaces (ENIs), elastic IP addresses (EIPs), snapshots, and custom images in bulk.

Background information

In this example, the tag team:dev is attached to multiple ECS instances, and all related resources must carry the same tag. Some related resources may be missing this tag. The OOS public template ACS-TAG-ExtendEcsInstanceTagsByInputParams automatically identifies the non-compliant resources and propagates the specified tags from the ECS instances to them.

Procedure

Log on to the OOS console.
In the left-side navigation pane, choose Automated Task > Public Template.
In the top navigation bar, select the desired region.

Note
By default, OOS deployed in a region manages resources only in that region. For example, OOS in the China (Hangzhou) region manages only ECS instances in that region. Although you can call API operations in other regions by specifying the region ID in the ACS::ExecuteAPI action, this approach is not recommended. Make sure the OOS region matches the region of the ECS instances you want to manage. For more information, see Limits.
On the Public Template page, find the ACS-TAG-ExtendEcsInstanceTagsByInputParams template and click Create Execution.
On the Basic Information page, configure the basic information and click Next Step: Parameter Settings.

For this example, use the default settings on the Basic Information page.

Note
For Execution Mode, select Automatic. This runs all tasks in the template automatically rather than individually.
On the Parameter Settings page, configure the parameters and click Next Step: OK.
1. For Region ID, select the region where your ECS instances are located.
2. For TargetInstance, select the target ECS instances.
  
  Multiple selection methods are available. In this example, select By Instance Tags to filter for ECS instances that have the team:dev tag.
3. In the TagKeys field, enter the tag key that you want to inherit from the ECS instances.
  
  In this example, enter the tag key team. You can enter multiple tag keys.
4. Set the ResourceTypes parameter to the desired resource type.
  
  Supported resource types include disk, snapshot, eni, eip, and image. You can select multiple resource types. In this example, all resource types are selected.
5. Choose whether to turn on the switch Whether to overwrite the tag value if the tag key is the same.
  
  In this example, the switch is turned on. If the tag keys are the same but the tag values differ, the new tag value overwrites the original value.
6. Keep the default settings for the RateControl and OOSAssumeRole parameters.
After you confirm the settings, click Create.

Result

A Success status indicates that the team:dev tag has been propagated to the related resources of the specified ECS instances. You can verify the result in the ECS console by checking whether the tag appears on the corresponding resources.