Create a fully managed service

Log on to the Compute Nest console.

In the left-side navigation pane, choose My Services. Then, on the My Services page, select the Created Services tab, and then click Create Service.

On the Create Service page, configure the service information.

1. Select a creation method.

   You can choose between Create Service from Featured Templates and Build Custom Service.

   • Create Service from Featured Templates: Compute Nest provides service templates for various architectures and applications to help you quickly create services.

   • Build Custom Service: Follow the guided process to configure service information, deployment, O&M, and advanced settings.

2. For the service type, select Fully Managed Service.

   If you chose Create Service from Featured Templates, first select Fully Managed Service and then select a service template below.

   Note

   After you select a service template, you can click View Details to view the template's deployment guide and configuration files.

3. Click Next: Configure Settings.

4. On the configuration page, configure the service settings.

   • If you chose Create Service from Featured Templates, you only need to configure the basic information for the service.

     Note

     The service icon and service name are pre-filled with the values from the service template. You can modify them as needed.

   • If you chose Build Custom Service, you need to provide the complete service information.

     1. In the Basic Information section, enter the basic service information.

        Parameter	Description
        Service Icon	The icon of the service. The JPG and PNG formats are supported. We recommend that you upload an image whose resolution is 192 × 192 pixels for optimal clarity.
        Service Name	The name of the service. The name must be 3 to 200 characters in length, and can contain digits, letters, and underscores (_).
        Service Description	The description of the service. The description must be 10 to 500 characters in length.
        Service agreement document	Enter the name and URL of the custom service agreement document for this service.
        Version Description	The description of the service version. The version description must be 1 to 200 characters in length. We recommend that you include a version number in the description. The description of each version of a service must be unique.
        Default Prefix for Service Instance Name	The default prefix of service instance names. The prefix can be up to 40 characters in length, and can contain digits, letters, hyphens (-), and underscores (_). The prefix must start with a letter. After you specify the default prefix, the prefix is automatically entered in the Service Instance Name field when customers create a service instance. Customers can modify the prefix.
        Tag Settings	The tag key and value. Select or enter a tag key and a tag value to add a tag to the service resources. You can add up to 20 tags to each resource. If no tag key or tag value is available, you can create a custom tag. For more information, see Add a custom tag.
        Resource group	Select the resource group to which your resources will be added. Resource groups allow you to group your cloud resources by purpose, permissions, or ownership for hierarchical resource management across multiple users and projects within an enterprise. For more information, see Resource groups.

     2. In the Service Deployment section, configure the resources required for the service.

        Parameter		Description
        	Create a member account in Resource Directory	Select whether to enable Whether to Create Member in Resource Directory based on your resource management requirements for the service instance. A member account in Resource Directory is a resource container that Compute Nest automatically creates in the service provider’s Resource Directory when a service consumer creates a service instance. This physically isolates the service instance resources into an independent resource group. For more information, see Account-level isolation for fully managed services.
        	User type	Select Alibaba Cloud or Third-party Cloud. Alibaba Cloud: Choose this option if service consumers can view service instances in their own Compute Nest console. Non-Alibaba Cloud: Choose this option if the service consumer does not have an Alibaba Cloud account or if you do not want to expose Alibaba Cloud to them.
        	nst.vendor.create.tplInputType.label	Includes three methods: Manually Import Template, Custom Template, and No Template. Manually Import Template: You need to select a Deployment Method, and enter a Template Name and Template Content. For the template content, you can upload a pre-written template file. Supported formats are ROS JSON, ROS YAML, and Terraform. When the Deployment Method is set to ROS or Terraform, see Resource Orchestration Service (ROS) for details on the Template Content. If you need to create different types of templates for the same service, you can add multiple templates. Click the icon next to a template to add another. For example, if you need to distinguish between single-availability zone and multi-availability zone deployments in the same service, you can add separate templates for each. Custom Template: In Select template, choose a saved ROS custom template and its version. The Template Content is automatically filled in. If you have not created a custom ROS template, go to the ROS Template Editor to create one first. No Template: In the Network Settings section below, configure the region-specific endpoint service information for VPC private access.
        	Add parameter mapping	You can set up mappings and sub-dependency mappings for parameters in the template. Select a Dependency Parameter and a Parameter, and set values for the Dependency Parameter and the Parameter. After you set the values, the corresponding parameter is automatically hidden. When you create a service instance, only the dependent parameter is displayed. After you select a value for the dependent parameter, the hidden parameter is automatically populated with the value that is set for the corresponding parameter in the mapping. For more information, see Configure parameter mappings.
        	Add package	The parameter sets. You can select a set of parameters in the template and specify the parameter values to create a parameter set. If you want to allow customers to modify all the parameters in a parameter set when they create a service instance, select Support Custom Parameter Set. Otherwise, clear this check box. For more information about parameter sets, see Package settings.
        	Hidden parameters	Select the parameters from the template that you want to hide. Selected parameters are hidden from service consumers during service instance creation. Note Corresponding parameters set in a parameter mapping are automatically added as hidden parameters. If you have already configured them in the parameter mapping, you do not need to select them again here.
        	Deployment region	Select the allowed deployment regions. You can select multiple regions. If no region is selected, all regions are allowed by default.
        	Role name	Select a role that is trusted by Compute Nest. Compute Nest uses this role to create resources. If you are using Compute Nest with a root account, create a role and grant it the necessary permissions. For more information, see Create a role that is trusted by Compute Nest. If you are using Compute Nest as a RAM user, first create a role and grant it permissions. Then, grant the PassRole permission to the RAM user. For more information, see Grant the PassRole permission to a RAM user.
        Deployed At	Estimated Time	The estimated time for deploying a service instance. If you configure this parameter, the specified value is displayed on the service instance deployment page to inform customers of the average time required to deploy a service instance.
        Deployment Package Association	Set ECS Image Association	You can set this parameter to replace the Elastic Compute Service (ECS) image specified in the template with the ECS image in the deployment package that has been distributed. For more information, see ECS image deployment package.
        	Set Container Image Association	We recommend that you use Container image deployment packages if Docker container images are used for service deployment. For more information, see Container image artifacts.
        	Set File Association	Compute Nest provides file deployment packages to resolve the issues that you may encounter when you download software resources for script-based deployment. For example, the cloud resources are inaccessible over the Internet, or the download source of the resources is not stable. For more information, see File deployment packages.
        	Set Helm chart association	To keep your Helm chart private, use a Compute Nest Helm chart deployment package. For more information, see Helm chart deployment package.
        Application Group	Create Application Group	The application groups of resources in the template. You can add resources in the template to application groups. This facilitates resource check and management for customers. On the details page of service instances, customers can view resources, view monitoring data, perform O&M operations, and view logs by group. For more information, see Configure application groups. Note Each resource can be added to only one group.

     3. In the Service O&M (Optional) section, configure the O&M features for the service.

        Parameter		Description
        O&M	Grant permissions to service consumers	If service consumers need to perform O&M on service instances, select Grant Permissions to Customers and choose the permissions to grant. If service consumers do not need to perform O&M on service instances, do not select Grant Permissions to Customers.
        	Add O&M operation	Define the O&M operations that appear on the service consumer's management page. For more information, see Custom O&M operations.
        Monitoring	Resource Monitoring	The monitoring configurations. If you want to receive alert notifications, you must select Obtain Permissions and then select Monitoring Permissions. Configure CloudMonitor Alert Template for All Resources: Select a CloudMonitor alert template. Configure CloudMonitor Alert Template for All Resources: Select a CloudMonitor alert template for each application group. Note This option is available only if application groups are configured. If no alert template is available, create one first. For more information, see Monitoring and alerting overview.
        	Prometheus Service	Specifies whether to enable the Prometheus monitoring feature. If you disable this feature, you do not need to configure the following parameters. For more information, see Configure business monitoring and alerting for a fully managed service deployed in an ACK cluster.
        Log	Application Log	The Logstore information. Click Add a Logstore. In the Add Logstore dialog box, configure the Logstore Name, Path, and File Name parameters. Note If a service is deployed on an ECS instance, you must configure the path and name of the file in a Logstore. If a service is deployed in a pod, you must configure the Logstore information in the environment variables of the pod.
        Modify Configurations	Service Instance Configuration Change	Specifies whether to enable the configuration change feature. If you disable this feature, you do not need to configure the following parameters. Click Add Operation. In the dialog box that appears, configure the configuration change operation. Select Template: the template that is used to implement the configuration change. Note To enable instance type change, you must set the UpdatePolicy property of the ALIYUN::ECS::InstanceGroup resource to ForAllInstances in the template. To enable the update of the ALIYUN::ECS::RunCommand resource, you must set the Syns property to true in the template. The updated ALIYUN::ECS::RunCommand resource is re-executed during the configuration change. Operation Name: the name of the configuration change operation. Operation Description: the description of the configuration change operation. Operation Type: the type of the configuration change operation. Valid values: Upgrade, Downgrade, and Custom. You can select only one operation type. Upgrade: If you select Change Plan as Method, customers can upgrade service instances by changing the current parameter set to a parameter set with a larger serial number. If you select Change Parameter as Method, customers must set parameters of a numeric type to larger values when they upgrade service instances. Custom parameter sets do not support upgrade operations. Downgrade: If you select Change Plan as Method, customers can downgrade service instances by changing the current parameter set to a parameter set with a smaller serial number. If you select Change Parameter as Method, customers must set parameters of a numeric type to smaller values when they downgrade service instances. Custom parameter sets do not support downgrade operations. Custom: No limits are set on the configurations of parameter sets and parameters, and custom parameter sets are supported. Method: the configuration change method. Select Parameters: the parameters that can be modified by customers. This parameter is available only if you select Change Parameter as Method. Parameters that cannot be changed are filtered out.

     4. In the Advanced configuration (optional) section, configure advanced features for the service.

        Parameter		Description
        Permission settings	Deployment link permission	Configure this setting according to your access control requirements. Public: All users with the deployment link can create service instances. Restricted: Only users on the deployment link permission whitelist can access or create service instances. For instructions on adding users to the whitelist, see Modify service deployment permissions. Hidden: Hides the service details page from all users not on the permission list. Unauthorized users who try to access the page receive a "service does not exist" message.
        Network settings	VPC private access	After you enable VPC private access, the service and the service consumer's networks are connected privately, keeping traffic off the public internet. Select the Server Load Balancer or endpoint service you defined in the deployment template.
        	Payer selection	Select the payment method for service resources. You can choose either Service Consumer or Service Provider. The payment feature for the Service Provider is disabled by default. To enable this feature, go to the Quota Center console and apply to enable the payment method for the Service Provider.
        	VPC reverse private access	When enabled, this allows you to access resources within the service consumer's VPC through reverse private access.
        	Reverse endpoint service configuration	Set the region and endpoint service information for the reverse endpoint.
        	Custom domain name	When creating a service instance, users can choose to access your service on a private network through this domain name. The custom domain name should ideally be consistent with your service's public domain name.
        Tenant settings	OAuth authentication	Enable OAuth authentication. Service providers can connect a RAM OAuth application through the Compute Nest console to provide users with a password-free login URL. They can use this URL to log in to the service's software with their Alibaba Cloud account, no password required.
        	Select application	After you enable OAuth authentication, you can select the password-free login URL you want to provide to users from the Select Application drop-down list. If you have not created an application, create and connect one first. For more information, see Configure password-free logon with OAuth.
        	Application login address	Set your application login URL. This URL is displayed on the service instance details page for service consumers.
        Distribution settings	Allow service providers to apply for distribution authorization	When this option is enabled, Compute Nest distributors can request authorization to distribute this service. You will receive notifications to review these requests. If you approve the request, the distributor can re-create and distribute the service. You must settle payments with the distributor separately.
        Instance time settings	Retention period after expiration	Set the retention period for the service instance after it expires, in days.
        Compliance package check	Enable data security risk check within VPC	Checks for potential data security risks within the VPC, such as an ECS instance being migrated out of the VPC or a new, unauthorized ECS instance being added.

Click Create Service, and then click OK in the confirmation dialog box.

In the confirmation prompt, you can click View Service or Test Service Now.

After the service is created, you can view it on the My Services page.

The My Services page has two tabs: Created Services and Used Services. From this page, you can click the Create New Service button or filter services by tag, service name, and type. Created services are displayed as cards. Each card shows the service tag, last updated time, and version information, along with action buttons such as Unpublish Service, Publish to Marketplace, Pre-release, and Edit Version.

Test the service.

After saving the service, you can test it yourself or pre-release it and share it with specific customers for testing. For more information, see Test a service.

Publish the service.

After the service passes testing, submit it for review. Once approved, you can publish it. For more information, see Publish a service.

Deploy a service instance.

A fully managed service instance is an entity that service consumers create from a Compute Nest service. All its resources and software are provided by the service provider. For more information, see Create a fully managed service instance.