An organization's deployment pipeline fails during a step that executes an AWS CloudFormation stack template. The pipeline is configured to update a stack that has a status of ROLLBACK_COMPLETE following a failed initial creation attempt. Which actions should a developer take to resolve this issue and enable a successful deployment? (Choose two.)
- Delete the CloudFormation stack in the ROLLBACK_COMPLETE state.Answer
- Resolve the underlying resource configuration issue that caused the initial creation failure.Answer
- CInitiate a stack update operation using the corrected template directly on the existing stack.
- DAdd the cloudformation:UpdateStack permission to the trust policy of the IAM service role.
- ERun a drift detection operation on the stack and import the failed resources to force the state to UPDATE_COMPLETE.
Answer
Delete the CloudFormation stack in the ROLLBACK_COMPLETE state and resolve the underlying resource configuration issue that caused the initial creation failure.
To resolve a failed initial deployment that resulted in a ROLLBACK_COMPLETE state, the developer must delete the stack and fix the root cause of the failure. CloudFormation does not allow updates to stacks that failed their initial creation (ROLLBACK_COMPLETE). Once the stack is deleted and the template/environment issues are resolved, the pipeline can successfully trigger a new stack creation.
Step-by-Step Solution
Key Concept
Managing CloudFormation stack states and resolving failed initial creations in a CI/CD pipeline.