Docs

Elastic Compute Service

Managing custom templates

Creating custom templates

You can define JSON templates based on real-world scenarios to preset standardized O&M processes. This allows for efficient handling of batch and customized O&M tasks across large-scale instances.

Usage note

A single account supports up to 100 custom templates at the same time. If the number of custom templates in your account has reached this limit, you can delete custom templates that are no longer required, and then create custom templates based on your business requirements.

Procedure

In the left-side navigation pane, select the "Maintenance & Monitoring > Orchestration" menu.

In the top menu bar, select the project and region where your business is located.

On the CloudOps Orchestration page, click the "Custom template" tab.

Click the "Create custom templates" button and configure the parameters in the following table.

Parameter	Description
Name	The name of the custom template. tip The template name must be unique within the current account or project. It cannot be the same as the name of the public template, nor can it be the same as the name of any other custom template.
JSON schema	Defines custom template files (O&M orchestration processes) in JSON format, including the data structure, field constraints, and validation rules for "Parameters", "Tasks", and "Outputs". Learn more. Default template structure: { "FormatVersion": "0.2", "Description": "", "Parameters": {}, "Tasks": [], "Outputs": {} } FormatVersion: Optional. The engine version. The default value is 0.2. Description: Optional. The description that explains details such as the usage and purpose of the template. Parameters: Optional. Defines the list of parameters used during template execution. For more information, see Parameters description. Tasks: Required. The Tasks parameter is the most important component of a template. Each task defines a specific action to be executed. These actions are defined and implemented by the Orchestration service. For more information, see Tasks description. Outputs: Optional. The Outputs parameter defines information returned after template execution and can reference the output of a task (by specifying the task name). For more information, see Outputs description.
Project	Used to select the scope of instances the custom template applies to based on projects. tip After you select a project, new instances that meet the conditions automatically match the custom template. The project displayed here is the one you selected in Step 3. You can change the project in the top menu bar.
Tag	Optional. Used to select the scope of instances the custom template applies to based on tags. Click the "Add tag" button, and then select or enter the tag key and corresponding tag value. tip Up to 20 tags can be added. A tag is a key-value pair used to identify cloud resources. Tags help you categorize resources based on different dimensions, such as purpose, owner, or environment. This allows you to search and aggregate your resources. Learn more.

Click "Confirm" to complete the operation.

Subsequent steps

After the custom template is created, you can use this template to create an orchestration plan for automated O&M.

Last updated: 2026.06.18 17:48:27