CloudConsole

No updates are to be performed

Updated 16 November 2026 · How we write and check guides

Short answer

CloudFormation compared your template and parameters with the stack's current ones and found nothing to change, so it refused the update with a ValidationError. In CI, treat it as success (aws cloudformation deploy has --no-fail-on-empty-changeset). If you did change something, CloudFormation could not see it: typically Lambda code uploaded to the same S3 key, or a change made outside the template.

On this page, in 5 steps: 1. What it means; 2. Make CI treat it as success; 3. When you did change something; 4. Check what…
The diagnosis and fix steps from this page, in the order to try them; commands and details are below.

What it means

An error occurred (ValidationError) when calling the UpdateStack operation:
No updates are to be performed.

It is reported as an error but nothing is wrong with the stack; its status is unchanged. Change sets report the same thing differently: the change set ends in FAILED with a status reason saying the submitted information did not contain changes.

Make CI treat it as success

With the high-level deploy command, use the built-in flag:

aws cloudformation deploy --stack-name orders-prod \
  --template-file packaged.yaml --capabilities CAPABILITY_IAM \
  --no-fail-on-empty-changeset

With update-stack, catch that specific message and only that one:

if ! out=$(aws cloudformation update-stack --stack-name orders-prod \
    --template-body file://template.yaml --capabilities CAPABILITY_IAM 2>&1); then
  echo "$out" | grep -q 'No updates are to be performed' || { echo "$out"; exit 1; }
  echo 'Stack already up to date'
fi

Do not swallow all ValidationErrors; real template problems use the same error type.

When you did change something

Change you madeWhy CloudFormation does not see itFix
New Lambda zip uploaded to the same S3 keyThe template still has the same S3Bucket and S3Key; CloudFormation does not inspect object contentsUse a unique key per build (hash or version), or set S3ObjectVersion; aws cloudformation package does this for you
New container image pushed with the same tagThe task definition's image string is unchangedDeploy immutable tags or digests, or force a new ECS deployment separately
Edited a resource in the consoleCloudFormation compares templates, not live resourcesPut the change in the template; run drift detection to find differences
Changed a nested stack template at the same URLThe parent's properties for that nested stack look identicalUpload nested templates to a new key per version
Passed the same parameter valuesUsePreviousValue or identical valuesCheck the values actually sent

Check what CloudFormation thinks is deployed

Compare the live template and parameters with what you are sending:

aws cloudformation get-template --stack-name orders-prod \
  --query TemplateBody --output text > deployed.yaml
diff deployed.yaml template.yaml

aws cloudformation describe-stacks --stack-name orders-prod \
  --query 'Stacks[0].Parameters'

Previewing with a change set shows exactly which resources CloudFormation would touch, which is the quickest way to confirm whether a change is visible to it.

Forcing an update

If you need resources to pick up something CloudFormation cannot detect, change something it can: a new artefact key, an image digest, or a harmless parameter such as a build ID passed into a description or environment variable. Avoid bumping unrelated properties by hand; it hides the real problem, which is that your artefacts are not versioned.

Questions

Is No updates are to be performed an error?

Not really. CloudFormation reports it as a ValidationError, but the stack is fine and already matches the template. Treat it as success in pipelines.

Why does CloudFormation not update my Lambda code?

If the template still points to the same S3 bucket and key, CloudFormation sees no change. Upload each build to a unique key or set S3ObjectVersion.

How do I ignore empty change sets with aws cloudformation deploy?

Add --no-fail-on-empty-changeset to the command so it exits successfully when there is nothing to change.

CloudConsole CodePipeline screen on a phone, for following up on No updates are to be performed away from your desk
When this happens away from your desk

A pipeline that reports success while nothing actually changed is how fixes fail to reach production. CloudConsole, a phone app for AWS, is built to show alarms and recent changes on your phone, so a fix that never deployed is easier to spot.

Did it start after a deploy? What changed? on the app’s alarm screen lists the deploys and configuration changes from the hour before the alarm fired.

About the app → · Download on the App Store

Sources