@turbot/aws-events
The aws-events mod contains resource, control and policy definitions for AWS Events service.
- Setting Policies Tutorial
- Mods Overview
- Policies Overview
- Resources Overview
- Common Policies and Controls
Recommended Version
Resource Types
Control Types
- AWS > Events > Event Bus > Active
- AWS > Events > Event Bus > Approved
- AWS > Events > Event Bus > CMDB
- AWS > Events > Event Bus > Configured
- AWS > Events > Event Bus > Discovery
- AWS > Events > Event Bus > Usage
- AWS > Events > Rule > Active
- AWS > Events > Rule > Approved
- AWS > Events > Rule > CMDB
- AWS > Events > Rule > Configured
- AWS > Events > Rule > Discovery
- AWS > Events > Rule > Tags
- AWS > Events > Rule > Usage
- AWS > Events > Target > Active
- AWS > Events > Target > Approved
- AWS > Events > Target > CMDB
- AWS > Events > Target > Configured
- AWS > Events > Target > Discovery
- AWS > Events > Target > Usage
Policy Types
- AWS > Events > API Enabled
- AWS > Events > Approved Regions [Default]
- AWS > Events > Enabled
- AWS > Events > Event Bus > Active
- AWS > Events > Event Bus > Active > Age
- AWS > Events > Event Bus > Active > Last Modified
- AWS > Events > Event Bus > Approved
- AWS > Events > Event Bus > Approved > Custom
- AWS > Events > Event Bus > Approved > Regions
- AWS > Events > Event Bus > Approved > Usage
- AWS > Events > Event Bus > CMDB
- AWS > Events > Event Bus > Configured
- AWS > Events > Event Bus > Configured > Claim Precedence
- AWS > Events > Event Bus > Configured > Source
- AWS > Events > Event Bus > Regions
- AWS > Events > Event Bus > Usage
- AWS > Events > Event Bus > Usage > Limit
- AWS > Events > Permissions
- AWS > Events > Permissions > Levels
- AWS > Events > Permissions > Levels > Modifiers
- AWS > Events > Permissions > Lockdown
- AWS > Events > Permissions > Lockdown > API Boundary
- AWS > Events > Regions
- AWS > Events > Rule > Active
- AWS > Events > Rule > Active > Age
- AWS > Events > Rule > Active > Last Modified
- AWS > Events > Rule > Active > Status
- AWS > Events > Rule > Approved
- AWS > Events > Rule > Approved > Custom
- AWS > Events > Rule > Approved > Regions
- AWS > Events > Rule > Approved > Usage
- AWS > Events > Rule > CMDB
- AWS > Events > Rule > Configured
- AWS > Events > Rule > Configured > Claim Precedence
- AWS > Events > Rule > Configured > Source
- AWS > Events > Rule > Regions
- AWS > Events > Rule > Tags
- AWS > Events > Rule > Tags > Template
- AWS > Events > Rule > Usage
- AWS > Events > Rule > Usage > Limit
- AWS > Events > Tags Template [Default]
- AWS > Events > Target > Active
- AWS > Events > Target > Active > Age
- AWS > Events > Target > Active > Last Modified
- AWS > Events > Target > Approved
- AWS > Events > Target > Approved > Custom
- AWS > Events > Target > Approved > Regions
- AWS > Events > Target > Approved > Usage
- AWS > Events > Target > CMDB
- AWS > Events > Target > Configured
- AWS > Events > Target > Configured > Claim Precedence
- AWS > Events > Target > Configured > Source
- AWS > Events > Target > Regions
- AWS > Events > Target > Usage
- AWS > Events > Target > Usage > Limit
- AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-events
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-events
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-events
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-events
Release Notes
5.12.0 (2023-10-30)
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.
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 > Events > Rule > Skip alarm for Approved control
- AWS > Events > Rule > Skip alarm for Approved control [90 days]
- AWS > Events > Target > Skip alarm for Active control
- AWS > Events > Target > Skip alarm for Active control [90 days]
- AWS > Events > Target > Skip alarm for Approved control
- AWS > Events > Target > Skip alarm for Approved control [90 days]
5.11.0 (2023-06-01)
What's new?
- Resource's metadata will now also include
createdBy
details in Guardrails CMDB. - README.md file is now available for users to check details about the resource types and service permissions that the mod covers.
5.10.0 (2023-03-03)
Resource Types
- AWS > Events > Event Bus
Control Types
- AWS > Events > Event Bus > Active
- AWS > Events > Event Bus > Approved
- AWS > Events > Event Bus > CMDB
- AWS > Events > Event Bus > Configured
- AWS > Events > Event Bus > Discovery
- AWS > Events > Event Bus > Usage
Policy Types
- AWS > Events > Event Bus > Active
- AWS > Events > Event Bus > Active > Age
- AWS > Events > Event Bus > Active > Last Modified
- AWS > Events > Event Bus > Approved
- AWS > Events > Event Bus > Approved > Custom
- AWS > Events > Event Bus > Approved > Regions
- AWS > Events > Event Bus > Approved > Usage
- AWS > Events > Event Bus > CMDB
- AWS > Events > Event Bus > Configured
- AWS > Events > Event Bus > Configured > Claim Precedence
- AWS > Events > Event Bus > Configured > Source
- AWS > Events > Event Bus > Regions
- AWS > Events > Event Bus > Usage
- AWS > Events > Event Bus > Usage > Limit
Action Types
- AWS > Events > Event Bus > Delete
- AWS > Events > Event Bus > Delete from AWS
- AWS > Events > Event Bus > Router
- AWS > Events > Event Bus > Skip alarm for Active control
- AWS > Events > Event Bus > Skip alarm for Active control [90 days]
- AWS > Events > Event Bus > Skip alarm for Approved control
- AWS > Events > Event Bus > Skip alarm for Approved control [90 days]
5.9.1 (2022-09-12)
Bug fixes
- We’ve made a few GraphQL query improvements in the router action and they will now be lighter and more reliable. You won’t notice any difference but things will now run quicker and smoother than before.
5.9.0 (2022-04-01)
What's new?
AWS/Events/Admin
,AWS/Events/Metadata
andAWS/Events/Operator
now includesschemas:*
permissions.
5.8.1 (2022-03-22)
Bug fixes
- The
AWS > Events > Target > Discovery
control would incorrectly remain in an OK state even when theAWS > Events > Target > CMDB
policy was set toEnforce: Disabled
. This is fixed and the control will now move to a skipped State.
5.8.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 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.
Policy Types
- AWS > Events > Rule > Approved > Custom
- AWS > Events > Target > Approved > Custom
5.7.0 (2022-01-13)
Control Types
- AWS > Events > Rule > Tags
Policy Types
- AWS > Events > Rule > Tags
- AWS > Events > Rule > Tags > Template
- AWS > Events > Tags Template [Default]
Action Types
- AWS > Events > Rule > Update Tags
5.6.0 (2022-01-06)
What's new?
AWS/Events/Admin
AWS/Events/Metadata
now include permissions for Replay, Api Destination, Archive and Connection.
5.5.1 (2021-08-27)
Bug fixes
- We've made a few improvements in the GraphQL queries for various router actions. You won't notice any difference, but things should run lighter and quicker than before.
5.5.0 (2021-06-24)
What's new?
AWS/Events/Admin
now includes event source, partner event source, and event bus permissions.AWS/Events/Operator
now includes put partner events permissions.
5.4.4 (2021-05-05)
Bug fixes
- We've updated the
AWS > Events > Rule > Discovery
control to sort theEventPattern.source
andEventPattern.detail.eventName
properties in the same way theAWS > Events > Rule > CMDB
control sorts them to ensure rules' CMDB data remains consistent.
5.4.3 (2021-03-05)
What's new?
- Users now can cleanup resources and stop tracking changes in the
AWS > Events > Target
resource type by setting theAWS > Events > Target > CMDB
policy toEnforce: Disabled
.
5.4.2 (2020-12-07)
Bug fixes
- We've optimized the GraphQL queries for various controls when they're in the
tbd
andskipped
states. You won't notice any difference but they should run a lot lighter now.
5.4.1 (2020-12-04)
Bug fixes
- We've updated various resources' Discovery and CMDB controls to ensure array properties are consistently sorted in the CMDB.
5.4.0 (2020-10-07)
What's new?
- We've renamed the service's default regions policy from
Regions [Default]
toRegions
to be consistent with our other regions policies.
Policy Types
Renamed
- AWS > Events > Regions [Default] to AWS > Events > Regions
5.3.1 (2020-09-15)
Bug fixes
- While formatting the
EventPattern
field of rule resources, the corresponding CMDB control would throw errors. This issue has been fixed and now we efficiently format data without errors.
5.3.0 (2020-09-04)
What's new?
- Discovery controls now have their own control category,
CMDB > Discovery
, to allow for easier filtering separately from other CMDB controls.
5.2.1 (2020-08-12)
Bug fixes
- The
EventPattern
field for rule resources is now properly and consistently formatted.
5.2.0 (2020-07-31)
What's new?
AWS/Events/Admin
now includes permissions which can be used for either allowing or denying specified AWS account to put events to the specified event bus.
5.1.2 (2020-07-06)
Bug fixes
- Updated various resource configurations to provide better compatibility with AWS China regions.
Policy Types
Renamed
- AWS > Events > Rule > Configured > Precedence to AWS > Events > Rule > Configured > Claim Precedence
- AWS > Events > Target > Configured > Precedence to AWS > Events > Target > Configured > Claim Precedence