Help Center> Resource Formation Service> User Guide (ME-Abu Dhabi Region)> Service Overview> Introduction
Updated on 2022-02-22 GMT+08:00
View PDF

Introduction

Application Orchestration Service (AOS) enables enterprises to automate application cloudification. By orchestrating mainstream cloud services, you can create, replicate, and migrate your applications and provision required cloud resources with a few clicks.

To work with AOS, all you need to do is create a template describing the applications and cloud resources that you would like, including their dependencies and references. AOS will then set up these applications and resources as specified in your template. For example, suppose you want to create an Elastic Cloud Server (ECS), together with a Virtual Private Cloud (VPC) and a subnet on which the ECS runs, you simply create a template defining an ECS, a VPC, a subnet, and their dependencies. AOS will then create a stack, namely, a collection of resources you specified in the template. After the stack has been successfully created, the ECS, VPC, and subnet are available to use.

AOS templates are text files that are easy to read and write. You can edit template files in YAML or JSON format.

AOS manages cloud resources and applications in a unified manner through stacks. During stack creation, AOS automatically configures the cloud resources and applications specified in the template. You can view the status and alarms of cloud resources or applications in a stack. You can create, delete, and copy cloud resources and applications by performing corresponding operations on stacks as a unit.

You can work with AOS on Console or through API.

Figure 1 How AOS works

Features

  • Automatic orchestration of resources

    AOS provides automatic orchestration of mainstream public cloud services. For list on the cloud resources that can be orchestrated, see Resource Indexes. AOS also provides lifecycle management including resource scheduling, application design, deployment, and modification to reduce O&M costs through automation.

  • Hybrid orchestration of applications and cloud service resources

    You can use standard languages, namely YAML and JSON, to describe required basic resources, application systems, upper-layer services, and their relationships. Based on your description, resource provision, application deployment, and service loading can be automatically performed in the order specified by dependencies with a few clicks. You can perform unified management on deployed resources and applications like deletion, scaling, replication, and migration.

Parent topic: Service Overview