@turbot/aws-msk

The aws-msk mod contains resource, control and policy definitions for AWS MSK service.

Version
5.4.0
Released On
Sep 25, 2023
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.4.0 (2023-09-25)

What's new?

  • AWS/MSK/Admin, AWS/MSK/Metadata and AWS/MSK/Operator now also include permissions for Cluster V2, Scram Secrets and Kafka VPC Connections.
  • Resource's metadata will now also include createdBy details in Turbot CMDB.
  • README.md file is now available for users to check details about the resource types and service permissions that the mod covers.
  • Rebranded to a Turbot Guardrails Mod. To maintain compatibility, none of the existing resource types, control types or policy types have changed, your existing configurations and settings will continue to work as before.

Bug fixes

  • Guardrails would sometimes fail to upsert clusters correctly in CMDB. This is now fixed.
  • 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.

Policy Types

Added

  • AWS > MSK > Cluster > Approved > Custom
  • AWS > MSK > Cluster > Approved > Instance Types

Action Types

Added

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

5.3.0 (2021-09-22)

What's new?

  • CMDB data for clusters now also includes client authentication details for IAM access control.
  • 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.

Bug fixes

  • The AWS > MSK > Cluster > Approved control would try and fail to delete clusters in CREATING state if the control was unapproved and the AWS > MSK > Cluster > Approved policy set to Enforce delete unapproved if new. This is now fixed.

5.2.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.2.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.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.2 (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.1 (2020-07-07)

Bug fixes

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

5.1.0 (2020-05-27)

What's new?

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

Bug fixes

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