Product logo
DocsBlogPricing

@turbot/aws-logs

The aws-logs mod contains resource, control and policy definitions for AWS Logs service.

Version
5.12.1
Released On
Feb 13, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.12.1 (2024-02-13)

Bug fixes

  • Added support for af-south-1, ap-northeast-3, ap-south-2, ap-southeast-3, ap-southeast-4, ca-west-1, eu-central-2, eu-south-1, eu-south-2, il-central-1 and me-central-1 regions in the AWS > Logs > Regions policy.

5.12.0 (2023-10-06)

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.

Action Types

  • AWS > Logs > Log Group > Delete from AWS
  • AWS > Logs > Log Group > Set Tags
  • AWS > Logs > Log Group > Skip alarm for Active control
  • AWS > Logs > Log Group > Skip alarm for Active control [90 days]
  • AWS > Logs > Log Group > Skip alarm for Approved control
  • AWS > Logs > Log Group > Skip alarm for Approved control [90 days]
  • AWS > Logs > Log Group > Skip alarm for Encryption at Rest control
  • AWS > Logs > Log Group > Skip alarm for Encryption at Rest control [90 days]
  • AWS > Logs > Log Group > Skip alarm for Tags control
  • AWS > Logs > Log Group > Skip alarm for Tags control [90 days]
  • AWS > Logs > Log Stream > Delete from AWS
  • AWS > Logs > Log Stream > Skip alarm for Active control
  • AWS > Logs > Log Stream > Skip alarm for Active control [90 days]
  • AWS > Logs > Log Stream > Skip alarm for Approved control
  • AWS > Logs > Log Stream > Skip alarm for Approved control [90 days]
  • AWS > Logs > Metric Filter > Delete from AWS
  • AWS > Logs > Metric Filter > Skip alarm for Active control
  • AWS > Logs > Metric Filter > Skip alarm for Active control [90 days]
  • AWS > Logs > Metric Filter > Skip alarm for Approved control
  • AWS > Logs > Metric Filter > Skip alarm for Approved control [90 days]
  • AWS > Logs > Resource Policy > Delete from AWS
  • AWS > Logs > Resource Policy > Skip alarm for Active control
  • AWS > Logs > Resource Policy > Skip alarm for Active control [90 days]
  • AWS > Logs > Resource Policy > Skip alarm for Approved control
  • AWS > Logs > Resource Policy > Skip alarm for Approved control [90 days]

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 Guardrails if their CMDB policy was set to Enforce: Disabled. The CMDB controls will now not look to resolve credentials via Guardrails' IAM role while deleting resources from Guardrails. This will allow the CMDB controls to process resource deletions from Guardrails 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

  • 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 Guardrails 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 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.7.0 (2020-12-07)

Resource Types

  • AWS > Logs > Resource Policy

Control Types

  • 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

  • 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

  • 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

  • AWS > Logs > Log Group > Encryption at Rest

Policy Types

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

Action Types

  • 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 Guardrails 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 Guardrails listens for and handles today.

Policy Types

  • 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

  • AWS > Logs > Metric Filter > Configured

Policy Types

  • 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