Control types for @turbot/aws-logs

• AWS > Logs > Log Group > Active
• AWS > Logs > Log Group > Approved
• AWS > Logs > Log Group > CMDB
• AWS > Logs > Log Group > Configured
• AWS > Logs > Log Group > Discovery
• AWS > Logs > Log Group > Encryption at Rest
• AWS > Logs > Log Group > Tags
• AWS > Logs > Log Group > Usage
• AWS > Logs > Log Stream > Active
• AWS > Logs > Log Stream > Approved
• AWS > Logs > Log Stream > CMDB
• AWS > Logs > Log Stream > Configured
• AWS > Logs > Log Stream > Discovery
• AWS > Logs > Log Stream > Usage
• AWS > Logs > Metric Filter > Active
• AWS > Logs > Metric Filter > Approved
• AWS > Logs > Metric Filter > CMDB
• AWS > Logs > Metric Filter > Configured
• AWS > Logs > Metric Filter > Discovery
• AWS > Logs > Metric Filter > Usage
• 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

AWS > Logs > Log Group > Active

Take an action when an AWS Logs log group is not active based on the
AWS > Logs > Log Group > 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 > Logs > Log Group > 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.

AWS > Logs > Log Group > Approved

Take an action when an AWS Logs log group is not approved based on AWS > Logs > Log Group > 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.

AWS > Logs > Log Group > CMDB

Record and synchronize details for the AWS Logs log group 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 > Logs > Log Group > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Logs > Log Group > Configured

Maintain AWS > Logs > Log Group 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.

AWS > Logs > Log Group > Discovery

Discover all AWS Logs log group 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 > Logs > Log Group > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Logs > Log Group > Encryption at Rest

Define the Encryption at Rest settings required for AWS > Logs > Log Group.

Encryption at Rest refers specifically to the encryption of data when written
to an underlying storage system. This control determines whether the resource
is encrypted at rest, and sets encryption to your desired level.

The Encryption at Rest
control compares the encryption settings against the encryption policies for the resource
(AWS > Logs > Log Group > Encryption at Rest > *),
raises an alarm, and takes the defined enforcement action.

AWS > Logs > Log Group > Tags

Take an action when an AWS Logs log group tags is not updated based on the AWS > Logs > Log Group > Tags > * policies.

If the resource is not updated with the tags defined in AWS > Logs > Log Group > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

AWS > Logs > Log Group > Usage

The Usage control determines whether the number of AWS Logs log group resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Logs > Log Group > Usage policy, and set the limit with the AWS > Logs > Log Group > Usage > Limit policy.

AWS > Logs > Log Stream > Active

Take an action when an AWS Logs log stream is not active based on the
AWS > Logs > Log Stream > 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 > Logs > Log Stream > 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.

AWS > Logs > Log Stream > Approved

Take an action when an AWS Logs log stream is not approved based on AWS > Logs > Log Stream > 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.

AWS > Logs > Log Stream > CMDB

Record and synchronize details for the AWS Logs log stream 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 > Logs > Log Stream > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Logs > Log Stream > Configured

Maintain AWS > Logs > Log Stream 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.

AWS > Logs > Log Stream > Discovery

Discover all AWS Logs log stream 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 > Logs > Log Stream > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Logs > Log Stream > Usage

The Usage control determines whether the number of AWS Logs log stream resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Logs > Log Stream > Usage policy, and set the limit with the AWS > Logs > Log Stream > Usage > Limit policy.

AWS > Logs > Metric Filter > Active

Take an action when an AWS Logs metric filter is not active based on the
AWS > Logs > Metric Filter > 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 > Logs > Metric Filter > 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.

AWS > Logs > Metric Filter > Approved

Take an action when an AWS Logs metric filter is not approved based on AWS > Logs > Metric Filter > 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.

AWS > Logs > Metric Filter > CMDB

Record and synchronize details for the AWS Logs metric filter 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 > Logs > Metric Filter > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Logs > Metric Filter > Configured

Maintain AWS > Logs > Metric Filter 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.

AWS > Logs > Metric Filter > Discovery

Discover all AWS Logs metric filter 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 > Logs > Metric Filter > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Logs > Metric Filter > Usage

The Usage control determines whether the number of AWS Logs metric filter resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Logs > Metric Filter > Usage policy, and set the limit with the AWS > Logs > Metric Filter > Usage > Limit policy.

AWS > Logs > Resource Policy > Active

Take an action when an AWS Logs resource policy is not active based on the
AWS > Logs > Resource Policy > 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 > Logs > Resource Policy > 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.

AWS > Logs > Resource Policy > Approved

Take an action when an AWS Logs resource policy is not approved based on AWS > Logs > Resource Policy > 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.

AWS > Logs > Resource Policy > CMDB

Record and synchronize details for the AWS Logs resource policy 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 > Logs > Resource Policy > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Logs > Resource Policy > Discovery

Discover all AWS Logs resource policy 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 > Logs > Resource Policy > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Logs > Resource Policy > Usage

The Usage control determines whether the number of AWS Logs resource policy resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Logs > Resource Policy > Usage policy, and set the limit with the AWS > Logs > Resource Policy > Usage > Limit policy.