Control types for @turbot/aws-emr

• AWS > EMR > Block Public Access Configuration > CMDB
• AWS > EMR > Block Public Access Configuration > Discovery
• AWS > EMR > Block Public Access Configuration > Settings
• AWS > EMR > Cluster > Active
• AWS > EMR > Cluster > Approved
• AWS > EMR > Cluster > CMDB
• AWS > EMR > Cluster > Discovery
• AWS > EMR > Cluster > Tags
• AWS > EMR > Cluster > Usage
• AWS > EMR > Security Configuration > Active
• AWS > EMR > Security Configuration > Approved
• AWS > EMR > Security Configuration > CMDB
• AWS > EMR > Security Configuration > Discovery
• AWS > EMR > Security Configuration > Usage

AWS > EMR > Block Public Access Configuration > CMDB

Record and synchronize details for the AWS EMR block public access configuration 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 > EMR > Block Public Access Configuration > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > EMR > Block Public Access Configuration > Discovery

Discover all AWS EMR block public access configuration 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 > EMR > Block Public Access Configuration > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > EMR > Block Public Access Configuration > Settings

This control, if configured, prevents launching an EMR cluster if any of the cluster's security groups have a rule that allows inbound traffic from all public addresses (IPv4 0.0.0.0/0 or IPv6 ::/0). This applies to all the clusters in the current region.

AWS > EMR > Cluster > Active

Take an action when an AWS EMR cluster is not active based on the
AWS > EMR > Cluster > 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 > EMR > Cluster > 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 > EMR > Cluster > Approved

Take an action when an AWS EMR cluster is not approved based on AWS > EMR > Cluster > 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 > EMR > Cluster > CMDB

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

AWS > EMR > Cluster > Discovery

Discover all AWS EMR cluster 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 > EMR > Cluster > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > EMR > Cluster > Tags

Take an action when an AWS EMR cluster tags is not updated based on the AWS > EMR > Cluster > Tags > * policies.

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

See Tags for more information.

AWS > EMR > Cluster > Usage

The Usage control determines whether the number of AWS EMR cluster resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > EMR > Cluster > Usage policy, and set the limit with the AWS > EMR > Cluster > Usage > Limit policy.

AWS > EMR > Security Configuration > Active

Take an action when an AWS EMR security configuration is not active based on the
AWS > EMR > Security Configuration > 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 > EMR > Security Configuration > 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 > EMR > Security Configuration > Approved

Take an action when an AWS EMR security configuration is not approved based on AWS > EMR > Security Configuration > 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 > EMR > Security Configuration > CMDB

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

AWS > EMR > Security Configuration > Discovery

Discover all AWS EMR security configuration 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 > EMR > Security Configuration > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > EMR > Security Configuration > Usage

The Usage control determines whether the number of AWS EMR security configuration resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > EMR > Security Configuration > Usage policy, and set the limit with the AWS > EMR > Security Configuration > Usage > Limit policy.