For a specified stack that’s in the
UPDATE_ROLLBACK_FAILED state, continues rolling it back to the
UPDATE_ROLLBACK_COMPLETE state. Depending on the cause of the failure, you can manually fix the error and continue the rollback. By continuing the rollback, you can return your stack to a working state (the
UPDATE_ROLLBACK_COMPLETE state), and then try to update the stack again.
A stack goes into the
UPDATE_ROLLBACK_FAILED state when CloudFormation can’t roll back all changes after a failed stack update. For example, you might have a stack that’s rolling back to an old database instance that was deleted outside of CloudFormation. Because CloudFormation doesn’t know the database was deleted, it assumes that the database instance still exists and attempts to roll back to it, causing the update rollback to fail.
See also: AWS API Documentation
See ‘aws help’ for descriptions of global parameters.
continue-update-rollback --stack-name <value> [--role-arn <value>] [--resources-to-skip <value>] [--client-request-token <value>] [--cli-input-json | --cli-input-yaml] [--generate-cli-skeleton <value>]
The name or the unique ID of the stack that you want to continue rolling back.
Don’t specify the name of a nested stack (a stack that was created by using the
AWS::CloudFormation::Stackresource). Instead, use this operation on the parent stack (the stack that contains the
The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) role that CloudFormation assumes to roll back the stack. CloudFormation uses the role’s credentials to make calls on your behalf. CloudFormation always uses this role for all future operations on the stack. Provided that users have permission to operate on the stack, CloudFormation uses this role even if the users don’t have permission to pass it. Ensure that the role grants least permission.
If you don’t specify a value, CloudFormation uses the role that was previously associated with the stack. If no role is available, CloudFormation uses a temporary session that’s generated from your user credentials.
A list of the logical IDs of the resources that CloudFormation skips during the continue update rollback operation. You can specify only resources that are in the
UPDATE_FAILEDstate because a rollback failed. You can’t specify resources that are in the
UPDATE_FAILEDstate for other reasons, for example, because an update was canceled. To check why a resource update failed, use the DescribeStackResources action, and view the resource status reason.
Specify this property to skip rolling back resources that CloudFormation can’t successfully roll back. We recommend that you troubleshoot resources before skipping them. CloudFormation sets the status of the specified resources to
UPDATE_COMPLETEand continues to roll back the stack. After the rollback is complete, the state of the skipped resources will be inconsistent with the state of the resources in the stack template. Before performing another stack update, you must update the stack or resources to be consistent with each other. If you don’t, subsequent stack updates might fail, and the stack will become unrecoverable.
Specify the minimum number of resources required to successfully roll back your stack. For example, a failed resource update might cause dependent resources to fail. In this case, it might not be necessary to skip the dependent resources.
To skip resources that are part of nested stacks, use the following format:
NestedStackName.ResourceLogicalID. If you want to specify the logical ID of a stack resource (
Type: AWS::CloudFormation::Stack) in the
ResourcesToSkiplist, then its corresponding embedded stack must be in one of the following states:
Don’t confuse a child stack’s name with its corresponding logical ID defined in the parent stack. For an example of a continue update rollback operation with nested stacks, see Using ResourcesToSkip to recover a nested stacks hierarchy .
"string" "string" ...
A unique identifier for this
ContinueUpdateRollbackrequest. Specify this token if you plan to retry requests so that CloudFormationknows that you’re not attempting to continue the rollback to a stack with the same name. You might retry
ContinueUpdateRollbackrequests to ensure that CloudFormation successfully received them.
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
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.
See ‘aws help’ for descriptions of global parameters.
To use the following examples, you must have the AWS CLI installed and configured. See the Getting started guide 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 in the AWS CLI User Guide .
To retry an update rollback
continue-update-rollback example resumes a rollback operation from a previously failed stack update.
aws cloudformation continue-update-rollback \ --stack-name my-stack
This command produces no output.