@turbot/aws-dax
Recommended Version
Version
5.3.1
Released On
Dec 17, 2020
Depends On
Resource Types
Control Types
- AWS > DAX > Cluster > Active
- AWS > DAX > Cluster > Approved
- AWS > DAX > Cluster > CMDB
- AWS > DAX > Cluster > Discovery
- AWS > DAX > Cluster > Tags
- AWS > DAX > Cluster > Usage
Policy Types
- AWS > DAX > API Enabled
- AWS > DAX > Approved Regions [Default]
- AWS > DAX > Cluster > Active
- AWS > DAX > Cluster > Active > Age
- AWS > DAX > Cluster > Active > Budget
- AWS > DAX > Cluster > Active > Last Modified
- AWS > DAX > Cluster > Approved
- AWS > DAX > Cluster > Approved > Budget
- AWS > DAX > Cluster > Approved > Encryption at Rest
- AWS > DAX > Cluster > Approved > Node Type
- AWS > DAX > Cluster > Approved > Regions
- AWS > DAX > Cluster > Approved > Usage
- AWS > DAX > Cluster > CMDB
- AWS > DAX > Cluster > Regions
- AWS > DAX > Cluster > Tags
- AWS > DAX > Cluster > Tags > Template
- AWS > DAX > Cluster > Usage
- AWS > DAX > Cluster > Usage > Limit
- AWS > DAX > Enabled
- AWS > DAX > Permissions
- AWS > DAX > Permissions > Levels
- AWS > DAX > Permissions > Levels > Modifiers
- AWS > DAX > Permissions > Lockdown
- AWS > DAX > Permissions > Lockdown > API Boundary
- AWS > DAX > Regions
- AWS > DAX > Tags Template [Default]
- AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-dax
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-dax
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-dax
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-dax
Release Notes
5.3.1 (2020-12-17)
Bug fixes
- Controls run faster now when in the
tbd
andskipped
states thanks to the new Turbot Precheck feature (not to be confused with TSA PreCheck). With Turbot Precheck, controls avoid running GraphQL input queries when intbd
andskipped
, 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 toinvalid
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]
toRegions
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: "Turbot 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 Turbot is outside of its allowed change window. This allows Turbot to maintain an up-to-date CMDB by handling resource updates at all times. Note that this only affects Turbot's 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.