@turbot/aws-fsx

The aws-fsx mod contains resource, control and policy definitions for AWS FSx service.

Version
5.3.0
Released On
Oct 26, 2023
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.3.0 (2023-10-26)

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.

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

  • Updated AWS > FSx > Regions policy default value to now include cn-north-1, cn-northwest-1, us-gov-east-1 and us-gov-west-1.

Policy Types

  • AWS > FSx > Backup > Approved > Custom
  • AWS > FSx > File System > Approved > Custom

Action Types

  • AWS > FSx > Backup > Delete from AWS
  • AWS > FSx > Backup > Set Tags
  • AWS > FSx > Backup > Skip alarm for Active control
  • AWS > FSx > Backup > Skip alarm for Active control [90 days]
  • AWS > FSx > Backup > Skip alarm for Approved control
  • AWS > FSx > Backup > Skip alarm for Approved control [90 days]
  • AWS > FSx > Backup > Skip alarm for Tags control
  • AWS > FSx > Backup > Skip alarm for Tags control [90 days]
  • AWS > FSx > File System > Delete from AWS
  • AWS > FSx > File System > Set Tags
  • AWS > FSx > File System > Skip alarm for Active control
  • AWS > FSx > File System > Skip alarm for Active control [90 days]
  • AWS > FSx > File System > Skip alarm for Approved control
  • AWS > FSx > File System > Skip alarm for Approved control [90 days]
  • AWS > FSx > File System > Skip alarm for Tags control
  • AWS > FSx > File System > Skip alarm for Tags control [90 days]

5.2.2 (2021-01-28)

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.2.1 (2020-09-21)

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-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.1.6 (2020-08-13)

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.5 (2020-07-06)

Bug fixes

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

5.1.4 (2020-07-01)

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-12)

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-12)

What's new?

  • Updated AWS > FSx > Regions policy default value to now include ap-east-1, ap-northeast-2.

Bug fixes

  • Removed AWS > FSx > Backup > Router control and re-added it as an action. It was previously released incorrectly as a control and should not appear in the UI.

Control Types

Removed

  • AWS > FSx > Backup > Router

Action Types

  • AWS > FSx > Backup > Router