If you want to use the template of an existing stack group to deploy stacks in different regions within specific accounts, you can create stack instances in the stack group. This way, stacks that correspond to the stack instances are automatically deployed in the regions within the accounts. If you specify accounts and regions when you create a stack group, stack instances are automatically created in the regions within the accounts in the Resource Orchestration Service (ROS) console.
Prerequisites
A stack group is created. For more information, see Step 2: Create a stack group.
Background information
Before you create stack instances, make sure that the following accounts are prepared:
Administrator account (Account A): the account within which you want to create stack instances. The account is the one that is used to create the stack group in which the stack instances are to be created.
Execution account (Account B): the account into which you want to deploy stacks in the stack group.
The administrator account and the execution account can be the same Alibaba Cloud account. For more information about administrator and execution accounts, see Terms.
This topic describes how to create stack instances to deploy stacks across regions in the Resource Orchestration Service (ROS) console. In this example, the stack instances are created within Account A. The stacks are deployed within Account B in the China (Hangzhou) and China (Beijing) regions.
Procedure
Log on to the ROS console by using Account A.
In the left-side navigation pane, click Stack Groups.
In the top navigation bar, select the region where the stack group you want to manage resides from the region drop-down list.
On the Stack Groups page, click the name of the stack group.
In the upper-right corner of the page that appears, choose
> Create Stack Instance. In the Set Deployment Options step, configure the following parameters and click Next.
Parameter
Description
Accounts
The accounts within which you want to deploy stacks.
Set the Deployment Locations parameter to one of the following values and enter values in the Accounts field based on your business requirements:
Deploy Stacks Within Accounts: If you use an Alibaba Cloud account to create stack instances, you can select Deploy Stacks Within Accounts. Then, enter the IDs of Alibaba Cloud accounts in the Accounts field. This way, you can deploy stacks within the specified Alibaba Cloud accounts. For example, you can enter the ID of Account B in the Accounts field to deploy stacks within Account B.
NoteIf you enter multiple account IDs, separate the IDs with commas (,). You can also enter the ID of Account A in the Accounts field to deploy stacks within Account A.
Deploy Stacks Within Resource Directories: If you use the management account in an active resource directory to create stack instances, you can select folders in the resource directory and deploy stacks within all members in the folders.
Regions
The regions where you want to deploy stacks. Examples: China (Hangzhou) and China (Beijing).
Maximum Number of Concurrent Accounts
The maximum number of accounts within which stacks are deployed at the same time in each region.
For more information about how to specify the value, see Overview.
Fault Tolerance
The number of accounts within which stack operation failures are allowed in each region. If the value of this parameter is exceeded in a region, ROS stops the operation in the region. If the operation is stopped in one region, the operation is no longer performed in other regions.
For more information about how to specify the value, see Overview.
Region Concurrency
The mode that you want to use to deploy stack instances across regions.
Sequential: deploys stack instances in each specified region based on the specified sequence of regions. ROS deploys stack instances in one region at a time.
Parallel: deploys stack instances in parallel in all specified regions.
Whether to Expand Modules in Current Account
This parameter takes effect only when modules are used in the template. If you want to expand modules within the current account, the modules must exist in the current account. If you want to expand modules within execution accounts, the modules must exist in the execution accounts.
In the Specify Override Settings step, select the parameters that you want to override, use one of the following methods to reset the parameter values, and then click Next.
Method 1: Choose .
Method 2: Choose .
NoteAfter the stack instances are created, you can perform the following operations to view the reset parameter values: Log on to the ROS console by using Account B. On the Stacks page, click the ID of the stack whose reset parameter values you want to view. On the Parameters tab, view the parameter values.
In the Check and Confirm step, verify that the stack instance parameters are valid and click Add.
Check the result
After the stack instances are created, you can perform the following operations to view the status of the stack instances within Account B: On the Stack Groups page, click the name of the stack group in which the stack instances are created. On the Instances tab, view the status of the stack instances.
When the stacks are being deployed, the stack instances are in the Expired state. After the stacks are deployed, the stack instances enter the Current state. In this case, you can log on to the ROS console by using Account B and view the stacks that are deployed in the China (Hangzhou) and China (Beijing) regions.