# No updates are to be performed

AWS error fixes · Updated 16 November 2026

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

## 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 made | Why CloudFormation does not see it | Fix |
|---|---|---|
| New Lambda zip uploaded to the same S3 key | The template still has the same `S3Bucket` and `S3Key`; CloudFormation does not inspect object contents | Use 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 tag | The task definition's image string is unchanged | Deploy immutable tags or digests, or force a new ECS deployment separately |
| Edited a resource in the console | CloudFormation compares templates, not live resources | Put the change in the template; run drift detection to find differences |
| Changed a nested stack template at the same URL | The parent's properties for that nested stack look identical | Upload nested templates to a new key per version |
| Passed the same parameter values | `UsePreviousValue` or identical values | Check 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.

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

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Update CloudFormation stacks using change sets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-changesets.html)
- [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/)

## Related

- [aws cloudformation describe-stacks](https://cloudconsole.dev/cli/cloudformation-describe-stacks)
- [aws cloudformation detect-stack-drift](https://cloudconsole.dev/cli/cloudformation-detect-stack-drift)
- [aws lambda update-function-code](https://cloudconsole.dev/cli/lambda-update-function-code)
- [AWS ECS force new deployment](https://cloudconsole.dev/how-to/force-new-deployment-ecs)
- [aws cloudformation validate-template](https://cloudconsole.dev/cli/cloudformation-validate-template)
- [UPDATE_ROLLBACK_FAILED](https://cloudconsole.dev/errors/cloudformation-update-rollback-failed)

---

Source: https://cloudconsole.dev/errors/cloudformation-no-updates-to-be-performed

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
