A CloudFormation update is UPDATE_ROLLBACK_FAILED because an external change prevented resource restoration. The underlying issue is corrected. What should happen next?

Published
  1. Skip every resource automatically without considering template consistency.
  2. Delete the local template and assume the remote stack resets itself.
  3. Start arbitrary new updates immediately without resolving rollback.
  4. Continue the update rollback and monitor the stack back to a stable state before attempting a new update.

Comments — 0