Control types for @turbot/aws-events
- 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
AWS > Events > Event Bus > Active
Take an action when an AWS Events event bus is not active based on theAWS > Events > Event Bus > Active > *
policies.
The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.
The Active control checks the status of all defined Active policies for the
resource (AWS > Events > Event Bus > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.
See Active for more information.
tmod:@turbot/aws-events#/control/types/eventBusActive
AWS > Events > Event Bus > Approved
Take an action when an AWS Events event bus is not approved based on AWS > Events > Event Bus > Approved > * policies
.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
tmod:@turbot/aws-events#/control/types/eventBusApproved
AWS > Events > Event Bus > CMDB
Record and synchronize details for the AWS Events event bus into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > Events > Event Bus > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
tmod:@turbot/aws-events#/control/types/eventBusCmdb
AWS > Events > Event Bus > Configured
Maintain AWS > Events > Event Bus configuration.
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored
and inherit from the stack that owns it.
tmod:@turbot/aws-events#/control/types/eventBusConfigured
AWS > Events > Event Bus > Discovery
Discover all AWS Events event bus resources and add them to the CMDB.
The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.
Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > Events > Event Bus > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-events#/control/types/eventBusDiscovery
AWS > Events > Event Bus > Usage
The Usage control determines whether the number of AWS Events event bus resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Events > Event Bus > Usage
policy, and set the limit with the AWS > Events > Event Bus > Usage > Limit
policy.
tmod:@turbot/aws-events#/control/types/eventBusUsage
AWS > Events > Rule > Active
Configure the behavior of the
Active control for
the AWS Events rule,
based on the AWS > Events > Rule > Active > *
policies.
The Active
control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated
compliance environment, it's common to end up with a wide range of alarms
that are difficult and time consuming to clear. The Active control brings
automated, well-defined control to this process.
The Active control checks the status of all defined Active policies for the
resource (AWS > Events > Rule > Active > *
), raises an alarm, and takes the defined enforcement
action. Each Active sub-policy can calculate a status of active, inactive
or skipped. Generally, if the resource appears to be Active for any reason
it will be considered Active. Note the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.
tmod:@turbot/aws-events#/control/types/ruleActive
AWS > Events > Rule > Approved
Take an action when an AWS Events rule is not approved based on AWS > Events > Rule > Approved > * policies
.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
tmod:@turbot/aws-events#/control/types/ruleApproved
AWS > Events > Rule > CMDB
Record and synchronize details for the AWS Events rule into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > Events > Rule > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
tmod:@turbot/aws-events#/control/types/ruleCmdb
AWS > Events > Rule > Configured
Maintain AWS > Events > Rule configuration
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored
and inherit from the stack that owns it
tmod:@turbot/aws-events#/control/types/ruleConfigured
AWS > Events > Rule > Discovery
Discover all AWS Events rule resources and add them to the CMDB.
The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.
Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > Events > Rule > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-events#/control/types/ruleDiscovery
AWS > Events > Rule > Tags
Take an action when an AWS Events rule tags is not updated based on the AWS > Events > Rule > Tags > * policies
.
If the resource is not updated with the tags defined in AWS > Events > Rule > Tags > Template
, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
tmod:@turbot/aws-events#/control/types/ruleTags
AWS > Events > Rule > Usage
The Usage control determines whether the number of AWS Events rule resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Events > Rule > Usage
policy, and set the limit with the AWS > Events > Rule > Usage > Limit
policy.
tmod:@turbot/aws-events#/control/types/ruleUsage
AWS > Events > Target > Active
Take an action when an AWS Events target is not active based on theAWS > Events > Target > Active > *
policies.
The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.
The Active control checks the status of all defined Active policies for the
resource (AWS > Events > Target > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.
See Active for more information.
tmod:@turbot/aws-events#/control/types/targetActive
AWS > Events > Target > Approved
Take an action when an AWS Events target is not approved based on AWS > Events > Target > Approved > * policies
.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
tmod:@turbot/aws-events#/control/types/targetApproved
AWS > Events > Target > CMDB
Record and synchronize details for the AWS Events target into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > Events > Target > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
tmod:@turbot/aws-events#/control/types/targetCmdb
AWS > Events > Target > Configured
Maintain AWS > Events > Target configuration
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored
and inherit from the stack that owns it
tmod:@turbot/aws-events#/control/types/targetConfigured
AWS > Events > Target > Discovery
Discover all AWS Events targets resources and add them to the CMDB.
The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.
Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > Events > Target > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-events#/control/types/targetDiscovery
AWS > Events > Target > Usage
The Usage control determines whether the number of AWS Events target resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Events > Target > Usage
policy, and set the limit with the AWS > Events > Target > Usage > Limit
policy.
tmod:@turbot/aws-events#/control/types/targetUsage