This topic provides answers to frequently asked questions (FAQ) about SaaS Boost.
Q1: What do I do if I associate an invalid URL or a product code with SaaS Boost?
If you enter an invalid URL of a SaaS Boost service instance or an invalid SaaS Boost product code, the system reports an error. error code:SaasBoostCommodityNotFound
In this case, you need to associate a valid code of the SaaS Boost product or a valid URL of the SaaS Boost service instance. Make sure that no spaces are contained in the code or URL.
The URL of the SaaS Boost service instance must be the same as the value of the SaaS Boost public network address parameter displayed on the Overview tab of the service instance details page.
Q2: What do I do if a task fails in the pipeline branch manager after I deploy a service instance?
The following error log is reported: failed: The TLS connection was non-properly terminated.
GitHub is frequently accessed during peak hours. Therefore, GitHub connection failures often occur. In this case, click Retry and wait until GitHub returns a response.
Q3: What do I do if a pipeline does not run as expected after I deploy a service instance?
The pipeline includes the npm project creation and Java project creation steps. After the projects are created, the JAR package of Function Compute is uploaded to an Object Storage Service (OSS) bucket. The JAR package of the server is uploaded to the deployment package repository of Compute Nest. Then, the server and Function Compute are deployed.
Function Compute is deployed by replacing the ZIP package in OSS.
The server is deployed by executing the deploy.sh script in the current project.
After you are familiar with the overall steps contained in the pipeline, you can troubleshoot common errors that occur during the development based on the error logs reported by the pipeline.
If you cannot troubleshoot the errors in the cloud, you can clone the error environment to your on-premises environment.
Q4: What do I do if a service instance fails to be deployed?
Service instances may fail to be deployed in the following cases:
The customer who creates the service instance has insufficient permissions.
If you create the service instance as a Resource Access Management (RAM) user, you must grant permissions on the resources described in the following table to the RAM user. For more information about how to grant permissions to a RAM user, see Grant permissions to a RAM user.
Required permissions on cloud resources
Policy
Permission
AliyunECSFullAccess
The full permissions on Elastic Compute Service (ECS).
AliyunVPCFullAccess
The full permissions on Virtual Private Cloud (VPC).
AliyunROSFullAccess
The full permissions on Resource Orchestration Service (ROS).
AliyunCloudMonitorFullAccess
The full permissions on CloudMonitor.
AliyunOSSFullAccess
The full permissions on OSS.
AliyunOOSFullAccess
The full permissions on CloudOps Orchestration Service (OOS).
AliyunFCFullAccess
The full permissions on Function Compute.
AliyunOTSFullAccess
The full permissions on Tablestore.
AliyunComputeNestSupplierFullAccess
The full service provider permissions on Compute Nest.
The selected ECS instance is unavailable in the current zone. Select an available ECS instance and try again later.
A plug-in is not installed in the Container Service for Kubernetes (ACK) cluster.
Install the ack-pod-identity-webhook plug-in in the ACK cluster.
You can view more detailed information on the Logs tab of the Service Instance Details page.
Q5: How do I map a domain name?
Configure a reverse proxy
You can map a domain name by using a reverse proxy server, such as NGINX, Apache, HAProxy, or Traefik. You can configure a reverse proxy on the server that uses Domain name B to forward requests from Domain name B to the port that is mapped to Domain name A.
Configure an SLB instance
You can map a domain name by configuring the Server Load Balancer (SLB) instance that uses ECS instances as backend servers. The SLB instance forwards requests from Domain name B to the backend server and port that is mapped to Domain name A. To implement this feature, you can configure the related settings on the Instances page in the SLB console.