All Products
Document Center

Reasons for template verification failure

Last Updated: Apr 11, 2018

If the template you edited fails the template verification, check the following items to find out the reason.


Make sure that your template is in a valid JSON format and is encoded in UTF-8. A valid JSON format means that JSON can be resolved by programming languages.

Version (ROSTemplateFormatVersion)

Make sure that ROSTemplateFormatVersion is spelled correctly, and its value is 2015-09-01.


Make sure that the mapping definition conforms to the ROS requirements.

Note: No function can be used in the mappings.


Make sure that the parameter definition conforms to the ROS requirements.

Note: No function can be used in the parameters. If the parameter definition contains a parameter restriction definition and a default value, the default value must also conform to the parameter restriction definition.


The resource ID cannot contain forward slashes (/).

The Type attribute must be contained in the resource definition, and its value must be a string.

Values other than Type, Properties, Metadata, DependsOn, DeletionPolicy, and Description cannot be contained in the resource definition.


If outputs are defined, the value must be specified in the Outputs field.

Unsupported resource types

Validation fails if an unsupported resource is defined in the template.

See the supported resource types on Resource Type page in the ROS console.


Make sure that the template file size does not exceed 512 KB.

Make sure that sections other than ROSTemplateFormatVersion, Description, Mappings, Parameters, Resources, and Outputs are not used in the first grade of the template.