Control types for @turbot/aws-ecs

• AWS > ECS > Cluster > Active
• AWS > ECS > Cluster > Approved
• AWS > ECS > Cluster > CMDB
• AWS > ECS > Cluster > Configured
• AWS > ECS > Cluster > Discovery
• AWS > ECS > Cluster > Tags
• AWS > ECS > Cluster > Usage
• AWS > ECS > Container Instance > Active
• AWS > ECS > Container Instance > Approved
• AWS > ECS > Container Instance > CMDB
• AWS > ECS > Container Instance > Discovery
• AWS > ECS > Container Instance > Usage
• AWS > ECS > Service > Active
• AWS > ECS > Service > Approved
• AWS > ECS > Service > CMDB
• AWS > ECS > Service > Discovery
• AWS > ECS > Service > Tags
• AWS > ECS > Task Definition > Active
• AWS > ECS > Task Definition > Approved
• AWS > ECS > Task Definition > CMDB
• AWS > ECS > Task Definition > Configured
• AWS > ECS > Task Definition > Discovery
• AWS > ECS > Task Definition > Tags
• AWS > ECS > Task Definition > Usage

AWS > ECS > Cluster > Active

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

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

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

AWS > ECS > Cluster > Configured

Maintain AWS > ECS > Cluster 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 > ECS > Cluster > Discovery

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

AWS > ECS > Cluster > Tags

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

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

See Tags for more information.

AWS > ECS > Cluster > Usage

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

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

AWS > ECS > Container Instance > Active

Take an action when an AWS ECS container instance is not active based on the
AWS > ECS > Container Instance > 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 > ECS > Container Instance > 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 > ECS > Container Instance > Approved

Take an action when an AWS ECS container instance is not approved based on AWS > ECS > Container Instance > 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 > ECS > Container Instance > CMDB

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

AWS > ECS > Container Instance > Discovery

Discover all AWS ECS container instance 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 > ECS > Container Instance > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > ECS > Container Instance > Usage

The Usage control determines whether the number of AWS ECS container instance resources exceeds the configured usage limit for this account.

You can configure the behavior of this control with the AWS > ECS > Container Instance > Usage policy, and set the limit with the AWS > ECS > Container Instance > Usage > Limit policy.

AWS > ECS > Service > Active

Take an action when an AWS ECS service is not active based on the
AWS > ECS > Service > 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 > ECS > Service > 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 > ECS > Service > Approved

Take an action when an AWS ECS service is not approved based on AWS > ECS > Service > 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 > ECS > Service > CMDB

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

AWS > ECS > Service > Discovery

Discover all AWS ECS service 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 > ECS > Service > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > ECS > Service > Tags

Take an action when an AWS ECS service tags is not updated based on the AWS > ECS > Service > Tags > * policies.

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

See Tags for more information.

AWS > ECS > Task Definition > Active

Take an action when an AWS ECS task definition is not active based on the
AWS > ECS > Task Definition > 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 > ECS > Task Definition > 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 > ECS > Task Definition > Approved

Take an action when an AWS ECS task definition is not approved based on AWS > ECS > Task Definition > 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 > ECS > Task Definition > CMDB

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

AWS > ECS > Task Definition > Configured

Maintain AWS > ECS > Task Definition 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 > ECS > Task Definition > Discovery

Discover all AWS ECS task definition 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 > ECS > Task Definition > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > ECS > Task Definition > Tags

Take an action when an AWS ECS task definition tags is not updated based on the AWS > ECS > Task Definition > Tags > * policies.

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

See Tags for more information.

AWS > ECS > Task Definition > Usage

The Usage control determines whether the number of AWS ECS task definition resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > ECS > Task Definition > Usage policy, and set the limit with the AWS > ECS > Task Definition > Usage > Limit policy.