This document provides the technical solution, resource list, and deployment configurations that service provider needs to prepare before launching services in the Compute Nest console.
1. Self-check and assessment
Before publishing a Compute Nest service, we recommend that software service providers and application developers (hereinafter referred to as service providers) complete the following self-check items:
a. Confirm software delivery method
Private delivery
Scenarios: The software and cloud resources are deployed under the user account, and the cloud resources are paid by user.
Service type: For privately deployed services, the managed O&M capability is available to assist with O&M tasks.
SaaS delivery (fully managed delivery)
Scenarios: The software and cloud resources are deployed under the service provider's account, and the cloud resources are paid by service publisher.
Service type: Fully managed deployment service.
b. Confirm middleware dependencies
Checklist:
Check the middleware required by the software, such as MySQL, Redis, object storage service, and log service.
Check whether the middleware has Alibaba Cloud versions, such as RDS, OSS.
NotePrioritize using Alibaba Cloud services such as ApsaraDB RDS to improve reliability. If no Alibaba Cloud service is available, you can use self-built middleware.
Special scenarios: Large model development may require frameworks such as Knative or KServe. Please confirm their compatibility beforehand.
c. Confirm deployment method
Select the deployment method based on your software requirements.
Creation method | Operation |
Pull and deploy through a repository (such as GitHub) | |
Use a template if the complex architecture is used or a large volume of underlying cloud resources are required | You must use the custom resource orchestration template (ROS/Terraform). |
Only ECS/ACK and basic cloud resources are required for deployment | Compute Nest provides standardized processes and sample templates. Refer to Create a service by using a featured template when creating a service. |
d. Confirm sales method
Option | Scenario | Core capabilities |
Alibaba Cloud Marketplace (Recommended) | Standardized software sales. | Powerful features with support for pay‑per‑use, subscription, and pay‑as‑you‑go billing options. |
Third-party payment (SaaS Boost) | Individual developers quickly build online market. | Offer annual or monthly subscriptions and automatically generates a web interface. |
Custom sales | No online transaction requirements (private deployment). | The console manages the validity period. You need to check the validity period of a service instance. |
For more information, refer to sell services.
e. Confirm resource orchestration method
Recommended method: Use the native ROS template, which supports a wider range of Alibaba Cloud resource types and deep integration capabilities.
Alternative method: Use ROS Terraform templates, which are compatible with Terraform syntax and suitable for existing Terraform scripts scenarios.
2. (Optional) Apply for being a service provider
Role type | Scenario | Operation |
Standard user | Default, no additional application required. | N/A (default role on logon). |
Compute Nest service provider | Requires the use of features like service trials or Alibaba Cloud Marketplace sales. | |
Distributor | Assists other service providers in selling their products. |
3. Configure services before publishing
a. Create deployment package
What is deployment package?
A deployment package is a carrier used in the deployment process, such as an ECS image, Helm chart, file, or container image. You can select an appropriate deployment package type for a service based on the deployment scenario. For more information, refer to Deployment package overview. This document introduces the usage scenarios of each deployment package.
When do you need a deployment package?
We recommended to use deployment package when the software requires complex installation, large file distribution, or has unstable sources.
b. Prepare resource orchestration
If you need complex architecture or large volume of underlying cloud resources, prepare the list according to the following requirements:
Resources: Confirm the cloud resource types (ECS, RDS, SLB, Redis, etc.), configurations, and dependencies between resources.
Custom parameters
Identifies parameters that require user input, such as password, storage capacity, instance specifications, etc.
Identifies parameters that are output for users, such as access URLs, API keys, etc.
Images and packages: Provide the image required for deployment (ECS image or container image) and the software package download link.
After finishing the above, create an ROS template. For guidance on creating the template, refer to Resource orchestration.
If you encounter any issues while creating the ROS template, you can contact the Compute Nest team for assistance.
To apply for cloud resources for service testing, refer to Configure a free trial.
What to do next
After completing all preparations, create, test, and publish your services. For more information, refer to Publish services.