Unable to update root stack in UPDATE_ROLLBACK_COMPLETE state because nested stack is in UPDATE_FAILED stack

Question

I have a nested stack in **UPDATE_FAILED** state. On investigation the error happened because I tried to update multiple dynamoDB gsi index as shown below
> Resource handler returned message: "Cannot perform more than one GSI creation or deletion in a single update

**What I did:**
First I updated the nested stack CF template hosted in an S3 bucket, then I updated the root stack (**Make Direct Update)** from the console. The root stack still transitioned to UPDATE_ROLLBACK_COMPLETE, but the nested stack remained in a failed state.

I tried this a couple of times via the console and CLI, still the same result. When I checked template tab in the nested stack, it was still referencing the old template and the timestamp in the events were like 4hrs behind the root stack events which makes me think the attempt to update the nested stack did not execute causing a rollback at the root stack.

Does anyone have any suggestion on how to resolve this.

re:Post Agent · Answer

Based on your situation, there are a few important points to address:

**Understanding the Current State:**
When a root stack is in UPDATE_ROLLBACK_COMPLETE state and a nested stack is in UPDATE_FAILED state, this indicates that the rollback operation completed successfully at the root level, but the nested stack didn't properly roll back. This is an unusual state that requires careful handling.

**Key Consideration:**
If a nested stack is in UPDATE_FAILED state while the root stack isn't in UPDATE_ROLLBACK_FAILED state, you may need to reach out to AWS Support through the AWS Support Center (https://console.aws.amazon.com/support/) to help unblock your stack. This specific combination of states can sometimes require assistance to resolve properly.

**Regarding Your DynamoDB GSI Error:**
The error you encountered about multiple GSI operations is a known limitation - you can only perform one GSI creation or deletion per update. For future updates, you'll need to stage these changes across multiple separate updates.

**Recommended Next Steps:**
1. Verify the exact current state of both your root and nested stacks in the CloudFormation console
2. Check if there are any resources in the nested stack that are preventing it from completing its rollback
3. If the nested stack remains stuck in UPDATE_FAILED while the root is in UPDATE_ROLLBACK_COMPLETE, consider opening a support case through the AWS Support Center to get assistance with unblocking the stack

Once the stacks are in a stable state, you can retry your update, making sure to apply GSI changes one at a time in separate updates.  
**Sources**  
[Identify resources to skip for continue-update-rollback operation | AWS re:Post](https://repost.aws/knowledge-center/cloudformation-identify-skip-resources)

Unable to update root stack in UPDATE_ROLLBACK_COMPLETE state because nested stack is in UPDATE_FAILED stack

Add your answer

Relevant content