AWS CDR Versions

Every version of the ARMO Cloud Detection & Response stack for AWS, newest first.

A new version is used by new connections only. A stack you already deployed keeps its version until you update it. To see your current version, open your stack in CloudFormation (the default name is armo-cadr), go to Parameters, and read the tag at the end of LambdaImageUri.

How to update

Each version says whether it changed the CDR stack template (the standard armo-cadr stack) and the Control Tower template. Check every version newer than yours, for the template your deployment uses:

  • If any of them changed that template, update with Replace current template and the latest template, so you also get the new resources and parameters. See Update with a new template.
  • Otherwise, update with Use existing template and change the image tags only.

The image tags of a version:

DeploymentStack parameterImage tag
CDR stackLambdaImageUri<version>
CDR stackS3NotificationImageUri<version>-notification
Control Tower stackLambdaImageUri<version>-ct

The update guide walks through the CDR stack. A Control Tower stack is updated the same way, with its one image parameter, LambdaImageUri, set to the -ct tag.

Version numbers that are skipped below (for example v0.0.27) were never released.

v0.0.33

Released 2026-11-16.

  • CDR stack template: unchanged since v0.0.32.
  • Control Tower template: unchanged since v0.0.32.

Maintenance release. No change to AWS detection behavior.

v0.0.32

Released 2026-10-20.

  • CDR stack template: unchanged since v0.0.29.
  • Control Tower template: unchanged since v0.0.29.

Rule C0028 (EBS snapshot made public) now matches real CloudTrail events and is enabled.

v0.0.29

Released 2026-10-14.

  • CDR stack template: changed since v0.0.28. Update with Replace current template.
  • Control Tower template: changed since v0.0.28. Update with Replace current template.

Detection rules can now be delivered from the ARMO Platform, so rule updates reach your stack without a new version. The templates add the RuleEndpointUrl parameter. When you replace the template, set it to the endpoint for your ARMO region:

  • EU: https://api.armosec.io/api/v1/cdr/rules
  • US: https://api.us.armosec.io/api/v1/cdr/rules

If you leave it empty, the stack keeps using the rules built into the image.

v0.0.28

Released 2026-10-07.

  • CDR stack template: unchanged since v0.0.26.
  • Control Tower template: unchanged since v0.0.26.

Detection rule fixes: several rules that could never match now detect the events they describe.

v0.0.26

Released 2026-10-07.

  • CDR stack template: unchanged since v0.0.25.
  • Control Tower template: unchanged since v0.0.25.

Detection rule fixes: twelve rules that could never match now detect the events they describe.

v0.0.25

Released 2026-10-05.

  • CDR stack template: changed since v0.0.23. Update with Replace current template.
  • Control Tower template: unchanged since v0.0.23.

Failed log processing is now retried, and events that still fail are kept in a dead-letter queue (LogProcessorDLQ) instead of being dropped.


Did this page help you?