Product logo
DocsBlogPricing

@turbot/aws-logs

Version
5.11.1
Released On
Feb 15, 2022
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.11.1 (2022-02-15)

Bug fixes

  • We've made a few improvements in the GraphQL query for AWS > Logs > Log Group > Encryption at Rest control. You won't notice any difference, but things should run lighter and quicker than before.
  • We've improved the process of deleting resources from Turbot if their CMDB policy was set to Enforce: Disabled. The CMDB controls will now not look to resolve credentials via Turbot's IAM role while deleting resources from Turbot. This will allow the CMDB controls to process resource deletions from Turbot more reliably than before.

5.11.0 (2022-02-03)

What's new?

  • Users can now create their own custom checks against resource attributes in the Approved control using the Approved > Custom policy. These custom checks would be a part of the evaluation of the Approved control. Custom messages can also be added which are then displayed in the control details table. See Custom Checks for more information.

Policy Types

Added

  • AWS > Logs > Log Group > Approved > Custom
  • AWS > Logs > Log Stream > Approved > Custom
  • AWS > Logs > Metric Filter > Approved > Custom
  • AWS > Logs > Resource Policy > Approved > Custom

5.10.0 (2022-01-06)

What's new?

  • AWS/Logs/Admin AWS/Logs/Metadata AWS/Logs/Operator now include permissions for Log Delivery and Query Definition.

5.9.0 (2021-08-10)

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.

Bug fixes

  • Metric Filters created in AWS were not upserted automatically into Turbot's CMDB. This is now fixed.

5.8.0 (2021-02-22)

What's new?

  • We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in 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.7.1 (2021-01-06)

Bug fixes

  • Controls run faster now when in the tbd and skipped 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 in tbd and skipped, resulting in faster and lighter control runs.

5.7.0 (2020-12-07)

Resource Types

Added

  • AWS > Logs > Resource Policy

Control Types

Added

  • AWS > Logs > Resource Policy > Active
  • AWS > Logs > Resource Policy > Approved
  • AWS > Logs > Resource Policy > CMDB
  • AWS > Logs > Resource Policy > Discovery
  • AWS > Logs > Resource Policy > Usage

Policy Types

Added

  • AWS > Logs > Resource Policy > Active
  • AWS > Logs > Resource Policy > Active > Age
  • AWS > Logs > Resource Policy > Active > Budget
  • AWS > Logs > Resource Policy > Active > Last Modified
  • AWS > Logs > Resource Policy > Approved
  • AWS > Logs > Resource Policy > Approved > Budget
  • AWS > Logs > Resource Policy > Approved > Regions
  • AWS > Logs > Resource Policy > Approved > Usage
  • AWS > Logs > Resource Policy > CMDB
  • AWS > Logs > Resource Policy > Regions
  • AWS > Logs > Resource Policy > Usage
  • AWS > Logs > Resource Policy > Usage > Limit

Action Types

Added

  • AWS > Logs > Resource Policy > Delete
  • AWS > Logs > Resource Policy > Router

5.6.2 (2020-09-24)

Bug fixes

  • Metric filter pattern update events were not being handled properly, so the metric filter's CMDB data would not reflect the latest pattern. This has been fixed.

5.6.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.6.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.5.1 (2020-08-14)

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

Control Types

Added

  • AWS > Logs > Log Group > Encryption at Rest

Policy Types

Added

  • AWS > Logs > Log Group > Encryption at Rest
  • AWS > Logs > Log Group > Encryption at Rest > Customer Managed Key

Action Types

Added

  • AWS > Logs > Log Group > Update Encryption at Rest

5.4.0 (2020-07-17)

What's new?

  • We’ve improved our event handling configuration and now filter which AWS events Turbot listens for based on resources’ CMDB policies. If a resource’s CMDB policy is not set to Enforce: Enabled, the EventBridge rules will be configured to not send any events for that resource. This will greatly reduce the amount of unnecessary events that Turbot listens for and handles today.

Policy Types

Added

  • AWS > Turbot > Event Handlers > Events > Rules > Custom Event Patterns > @turbot/aws-logs

Removed

  • AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-logs

5.3.1 (2020-07-07)

Bug fixes

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

5.3.0 (2020-05-26)

Control Types

Added

  • AWS > Logs > Metric Filter > Configured

Policy Types

Added

  • AWS > Logs > Metric Filter > Configured
  • AWS > Logs > Metric Filter > Configured > Claim Precedence
  • AWS > Logs > Metric Filter > Configured > Source

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

Policy Types

Renamed

  • AWS > Logs > Log Group > Configured > Precedence to AWS > Logs > Log Group > Configured > Claim Precedence
  • AWS > Logs > Log Stream > Configured > Precedence to AWS > Logs > Log Stream > Configured > Claim Precedence