Bug fixes

• VPC CMDB controls, such as AWS > VPC > Security Group > 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 its 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.
• The AWS > VPC > Security Group > Ingress Rules > Approved, AWS > VPC > Security Group > Egress Rules > Approved and AWS > VPC > Network ACL > Ingress Rules > Approved controls no longer sit in tbd for up to an hour on a newly discovered resource. They now wait for the CMDB control and evaluate within seconds of it finishing, instead of running before CMDB has stored the resource.