Examples of using Stack set in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
AWS CloudFormation starts creating your stack set.
With the stack set selected, choose Delete stack set from the Actions menu.
Prerequisites: Granting Permissions for Stack Set Operations.
When updating a stack set, the user has the choice of specifying a customized administrator role.
At the top of the page, choose StackSets, and then choose Create stack set.
Stack set names must begin with an alphabetical character, and contain only letters, numbers, and hyphens.
Maximum number of stack instances you can create per stack set.
You can update your stack set in either the AWS Management Console, or by using AWS CloudFormation commands in the AWS CLI.
StackSets now supports a maximum of 500 stack instances per stack set.
After you have defined a stack set, you can create, update, or delete stacks in the target accounts and regions you specify.
You can nowcreate up to a maximum of 500 stack instances per stack set.
To learn how to override stack set parameter values when you create stack instances,see Add Stacks to a Stack Set.
AWS CloudFormation stacks created using stack sets now follow a new naming convention,in which the stack name contains the stack set name.
After you have deleted all stack instances, you can delete the stack set.
Delete stacks from your stack set, but save them so they continue to run independently of your stack set by choosing the Retain Stacks option.
For more information about failure tolerance, see Stack set operation options.
Before you can update the stack set, you must fill the check box in the Capabilitiesarea to acknowledge that some of the resources that you are updating with the stack set might require new IAM resources and permissions.
When you are prompted to confirm that you want to delete the stack set, choose Yes, Delete.
Because stack sets perform stack operations across multiple accounts,before you can get started creating your first stack set you need to have the necessary permissions defined in your AWS accounts.
For more information, see Prerequisites: Granting Permissions for Stack Set Operations.
When you are deleting stacks from a stack set, the Retain stacks option lets you choose to remove the stack instances from your stack set, but save the stacks and their associated resources.
A target account is the account into which you create, update, or delete one or more stacks in your stack set.
In general, here's how it works once you have thenecessary permissions in place: When creating a stack set, the user must specify a customized administrator role to associate with the stack set. .
On the Set deployment options page,provide the accounts and regions into which you want stacks in your stack set deployed.
When you create stack sets by using AWS CLI commands, you run two separate commands: create-stack-set to upload your template and create the stack set container,and create-stack-instances to create the stacks within your stack set.
If you have 20 accounts each in two regions, you will have 40 stack instances,and all will be updated when you update the stack set.
In addition, the customizedadministrator role must have a trust relationship with the target accounts specified for the stack set.
This setting, available in delete stack workflows, lets you keep stacks andtheir resources running even after they have been removed from a stack set.
In certain cases, you might want stack instances in certain regions oraccounts to have different property values than those specified in the stack set itself.