@turbot/aws-cloudwatch
Recommended Version
Version
5.6.1
Released On
Feb 24, 2022
Depends On
Resource Types
Control Types
- AWS > CloudWatch > Alarm > Active
- AWS > CloudWatch > Alarm > Approved
- AWS > CloudWatch > Alarm > CMDB
- AWS > CloudWatch > Alarm > Discovery
- AWS > CloudWatch > Alarm > Tags
- AWS > CloudWatch > Alarm > Usage
- AWS > CloudWatch > Stack
Policy Types
- AWS > CloudWatch > API Enabled
- AWS > CloudWatch > Alarm > Active
- AWS > CloudWatch > Alarm > Active > Age
- AWS > CloudWatch > Alarm > Active > Last Modified
- AWS > CloudWatch > Alarm > Approved
- AWS > CloudWatch > Alarm > Approved > Custom
- AWS > CloudWatch > Alarm > Approved > Regions
- AWS > CloudWatch > Alarm > Approved > Usage
- AWS > CloudWatch > Alarm > CMDB
- AWS > CloudWatch > Alarm > Regions
- AWS > CloudWatch > Alarm > Tags
- AWS > CloudWatch > Alarm > Tags > Template
- AWS > CloudWatch > Alarm > Usage
- AWS > CloudWatch > Alarm > Usage > Limit
- AWS > CloudWatch > Approved Regions [Default]
- AWS > CloudWatch > Enabled
- AWS > CloudWatch > Permissions
- AWS > CloudWatch > Permissions > Levels
- AWS > CloudWatch > Permissions > Levels > Modifiers
- AWS > CloudWatch > Permissions > Lockdown
- AWS > CloudWatch > Permissions > Lockdown > API Boundary
- AWS > CloudWatch > Regions
- AWS > CloudWatch > Stack
- AWS > CloudWatch > Stack > Secret Variables
- AWS > CloudWatch > Stack > Source
- AWS > CloudWatch > Stack > Terraform Version
- AWS > CloudWatch > Stack > Variables
- AWS > CloudWatch > Tags Template [Default]
- AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-cloudwatch
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-cloudwatch
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-cloudwatch
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-cloudwatch
Release Notes
5.6.1 (2022-02-24)
Bug fixes
- The
AWS > CloudWatch > Alarm > Discovery
control would go into an error state while upserting alarms into Turbot CMDB if an alarm name included special characters. This is now fixed.
5.6.0 (2022-02-16)
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.
Bug fixes
- 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.
Policy Types
Added
- AWS > CloudWatch > Alarm > Approved > Custom
5.5.0 (2022-01-06)
What's new?
AWS/CloudWatch/Metadata
AWS/CloudWatch/Operator
now include permissions for Insight Rules and Metric Stream.
5.4.0 (2021-07-19)
What's new?
AWS/Cloudwatch/Metadata
now includes get metric widget image permissions.
Control Types
Added
- AWS > CloudWatch > Stack
Policy Types
Added
- AWS > CloudWatch > Stack
- AWS > CloudWatch > Stack > Secret Variables
- AWS > CloudWatch > Stack > Source
- AWS > CloudWatch > Stack > Terraform Version
- AWS > CloudWatch > Stack > Variables
5.3.0 (2021-07-08)
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.
5.2.0 (2021-07-02)
What's new?
AWS/CloudWatch/Operator
now includes synthetic monitoring permissions.
Bug fixes
- The
AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-cloudwatch
policy no longer includesaws.tagging
as an event source. This event source was unnecessary as CloudWatch has its own tagging events, which are captured through theaws.monitoring
event source. Removal of theaws.tagging
event source will greatly reduce the number of unnecessary tagging events that Turbot listens for and handles today.
5.1.3 (2021-01-07)
Bug fixes
- We'd sometimes fail to delete alarms automatically from Turbot due to mishandled
DeleteAlarms
event. This is now fixed.
5.1.2 (2020-12-17)
Bug fixes
- Controls run faster now when in the
tbd
andskipped
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 intbd
andskipped
, resulting in faster and lighter control runs.
5.1.1 (2020-09-23)
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.
AWS > CloudWatch > Alarm > CMDB
control would go into an error state if the alarm name had acolon (:)
. This issue has now been fixed.
5.1.0 (2020-09-01)
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]
toRegions
to be consistent with our other regions policies.
5.0.5 (2020-08-11)
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.0.4 (2020-06-30)
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.0.3 (2020-05-14)
Bug fixes
- Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.