ROS is designed to streamline the management of cloud computing resources. Customers create stack templates using ROS-defined specifications. Within these templates, users can define cloud computing resources, including Elastic Compute Service (ECS) and ApsaraDB RDS instances, along with resource dependencies. The ROS engine then automates the creation and configuration of all resources in a stack based on the template, enabling seamless automatic deployment and operational management (O&M).
Effortlessly manage cloud resources through stack creation, deletion, and updates, simplifying application migration and scaling.
Modify templates and configurations on a stack without changing the region, ensuring seamless updates.
Modify templates and configurations with region changes by recreating a stack to meet evolving needs.
Efficiently remove unnecessary stacks, with the option to retain or release associated resources as needed.
-
Infrastructure as Code
Provides advance infrastructure by provides the easy mechanism and flows for configuration.
-
Fully managed automation service
No need to manage it by yourself with inurement in compliance with your specifications.
-
Repeatable deployment
Allows users to easily repeatable deployment by reduces the time and effort.
-
Standardized deployment
Provides unified authentication, security, and audit in implementing the technology stack.
What is Resource Orchestration (ROS)?
ROS is a service that enables you to automate the deployment, scaling, and management of cloud resources by defining them in templates, supporting infrastructure-as-code (IaC).
How do I use ROS to deploy my infrastructure?
You can use ROS to create templates that define the cloud resources you need (e.g., ECS, RDS, VPC), and deploy them using ROS’s automated orchestration engine.
Is ROS integrated with other Zain Cloud services?
Yes, ROS is fully integrated with other Zain Cloud services, enabling seamless management and provisioning of resources across your infrastructure.
How is ROS billed?
ROS is free of charge. However, the resources deployed via ROS, such as ECS instances or databases, are billed based on their individual usage.