@turbot/aws-dax

The aws-dax mod contains resource, control and policy definitions for AWS DAX service.

Version
5.4.0
Released On
Nov 09, 2023
Depends On

Resource Types

Control Types

Policy Types

Release Notes

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

  • Resource's metadata will now also include createdBy details in Turbot CMDB.

Policy Types

  • AWS > DAX > Cluster > Approved > Custom

Action Types

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

5.3.1 (2020-12-17)

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.3.0 (2020-10-09)

What's new?

  • We've made improvements to how Active controls interact with CMDB policies and controls for more reliable active checks. Now, if a resource's CMDB policy is set to Skip, its Active control will move to invalid to prevent the Active control from making a decision based on outdated information. Also, Active controls will now wait until the resource's CMDB control has run at least once to ensure the required data is available.

5.2.1 (2020-09-18)

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.2.0 (2020-09-01)

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.1.5 (2020-08-11)

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.1.4 (2020-06-30)

Bug fixes

  • Sometimes when updating CMDB for resources with tags that have empty string values, e.g., [{Key: "Empty", Value: ""}, {Key: "Guardrails is great", Value: "true"}], we would not store all of the tags correctly. This has been fixed and now all tags are accounted for.

5.1.3 (2020-06-11)

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.1.2 (2020-05-26)

Bug fixes

  • Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.