1 |
ACS-ADB-BulkyModifyDBClusterMaintainTime |
Modify instance's maintain time |
YAML JSON |
Immediate execution |
2 |
ACS-ADB-EnableBackupPolicy |
Enable adb instance's backup policy. |
YAML JSON |
Immediate execution |
3 |
ACS-ALB-BulkyEnableDeletionProtection |
Bulky set loadbalancer deletion protection |
YAML JSON |
Immediate execution |
4 |
ACS-Actiontrail-EnableActionTrail |
Enable action trail |
YAML JSON |
Immediate execution |
5 |
ACS-ApiGateway-BulkyAbolishApi |
Abolishing a specified API in a specified stage |
YAML JSON |
Immediate execution |
6 |
ACS-ApiGateway-BulkyModifyApi |
Modify API to private |
YAML JSON |
Immediate execution |
7 |
ACS-ApiGateway-BulkyModifyApiGroupNetworkPolicy |
Modify the https version of apigateway instance to support tls1.2 |
YAML JSON |
Immediate execution |
8 |
ACS-BssOpenApi-EnableAutoRenewal |
Enable resource auto renew |
YAML JSON |
Immediate execution |
9 |
ACS-BssOpenApi-SetRenewal |
Modify resource auto renew attribute |
YAML JSON |
Immediate execution |
10 |
ACS-CDN-EnableForceHttps |
Turn on the HTTP-HTTPS force redirect configuration of CDN |
YAML JSON |
Immediate execution |
11 |
ACS-CDN-SetDomainServerCertificate |
Set domain server certificate |
YAML JSON |
Immediate execution |
12 |
ACS-CN-BulkyConfigureOOSPackage |
Use this template to configure oos package on ECS |
YAML JSON |
Immediate execution |
13 |
ACS-CN-BulkyRollbackServiceInstance |
Use this template to bulky rollback CN service instance |
YAML JSON |
Immediate execution |
14 |
ACS-CN-BulkyUpgradeServiceInstance |
Use this template to bulky upgrade CN service instance |
YAML JSON |
Immediate execution |
15 |
ACS-CN-PrePostUpgradeServiceInstance |
Run command in ComputeNest service instance‘s Pre/PostUpgrade stage |
YAML JSON |
Immediate execution |
16 |
ACS-CN-UpgradeServiceInstance |
ComputeNest service instance‘s Upgrade stage |
YAML JSON |
Immediate execution |
17 |
ACS-CS-AttachInstancesToClusterByRunAttachScript |
Attach ECS instances to cluster |
YAML JSON |
Immediate execution |
18 |
ACS-CS-BulkyEnableDeletionProtection |
Enable deletion protection for the cluster |
YAML JSON |
Immediate execution |
19 |
ACS-CS-BulkyOSSecurityUpdate |
Updates OS security |
YAML JSON |
Immediate execution |
20 |
ACS-CS-DedicatedMigration |
Sleep control plane, make etcd snapshot and upload it to oss bucket |
YAML JSON |
Immediate execution |
21 |
ACS-CS-RunCommand |
Run command on k8s cluster |
YAML JSON |
Immediate execution |
22 |
ACS-Cloudfw-ModifyIPSConfig |
Modify the Cloudfw IPS config |
YAML JSON |
Immediate execution |
23 |
ACS-ECD-BulkyModifyDesktopAutoRenewAttribute |
Bulky modify ECD desktop auto renew attribute |
YAML JSON |
Immediate execution |
24 |
ACS-ECD-BulkyModifyDesktopChargeType |
Bulky Modify ECD desktop charge type |
YAML JSON |
Immediate execution |
25 |
ACS-ECD-BulkyRebootDesktops |
Bulky reboot ECD desktops |
YAML JSON |
Immediate execution |
26 |
ACS-ECD-BulkyRebuildDesktops |
Bulky rebuild ECD desktops |
YAML JSON |
Immediate execution |
27 |
ACS-ECD-BulkyRenewDesktops |
Bulky renew subscription cloud desktops |
YAML JSON |
Immediate execution |
28 |
ACS-ECD-BulkyRunCommand |
Bulky run command on ECD desktops |
YAML JSON |
Immediate execution |
29 |
ACS-ECD-BulkyStartDesktops |
Bulky start ECD desktops |
YAML JSON |
Immediate execution |
30 |
ACS-ECD-BulkyStopDesktops |
Bulky stop ECD desktops |
YAML JSON |
Immediate execution |
31 |
ACS-ECD-ScheduleToStartAndStopDesktops |
Schedule to start and stop desktops |
YAML JSON |
Immediate execution |
32 |
ACS-ECS-AlarmAccountResourceUsage |
Resource usage exceeds threshold alarm notification |
YAML JSON |
Immediate execution |
33 |
ACS-ECS-AlarmDiscountOrPriceInScalingGroupExistingInstanceTypes |
Monitor the discounts and prices of spot instances that currently exist in the scaling group, and send out alarm notifications if they exceed |
YAML JSON |
Immediate execution |
34 |
ACS-ECS-AlarmWhenDiscountAndPriceExceedsThresholdInMultiZoneAndInstanceType |
Alarm when monitoring the discount and spot price of multi-instance types in multi-availability zone exceeding the threshold |
YAML JSON |
Immediate execution |
35 |
ACS-ECS-AlarmWhenDiscountOrSpotPriceExceedsThresholdByScalingGroup |
Monitor the discounts and prices of spot instances in the scaling group, and send out alarm notifications if they exceed |
YAML JSON |
Immediate execution |
36 |
ACS-ECS-ApplyAnsiblePlayBooks |
Use this template to run Ansible playbook on ECS Instance.Only supports CentOS, Alibaba Cloud Linux and Ubuntu. |
YAML JSON |
Immediate execution |
37 |
ACS-ECS-ApproveBulkyRunCommand |
Approve Bulky RunCommand |
YAML JSON |
Immediate execution |
38 |
ACS-ECS-ApproveROSCreateInstances |
Create ECS instances by ROS with approval |
YAML JSON |
Immediate execution |
39 |
ACS-ECS-AutoStartECSWhenStoppedByTags |
Start ECS instance when instance enter stopped status with specified tag |
YAML JSON |
Immediate execution |
40 |
ACS-ECS-BuilkyAttachKeyPairOnline |
Bulky attach key pair on Linux instances without reboot |
YAML JSON |
Immediate execution |
41 |
ACS-ECS-BulkyActivateRedHatEnterpriseLinux |
Red Hat Enterprise Linux template activation |
YAML JSON |
Immediate execution |
42 |
ACS-ECS-BulkyActivateRedHatEnterpriseLinuxExtendedLifecycleSupport |
Red Hat Enterprise Linux Extended Lifecycle Support template activation |
YAML JSON |
Immediate execution |
43 |
ACS-ECS-BulkyActivateSQLServerEnterpriseEdition |
SQL Server Enterprise Edition template activation |
YAML JSON |
Immediate execution |
44 |
ACS-ECS-BulkyActivateSUSELinuxEnterpriseServer |
SUSE Linux Enterprise Server template activation |
YAML JSON |
Immediate execution |
45 |
ACS-ECS-BulkyActivateSUSELinuxEnterpriseServerforSAP |
SUSE Linux Enterprise Server for SAP template activation |
YAML JSON |
Immediate execution |
46 |
ACS-ECS-BulkyAddEipsToCommonBandwidthPackage |
Bulky add EIPs to common bandwidth package |
YAML JSON |
Immediate execution |
47 |
ACS-ECS-BulkyAllocateAndAssociateEipAddress |
Bulky add EIPs to common bandwidth package |
YAML JSON |
Immediate execution |
48 |
ACS-ECS-BulkyApplyPatchBaseline |
Bulky apply patch baseline on ECS instance |
YAML JSON |
Immediate execution |
49 |
ACS-ECS-BulkyAttachInstanceRamRole |
Bulky attaches instance ram role |
YAML JSON |
Immediate execution |
50 |
ACS-ECS-BulkyAttachKeyPair |
Bulky attach keypair to ECS instances |
YAML JSON |
Immediate execution |
51 |
ACS-ECS-BulkyAuthorizeSecurityGroup |
Add a security group policy to multiple security groups |
YAML JSON |
Immediate execution |
52 |
ACS-ECS-BulkyCloneInstances |
Clone ECS instances in batches. Note: - Please check for missing drivers before migrating, so as not to cause the new instance to fail to start.
- Based on mirror snapshot migration, if you need to retain complete data, please select Incremental snapshots for downtime as Yes, and then go to the next step; if you do not need to retain For data generated during the migration process, select No and migrate directly according to the guidelines. It is recommended that you select No to test whether the new instance is normal, and then select Yes to ensure complete data.
- The time required to create a snapshot is in minutes and depends on the size of the cloud disk. The first snapshot of the cloud disk is a full snapshot, which takes a long time and may be at the hour level. Creating a snapshot again takes a relatively short time, but still depends on the amount of data changes since the last snapshot. The bigger the change, the longer it will take.
- Because the machine will restart, please make sure that the data disk has been set to be automatically mounted, otherwise the data disk will not be mounted after restarting.
- The current operation is a high-risk operation. If you select Yes for snapshot migration, please confirm that the business impact of the shutdown is controllable.
- Public IP and Elastic IP need to be manually re-bound to the new instance. Refer to the documentation: Classic network type ECS public IP is converted to elastic public IP, Convert the fixed public IP of the VPC ECS instance to EIP, Modify private IP address
- Take a snapshot of the instance before execution, which will greatly shorten the execution time.
- Please make sure that your account balance is greater than the cost of the newly purchased instance.
|
YAML JSON |
Immediate execution |
53 |
ACS-ECS-BulkyConfigureMultipleOOSPackagesWithTemporaryURL |
Use this template to install multiple oos packages on ecs |
YAML JSON |
Immediate execution |
54 |
ACS-ECS-BulkyConfigureNVMe |
Batch automated installation of NVMe drivers and modification of instance NVMe properties to support |
YAML JSON |
Immediate execution |
55 |
ACS-ECS-BulkyConfigureOOSPackage |
Use this template to install sls agent on ecs |
YAML JSON |
Immediate execution |
56 |
ACS-ECS-BulkyConfigureOOSPackageWithTemporaryURL |
Use this template to install oos package on ecs |
YAML JSON |
Immediate execution |
57 |
ACS-ECS-BulkyConfigureSoftwareFromEcsAppStore |
Use this template to install software on ecs |
YAML JSON |
Immediate execution |
58 |
ACS-ECS-BulkyConvertPublicToEIPAndAddToCommonBandwidthPackage |
Bulky convert the public IP address of a VPC-connected ECS instance to an Elastic IP (EIP) address and add it to common bandwith package |
YAML JSON |
Immediate execution |
59 |
ACS-ECS-BulkyCopyImage |
Cross Regions copy image |
YAML JSON |
Immediate execution |
60 |
ACS-ECS-BulkyCreateAndExportImage |
Bulky creates ECS image and exports them into OSS |
YAML JSON |
Immediate execution |
61 |
ACS-ECS-BulkyCreateDiagnoseReportForInstanceConnectionFailure |
Bulky create diagnostic report for ECS instance connection failure |
YAML JSON |
Immediate execution |
62 |
ACS-ECS-BulkyCreateInstanceDiagnosticReport |
Create diagnostic report for ECS instance in bulk |
YAML JSON |
Immediate execution |
63 |
ACS-ECS-BulkyCreateSavingsPlan |
Bulky create savings plan |
YAML JSON |
Immediate execution |
64 |
ACS-ECS-BulkyCreateSavingsPlanDeductRule |
Batch purchase of instances and data disks through savings plans and setting deduction rules |
YAML JSON |
Immediate execution |
65 |
ACS-ECS-BulkyCreateSnapshot |
Bulky create snapshot |
YAML JSON |
Immediate execution |
66 |
ACS-ECS-BulkyDeleteExpiredImage |
Bulky delete expired image |
YAML JSON |
Immediate execution |
67 |
ACS-ECS-BulkyDeleteExpiredSnapshot |
Bulky delete expired snapshot |
YAML JSON |
Immediate execution |
68 |
ACS-ECS-BulkyDeleteInstances |
Bulky delete ECS postpaid instances, applicable to scenarios that require managing and deleting multiple pay-as-you-go ECS instances simultaneously, such as resource release and cost optimization. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be deleted, and Target Instances (targets), which defines the specific ECS instances to be operated on. Users can also choose whether to force delete running instances (force). Upon execution, the template will return a list of the deleted instance IDs, enabling users to verify the status of the instance deletions. |
YAML JSON |
Immediate execution |
69 |
ACS-ECS-BulkyDeleteInstancesWithApproval |
Deletes the ECS postpaid instances with approval |
YAML JSON |
Immediate execution |
70 |
ACS-ECS-BulkyDeletePrepaidInstances |
Bulky delete prepaid instances |
YAML JSON |
Immediate execution |
71 |
ACS-ECS-BulkyDeleteSnapshot |
Bulky delete snapshot |
YAML JSON |
Immediate execution |
72 |
ACS-ECS-BulkyDescribeDisks |
Bulky query instance ID and disk information |
YAML JSON |
Immediate execution |
73 |
ACS-ECS-BulkyDescribeSavingsPlanEstimation |
Bulky describe savings plan estimation |
YAML JSON |
Immediate execution |
74 |
ACS-ECS-BulkyDescribeSavingsPlanEstimationPrice |
Batch calculation inquiry for ECS instances and data disk SP types |
YAML JSON |
Immediate execution |
75 |
ACS-ECS-BulkyDetachInstanceRamRole |
Bulky detaches instance ram role |
YAML JSON |
Immediate execution |
76 |
ACS-ECS-BulkyDetachKeyPairOnline |
Bulky detach key pair from Linux instances without reboot |
YAML JSON |
Immediate execution |
77 |
ACS-ECS-BulkyDownloadFile |
Bulky upload files to multiple Alibaba Cloud ECS instances, applicable to scenarios that require distributing files across multiple instances, such as application deployment and data synchronization. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the target ECS instances where the files will be uploaded, Target Instances (targets), which defines the specific ECS instances to be operated on, Source Type (sourceType), which specifies the source method of the file (e.g., local, OSS, or HTTPS), and Source Path (sourcePath), which is the exact location of the file. Upon execution, the template provides the results of the file upload operation, enabling users to verify the status of the file uploads. |
YAML JSON |
Immediate execution |
78 |
ACS-ECS-BulkyDownloadFileAndRunCommand |
Bulky downLoad file to instances and run command |
YAML JSON |
Immediate execution |
79 |
ACS-ECS-BulkyDownloadOSSFileAndRunCommand |
Bulky downLoad OSS file to instances and run command |
YAML JSON |
Immediate execution |
80 |
ACS-ECS-BulkyEnableDeletionProtection |
Bulky enable instances deletionprotection |
YAML JSON |
Immediate execution |
81 |
ACS-ECS-BulkyEncryptDisks |
Bulky encrypt the disks |
YAML JSON |
Immediate execution |
82 |
ACS-ECS-BulkyEncryptSystemDisk |
Bulky encrypt the system disks |
YAML JSON |
Immediate execution |
83 |
ACS-ECS-BulkyGenerateCloudAssistantRsaKeyPair |
Use this template to generate Cloud Assistant RSA key pair on ecs |
YAML JSON |
Immediate execution |
84 |
ACS-ECS-BulkyInstallARMSAgent |
Use this template to install ARMS agent on ecs |
YAML JSON |
Immediate execution |
85 |
ACS-ECS-BulkyInstallAegisAgent |
Bulky install aegis agent on ECS instance |
YAML JSON |
Immediate execution |
86 |
ACS-ECS-BulkyInstallDockerCE |
Bulky install docker CE on ECS instance |
YAML JSON |
Immediate execution |
87 |
ACS-ECS-BulkyInstallHibernateAgent |
Use this template to install Hibernate agent on ecs |
YAML JSON |
Immediate execution |
88 |
ACS-ECS-BulkyInstallLogAgent |
Use this template to install sls agent on ecs |
YAML JSON |
Immediate execution |
89 |
ACS-ECS-BulkyLeaveSecurityGroup |
Bulky leave security group |
YAML JSON |
Immediate execution |
90 |
ACS-ECS-BulkyModifyAutoSnapshotPolicyTimePoint |
Modifies timepoints of AutoSnapshotPolicy |
YAML JSON |
Immediate execution |
91 |
ACS-ECS-BulkyModifyDiskSpec |
Bulky modify disk spec |
YAML JSON |
Immediate execution |
92 |
ACS-ECS-BulkyModifyInstanceAttributes |
Bulky modify the information of an ECS instance |
YAML JSON |
Immediate execution |
93 |
ACS-ECS-BulkyModifyInstanceAutoRenewAttribute |
Bulky modify instance auto renew attribute |
YAML JSON |
Immediate execution |
94 |
ACS-ECS-BulkyModifyInstanceChargeType |
Bulky modify instance charge type |
YAML JSON |
Immediate execution |
95 |
ACS-ECS-BulkyModifyInstanceChargeTypeSpecifiedInstanceTypeFamilies |
Bulky modify the billing method of instances in a specified instance type family. |
YAML JSON |
Immediate execution |
96 |
ACS-ECS-BulkyModifyInstanceMaintenanceAttributes |
Bulky modify instance maintenance attributes |
YAML JSON |
Immediate execution |
97 |
ACS-ECS-BulkyModifyInstanceNetworkChargeType |
Bulky modify ECS network charge type |
YAML JSON |
Immediate execution |
98 |
ACS-ECS-BulkyModifyPostPaidInstanceSpec |
Bulky modify postpaid instance spec |
YAML JSON |
Immediate execution |
99 |
ACS-ECS-BulkyModifyPrepayInstanceSpec |
Bulky modify prepay instance spec |
YAML JSON |
Immediate execution |
100 |
ACS-ECS-BulkyModifyT5InstanceCreditSpecification |
Bulky modify the column creditspecification for the T5 series instance |
YAML JSON |
Immediate execution |
101 |
ACS-ECS-BulkyModifyUserPasswordByCloudAssistantKeyPair |
Bulky modify ECS instance user password by cloud assistant key pair |
YAML JSON |
Immediate execution |
102 |
ACS-ECS-BulkyModifyUserPasswordBySecretParameter |
Bulky modify ECS instance user password by secret parameter |
YAML JSON |
Immediate execution |
103 |
ACS-ECS-BulkyQueryInstanceAttributes |
Bulky query ECS instance attributes |
YAML JSON |
Immediate execution |
104 |
ACS-ECS-BulkyReInitSystemDisk |
Bulky resets system disks to its initial state.The ECS instances must be in stopped status |
YAML JSON |
Immediate execution |
105 |
ACS-ECS-BulkyRebootInstances |
Bulky restarts the ECS instances, applicable to scenarios that require managing and restarting multiple ECS instances simultaneously, such as system updates and maintenance. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be restarted, and Target Instances (targets), which defines the specific ECS instances to be operated on. Upon execution, the template will return a list of the restarted instance IDs, enabling users to verify the status of the instance restart operations. |
YAML JSON |
Immediate execution |
106 |
ACS-ECS-BulkyReleasePublicIpAddress |
Bulky release the public ip address |
YAML JSON |
Immediate execution |
107 |
ACS-ECS-BulkyRemoveEipsFromCommonBandwidthPackage |
Bulky remove EIPs from common bandwidth package |
YAML JSON |
Immediate execution |
108 |
ACS-ECS-BulkyRenewInstances |
Bulky renew ECS prepaid instances |
YAML JSON |
Immediate execution |
109 |
ACS-ECS-BulkyReplaceSystemDisk |
Bulky replace the system disks of ECS instances, applicable to scenarios that require system disk replacement on multiple ECS instances, such as system upgrades and fault recovery. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances where the system disks will be replaced, Image ID (imageId), which specifies the image to use for the system disk replacement, and Target Instances (targets), which defines the specific ECS instances to be operated on. Upon execution, the template provides the IDs of the new system disks, enabling users to verify the status of the system disk replacements. |
YAML JSON |
Immediate execution |
110 |
ACS-ECS-BulkyReplaceSystemDiskInSLBDefaultServerGroup |
Bulky replaces system disk of ECS instances in default server group |
YAML JSON |
Immediate execution |
111 |
ACS-ECS-BulkyReplaceSystemDiskInSLBVServerGroup |
Bulky replaces system disk of ECS instances in Vserver group |
YAML JSON |
Immediate execution |
112 |
ACS-ECS-BulkyResizeDisk |
Bulky resize disk |
YAML JSON |
Immediate execution |
113 |
ACS-ECS-BulkyRunCommand |
Bulky run commands on multiple ECS instances, applicable to scenarios that require managing multiple ECS instances simultaneously, such as application management and resource tagging operations. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the target ECS instances where the commands will be executed, Resource Type (resourceType), to determine the type of target ECS instances (e.g., ECS instance or managed instance), and Target Instances (targets), to select the specific instances to be operated on. Other parameters include Command Type (commandType), which specifies the type of command to be executed (e.g., Shell script, Python script, etc.), and Command Content (commandContent), which is the actual command or script. Upon execution, the template provides the output results of the bulk operation, enabling users to verify the status of the command executions. |
YAML JSON |
Immediate execution |
114 |
ACS-ECS-BulkyRunCommandAcrossRegions |
Bulky run command on ECS instances across multiple regions |
YAML JSON |
Immediate execution |
115 |
ACS-ECS-BulkyRunCommandInSLBDefaultServerGroup |
Bulky run command on ECS instances of default server group |
YAML JSON |
Immediate execution |
116 |
ACS-ECS-BulkyRunCommandInSLBVServerGroup |
Bulky run command on ECS instances of VServer group |
YAML JSON |
Immediate execution |
117 |
ACS-ECS-BulkyStartInstances |
Bulky starts the ECS instances, applicable to scenarios that require managing and starting multiple ECS instances simultaneously, such as application deployment and high-availability scenarios. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be started, and Target Instances (targets), which defines the specific ECS instances to be operated on. Upon execution, the template will return a list of the started instance IDs, enabling users to verify the status of the instance start operations. |
YAML JSON |
Immediate execution |
118 |
ACS-ECS-BulkyStopClassicInstances |
Bulky stops the classic ECS instances |
YAML JSON |
Immediate execution |
119 |
ACS-ECS-BulkyStopInstances |
Bulky stops the ECS instances, applicable to scenarios that require managing and stopping multiple ECS instances simultaneously, such as resource optimization and cost management. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be stopped, and Target Instances (targets), which defines the specific ECS instances to be operated on. Upon execution, the template will return a list of the stopped instance IDs, enabling users to verify the status of the instance stop operations. |
YAML JSON |
Immediate execution |
120 |
ACS-ECS-BulkyStopInstancesWithPublicIp |
Bulky stops the ECS instances with public ip |
YAML JSON |
Immediate execution |
121 |
ACS-ECS-BulkyTagInstanceByLinuxKernelVersion |
Bulky tag ECS instances using Linux kernel version as tag value by specifying instance IDs |
YAML JSON |
Immediate execution |
122 |
ACS-ECS-BulkyTagInstanceByOSType |
Bulky tag ECS instances using OS type as tag value by specifying instance IDs |
YAML JSON |
Immediate execution |
123 |
ACS-ECS-BulkyTagInstanceByRunCommandResult |
Bulky tag ECS instances using RunCommand invocation result as tag value |
YAML JSON |
Immediate execution |
124 |
ACS-ECS-BulkyTagInstances |
Bulky tag ECS instances |
YAML JSON |
Immediate execution |
125 |
ACS-ECS-BulkyUpgradeInternetBandwidth |
Bulky upgrades internet bandwidth of ECS instances |
YAML JSON |
Immediate execution |
126 |
ACS-ECS-CloneInstancesAcrossAZ |
Cross available zone clone and bulky run ECS instance |
YAML JSON |
Immediate execution |
127 |
ACS-ECS-CloneInstancesAcrossRegion |
Cross Region copy and run ECS instance by InstanceIds |
YAML JSON |
Immediate execution |
128 |
ACS-ECS-ConfigureCloudMonitorAgent |
Use this template to install cloud monitor agent on ecs |
YAML JSON |
Immediate execution |
129 |
ACS-ECS-ConfigureDocker |
Use this template to install or unistall docker on ecs |
YAML JSON |
Immediate execution |
130 |
ACS-ECS-ConfigurePackage |
Use this template to install or unistall package on ecs |
YAML JSON |
Immediate execution |
131 |
ACS-ECS-ConvertsPublicIPToNewEIPByInstanceId |
Converts the public IP address of a VPC-connected ECS instance with another Elastic IP (EIP) address |
YAML JSON |
Immediate execution |
132 |
ACS-ECS-CorrectSecurityGroupInstancesByTags |
Gets an instance from a label and adds the acquired instance to the security group under the specified label |
YAML JSON |
Immediate execution |
133 |
ACS-ECS-CreateAndCopyImage |
Creates an ECS image and copies the new image to other regions, applicable to scenarios requiring creation and synchronization of ECS images across different regions, such as system updates and backups. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instance for which the image will be created, ECS Instance ID (instanceId), which identifies the instance to create the image from, and Target Image Name (targetImageName), which names the new ECS image. Optionally, users may execute tasks on the instance via cloud assistant commands (commandContent). The created image will be synchronized to specified target regions (targetRegionIds), and users can also opt to share the image with other Alibaba Cloud accounts (accountIds). Upon execution, the template will return a list of the created and cloned image IDs, facilitating verification of the operations. |
YAML JSON |
Immediate execution |
134 |
ACS-ECS-CreateImage |
Creates an ECS image, applicable to scenarios requiring the creation of a custom image from an existing ECS instance, such as for backup and system migration. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instance for which the image will be created, ECS Instance ID (instanceId), which identifies the instance from which the image will be created, and Image Name (imageName). Users can also choose whether to create an image only from the system disk (whetherOnlySystemDisk). After the image creation, the template will return the ID of the newly created image. |
YAML JSON |
Immediate execution |
135 |
ACS-ECS-CreateImageAndUpdateLaunchTemplates |
Creates an ECS image and update launch template |
YAML JSON |
Immediate execution |
136 |
ACS-ECS-DeleteImage |
Deletes an ECS image, applicable to freeing up storage space by removing custom images that are no longer needed. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS image to be deleted, and Image ID (imageId), which identifies the image to be deleted. Additionally, users can choose whether to enforce the deletion (force). Upon execution, the template will confirm the deletion of the specified ECS image. |
YAML JSON |
Immediate execution |
137 |
ACS-ECS-DownloadFileFromECS |
Upload ECS files to OSS and generate temporary download links |
YAML JSON |
Immediate execution |
138 |
ACS-ECS-InheritDiskTagToSnapshot |
All snapshots in the specified region inherit the specified tag on the corresponding disk. |
YAML JSON |
Immediate execution |
139 |
ACS-ECS-InstallXDragonAndCloudMonitor |
Bulky install XDragon hardware detection plug-in, cloud monitor, smartmontools, or uninstall and update XDragon hardware detection plug-in |
YAML JSON |
Immediate execution |
140 |
ACS-ECS-InventoryDataCollection |
Inventory data collection |
YAML JSON |
Immediate execution |
141 |
ACS-ECS-JoinSecurityGroupToMultipleInstance |
Join a security group to multiple instances |
YAML JSON |
Immediate execution |
142 |
ACS-ECS-LocalBuildAndDeployOnSingleECS |
Build and deploy applications on a single ECS |
YAML JSON |
Immediate execution |
143 |
ACS-ECS-ModifyAutoRenewAttributeAfterOrderPaid |
Modify the automatic renewal properties of the instance after waiting for the specified order to be paid successfully |
YAML JSON |
Immediate execution |
144 |
ACS-ECS-ModifyInstanceSpec |
Modify postpaid instance's type |
YAML JSON |
Immediate execution |
145 |
ACS-ECS-RebootInstanceAtHighCpuByTags |
Reboot ECS instance with specified tag when its CPU utilization exceeded threshold.The selected instance must already have the Cloud Monitor agent installed |
YAML JSON |
Immediate execution |
146 |
ACS-ECS-RebootSpecifiedInstanceAtHighCpu |
Reboot the specified ECS instance when it's CPU utilization excceded threshold.The selected instance must already have the Cloud Monitor agent installed |
YAML JSON |
Immediate execution |
147 |
ACS-ECS-RemoveFromSLBWhenPreemptibleInstanceInterrupted |
Remove backend servers from SLB when preemptible instance of current region is about to be interrupted |
YAML JSON |
Immediate execution |
148 |
ACS-ECS-RepairImage |
Image repair, which is an offline repair of an image based on the results of image check, Please refer to this document for image check https://www.alibabacloud.com/help/en/ecs/user-guide/overview-18 The repair process will first create a repair instance based on the Alibaba cloud Linux image, create a cloud disk snapshot of your image, mount it to the repair instance, repair the data disk offline, and then create a new image of the repaired data disk. |
YAML JSON |
Immediate execution |
149 |
ACS-ECS-RepairWindowsBlueScreenIssue |
Solutions to Repair Windows System Blue Screen Issues |
YAML JSON |
Immediate execution |
150 |
ACS-ECS-RescueUnreachableInstance-Linux |
When using ECS instances, some situations can lead to system disk corruption, such as instances being forced to stop or restart, or sudden downtime, failure to update /etc/fstab when the disk is unloaded, or even loss or corruption of /etc/fstab or initrd files. When the instance cannot be accessed, the state of the instance displayed in the ECS instance console may still be Running, but the application in the instance cannot be accessed, the network in the instance cannot be reached, and the connection cannot be established through workbench or SSH. If you can connect to an instance from the console with VNC, you will probably see a page that indicates a system startup failure. At this point, you can consider executing the template to cure the damaged instance. The cure process is that the system disk of the damaged instance will be mounted to the newly created temporary instance, then a cure script will be executed in the temporary instance, and finally the cured system disk will be mounted back to the original instance. |
YAML JSON |
Immediate execution |
151 |
ACS-ECS-ResetDiskWithSnapshot |
Use snapshot to create a temporary cloud disk to restore data |
YAML JSON |
Immediate execution |
152 |
ACS-ECS-RestoreDataWithSnapshot |
Use snapshot to create a temporary cloud disk to restore data |
YAML JSON |
Immediate execution |
153 |
ACS-ECS-RevokeSecurityGroupRules |
Del the security gorup rule |
YAML JSON |
Immediate execution |
154 |
ACS-ECS-RunCommandWhenDiskUsageLimitExceeded |
Run command when disk usage limit is exceeded |
YAML JSON |
Immediate execution |
155 |
ACS-ECS-RunInstancesWithApproval |
Creates one or more ECS instances with approval |
YAML JSON |
Immediate execution |
156 |
ACS-ECS-RunPacker |
Run packer template |
YAML JSON |
Immediate execution |
157 |
ACS-ECS-RunRemoteShellScript |
Run remote shell script |
YAML JSON |
Immediate execution |
158 |
ACS-ECS-RunShellScript |
Run shell script. |
YAML JSON |
Immediate execution |
159 |
ACS-ECS-ScheduleApplyPatchBaseline |
Schedule to apply patch baseline on ECS instance |
YAML JSON |
Immediate execution |
160 |
ACS-ECS-ScheduleToAcceptInquiredSystemEvent |
Regularly accept and authorize the execution of system event operations. Template process: - Stop ECS instance
- Accept inquired system event
- Start ECS instance</li
|
YAML JSON |
Immediate execution |
161 |
ACS-ECS-ScheduleToBulkyCreateSnapshot |
Schedule bulky create snapshot |
YAML JSON |
Immediate execution |
162 |
ACS-ECS-ScheduleToCleanUpDisks |
Schedule to clean up disks, applicable to scenarios that require periodic management and cleaning of disk space on ECS instances, such as automatic log file cleanup and deletion of temporary files. During configuration, users need to provide the following required parameter information: Timer Trigger (timerTrigger), which defines when the cleanup task is triggered, Region ID (regionId), which specifies the region of the ECS instances where the disks will be cleaned, Target Instances (targets), which defines the specific ECS instances to be operated on, and Cleanup Rule (cleanUpInfos), which specifies the specific disk cleanup rules. Upon execution, the template will return a list of the output results of the cleanup command, enabling users to verify the status of the disk cleanup operations. |
YAML JSON |
Immediate execution |
163 |
ACS-ECS-ScheduleToCollectInventoryData |
Collect inventory data periodically |
YAML JSON |
Immediate execution |
164 |
ACS-ECS-ScheduleToExecuteDiagnosticReports |
Schedules to execute ECS diagnostic reports in bulk |
YAML JSON |
Immediate execution |
165 |
ACS-ECS-ScheduleToExecuteTemplate |
Schedules to execute specified template, applicable to scenarios where OOS templates need to be executed at specific intervals or time points, such as automated maintenance tasks and scheduled management tasks. During configuration, users need to provide the following required parameter information: Timer Trigger (timerTrigger), which configures the trigger type and expression, Template Name (templateName), which specifies the name of the OOS template to be executed, and Template Parameters (templateParameters), which are the parameters required for executing the template. Once defined, the template will trigger and execute the specified OOS template according to the configured schedule. |
YAML JSON |
Immediate execution |
166 |
ACS-ECS-ScheduleToRebootInstances |
Schedule to reboot ECS instances, applicable to scenarios that require periodic management and reboot of ECS instances, such as system maintenance and updates. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be operated on, Cron Expression (cron), which defines the schedule for the task, and Target Instances (targets), which defines the specific ECS instances to be operated on. Upon execution, the template will periodically reboot the ECS instances according to the configured schedule. |
YAML JSON |
Immediate execution |
167 |
ACS-ECS-ScheduleToRebootInstancesWithSLR |
Schedule to reboots the ECS instances |
YAML JSON |
Immediate execution |
168 |
ACS-ECS-ScheduleToRunCommand |
Schedule to run command on ECS instances, applicable to scenarios that require periodically running commands on multiple ECS instances, such as system maintenance and task automation. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances where the commands will be run, Cron Expression (triggerCron), which defines the schedule for the task, Target Instances (targets), which defines the specific ECS instances to be operated on, and Command Type (commandType) and Command Content (commandContent). Upon execution, the template will return a list of the output results of the run command, enabling users to verify the status of the command executions. |
YAML JSON |
Immediate execution |
169 |
ACS-ECS-ScheduleToStartAndStopInstances |
Schedule to start and stop ECS instances, applicable to scenarios where regular and scheduled management of ECS instances is required, such as automated operations of development environments and cost optimization. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be operated on, Daily Start Time (dailyStartTime), Daily Stop Time (dailyStopTime), and the Days of Week (weekdays), which define the schedule for the tasks. Upon execution, the template will start and stop the ECS instances according to the configured schedule. |
YAML JSON |
Immediate execution |
170 |
ACS-ECS-ScheduleToStartAndStopOrStopAndStartInstances |
Schedule to start and stop ECS instances |
YAML JSON |
Immediate execution |
171 |
ACS-ECS-ScheduleToStartInstances |
Schedule to start the ECS instances, applicable to scenarios where ECS instances need to be started at scheduled times, such as automatically starting development or test environments within specific periods. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be operated on, Cron Expression (cron), which defines the schedule for the task, and Target Instances (targets), which defines the specific ECS instances to be operated on. Upon execution, the template will start the ECS instances according to the configured schedule. |
YAML JSON |
Immediate execution |
172 |
ACS-ECS-ScheduleToStopAndStartInstances |
Schedules to stop and start ECS instances, applicable to scenarios that require automatically stopping and starting ECS instances at specific times, such as automated maintenance tasks and resource management. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be operated on, Daily Stop Time (dailyStopTime) and Daily Start Time (dailyStartTime), and Days of Week (weekdays), which define the schedule for the tasks, as well as Target Instances (targets), which define the specific ECS instances to be operated on. Users can also choose whether to stop or hibernate the instances. The template will stop and start the ECS instances according to the configured schedule. |
YAML JSON |
Immediate execution |
173 |
ACS-ECS-ScheduleToStopInstances |
Schedule to stop the ECS instances, applicable to scenarios where ECS instances need to be stopped at scheduled times, such as automatically stopping development or test environments to save costs. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances to be operated on, Cron Expression (cron), which defines the schedule for the task, and Target Instances (targets), which defines the specific ECS instances to be operated on. Upon execution, the template will stop the ECS instances according to the configured schedule. |
YAML JSON |
Immediate execution |
174 |
ACS-ECS-ScheduleToUpgradeInternetBandwidth |
Schedule to upgrades internet bandwidth for ECS instances |
YAML JSON |
Immediate execution |
175 |
ACS-ECS-ScheduleToUpgradeInternetBandwidthNew |
Schedule to upgrades internet bandwidth for ECS instances |
YAML JSON |
Immediate execution |
176 |
ACS-ECS-SetDiskEncryption |
ACS-ECS-SetDiskEncryption |
YAML JSON |
Immediate execution |
177 |
ACS-ECS-UpdateAndCopyImage |
Updates an existing ECS image via ECS Cloud Assistant then creates an ECS image and copies the new image to other regions. This is applicable to scenarios requiring update and synchronization of ECS images across multiple regions, such as software upgrade and system configuration. During configuration, users need to provide the following required parameter information: Region ID (regionId), which specifies the region of the ECS instances for the update and creation operations, Source Image ID (sourceImageId), which identifies the original ECS image that needs updating, and Target Image Name (targetImageName), for naming the newly created ECS image. Additionally, users need to configure the Instance Type (instanceType) for installing and configuring the new image, and Target Region IDs (targetRegionIds), which specify the other regions to clone the new image to. Upon execution, the template will return the IDs of the newly created and cloned images, facilitating the verification of the image update and cloning status. |
YAML JSON |
Immediate execution |
178 |
ACS-ECS-UpdateImage |
Update an existing ECS image by running commands and create a new ECS image. This is applicable to scenarios requiring batch updates and management of ECS images, such as software installation and system configuration changes. During configuration, users need to provide the following required parameters: Region ID (regionId), which specifies the region where the image update and creation operations occur, and Source Image ID (sourceImageId), which identifies the original ECS image that needs updating. Additional parameters that can be modified from their default values include: Target Image Name (targetImageName) for naming the newly created ECS image, Instance Type (instanceType) for the type of instance to install and configure the new image on, and Update Type (updateType), which can be selected to either run commands or install packages. Upon execution, the template will return the ID of the newly created image, facilitating the verification and management of the created ECS image. |
YAML JSON |
Immediate execution |
179 |
ACS-ENS-BulkyQueryDisksAttributes |
Bulky query ENS disk info |
YAML JSON |
Immediate execution |
180 |
ACS-ENS-BulkyQueryInstanceInfo |
Bulky query ENS instance info |
YAML JSON |
Immediate execution |
181 |
ACS-ENS-BulkyQueryInstanceSliceInfo |
Bulky query ENS instance info sliced by column name |
YAML JSON |
Immediate execution |
182 |
ACS-ENS-BulkyQueryNasFileSystemsInfo |
Bulky query ENS nas file system info |
YAML JSON |
Immediate execution |
183 |
ACS-ENS-BulkyQueryRouteEntryInfo |
Bulky query ENS route entry info |
YAML JSON |
Immediate execution |
184 |
ACS-ENS-BulkyQueryRouteTableInfo |
Bulky query ENS route table info |
YAML JSON |
Immediate execution |
185 |
ACS-ENS-BulkyQuerySecurityGroupInfo |
Bulky query ENS security group info |
YAML JSON |
Immediate execution |
186 |
ACS-ENS-BulkyQuerySnapshotsInfo |
Bulky query ENS snapshot info |
YAML JSON |
Immediate execution |
187 |
ACS-ENS-BulkyQueryVSwitchInfo |
Bulky query ENS vswitch info |
YAML JSON |
Immediate execution |
188 |
ACS-ENS-BulkyQueryVpcInfo |
Bulky query ENS vpc info |
YAML JSON |
Immediate execution |
189 |
ACS-ESS-AdjustScalingGroupInstanceCount |
Adjust the number of instances in a scaling group by creating and executing scaling group rules. Description: - If the scaling group has been configured with the desired number of instances, when the number of instances in the scaling group is not equal to the expected number of instances, the auto scaling service will automatically scale to ensure that the number of instances in the scaling group is always maintained After the execution is complete, please go to the ESS console to view the adjustment results.
- The number of cluster nodes after scaling down the nodes cannot be less than the minimum node requirements of the component, otherwise the scaling operation may return an error of code:IncorrectCapacity.
- Please ensure that your account balance is greater than the cost of the newly purchased instance, otherwise an error of code:InvalidAccountStatus.NotEnoughBalance will be returned.
- If it is multi-zone, please expand the multiple of the number of zones.
- The payment method for the expanded ECS is pay-as-you-go. If necessary, customers need to Manual subcontracting yearly and monthly.
- There are two ways to scale down:scale down the specified number of ECS (the number of ECS instance adjustments in the scaling group is not 0), remove the specified ECS from the scaling group ( The number of ECS instance adjustments in the scaling group is 0 and the ECS to be removed is selected)
- The scaling cannot be less than the number initially opened in the scaling group.
Adjust the number of instances in a scaling group by creating and executing scaling group rules. Description: - Adjust ACK cluster node poolExpected number of nodes, please read the linked document carefully and authorize the role AliyunOOSLifecycleHook4CSRole.
|
YAML JSON |
Immediate execution |
190 |
ACS-ESS-CreateImageAndUpdateScalingConfiguration |
Creates an ECS image and updates scaling configuration image ID |
YAML JSON |
Immediate execution |
191 |
ACS-ESS-ECILifeCycleExecContainerCommand |
Use lifecycleHook to run command in the specified scaling activity ECI instance |
YAML JSON |
Immediate execution |
192 |
ACS-ESS-ECILifeCycleModifyAnalyticDBIPWhitelist |
Use lifecycleHook to modify the IP whitelist of the AnalyticDB instance |
YAML JSON |
Immediate execution |
193 |
ACS-ESS-ECILifeCycleModifyMongoDBIPWhitelist |
Use lifecycleHook to modify the IP whitelist of the MongoDB instance |
YAML JSON |
Immediate execution |
194 |
ACS-ESS-ECILifeCycleModifyPolarDBIPWhitelist |
Use lifecycleHook to modify the IP whitelist of the PolarDB instance |
YAML JSON |
Immediate execution |
195 |
ACS-ESS-ECILifeCycleModifyRedisIPWhitelist |
Use lifecycleHook to modify the IP whitelist of the redis instance |
YAML JSON |
Immediate execution |
196 |
ACS-ESS-EnableInstanceHealthCheck |
Enables health checks for ECS instances in the scaling group |
YAML JSON |
Immediate execution |
197 |
ACS-ESS-LifeCycleAllocateEipAddressAndAttachToInstance |
Use lifecycleHook to create EIP and attach them to the instance(only supports elastic expansion activities) |
YAML JSON |
Immediate execution |
198 |
ACS-ESS-LifeCycleApplyAutoSnapshotPolicy |
Use lifecycleHook to apply an automatic snapshot policy to one or more disks, only supports elastic expansion activities |
YAML JSON |
Immediate execution |
199 |
ACS-ESS-LifeCycleAttachEipToInstance |
Use lifecycle hook to attach EIP to the instance(only supports elastic expansion activities) |
YAML JSON |
Immediate execution |
200 |
ACS-ESS-LifeCycleAttachNASFileSystemToInstance |
Use lifecyclehook to attach NAS file system to instance (only supports elastic expansion activities) |
YAML JSON |
Immediate execution |
201 |
ACS-ESS-LifeCycleBulkyDeleteClusterNodes |
Use lifecyclehook to delete cluster nodes (only supports elastic contraction activities) |
YAML JSON |
Immediate execution |
202 |
ACS-ESS-LifeCycleCreateNetworkInterfaceAndEipAndAttachToInstance |
Use lifecycleHook to create NetworkInterface and EIP and attach them to the instance, The NetworkInterface currently only needs to be configured on CentOS 7.3 64-bit, CentOS 6.8 64-bit, Window Server 2008 R2 and higher versions, and other images, please refer to the official document for configure NetworkInterFace https://help.aliyun.com/document_detail/56955. html(only supports elastic expansion activities) |
YAML JSON |
Immediate execution |
203 |
ACS-ESS-LifeCycleDetachNetworkInterfaceAndDeleteEip |
Use lifecyclehook to uninstall and delete network interface and eip on instances in batches (only supports elastic contraction activities) |
YAML JSON |
Immediate execution |
204 |
ACS-ESS-LifeCycleDownloadFileAndRunCommand |
Use lifecycleHook to download file and run command in the specified scaling activity instance |
YAML JSON |
Immediate execution |
205 |
ACS-ESS-LifeCycleDownloadOSSFileAndRunCommand |
Use lifecycleHook to download OSS file and run command in the specified scaling activity ECS instance |
YAML JSON |
Immediate execution |
206 |
ACS-ESS-LifeCycleGetIpAddressAndModifyInstanceName |
Use lifecycleHook to get the private network IP and modify the name of the ECS instance |
YAML JSON |
Immediate execution |
207 |
ACS-ESS-LifeCycleInstallAAS |
Use lifecycleHook to install AAS(Additional application server) in the specified scaling activity instance. |
YAML JSON |
Immediate execution |
208 |
ACS-ESS-LifeCycleModifyAnalyticDBIPWhitelist |
Use lifecycleHook to modify the IP whitelist of the AnalyticDB instance |
YAML JSON |
Immediate execution |
209 |
ACS-ESS-LifeCycleModifyInstanceChargeType |
Use lifecycleHook to modify instance charge type in the specified scaling activity |
YAML JSON |
Immediate execution |
210 |
ACS-ESS-LifeCycleModifyMongoDBIPWhitelist |
Use lifecycleHook to modify the IP whitelist of the MongoDB instance |
YAML JSON |
Immediate execution |
211 |
ACS-ESS-LifeCycleModifyPolarDBIPWhitelist |
Use lifecycleHook to modify the IP whitelist of the PolarDB instance |
YAML JSON |
Immediate execution |
212 |
ACS-ESS-LifeCycleModifyRedisIPWhitelist |
Use lifecycleHook to modify the IP whitelist of the redis instance |
YAML JSON |
Immediate execution |
213 |
ACS-ESS-LifeCycleReleaseEipAddressFromInstance |
Use lifecyclehook to uninstall and release the eip on instances in batches (only supports elastic contraction activities) |
YAML JSON |
Immediate execution |
214 |
ACS-ESS-LifeCycleRunCmdOnSpecifiedInstanceToEssCreatedInstances |
Use lifecycleHook to run command on one specified instance to other instances created by ESS. |
YAML JSON |
Immediate execution |
215 |
ACS-ESS-LifeCycleRunCommand |
Use lifecycleHook to run command in the specified scaling activity instance |
YAML JSON |
Immediate execution |
216 |
ACS-ESS-LifeCycleRunCommandNew |
Use lifecycleHook to run command in the specified scaling activity instance |
YAML JSON |
Immediate execution |
217 |
ACS-ESS-LifeCycleRunCommandOnSpecifiedInstance |
Use lifecycleHook to run command in the specified scaling activity instance |
YAML JSON |
Immediate execution |
218 |
ACS-ESS-RollingUpdateByConfigureOOSPackage |
Rolling update ECS instances that in scaling group by configure oos package |
YAML JSON |
Immediate execution |
219 |
ACS-ESS-RollingUpdateByDownloadFileAndRunCommand |
Rolling update ECS instances that in scaling group by download file and run command |
YAML JSON |
Immediate execution |
220 |
ACS-ESS-RollingUpdateByDownloadOSSFileAndRunCommand |
Rolling update ECS instances that in scaling group by download OOS file and run command |
YAML JSON |
Immediate execution |
221 |
ACS-ESS-RollingUpdateByReplaceSystemDiskInScalingGroup |
Rolling update ECS instances that in scaling group by replace system disk |
YAML JSON |
Immediate execution |
222 |
ACS-ESS-RollingUpdateByRunCommandInScalingGroup |
Rolling update ECS instances that in scaling group by run command |
YAML JSON |
Immediate execution |
223 |
ACS-ESS-RollingUpdateByUpdateContainerGroup |
Rolling update ECI instances in scaling group by update container group |
YAML JSON |
Immediate execution |
224 |
ACS-ESS-UpdateScalingConfigurationImage |
Updates an existing ECS image via ECS Cloud Assistant then creates an ECS image and updates scaling configuration image ID |
YAML JSON |
Immediate execution |
225 |
ACS-EventBridge-PutEvents |
Put one or more events |
YAML JSON |
Immediate execution |
226 |
ACS-FC-InvokeFunction |
Invoke the function and return the result |
YAML JSON |
Immediate execution |
227 |
ACS-FC-RunScript |
FC runs script(Only support python), To use this template, you must first activate the function computing service< /a> |
YAML JSON |
Immediate execution |
228 |
ACS-HBR-SAPHanaRestorationAutomation |
This template uses an existing VPC and SAP HANA instance(source instance) to create a single-node SAP instance(destination instance), restore the source instance backup data to the destination instance through the HBR service, and check the restored destination instance status. |
YAML JSON |
Immediate execution |
229 |
ACS-HBR-SAPHanaRestorationAutomationByExistingECS |
This template uses existing SAP HANA instances(source instance and destination instance) to restore the source instance backup data to the destination instance through the HBR service, and check the restored destination instance status. |
YAML JSON |
Immediate execution |
230 |
ACS-KMS-BulkySetDeletionProtection |
Enable deletion protection for CMK |
YAML JSON |
Immediate execution |
231 |
ACS-KMS-BulkyUpdateRotationPolicy |
Update rotation policy |
YAML JSON |
Immediate execution |
232 |
ACS-LOG-BulkyInstallLogtail |
Use this template to install sls logtail on ecs |
YAML JSON |
Immediate execution |
233 |
ACS-MNS-PublishMessage |
Publish a message to the specified MNS topic. After the message is published to the topic, it will be pushed to Endpoint for consumption |
YAML JSON |
Immediate execution |
234 |
ACS-MongoDB-ModifyAccessWhiteList |
Modify mongoDB instance ip whitelist |
YAML JSON |
Immediate execution |
235 |
ACS-Mongodb-BulkyModifyBackupPolicy |
Update mongodb instance backup policy |
YAML JSON |
Immediate execution |
236 |
ACS-OOS-ExecuteTemplateByAlarm |
Execute specified template when alarm is raised according to alarm rule. AlarmTrigger will always run until being canceled |
YAML JSON |
Immediate execution |
237 |
ACS-OOS-ExecuteTemplateBySystemEvent |
Execute specified template when system event happens. EventTrigger will always run until being canceled |
YAML JSON |
Immediate execution |
238 |
ACS-OSS-EnableBucketZRS |
Change the storage redundancy type of a bucket to zone-redundant storage (ZRS) |
YAML JSON |
Immediate execution |
239 |
ACS-OSS-PutBucketAcl |
Set or modify the access permission (ACL) of the bucket |
YAML JSON |
Immediate execution |
240 |
ACS-OSS-PutBucketEncryption |
Encryption rules for configuring buckets |
YAML JSON |
Immediate execution |
241 |
ACS-OSS-PutBucketLogging |
Enable logging for a bucket |
YAML JSON |
Immediate execution |
242 |
ACS-OSS-PutBucketPolicy |
Put the bucket policy |
YAML JSON |
Immediate execution |
243 |
ACS-OSS-PutBucketReferer |
Put the bucket referer |
YAML JSON |
Immediate execution |
244 |
ACS-OSS-PutBucketVersioning |
Enable the versioning state of a bucket |
YAML JSON |
Immediate execution |
245 |
ACS-OSS-ScheduleToBulkyDeleteBuckets |
Schedule to cleanup of buckets in a specified resource group |
YAML JSON |
Immediate execution |
246 |
ACS-PolarDB-BulkyModifyBackupPolicyForLevel2Backup |
Modify maintain time of polardb cluster |
YAML JSON |
Immediate execution |
247 |
ACS-PolarDB-BulkyModifyDBClusterDeletion |
Modify deletion of polardb clusters |
YAML JSON |
Immediate execution |
248 |
ACS-PolarDB-BulkyModifyDBClusterMaintainTime |
Modifies maintain time of polardb clusters |
YAML JSON |
Immediate execution |
249 |
ACS-PolarDB-ModifyAccessWhiteList |
Modify polarDB cluseter ip whitelist |
YAML JSON |
Immediate execution |
250 |
ACS-RAM-ApproveAttachCustomPolicyToUser |
Attach custom policy to user that template executed by after approving |
YAML JSON |
Immediate execution |
251 |
ACS-RAM-ApproveAttachPolicyToUser |
Attach policy to user that template executed by after approving |
YAML JSON |
Immediate execution |
252 |
ACS-RAM-BulkyUpdateLoginProfile |
Bulky modify the logon configurations of a RAM user |
YAML JSON |
Immediate execution |
253 |
ACS-RAM-CreateRoleAndAttachCustomPolicy |
Create RAM role and attach custom policy |
YAML JSON |
Immediate execution |
254 |
ACS-RAM-SetPasswordPolicy |
Call SetPasswordPolicy to set the RAM user password strength policy |
YAML JSON |
Immediate execution |
255 |
ACS-RDC-RunCommandByDevops |
Bulky run command on ECS instances |
YAML JSON |
Immediate execution |
256 |
ACS-RDC-RunCommandByStaragent |
Bulky run command on ECS instances |
YAML JSON |
Immediate execution |
257 |
ACS-RDS-BulkyEnableBackupLogPolicy |
Enable rds instance backup policy log backup setting |
YAML JSON |
Immediate execution |
258 |
ACS-RDS-BulkyMigrateSecurityIPMode |
Migrate security ip mode |
YAML JSON |
Immediate execution |
259 |
ACS-RDS-BulkyModifyActionEventPolicy |
Modify action event policy |
YAML JSON |
Immediate execution |
260 |
ACS-RDS-BulkyModifyDBInstanceDeletionProtection |
Bulky enable deletion protection for instances |
YAML JSON |
Immediate execution |
261 |
ACS-RDS-BulkyModifyDBInstanceMaintainTime |
Modifies maintain time of rds instance |
YAML JSON |
Immediate execution |
262 |
ACS-RDS-BulkyModifyDBInstanceSpec |
Modify the configuration of the RDS instance, change reminder: |
|
|