Control types for @turbot/aws-ecr
- AWS > ECR > Image > Active
- AWS > ECR > Image > Approved
- AWS > ECR > Image > CMDB
- AWS > ECR > Image > Discovery
- AWS > ECR > Image > Usage
- AWS > ECR > Private Registry > CMDB
- AWS > ECR > Private Registry > Discovery
- AWS > ECR > Private Registry > Scanning Configuration
- AWS > ECR > Public Repository > Active
- AWS > ECR > Public Repository > Approved
- AWS > ECR > Public Repository > CMDB
- AWS > ECR > Public Repository > Discovery
- AWS > ECR > Public Repository > Tags
- AWS > ECR > Public Repository > Usage
- AWS > ECR > Repository > Active
- AWS > ECR > Repository > Approved
- AWS > ECR > Repository > CMDB
- AWS > ECR > Repository > Discovery
- AWS > ECR > Repository > Scan on Push
- AWS > ECR > Repository > Tags
- AWS > ECR > Repository > Usage
AWS > ECR > Image > Active
Take an action when an AWS ECR image is not active based on the\nAWS > ECR > Image > 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 > ECR > Image > 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
AWS > ECR > Image > Approved
Take an action when an AWS ECR image is not approved based on AWS > ECR > Image > 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
AWS > ECR > Image > CMDB
Record and synchronize details for the AWS ECR image 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 > ECR > Image > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > ECR > Image > Discovery
Discover all AWS ECR image 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 > ECR > Image > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > ECR > Image > Usage
The Usage control determines whether the number of AWS ECR image resources exceeds the configured usage limit for this repository.\n\nYou can configure the behavior of this control with the AWS > ECR > Image > Usage
policy, and set the limit with the AWS > ECR > Image > Usage > Limit
policy.\n
AWS > ECR > Private Registry > CMDB
Record and synchronize details for the AWS ECR private registry 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 > ECR > Private Registry > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > ECR > Private Registry > Discovery
Discover all AWS ECR private registry resources and add them to the CMDB.\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.\nNote that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > ECR > Private Registry > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > ECR > Private Registry > Scanning Configuration
Define the Scanning Configuration settings required for AWS > ECR > Private Registry
.\n\nThe Scanning configuration determines the type of scanning performed on the contents of repositories.\n\nNote: Enforcing Basic or Enhanced Scanning on a Private Registry via this control with AWS > ECR > Private Registry > Scanning Configuration > *
policies set to an empty array ([]
) will remove all existing Scanning Configuration filters on the Private Registry.\n
AWS > ECR > Public Repository > Active
Take an action when an AWS ECR public repository is not active based on the\nAWS > ECR > Public Repository > 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 > ECR > Public Repository > 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
AWS > ECR > Public Repository > Approved
Take an action when an AWS ECR public repository is not approved based on AWS > ECR > Public Repository > 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
AWS > ECR > Public Repository > CMDB
Record and synchronize details for the AWS ECR public repository 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
AWS > ECR > Public Repository > Discovery
Discover all AWS ECR public repository 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
AWS > ECR > Public Repository > Tags
Take an action when an AWS ECR public repository tags is not updated based on the AWS > ECR > Public Repository > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > ECR > Public Repository > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > ECR > Public Repository > Usage
The Usage control determines whether the number of AWS ECR public repository resources exceeds the configured usage limit for this account.\n\nYou can configure the behavior of this control with the AWS > ECR > Public Repository > Usage
policy, and set the limit with the AWS > ECR > Public Repository > Usage > Limit
policy.\n
AWS > ECR > Repository > Active
Take an action when an AWS ECR repository is not active based on the\nAWS > ECR > Repository > 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 > ECR > Repository > 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
AWS > ECR > Repository > Approved
Take an action when an AWS ECR repository is not approved based on AWS > ECR > Repository > 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
AWS > ECR > Repository > CMDB
Record and synchronize details for the AWS ECR repository 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 > ECR > Repository > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > ECR > Repository > Discovery
Discover all AWS ECR repository 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 > ECR > Repository > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > ECR > Repository > Scan on Push
Configure the Scan on Push setting required for AWS > ECR > Repository
.\nThis setting determines whether images are scanned after being pushed to the repository.\n
AWS > ECR > Repository > Tags
Take an action when an AWS ECR repository tags is not updated based on the AWS > ECR > Repository > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > ECR > Repository > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > ECR > Repository > Usage
The Usage control determines whether the number of AWS ECR repository resources exceeds the configured usage limit for this account.\n\nYou can configure the behavior of this control with the AWS > ECR > Repository > Usage
policy, and set the limit with the AWS > ECR > Repository > Usage > Limit
policy.\n