For a specified stack that is in the
continues rolling it back to the
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
and then try to update the stack again.
A stack goes into the
UPDATE_ROLLBACK_FAILED state when AWS
CloudFormation cannot roll back all changes after a failed stack update.
For example, you might have a stack that is rolling back to an old
database instance that was deleted outside of AWS CloudFormation.
Because AWS 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.
cloudformation_continue_update_rollback(StackName, RoleARN, ResourcesToSkip, ClientRequestToken)
[required] 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
The Amazon Resource Name (ARN) of an AWS Identity and Access Management (IAM) role that AWS CloudFormation assumes to roll back the stack. AWS CloudFormation uses the role's credentials to make calls on your behalf. AWS CloudFormation always uses this role for all future operations on the stack. As long as users have permission to operate on the stack, AWS CloudFormation uses this role even if the users don't have permission to pass it. Ensure that the role grants least privilege.
If you don't specify a value, AWS CloudFormation uses the role that was previously associated with the stack. If no role is available, AWS CloudFormation uses a temporary session that is generated from your user credentials.
A list of the logical IDs of the resources that AWS CloudFormation skips
during the continue update rollback operation. You can specify only
resources that are in the
Specify this property to skip rolling back resources that AWS
CloudFormation can't successfully roll back. We recommend that you
resources before skipping them. AWS CloudFormation sets the status of
the specified resources to
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
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.
A unique identifier for this
An empty list.
1 2 3 4 5 6 7 8
svc$continue_update_rollback( StackName = "string", RoleARN = "string", ResourcesToSkip = list( "string" ), ClientRequestToken = "string" )
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.