AWS CloudFormation StackSets improves insights on stack instances for stack set operations

Today, AWS CloudFormation StackSets improves access to detailed information on stack instances for stack set operations. You can get the count of failed stack instances for stack set operations in DescribeStackSetOperation. Additionally, you can list and filter stack instances for stack set operations in ListStackInstances.

Customers use CloudFormation StackSets to provision and manage stacks in multiple AWS accounts and Regions in a single operation. However, a stack set does not provision and update stack instances to AWS accounts in cases where accounts have same resources, accounts have missing IAM role dependencies, and more. Customers want to know the AWS accounts in which StackSets did not provision and update stack instances, so they can re-deploy stack instances to these missed AWS accounts. Previously, customers had to wait for StackSets to complete operation before estimating the AWS accounts that need re-deployment. With this launch, customers can use DescribeStackSetOperation during a stack set deployment to get the count of failed stack instances. Customers can also use the new filtering option LastOperationID in ListStackInstances to list stack instances for a given stack set operation. For example, you can combine the status, region, and last operation ID filters in ListStackInstances to list all failed stack instances in us-east-1 and eu-west-2 for a particular operation. Customers can use this information to redeploy stack instances to missed AWS accounts.

You can use these features via AWS Management Console, AWS Command Line Interface, and AWS Software Development Kit. These features are available in all AWS Regions where StackSets is available. To learn more about these features, visit CloudFormation StackSets documentation.