When a product instance fails to be created after you launch a product, you can troubleshoot the issue based on the causes and solutions described below.
The launch role is not granted the required permissions in the Resource Orchestration Service (ROS) console.
Service Catalog runs Terraform templates by using ROS. You must attach the AliyunROSFullAccess policy to the launch role to grant full permissions on ROS.
The launch role is not granted the required permissions on specific resources.
The launch role must have permissions to create, view, and update the cloud services defined in the Terraform template of the product.
For example, if a product uses a Terraform template that creates Elastic Compute Service (ECS) instances, the administrator must attach the AliyunECSFullAccess policy to the launch role.
The system fails to create a resource.
A resource creation failure during product launch causes the product instance creation to fail. Possible reasons include:
-
The zone of the resource does not match the specified region. For example, if the Terraform template specifies the zone as cn-beijing-h but the end user selects the China (Shanghai) region, instance creation fails. Make sure the region matches the zone specified in the Terraform template.
-
The resources of the specified instance type are insufficient in the selected region. For example, if the specified ECS instance type is unavailable in the China (Shanghai) region, the instance fails to be created. In this case, select another region or change the instance type.
-
A resource attribute does not meet the requirements. For example, if a RAM role name does not comply with the naming conventions or is already in use, instance creation fails. Specify a valid RAM role name that follows the naming conventions.
The number of the product instances exceeds the upper limit.
Each Alibaba Cloud account can have a maximum of 200 product instances in the Service Catalog console. If this limit is reached, delete the product instances that are no longer in use.