Home › AWS SysOps Associate › cloudcomputing › sysopsdeployment › A CloudFormation stack fails midway with an `IAM…
A CloudFormation stack fails midway with an `IAM role doesn't have permission` error and leaves the stack in `CREATE_FAILED`. What's the recommended action?
AEdit the CloudFormation template to disable error reporting
BInvestigate the missing permission, fix the deploying IAM role/policy, delete the failed stack, then redeploy
CIgnore the failure and call the app a success
DMove all the resources into Amazon Glacier
Answer & Solution
Correct answer: B. Investigate the missing permission, fix the deploying IAM role/policy, delete the failed stack, then redeploy
Root-cause the permission, fix the role/policy, clean up the failed stack, redeploy. Hiding errors or moving to Glacier defeats the purpose.
Related questions
Which rollout strategy minimises blast radius when shipping a risky change to a fleet of EWhich feature of AWS Resource Access Manager (RAM) lets one account share resources like sWhich AWS service lets a team package and version their own internal application configuraA new EC2 launch in a private subnet repeatedly fails to download a yum package. The instaWhich CloudFormation feature lets you reference a value created in one stack from another Which combination correctly provisions a centrally-managed multi-account landing zone for Which AWS Systems Manager capability lets administrators run a documented automation sequeAn organisation needs to deploy a new version of a web app to 100 EC2 instances behind an