Resource Orchestration Service

Simplify the Operations and Management (O&M) of your computing resources

Alibaba Cloud Resource Orchestration Service (ROS) provides developers and system managers with a simple method to create and manage their Alibaba Cloud resources. Through ROS you can use text files in JSON format to define any required Alibaba Cloud resources, dependencies between resources, and configuration details.

ROS offers a template for resource aggregation and blueprint architecture that can be used as code for development, testing, and version control. Templates can be used to deliver Alibaba Cloud resources and system architectures. Based on the template, API, and SDK, you can then conveniently manage your Alibaba Cloud resource by code. ROS is free of charge for Alibaba Cloud users.


ROS supports a wide range of Alibaba Cloud resources, as well as providing a management console, API, and CLI.
ROS templates offer code that can be used to operate on cloud infrastructure. You can use these templates as code for version control, automatic testing, and continuous integration and deployment, thereby greatly increasing your DevOps capability.
Flexible and Secure
ROS supports both primary accounts and sub-accounts, and isolates resources between users to improve security.


  • Easy Integration

    ROS enables you to use templates to remove the hassle of calling resource APIs. You therefore only need to use declarative syntax to define required resources and dependencies between resources. ROS then automatically creates and configures resources and ensures consistency between the process and final resource status. The entire process is fully automated, and with API/SDK/CLI provided by ROS you can easily construct a complete automatic O&M system.

  • Convenient Resource Delivery

    ROS templates provide a standardized way of delivering resources and applications. Based on abundant expression capabilities of ROS templates, you can define a complete architecture for the software system, including cloud resource creation and dependencies and software configuration. Besides, ROS templates are highly reusable. That is, one template can be deployed many times. You can adjust parameters and variables defined in the template based on your needs to increase deployment flexibility.

  • Orchestration Template

    Abundant template samples are provided, covering multiple application scenarios.

    The online template editor can verify that the template is correct, and provides error details.

    Resources can be created through URLs of specified templates.

  • Resource Creation

    Currently, ROS enables you to create and buy resources including Elastic Compute Service (ECS), ApsaraDB, Server Load Balancer, Virtual Private Cloud (VPC), Object Storage Service (OSS), Redis, ApsaraDB for Memcache, Auto Scaling, Log Service, Resource Access Management (RAM), and products from other cloud markets.

    ROS allows you to create resources in most Alibaba Cloud regions.

    ROS supports Cloud Init for custom ECS resource configuration.

    ROS allows you to specify a resource deletion policy when you create a resource.

    ROS allows you to create the specification of each ECS instance with one key.

  • Resource Updating

    ROS allows users to edit the original template and parameters online.

    Modify the template or parameters to configure and change resource attributes.

    Modify the template or parameters for resource auto scaling.

  • Resource Deletion

    Use other services to delete resources from Stack.

    Completely delete Stack and its resources.

    Delete just the Stack and retain its resources.

    ROS processes the resources based on the deletion policy.

  • Resource Query

    ROS allows you to check resource status and error details from the perspective of Stack, Resource or Event.

    You can query the template of a Stack.

    You can check the status of resources in a Stack.

How it works

  • Enterprise Resource Management
  • DevOps
  • Application O&M
Enterprise Resource Management

Enterprise Resource Management

Applicable to complicated enterprise asset management scenarios.

Solution Description

  • An enterprise consists of numerous departments. In many cases, each department requires its own IT infrastructure. The Finance Department, for example, has to approve fund applications from other departments as required, and collect statistics on fund expenditure from each department as well as IT assets of the entire enterprise. ROS provides a method for enterprises to meet these demands through the use of subaccounts to generate a Stack for each department, so that each department can use only resources in its own Stack. The Finance Department can use these Stacks to collect statistics on fund expenditure from each department and the IT assets of the enterprise.



Applicable to developers who want to enhance their DevOps capability.

Solution Description

  • Many cloud resource management and utilization problems occur during the agile development of Cloud Native Applications, causing failure in automatic testing and deployment of code, thereby affecting continuous integration and delivery, and reducing development efficiency. Through ROS, you can use a template to operate cloud resources in the same way you manage code. This provides easy automated testing and deployment, and supports continuous integration and deployment, helping to greatly improve your DevOps capabilities.

Application O&M

Application O&M

This scenario is applicable for O&M personnel who want to scale resources for a launched application in response to fluctuations in traffic.

Solution Description

  • How can an application launch quickly and stably respond to user requests at the lowest cost while traffic is fluctuating? ROS provides a solution for you to automatically scale computing capability of the application without affecting existing deployment, so that the application can provide services economically and stably. The resource updating feature of ROS provides such capability.

Upgraded Support For You

1 on 1 Presale Consultation, 24/7 Technical Support, Faster Response, and More Tickets.

1 on 1 Presale Consultation

Consulting by experienced cloud experts. Learn More

24/7 Technical Support

Extended service time from 10 hours 5 days a week to 24/7. Learn More

6 Free Tickets per Quarter

The number of free tickets doubled from 3 to 6 per quarter. Learn More

Faster Response

Shorten after-sale response time from 36 hours to 18 hours. Learn More


1. Template verification failure


Ensure that the template is in the valid JSON format and is UTF8-encoded. A valid JSON format means that the JSON can be resolved through programming language.

Version (ROSTemplateFormatVersion)

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


Check whether the mapping definition conforms to ROS requirements. Functions cannot be used in the mappings.


Check whether the parameter definition conforms to ROS requirements. No function can be used in the mappings. 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 the character "/".

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 output field.

Unsupported resource types

The verification fails if an unsupported resource is defined in the template.


Check that the template file size does not exceed 512 KB.

Check that SECTIONs other than 'ROSTemplateFormatVersion', 'Description', 'Mappings', 'Parameters', 'Resources', 'Conditions' and 'Outputs' are not used in the template.

2. Stack Creation Failure

Name duplication

The stack names created by the same user cannot be duplicated.

Stack name format

The stack name cannot contain non-letter and non-number characters, and cannot start with a number.

Resource creation failure

Resource creation failure may cause a failure to create stacks. For example, the inventory is insufficient when you create an ECS resource in a region.

Maximum limit exceeded

You cannot create a number of stacks exceeding the maximum limit.

3. Stack deletion failure

The stack is in use

You cannot delete a stack which is being created or deleted.