To use a stack group template to deploy stacks across different regions within a destination account, you must create stack instances in the stack group. If you specified destination accounts and regions when you created the stack group, Resource Orchestration Service (ROS) automatically creates the stack instances.
Prerequisites
A stack group has been created. For more information, see Step 2: Create a stack group.
Background information
Before you create stack instances, prepare the following accounts:
Management account (Account A): The account used to create stack instances. This must be the same account that was used to create the stack group.
Destination account (Account B): The account where the stacks are deployed.
The administrator account and the execution account can be the same Alibaba Cloud account. For more information about administrator and execution accounts, see Overview.
This topic describes how to use a management account (Account A) to create stack instances and deploy stacks to a destination account (Account B) in the China (Hangzhou) and China (Beijing) regions.
Procedure
Log on to the ROS console using the management account (Account A).
In the navigation pane on the left, click Stack Groups.
In the top menu bar, select the region where the stack group is located.
On the Stack Groups page, click the name of the destination Stack Group.
In the upper-right corner, choose .
On the Deployment Options page, you can set the following parameters and click Next.
Parameter
Description
Accounts
The accounts where you want to deploy stacks.
Select a deployment location and set the accounts as needed.
Deploy Stacks Within Accounts: If you use an Alibaba Cloud account to create stack instances, you can select this option to deploy stacks in other Alibaba Cloud accounts. For example, enter the ID of the destination account (Account B) to deploy stacks in that account.
NoteYou can add multiple accounts. Separate account IDs with commas (,). You can also add the management account (Account A) to deploy stacks in the management account.
Deploy Stacks Within Resource Directories: If you enabled Resource Directory and use its management account to create stack instances, you can select this option. Then, select folders in the resource directory to deploy stacks in all member accounts within the folders.
Regions
The regions where you want to deploy stacks. For example, China (Hangzhou) and China (Beijing).
Maximum Number of Concurrent Accounts- Optional
The maximum number of accounts where stacks can be deployed at the same time in each region.
For more information, see Overview.
Fault Tolerance- Optional
The number of accounts in which stack deployments can fail in each region. If this number is exceeded in a region, ROS stops the operation in that region. If the operation is stopped in one region, it does not continue in other regions.
For more information, see Overview.
Region Concurrency
The concurrency mode for deploying stack instances across regions.
Sequential: Deploys stacks in each specified region in order. Stacks are deployed in only one region at a time.
Parallel: Deploys stacks in all specified regions at the same time.
Expand Modules in Current Account
This parameter takes effect only if the template uses modules. If you expand modules in the current account, the modules must exist in the current account. If you do not expand modules in the current account, the modules must exist in all destination accounts.
On the Specify Override Settings page, select the parameters to override. Change their values using one of the following methods, and then click Next.
Method 1: Choose to reset the parameter values.
Method 2: Choose to enter new values.
NoteAfter the stack instances are created, you can view the new parameter values in the destination account (Account B). On the Stacks page, click the stack ID. The new parameter values are displayed on the Parameters tab.
On the Check and Confirm (Optional) page, confirm the stack instance details and click Add.
Result
After the stack instances are created, go to the Stack Groups page and click the name of the destination stack group. Then, click the Instances tab to view their status in the destination account (Account B).
The instance status is Outdated during stack deployment and automatically changes to Current after the deployment is complete. You can then log on to the ROS console using the destination account (Account B) to view the deployed stacks in the China (Hangzhou) and China (Beijing) regions.