Control types for @turbot/aws-efs

AWS > EFS > FileSystem > Active

Take an action when an AWS EFS filesystem is not active based on the\nAWS > EFS > FileSystem > Active > * policies.\n\nThe Active control determines whether the resource is in active use, and if not, has\nthe ability to delete / cleanup the resource. When running an automated compliance\nenvironment, it's common to end up with a wide range of alarms that are difficult\nand time consuming to clear. The Active control brings automated, well-defined\ncontrol to this process.\n\nThe Active control checks the status of all defined Active policies for the\nresource (AWS > EFS > FileSystem > Active > *),\nraises an alarm, and takes the defined enforcement action. Each Active\nsub-policy can calculate a status of active, inactive or skipped. Generally,\nif the resource appears to be Active for any reason it will be considered Active.\n\nNote the contrast with Approved, where if the resource appears to be Unapproved\nfor any reason it will be considered Unapproved.\n\nSee Active for more information.\n

URI
tmod:@turbot/aws-efs#/control/types/fileSystemActive

AWS > EFS > FileSystem > Approved

Take an action when an AWS EFS filesystem is not approved based on AWS > EFS > FileSystem > Approved > * policies.\n\nThe 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.\n\nFor 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.\n\nSee Approved for more information.\n

URI
tmod:@turbot/aws-efs#/control/types/fileSystemApproved

AWS > EFS > FileSystem > CMDB

Record and synchronize details for the AWS EFS filesystem into the CMDB.\n\nThe CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.\n\nIf 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.\n\nTo cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".\n\nCMDB controls also use the Regions policy associated with the resource. If region is not in AWS > EFS > FileSystem > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n

URI
tmod:@turbot/aws-efs#/control/types/fileSystemCmdb
Category

AWS > EFS > FileSystem > Discovery

Discover all AWS EFS filesystem resources and add them to the CMDB.\n\nThe 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.\n\nNote that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > EFS > FileSystem > Regions policy, the CMDB control will delete the resource from the CMDB.\n

URI
tmod:@turbot/aws-efs#/control/types/fileSystemDiscovery

AWS > EFS > FileSystem > Tags

Take an action when an AWS EFS filesystem tags is not updated based on the AWS > EFS > FileSystem > Tags > * policies.\n\nIf the resource is not updated with the tags defined in AWS > EFS > FileSystem > Tags > Template, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n

URI
tmod:@turbot/aws-efs#/control/types/fileSystemTags

AWS > EFS > FileSystem > Usage

The Usage control determines whether the number of AWS EFS filesystem resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > EFS > FileSystem > Usage policy, and set the limit with the AWS > EFS > FileSystem > Usage > Limit policy.\n

URI
tmod:@turbot/aws-efs#/control/types/fileSystemUsage

AWS > EFS > Mount Target > Active

Take an action when an AWS EFS mount target is not active based on the\nAWS > EFS > Mount Target > Active > * policies.\n\nThe Active control determines whether the resource is in active use, and if not, has\nthe ability to delete / cleanup the resource. When running an automated compliance\nenvironment, it's common to end up with a wide range of alarms that are difficult\nand time consuming to clear. The Active control brings automated, well-defined\ncontrol to this process.\n\nThe Active control checks the status of all defined Active policies for the\nresource (AWS > EFS > Mount Target > Active > *),\nraises an alarm, and takes the defined enforcement action. Each Active\nsub-policy can calculate a status of active, inactive or skipped. Generally,\nif the resource appears to be Active for any reason it will be considered Active.\n\nNote the contrast with Approved, where if the resource appears to be Unapproved\nfor any reason it will be considered Unapproved.\n\nSee Active for more information.\n

URI
tmod:@turbot/aws-efs#/control/types/mountTargetActive

AWS > EFS > Mount Target > Approved

Take an action when an AWS EFS mount target is not approved based on AWS > EFS > Mount Target > Approved > * policies.\n\nThe 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.\n\nFor 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.\n\nSee Approved for more information.\n

URI
tmod:@turbot/aws-efs#/control/types/mountTargetApproved

AWS > EFS > Mount Target > CMDB

Record and synchronize details for the AWS EFS mount target into the CMDB.\n\nThe CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.\n\nIf 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.\n\nTo cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".\n\nCMDB controls also use the Regions policy associated with the resource. If region is not in AWS > EFS > Mount Target > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n

URI
tmod:@turbot/aws-efs#/control/types/mountTargetCmdb
Category

AWS > EFS > Mount Target > Discovery

Discover all AWS EFS mount target resources and add them to the CMDB.\n\nThe 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.\n\nNote that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > EFS > Mount Target > Regions policy, the CMDB control will delete the resource from the CMDB.\n

URI
tmod:@turbot/aws-efs#/control/types/mountTargetDiscovery

AWS > EFS > Mount Target > Usage

The Usage control determines whether the number of AWS EFS mount target resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > EFS > Mount Target > Usage policy, and set the limit with the AWS > EFS > Mount Target > Usage > Limit policy.\n

URI
tmod:@turbot/aws-efs#/control/types/mountTargetUsage