Skip to content

aws cloudformation deploy stuck REVIEW_IN_PROGRESS

0

I'm trying to run aws cloudformation deploy to create an EMR cluster. Parameters in this command: -region us-west-1 --stack-name xxx --template-file xxx.yaml --no-fail-on-empty-changeset --parameter-overrides Application=xxx AutoScalingRole=xxx CoreInstanceType=xxx Environment=dev EbsRootVolumeSize=xxx Env=dev JobFlowRole=xxx LogBucket=xxx MasterInstanceType=xxx Owner=xxx PipelineName=xxx ReleaseLabel=emr-6.9.0 SecurityConfiguration=xxx ServiceRole=xxx Stack=xxx SubnetId=xxx TerminationProtected=false TaskInstanceTypeMin=xxx TaskInstanceTypeMax=xxx IcebergEnabled=false Version=1.0 And it creates a stack, the status is REVIEW_IN_PROGRESS. There is one change set under the stack, I should execute the change set to proceed the cluster creation process. Is there some way to let it execute the change set automatically? probably add some parameters or set it in the template-file. Thank you!

asked 3 years ago3.3K views

1 Answer
1
Accepted Answer

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.
EXPERT

answered 3 years ago

  • added cloudformation:ExecuteChangeSet and it continues, thank you!

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.