<a id="cli-aws-cloudformation-describe-stack-set-operation"></a>

# describe-stack-set-operation

## Description

Returns the description of the specified StackSet operation.

Reports role provisioning and stack instances deployment progress in `StatusDetails.Stages` . A breakdown for each Amazon Web Services Region is available in `RegionalStatusDetails` .

#### NOTE
This API provides *strongly consistent* reads meaning it will always return the most up-to-date data.

See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/cloudformation-2010-05-15/DescribeStackSetOperation)

## Synopsis

```
  describe-stack-set-operation
--stack-set-name <value>
--operation-id <value>
[--call-as <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
[--debug]
[--endpoint-url <value>]
[--no-verify-ssl]
[--no-paginate]
[--output <value>]
[--query <value>]
[--profile <value>]
[--region <value>]
[--version <value>]
[--color <value>]
[--no-sign-request]
[--ca-bundle <value>]
[--cli-read-timeout <value>]
[--cli-connect-timeout <value>]
[--cli-binary-format <value>]
[--no-cli-pager]
[--cli-auto-prompt]
[--no-cli-auto-prompt]
[--cli-error-format <value>]
[--help]
```

## Options

`--stack-set-name` (string) [required]

> The name or the unique stack ID of the StackSet for the stack operation.

`--operation-id` (string) [required]

> The unique ID of the StackSet operation.

> Constraints:

> * min: `1`
> * max: `128`
> * pattern: `[a-zA-Z0-9][-a-zA-Z0-9]*`

`--call-as` (string)

> [Service-managed permissions] Specifies whether you are acting as an account administrator in the organization’s management account or as a delegated administrator in a member account.

> By default, `SELF` is specified. Use `SELF` for StackSets with self-managed permissions.

> * If you are signed in to the management account, specify `SELF` .
> * If you are signed in to a delegated administrator account, specify `DELEGATED_ADMIN` . Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see [Register a delegated administrator](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html) in the *CloudFormation User Guide* .

> Possible values:

> * `SELF`
> * `DELEGATED_ADMIN`

`--cli-input-json` | `--cli-input-yaml` (string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by `--generate-cli-skeleton`. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with `--cli-input-yaml`.

`--generate-cli-skeleton` (string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value `input`, prints a sample input JSON that can be used as an argument for `--cli-input-json`. Similarly, if provided `yaml-input` it will print a sample input YAML that can be used with `--cli-input-yaml`. If provided with the value `output`, it validates the command inputs and returns a sample output JSON for that command. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated.

## Global Options

`--debug` (boolean)

Turn on debug logging.

`--endpoint-url` (string)

Override command’s default URL with the given URL.

`--no-verify-ssl` (boolean)

By default, the AWS CLI uses SSL when communicating with AWS services. For each SSL connection, the AWS CLI will verify SSL certificates. This option overrides the default behavior of verifying SSL certificates.

`--no-paginate` (boolean)

Disable automatic pagination. If automatic pagination is disabled, the AWS CLI will only make one call, for the first page of results.

`--output` (string)

The formatting style for command output.

* json
* text
* table
* yaml
* yaml-stream
* off

`--query` (string)

A JMESPath query to use in filtering the response data.

`--profile` (string)

Use a specific profile from your credential file.

`--region` (string)

The region to use. Overrides config/env settings.

`--version` (string)

Display the version of this tool.

`--color` (string)

Turn on/off color output.

* on
* off
* auto

`--no-sign-request` (boolean)

Do not sign requests. Credentials will not be loaded if this argument is provided.

`--ca-bundle` (string)

The CA certificate bundle to use when verifying SSL certificates. Overrides config/env settings.

`--cli-read-timeout` (int)

The maximum socket read time in seconds. If the value is set to 0, the socket read will be blocking and not timeout. The default value is 60 seconds.

`--cli-connect-timeout` (int)

The maximum socket connect time in seconds. If the value is set to 0, the socket connect will be blocking and not timeout. The default value is 60 seconds.

`--cli-binary-format` (string)

The formatting style to be used for binary blobs. The default format is base64. The base64 format expects binary blobs to be provided as a base64 encoded string. The raw-in-base64-out format preserves compatibility with AWS CLI V1 behavior and binary values must be passed literally. When providing contents from a file that map to a binary blob `fileb://` will always be treated as binary and use the file contents directly regardless of the `cli-binary-format` setting. When using `file://` the file contents will need to properly formatted for the configured `cli-binary-format`.

* base64
* raw-in-base64-out

`--no-cli-pager` (boolean)

Disable cli pager for output.

`--cli-auto-prompt` (boolean)

Automatically prompt for CLI input parameters.

`--no-cli-auto-prompt` (boolean)

Disable automatically prompt for CLI input parameters.

`--cli-error-format` (string)

The formatting style for error output. By default, errors are displayed in enhanced format.

* legacy
* json
* yaml
* text
* table
* enhanced

`--help` (boolean)

Display help for the command/subcommand.

## Examples

#### NOTE
To use the following examples, you must have the AWS CLI installed and configured. See the [Getting started guide](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) in the *AWS CLI User Guide* for more information.

Unless otherwise stated, all examples have unix-like quotation rules. These examples will need to be adapted to your terminal’s quoting rules. See [Using quotation marks with strings](https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters-quoting-strings.html) in the *AWS CLI User Guide* .

**To get information about a stack set operation**

The following `describe-stack-set-operation` example displays details for an update operation on the specified stack set.

```bash
aws cloudformation describe-stack-set-operation \
    --stack-set-name enable-config \
    --operation-id a1b2c3d4-5678-90ab-cdef-EXAMPLE11111
```

Output:

```json
{
    "StackSetOperation": {
        "OperationId": "a1b2c3d4-5678-90ab-cdef-EXAMPLE11111",
        "StackSetId": "enable-config:a1b2c3d4-5678-90ab-cdef-EXAMPLE22222",
        "Action": "UPDATE",
        "Status": "SUCCEEDED",
        "OperationPreferences": {
            "RegionOrder": [
                "us-east-1",
                "us-west-2",
                "eu-west-1",
                "us-west-1"
            ],
            "FailureToleranceCount": 7,
            "MaxConcurrentCount": 2
        },
        "AdministrationRoleARN": "arn:aws:iam::123456789012:role/AWSCloudFormationStackSetAdministrationRole",
        "ExecutionRoleName": "AWSCloudFormationStackSetExecutionRole",
        "CreationTimestamp": "2019-10-03T16:28:44.377Z",
        "EndTimestamp": "2019-10-03T16:42:08.607Z"
    }
}
```

For more information, see [StackSets concepts](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html) in the *AWS CloudFormation User Guide*.

## Output

StackSetOperation -> (structure)

> The specified StackSet operation.

> OperationId -> (string)

> > The unique ID of a StackSet operation.

> > Constraints:

> > * min: `1`
> > * max: `128`
> > * pattern: `[a-zA-Z0-9][-a-zA-Z0-9]*`

> StackSetId -> (string)

> > The ID of the StackSet.

> Action -> (string)

> > The type of StackSet operation: `CREATE` , `UPDATE` , or `DELETE` . Create and delete operations affect only the specified stack instances that are associated with the specified StackSet. Update operations affect both the StackSet itself, in addition to *all* associated stack instances.

> > Possible values:

> > * `CREATE`
> > * `UPDATE`
> > * `DELETE`
> > * `DETECT_DRIFT`

> Status -> (string)

> > The status of the operation.

> > * `FAILED` : The operation exceeded the specified failure tolerance. The failure tolerance value that you’ve set for an operation is applied for each Region during stack create and update operations. If the number of failed stacks within a Region exceeds the failure tolerance, the status of the operation in the Region is set to `FAILED` . This in turn sets the status of the operation as a whole to `FAILED` , and CloudFormation cancels the operation in any remaining Regions.
> > * `QUEUED` : [Service-managed permissions] For automatic deployments that require a sequence of operations, the operation is queued to be performed. For more information, see the [StackSets status codes](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html#stackset-status-codes) in the *CloudFormation User Guide* .
> > * `RUNNING` : The operation is currently being performed.
> > * `STOPPED` : The user has canceled the operation.
> > * `STOPPING` : The operation is in the process of stopping, at user request.
> > * `SUCCEEDED` : The operation completed creating or updating all the specified stacks without exceeding the failure tolerance for the operation.

> > Possible values:

> > * `RUNNING`
> > * `SUCCEEDED`
> > * `FAILED`
> > * `STOPPING`
> > * `STOPPED`
> > * `QUEUED`

> OperationPreferences -> (structure)

> > The preferences for how CloudFormation performs this StackSet operation.

> > RegionConcurrencyType -> (string)

> > > The concurrency type of deploying StackSets operations in Regions, could be in parallel or one Region at a time.

> > > Possible values:

> > > * `SEQUENTIAL`
> > > * `PARALLEL`

> > RegionOrder -> (list)

> > > The order of the Regions where you want to perform the stack operation.

> > > (string)

> > > > Constraints:

> > > > * pattern: `^[a-zA-Z0-9-]{1,128}$`

> > FailureToleranceCount -> (integer)

> > > The number of accounts per Region this operation can fail in before CloudFormation stops the operation in that Region. If the operation is stopped in a Region, CloudFormation doesn’t attempt the operation in any subsequent Regions.

> > > You can specify either `FailureToleranceCount` or `FailureTolerancePercentage` , but not both.

> > > By default, `0` is specified.

> > > Constraints:

> > > * min: `0`

> > FailureTolerancePercentage -> (integer)

> > > The percentage of accounts per Region this stack operation can fail in before CloudFormation stops the operation in that Region. If the operation is stopped in a Region, CloudFormation doesn’t attempt the operation in any subsequent Regions.

> > > When calculating the number of accounts based on the specified percentage, CloudFormation rounds *down* to the next whole number.

> > > You can specify either `FailureToleranceCount` or `FailureTolerancePercentage` , but not both.

> > > By default, `0` is specified.

> > > Constraints:

> > > * min: `0`
> > > * max: `100`

> > MaxConcurrentCount -> (integer)

> > > The maximum number of accounts in which to perform this operation at one time. This can depend on the value of `FailureToleranceCount` depending on your `ConcurrencyMode` . `MaxConcurrentCount` is at most one more than the `FailureToleranceCount` if you’re using `STRICT_FAILURE_TOLERANCE` .

> > > Note that this setting lets you specify the *maximum* for operations. For large deployments, under certain circumstances the actual number of accounts acted upon concurrently may be lower due to service throttling.

> > > You can specify either `MaxConcurrentCount` or `MaxConcurrentPercentage` , but not both.

> > > By default, `1` is specified.

> > > Constraints:

> > > * min: `1`

> > MaxConcurrentPercentage -> (integer)

> > > The maximum percentage of accounts in which to perform this operation at one time.

> > > When calculating the number of accounts based on the specified percentage, CloudFormation rounds down to the next whole number. This is true except in cases where rounding down would result is zero. In this case, CloudFormation sets the number as one instead.

> > > Note that this setting lets you specify the *maximum* for operations. For large deployments, under certain circumstances the actual number of accounts acted upon concurrently may be lower due to service throttling.

> > > You can specify either `MaxConcurrentCount` or `MaxConcurrentPercentage` , but not both.

> > > By default, `1` is specified.

> > > Constraints:

> > > * min: `1`
> > > * max: `100`

> > ConcurrencyMode -> (string)

> > > Specifies how the concurrency level behaves during the operation execution.

> > > * `STRICT_FAILURE_TOLERANCE` : This option dynamically lowers the concurrency level to ensure the number of failed accounts never exceeds the value of `FailureToleranceCount` +1. The initial actual concurrency is set to the lower of either the value of the `MaxConcurrentCount` , or the value of `FailureToleranceCount` +1. The actual concurrency is then reduced proportionally by the number of failures. This is the default behavior. If failure tolerance or Maximum concurrent accounts are set to percentages, the behavior is similar.
> > > * `SOFT_FAILURE_TOLERANCE` : This option decouples `FailureToleranceCount` from the actual concurrency. This allows StackSet operations to run at the concurrency level set by the `MaxConcurrentCount` value, or `MaxConcurrentPercentage` , regardless of the number of failures.

> > > Possible values:

> > > * `STRICT_FAILURE_TOLERANCE`
> > > * `SOFT_FAILURE_TOLERANCE`

> RetainStacks -> (boolean)

> > For StackSet operations of action type `DELETE` , specifies whether to remove the stack instances from the specified StackSet, but doesn’t delete the stacks. You can’t re-associate a retained stack, or add an existing, saved stack to a new StackSet.

> AdministrationRoleARN -> (string)

> > The Amazon Resource Name (ARN) of the IAM role used to perform this StackSet operation.

> > Use customized administrator roles to control which users or groups can manage specific StackSets within the same administrator account. For more information, see [Grant self-managed permissions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs-self-managed.html) in the *CloudFormation User Guide* .

> > Constraints:

> > * min: `20`
> > * max: `2048`

> ExecutionRoleName -> (string)

> > The name of the IAM execution role used to create or update the StackSet.

> > Use customized execution roles to control which stack resources users and groups can include in their StackSets.

> > Constraints:

> > * min: `1`
> > * max: `64`
> > * pattern: `[a-zA-Z_0-9+=,.@-]+`

> CreationTimestamp -> (timestamp)

> > The time at which the operation was initiated. Note that the creation times for the stack set operation might differ from the creation time of the individual stacks themselves. This is because CloudFormation needs to perform preparatory work for the operation, such as dispatching the work to the requested Regions, before actually creating the first stacks.

> EndTimestamp -> (timestamp)

> > The time at which the StackSet operation ended, across all accounts and Regions specified. Note that this doesn’t necessarily mean that the StackSet operation was successful, or even attempted, in each account or Region.

> DeploymentTargets -> (structure)

> > The Organizations accounts affected by the stack operation. Valid only if the StackSet uses service-managed permissions.

> > Accounts -> (list)

> > > The Amazon Web Services account IDs where you want to perform stack operations. How these accounts are used depends on the `AccountFilterType` property.

> > > If you have many account numbers, you can provide those accounts using the `AccountsUrl` property instead.

> > > (string)

> > > > Constraints:

> > > > * pattern: `^[0-9]{12}$`

> > AccountsUrl -> (string)

> > > The Amazon S3 URL path to a file that contains a list of Amazon Web Services account IDs. The file format must be either `.csv` or `.txt` , and the data can be comma-separated or new-line-separated. There is currently a 10MB limit for the data (approximately 800,000 accounts).

> > > This property serves the same purpose as `Accounts` but allows you to specify a large number of accounts.

> > > Constraints:

> > > * min: `1`
> > > * max: `5120`
> > > * pattern: `(s3://|http(s?)://).+`

> > OrganizationalUnitIds -> (list)

> > > The organization root ID or organizational unit (OU) IDs where you want to perform stack operations. CloudFormation will perform operations on accounts within these OUs and their child OUs.

> > > (string)

> > > > Constraints:

> > > > * pattern: `^(ou-[a-z0-9]{4,32}-[a-z0-9]{8,32}|r-[a-z0-9]{4,32})$`

> > AccountFilterType -> (string)

> > > Refines which accounts will have stack operations performed on them by specifying how to use the `Accounts` and `OrganizationalUnitIds` properties together.

> > > The following values determine how CloudFormation selects target accounts:

> > > * `INTERSECTION` : Performs stack operations only on specific individual accounts within the selected OUs. Only accounts that are both specified in the `Accounts` property and belong to the specified OUs will be targeted.
> > > * `DIFFERENCE` : Performs stack operations on all accounts in the selected OUs except for specific accounts listed in the `Accounts` property. This enables you to exclude certain accounts within an OU, such as suspended accounts.
> > > * `UNION` : Performs stack operations on the specified OUs plus additional individual accounts listed in the `Accounts` property. This is the default value if `AccountFilterType` is not provided. This lets you target an entire OU and individual accounts from a different OU in one request. Note that `UNION` is not supported for `CreateStackInstances` operations.
> > > * `NONE` : Performs stack operations on all accounts in the specified organizational units (OUs).

> > > Possible values:

> > > * `NONE`
> > > * `INTERSECTION`
> > > * `DIFFERENCE`
> > > * `UNION`

> StackSetDriftDetectionDetails -> (structure)

> > Detailed information about the drift status of the StackSet. This includes information about drift operations currently being performed on the StackSet.

> > This information will only be present for StackSet operations whose `Action` type is `DETECT_DRIFT` .

> > For more information, see [Performing drift detection on CloudFormation StackSets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-drift.html) in the *CloudFormation User Guide* .

> > DriftStatus -> (string)

> > > Status of the StackSet’s actual configuration compared to its expected template and parameter configuration.

> > > * `DRIFTED` : One or more of the stack instances belonging to the StackSet differs from the expected template and parameter configuration. A stack instance is considered to have drifted if one or more of the resources in the associated stack have drifted.
> > > * `NOT_CHECKED` : CloudFormation hasn’t checked the StackSet for drift.
> > > * `IN_SYNC` : All of the stack instances belonging to the StackSet stack match the expected template and parameter configuration.

> > > Possible values:

> > > * `DRIFTED`
> > > * `IN_SYNC`
> > > * `NOT_CHECKED`

> > DriftDetectionStatus -> (string)

> > > The status of the StackSet drift detection operation.

> > > * `COMPLETED` : The drift detection operation completed without failing on any stack instances.
> > > * `FAILED` : The drift detection operation exceeded the specified failure tolerance.
> > > * `PARTIAL_SUCCESS` : The drift detection operation completed without exceeding the failure tolerance for the operation.
> > > * `IN_PROGRESS` : The drift detection operation is currently being performed.
> > > * `STOPPED` : The user has canceled the drift detection operation.

> > > Possible values:

> > > * `COMPLETED`
> > > * `FAILED`
> > > * `PARTIAL_SUCCESS`
> > > * `IN_PROGRESS`
> > > * `STOPPED`

> > LastDriftCheckTimestamp -> (timestamp)

> > > Most recent time when CloudFormation performed a drift detection operation on the StackSet. This value will be `NULL` for any StackSet that drift detection hasn’t yet been performed on.

> > TotalStackInstancesCount -> (integer)

> > > The total number of stack instances belonging to this StackSet.

> > > The total number of stack instances is equal to the total of:

> > > * Stack instances that match the StackSet configuration.
> > > * Stack instances that have drifted from the StackSet configuration.
> > > * Stack instances where the drift detection operation has failed.
> > > * Stack instances currently being checked for drift.

> > > Constraints:

> > > * min: `0`

> > DriftedStackInstancesCount -> (integer)

> > > The number of stack instances that have drifted from the expected template and parameter configuration of the StackSet. A stack instance is considered to have drifted if one or more of the resources in the associated stack don’t match their expected configuration.

> > > Constraints:

> > > * min: `0`

> > InSyncStackInstancesCount -> (integer)

> > > The number of stack instances which match the expected template and parameter configuration of the StackSet.

> > > Constraints:

> > > * min: `0`

> > InProgressStackInstancesCount -> (integer)

> > > The number of stack instances that are currently being checked for drift.

> > > Constraints:

> > > * min: `0`

> > FailedStackInstancesCount -> (integer)

> > > The number of stack instances for which the drift detection operation failed.

> > > Constraints:

> > > * min: `0`

> StatusReason -> (string)

> > The status of the operation in details.

> StatusDetails -> (structure)

> > Detailed information about the StackSet operation.

> > Stages -> (structure)

> > > The detailed progress information for the individual stages of the StackSet operation: the role provisioning stage and the stack instances deployment stage.

> > > RoleProvisioning -> (structure)

> > > > The progress detail for the role provisioning stage. For operations that do not provision roles, this stage is present with a `Status` of `NOT_APPLICABLE` .

> > > > Status -> (string)

> > > > > The status of the role provisioning stage can be one of the following values:

> > > > > * `NOT_APPLICABLE` : The operation does not provision roles. This includes self-managed operations and service-managed operations whose configuration does not require role provisioning.
> > > > > * `NOT_STARTED` : Role provisioning has not started. The operation has not begun resolving target accounts, or it failed or stopped before the total number of target accounts was resolved.
> > > > > * `IN_PROGRESS` : Role provisioning is actively processing target accounts.
> > > > > * `SUCCEEDED` : Role provisioning finished and succeeded for all target accounts.
> > > > > * `PARTIAL_SUCCESS` : Role provisioning finished, but succeeded for only a subset of target accounts; one or more accounts failed.
> > > > > * `FAILED` : Role provisioning finished and failed for all target accounts.

> > > > > Possible values:

> > > > > * `PENDING`
> > > > > * `NOT_APPLICABLE`
> > > > > * `NOT_STARTED`
> > > > > * `IN_PROGRESS`
> > > > > * `SUCCEEDED`
> > > > > * `PARTIAL_SUCCESS`
> > > > > * `FAILED`

> > > > SucceededAccountsCount -> (integer)

> > > > > The number of accounts for which role provisioning succeeded.

> > > > > Constraints:

> > > > > * min: `0`

> > > > FailedAccountsCount -> (integer)

> > > > > The number of accounts for which role provisioning failed.

> > > > > Constraints:

> > > > > * min: `0`

> > > > CompletedAccountsCount -> (integer)

> > > > > The number of accounts that have finished role provisioning, including both succeeded and failed accounts.

> > > > > Constraints:

> > > > > * min: `0`

> > > > PendingAccountsCount -> (integer)

> > > > > The number of accounts that are still awaiting role provisioning.

> > > > > Constraints:

> > > > > * min: `0`

> > > > PercentageCompleted -> (double)

> > > > > The percentage of accounts that have completed role provisioning.

> > > > > Constraints:

> > > > > * min: `0`
> > > > > * max: `100`

> > > StackInstancesDeployment -> (structure)

> > > > The progress detail for the stack instances deployment stage. This stage reports the deployment of stack instances to the target accounts and Amazon Web Services Regions, after any role provisioning has finished.

> > > > Status -> (string)

> > > > > The status of the stack instances deployment stage can be one of the following values:

> > > > > * `NOT_APPLICABLE` : The operation does not deploy stack instances, such as a drift detection operation.
> > > > > * `NOT_STARTED` : Stack instances deployment has not started. The operation is still provisioning roles, has not begun, or failed before this stage was reached.
> > > > > * `IN_PROGRESS` : At least one stack instance has started deploying.
> > > > > * `SUCCEEDED` : Deployment finished and succeeded for all stack instances that were not skipped.
> > > > > * `PARTIAL_SUCCESS` : Deployment finished with a mix of succeeded, failed, and canceled stack instances.
> > > > > * `FAILED` : Deployment finished and every stack instance that was not skipped failed or was canceled.

> > > > > Possible values:

> > > > > * `PENDING`
> > > > > * `NOT_APPLICABLE`
> > > > > * `NOT_STARTED`
> > > > > * `IN_PROGRESS`
> > > > > * `SUCCEEDED`
> > > > > * `PARTIAL_SUCCESS`
> > > > > * `FAILED`

> > > > SucceededStackInstancesCount -> (integer)

> > > > > The number of stack instances that deployed successfully.

> > > > > Constraints:

> > > > > * min: `0`

> > > > FailedStackInstancesCount -> (integer)

> > > > > The number of stack instances that failed to deploy.

> > > > > Constraints:

> > > > > * min: `0`

> > > > CompletedStackInstancesCount -> (integer)

> > > > > The number of stack instances that have reached a final state. This count includes stack instances that succeeded, failed, were skipped, or were canceled.

> > > > > Constraints:

> > > > > * min: `0`

> > > > PendingStackInstancesCount -> (integer)

> > > > > The number of stack instances that have not reached a final state. This is the total number of stack instances minus the completed count.

> > > > > Constraints:

> > > > > * min: `0`

> > > > CancelledStackInstancesCount -> (integer)

> > > > > The number of stack instances that were canceled because the operation exceeded its failure tolerance or was stopped.

> > > > > Constraints:

> > > > > * min: `0`

> > > > SkippedStackInstancesCount -> (integer)

> > > > > The number of stack instances that were skipped because role provisioning failed for their target account.

> > > > > Constraints:

> > > > > * min: `0`

> > > > PercentageCompleted -> (double)

> > > > > The percentage of stack instances that have reached a final state.

> > > > > Constraints:

> > > > > * min: `0`
> > > > > * max: `100`

> > TotalAccountsCount -> (integer)

> > > The total number of accounts targeted by this StackSet operation. Self-managed operations and service-managed operations that do not provision roles also report this value when it is known. CloudFormation populates this value after it resolves the target accounts. Until then, this field is not present.

> > > Constraints:

> > > * min: `0`

> > TotalStackInstancesCount -> (integer)

> > > The total number of stack instances targeted by this StackSet operation. CloudFormation populates this value after it resolves the target stack instances. Until then, this field is not present.

> > > Constraints:

> > > * min: `0`

> > FailedStackInstancesCount -> (integer)

> > > The number of stack instances for which the StackSet operation failed.

> > > Constraints:

> > > * min: `0`

> RegionalStatusDetails -> (map)

> > The progress detail for each Region of the operation, keyed by Region. Each entry reports the stack instances deployment progress for that Region. This field is returned only by  DescribeStackSetOperation . It is not included in the  ListStackSetOperations summary.

> > key -> (string)

> > > Constraints:

> > > * pattern: `^[a-zA-Z0-9-]{1,128}$`

> > value -> (structure)

> > > Contains the progress detail for a single Region of a StackSet operation. This information is returned only by  DescribeStackSetOperation .

> > > Stages -> (structure)

> > > > The progress information for the individual stages of the operation in this Region.

> > > > RegionalStackInstancesDeployment -> (structure)

> > > > > The progress detail for the stack instances deployment stage in this Region.

> > > > > Status -> (string)

> > > > > > The status of the stack instances deployment stage can be one of the following values:

> > > > > > * `NOT_APPLICABLE` : The operation does not deploy stack instances, such as a drift detection operation.
> > > > > > * `NOT_STARTED` : Stack instances deployment has not started. The operation is still provisioning roles, has not begun, or failed before this stage was reached.
> > > > > > * `IN_PROGRESS` : At least one stack instance has started deploying.
> > > > > > * `SUCCEEDED` : Deployment finished and succeeded for all stack instances that were not skipped.
> > > > > > * `PARTIAL_SUCCESS` : Deployment finished with a mix of succeeded, failed, and canceled stack instances.
> > > > > > * `FAILED` : Deployment finished and every stack instance that was not skipped failed or was canceled.

> > > > > > Possible values:

> > > > > > * `PENDING`
> > > > > > * `NOT_APPLICABLE`
> > > > > > * `NOT_STARTED`
> > > > > > * `IN_PROGRESS`
> > > > > > * `SUCCEEDED`
> > > > > > * `PARTIAL_SUCCESS`
> > > > > > * `FAILED`

> > > > > SucceededStackInstancesCount -> (integer)

> > > > > > The number of stack instances that deployed successfully in this Region.

> > > > > > Constraints:

> > > > > > * min: `0`

> > > > > FailedStackInstancesCount -> (integer)

> > > > > > The number of stack instances that failed to deploy in this Region.

> > > > > > Constraints:

> > > > > > * min: `0`

> > > > > CompletedStackInstancesCount -> (integer)

> > > > > > The number of stack instances in this Region that have reached a final state. This count includes stack instances that succeeded, failed, were skipped, or were canceled.

> > > > > > Constraints:

> > > > > > * min: `0`

> > > > > PendingStackInstancesCount -> (integer)

> > > > > > The number of stack instances in this Region that have not reached a final state. This is the total number of stack instances in this Region minus the completed count.

> > > > > > Constraints:

> > > > > > * min: `0`

> > > > > CancelledStackInstancesCount -> (integer)

> > > > > > The number of stack instances in this Region that were canceled because the operation exceeded its failure tolerance or was stopped.

> > > > > > Constraints:

> > > > > > * min: `0`

> > > > > SkippedStackInstancesCount -> (integer)

> > > > > > The number of stack instances in this Region that were skipped because role provisioning failed for their target account.

> > > > > > Constraints:

> > > > > > * min: `0`

> > > > > TotalStackInstancesCount -> (integer)

> > > > > > The total number of stack instances targeted by this operation in this Region.

> > > > > > Constraints:

> > > > > > * min: `0`

> > > > > PercentageCompleted -> (double)

> > > > > > The percentage of stack instances in this Region that have reached a final state.

> > > > > > Constraints:

> > > > > > * min: `0`
> > > > > > * max: `100`
