AWS mods - AWS metadata no longer nests inside resources on upgrade (ACM, Athena, ECS, Elastic Beanstalk, Elasticsearch, Route 53 Resolver, S3 Multi-Region Access Point, Shield, WAF Regional)
Nov 12, 2026•GuardrailsMods
Bug fixes
- The CMDB controls in the mods listed below, such as AWS > ECS > Cluster > CMDB, no longer nest a resource's AWS metadata (account ID, region, partition) inside itself during a mod upgrade. An affected resource lost its account ID and region, so a regional resource's CMDB control looked it up in the wrong region; the CMDB controls now repair the resource in a single run. To find affected resources, filter on $.turbot.custom.aws.aws:!null and run their CMDB control. If that fails with an akas_aka_key error, or the resource stays nested, delete it: discovery keeps or re-creates the correct record.
Released versions:
- aws-acm v5.14.1
- aws-athena v5.8.1
- aws-ecs v5.12.1
- aws-elasticbeanstalk v5.6.1
- aws-elasticsearch v5.11.1
- aws-route53resolver v5.8.1
- aws-s3multiregionaccesspoint v5.4.1
- aws-shield v5.6.1
- aws-wafregional v5.9.1