Skip to content

4.2.0

Latest
Compare
Choose a tag to compare
@EreminAnton EreminAnton released this 12 Nov 10:07

What Changed:

Breaking Changes

It was decided to discontinue pushing the AccessDeniedByEvent metric that was added in the previous 4.1.0 release of CloudTrailToSlack. Because this metric was pushed by event type, it resulted in excessive costs.

New functionality

  • Now, by default, every time Lambda receives an AccessDenied event, it pushes a TotalAccessDeniedEvents metric to CloudWatch. This metric is pushed for all access-denied events, including events ignored by rules. To separate ignored events from the total, the module also pushes a TotalIgnoredAccessDeniedEvents metric to CloudWatch. Both metrics are placed in the CloudTrailToSlack/AccessDeniedEvents namespace. This feature allows you to gain more insights into the number and dynamics of access-denied events in your AWS Organization. This functionality can be disabled by setting push_access_denied_cloudwatch_metrics to false.
  • Fix and update examples in the /examples directory

Internal changes:

  • Fix log formatter to properly display set and str logs.
  • Fix passing boolean variables from Terraform to Python.
  • More logs for debugging purposes
  • Refactor rule processing to separate ignored events from others.
  • Update dependencies

Full Changelog: 4.1.0...4.2.0