AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
For a specified stack that is 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 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.
For PCL this operation is only available in asynchronous form. Please refer to ContinueUpdateRollbackAsync.
public abstract ContinueUpdateRollbackResponse ContinueUpdateRollback( ContinueUpdateRollbackRequest request )
Container for the necessary parameters to execute the ContinueUpdateRollback service method.
|TokenAlreadyExistsException||A client request token already exists.|
Supported in: 4.5, 4.0, 3.5
Portable Class Library:
Supported in: Windows Store Apps
Supported in: Windows Phone 8.1
Supported in: Xamarin Android
Supported in: Xamarin iOS (Unified)
Supported in: Xamarin.Forms