1 Answer
- Newest
- Most votes
- Most comments
1
The aws cloudformation deploy command by default creates a changeset and then executes it if the changeset creation is successful. This is typically the behavior you would expect when you're deploying a CloudFormation stack. However, when you see the status of REVIEW_IN_PROGRESS, it suggests that the changeset was created but not executed.
- If your CloudFormation stack is creating IAM resources, you'll need to explicitly acknowledge that your template is creating these resources. You can do this by adding the --capabilities CAPABILITY_IAM CAPABILITY_NAMED_IAM CAPABILITY_AUTO_EXPAND parameters to your aws cloudformation deploy command.
- The role you're using to execute the CloudFormation stack might not have the necessary permissions to create and execute changesets. Check your IAM permissions to ensure your role has the cloudformation:CreateChangeSet, cloudformation:DescribeChangeSet, cloudformation:ExecuteChangeSet, and cloudformation:DeleteChangeSet permissions.
- Check the AWS CloudFormation console to see if there are any stack events that might give you a clue as to why the changeset isn't executing. Sometimes a changeset won't execute if there are errors with the stack or the resources it's trying to create.
- If your stack contains nested stacks, make sure that the nested stack templates are accessible (i.e., the S3 URLs are correct) and that they don't contain any errors.

added cloudformation:ExecuteChangeSet and it continues, thank you!