The aws-qldb mod contains resource, control and policy definitions for AWS QLDB service.

Released On
Nov 09, 2023
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.3.0 (2023-11-09)

What's new?

  • We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

  • Users can now perform quick actions on resources to remediate cloud configuration issues or skip Turbot alarms for issues that they want to come back to later. To get started, click on the Actions button, which will reveal a dropdown menu with available actions, and select one. See Quick Actions for more information.

Policy Types

  • AWS > QLDB > Ledger > Approved > Custom

Action Types

  • AWS > QLDB > Ledger > Delete from AWS
  • AWS > QLDB > Ledger > Set Tags
  • AWS > QLDB > Ledger > Skip alarm for Active control
  • AWS > QLDB > Ledger > Skip alarm for Active control [90 days]
  • AWS > QLDB > Ledger > Skip alarm for Approved control
  • AWS > QLDB > Ledger > Skip alarm for Approved control [90 days]
  • AWS > QLDB > Ledger > Skip alarm for Tags control
  • AWS > QLDB > Ledger > Skip alarm for Tags control [90 days]

5.2.0 (2021-07-13)

What's new?

  • We've improved the details tables in the Tags controls to be more helpful, especially when a resource's tags are not set correctly as expected. Previously, to understand why the Tags controls were in an Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

5.1.2 (2021-01-06)

Bug fixes

  • Controls run faster now when in the tbd and skipped states thanks to the new Guardrails Precheck feature (not to be confused with TSA PreCheck). With Guardrails Precheck, controls avoid running GraphQL input queries when in tbd and skipped, resulting in faster and lighter control runs.

5.1.1 (2020-09-22)

Bug fixes

  • We've made some improvements to our real-time event handling that reduces the risk of creating resources in CMDB with malformed AKAs. There's no noticeable difference, but things should run more reliably now.

5.1.0 (2020-09-02)

What's new?

  • Discovery controls now have their own control category, CMDB > Discovery, to allow for easier filtering separately from other CMDB controls.
  • We've renamed the service's default regions policy from Regions [Default] to Regions to be consistent with our other regions policies.

5.0.5 (2020-08-12)

Bug fixes

  • In various Active controls, we were outputting log messages that did not properly show how many days were left until we'd delete the inactive resources (we were still deleting them after the correct number of days). These log messages have been fixed and now contain the correct number of days.

5.0.4 (2020-07-06)

Bug fixes

  • Updated various resource configurations to provide better compatibility with AWS China regions.

5.0.3 (2020-06-15)

What's new?

  • All resource Router actions now run even if Guardrails is outside of its allowed change window. This allows Guardrails to maintain an up-to-date CMDB by handling resource updates at all times. Note that this only affects Guardrails' ability to process resources changes that were made in the cloud provider - enforcement actions are still disabled outside of the change window.

5.0.2 (2020-05-08)

Bug fixes

  • Several permissions did not have grant levels assigned, so when this service was enabled, the IAM permission model would be unable to calculate the full permission set across all services. The missing grant levels have been added and permission calculations are now running smoothly again.