I have watched a CloudFormation deploy fail at minute nine because I misspelled a property, and I have quietly made peace with the fact that this is a rite of passage for anyone shipping IaC. AWS just removed one of those rites. In a June 30 post on the AWS DevOps blog, the CloudFormation team extended pre-deployment validation to run automatically on every stack operation, not only on change sets. If your team ships small updates through direct CreateStack and UpdateStack calls, the safety net that used to appear only when you explicitly asked for a preview now shows up by default.
This is one of those quiet infrastructure changes that only reveals its value the third or fourth time your CI does not spend fifteen minutes rolling back a stack that never should have started.
What the CloudFormation team shipped
Validation used to be a change-set exclusive. You called CreateChangeSet, waited, reviewed the preview, then decided whether to execute. In the new behaviour, CreateStack and UpdateStack also run the same synchronous checks before the stack transitions into IN_PROGRESS. Two tiers are involved.
The FAIL tier stops the operation before any resource is touched. It covers property syntax errors and resource name conflicts, the class of mistakes where a stack cannot possibly succeed but the platform previously discovered that only after it had started creating siblings and had to unwind them.
