Resource Orchestration Service:Why a stack fails to be created?

This topic describes the causes why a Resource Orchestration Service (ROS) stack fails to be created.

Name duplication

Stacks that you create must have unique names.

Invalid name format

The name of a stack can contain only letters and digits. The name cannot start with a digit.

Resource creation failure

If a resource in a stack fails to be created, the stack also fails to be created. For example, if an Elastic Compute Service (ECS) resource in a stack fails to be created due to insufficient memory in a specified region, the stack also fails to be created.

Quantity limit reached

You can create up to 200 stacks in ROS. For more information, see Limits.