Control types for @turbot/aws-rds
- AWS > RDS > DB Cluster > Active
- AWS > RDS > DB Cluster > Approved
- AWS > RDS > DB Cluster > Backup Retention Period
- AWS > RDS > DB Cluster > CMDB
- AWS > RDS > DB Cluster > Configured
- AWS > RDS > DB Cluster > Copy Tags to Snapshot
- AWS > RDS > DB Cluster > Deletion Protection
- AWS > RDS > DB Cluster > Discovery
- AWS > RDS > DB Cluster > Logs Export Configuration
- AWS > RDS > DB Cluster > Schedule
- AWS > RDS > DB Cluster > Tags
- AWS > RDS > DB Cluster > Usage
- AWS > RDS > DB Cluster Parameter Group > Active
- AWS > RDS > DB Cluster Parameter Group > Approved
- AWS > RDS > DB Cluster Parameter Group > CMDB
- AWS > RDS > DB Cluster Parameter Group > Configured
- AWS > RDS > DB Cluster Parameter Group > Discovery
- AWS > RDS > DB Cluster Parameter Group > Tags
- AWS > RDS > DB Cluster Parameter Group > Usage
- AWS > RDS > DB Cluster Snapshot [Manual] > Active
- AWS > RDS > DB Cluster Snapshot [Manual] > Approved
- AWS > RDS > DB Cluster Snapshot [Manual] > CMDB
- AWS > RDS > DB Cluster Snapshot [Manual] > Configured
- AWS > RDS > DB Cluster Snapshot [Manual] > Discovery
- AWS > RDS > DB Cluster Snapshot [Manual] > Tags
- AWS > RDS > DB Cluster Snapshot [Manual] > Trusted Access
- AWS > RDS > DB Cluster Snapshot [Manual] > Usage
- AWS > RDS > DB Instance > Active
- AWS > RDS > DB Instance > Approved
- AWS > RDS > DB Instance > Auto Minor Version Upgrade
- AWS > RDS > DB Instance > Backup Retention Period
- AWS > RDS > DB Instance > CMDB
- AWS > RDS > DB Instance > Configured
- AWS > RDS > DB Instance > Copy Tags to Snapshot
- AWS > RDS > DB Instance > Deletion Protection
- AWS > RDS > DB Instance > Discovery
- AWS > RDS > DB Instance > Logs Export Configuration
- AWS > RDS > DB Instance > Multi-AZ
- AWS > RDS > DB Instance > Parameter Group
- AWS > RDS > DB Instance > Performance Insights
- AWS > RDS > DB Instance > Publicly Accessible
- AWS > RDS > DB Instance > Schedule
- AWS > RDS > DB Instance > Tags
- AWS > RDS > DB Instance > Usage
- AWS > RDS > DB Parameter Group > Active
- AWS > RDS > DB Parameter Group > Approved
- AWS > RDS > DB Parameter Group > CMDB
- AWS > RDS > DB Parameter Group > Configured
- AWS > RDS > DB Parameter Group > Discovery
- AWS > RDS > DB Parameter Group > Tags
- AWS > RDS > DB Parameter Group > Usage
- AWS > RDS > DB Snapshot [Manual] > Active
- AWS > RDS > DB Snapshot [Manual] > Approved
- AWS > RDS > DB Snapshot [Manual] > CMDB
- AWS > RDS > DB Snapshot [Manual] > Configured
- AWS > RDS > DB Snapshot [Manual] > Discovery
- AWS > RDS > DB Snapshot [Manual] > Tags
- AWS > RDS > DB Snapshot [Manual] > Trusted Access
- AWS > RDS > DB Snapshot [Manual] > Usage
- AWS > RDS > Global Cluster > Active
- AWS > RDS > Global Cluster > Approved
- AWS > RDS > Global Cluster > CMDB
- AWS > RDS > Global Cluster > Discovery
- AWS > RDS > Option Group > Active
- AWS > RDS > Option Group > Approved
- AWS > RDS > Option Group > CMDB
- AWS > RDS > Option Group > Configured
- AWS > RDS > Option Group > Discovery
- AWS > RDS > Option Group > Tags
- AWS > RDS > Option Group > Usage
- AWS > RDS > Stack
- AWS > RDS > Subnet Group > Active
- AWS > RDS > Subnet Group > Approved
- AWS > RDS > Subnet Group > CMDB
- AWS > RDS > Subnet Group > Configured
- AWS > RDS > Subnet Group > Discovery
- AWS > RDS > Subnet Group > Tags
- AWS > RDS > Subnet Group > Usage
AWS > RDS > DB Cluster > Active
Take an action when an AWS RDS db cluster is not active based on the\nAWS > RDS > DB Cluster > 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 > RDS > DB Cluster > 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 > RDS > DB Cluster > Approved
Take an action when an AWS RDS db cluster is not approved based on AWS > RDS > DB Cluster > 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 > RDS > DB Cluster > Backup Retention Period
Raise an alarm if the RDS cluster's backup retention period is not configured to meet policy.\n
AWS > RDS > DB Cluster > CMDB
Record and synchronize details for the AWS RDS db cluster 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 > RDS > DB Cluster > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > RDS > DB Cluster > Configured
Maintain AWS > RDS > DB Cluster configuration\n\nNote: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored\nand inherit from the stack that owns it\n
AWS > RDS > DB Cluster > Copy Tags to Snapshot
Configure Copy Tags to Snapshot settings on an AWS > RDS > DB Cluster
.\n
AWS > RDS > DB Cluster > Deletion Protection
Configure Deletion Protection settings on an AWS > RDS > DB Cluster
.\n
AWS > RDS > DB Cluster > Discovery
Discover all AWS RDS db cluster 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 > RDS > DB Cluster > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > RDS > DB Cluster > Logs Export Configuration
Configure logs export to CloudWatch for an AWS > RDS > DB Cluster
as per the AWS > RDS > DB Cluster > Logs Export Configuration > *
policies.\n
AWS > RDS > DB Cluster > Schedule
Set a schedule for starting and stopping an AWS RDS db cluster.\n\nNote If both "Schedule" and "Schedule Tag" are set to enforce and the\ndb cluster has a turbot_custom_schedule tag, then the schedule specified by\nthe tag will be in effect.\n
AWS > RDS > DB Cluster > Tags
Take an action when an AWS RDS db cluster tags is not updated based on the AWS > RDS > DB Cluster > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > RDS > DB Cluster > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > RDS > DB Cluster > Usage
The Usage control determines whether the number of AWS RDS db cluster resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > RDS > DB Cluster > Usage
policy, and set the limit with the AWS > RDS > DB Cluster > Usage > Limit
policy.\n
AWS > RDS > DB Cluster Parameter Group > Active
Take an action when an AWS RDS db cluster parameter group is not active based on the\nAWS > RDS > DB Cluster Parameter Group > 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 > RDS > DB Cluster Parameter Group > 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 > RDS > DB Cluster Parameter Group > Approved
Take an action when an AWS RDS db cluster parameter group is not approved based on AWS > RDS > DB Cluster Parameter Group > 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 > RDS > DB Cluster Parameter Group > CMDB
Record and synchronize details for the AWS RDS db cluster parameter group 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 > RDS > DB Cluster Parameter Group > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > RDS > DB Cluster Parameter Group > Configured
Maintain AWS > RDS > DB Cluster Parameter Group configuration\n\nNote: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored\nand inherit from the stack that owns it\n
AWS > RDS > DB Cluster Parameter Group > Discovery
Discover all AWS RDS db cluster parameter group 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 > RDS > DB Cluster Parameter Group > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > RDS > DB Cluster Parameter Group > Tags
Take an action when an AWS RDS db cluster parameter group tags is not updated based on the AWS > RDS > DB Cluster Parameter Group > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > RDS > DB Cluster Parameter Group > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > RDS > DB Cluster Parameter Group > Usage
The Usage control determines whether the number of AWS RDS db cluster parameter group resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > RDS > DB Cluster Parameter Group > Usage
policy, and set the limit with the AWS > RDS > DB Cluster Parameter Group > Usage > Limit
policy.\n
AWS > RDS > DB Cluster Snapshot [Manual] > Active
Take an action when an AWS RDS db cluster snapshot [manual] is not active based on the\nAWS > RDS > DB Cluster Snapshot [Manual] > 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 > RDS > DB Cluster Snapshot [Manual] > 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 > RDS > DB Cluster Snapshot [Manual] > Approved
Take an action when an AWS RDS db cluster snapshot [manual] is not approved based on AWS > RDS > DB Cluster Snapshot [Manual] > 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 > RDS > DB Cluster Snapshot [Manual] > CMDB
Record and synchronize details for the AWS RDS db cluster snapshot [manual] 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 > RDS > DB Cluster Snapshot [Manual] > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > RDS > DB Cluster Snapshot [Manual] > Configured
Maintain AWS > RDS > DB Cluster Snapshot [Manual] configuration\n\nNote: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored\nand inherit from the stack that owns it\n
AWS > RDS > DB Cluster Snapshot [Manual] > Discovery
Discover all AWS RDS db cluster snapshot [manual] 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 > RDS > DB Cluster Snapshot [Manual] > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > RDS > DB Cluster Snapshot [Manual] > Tags
Take an action when an AWS RDS db cluster snapshot [manual] tags is not updated based on the AWS > RDS > DB Cluster Snapshot [Manual] > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > RDS > DB Cluster Snapshot [Manual] > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > RDS > DB Cluster Snapshot [Manual] > Trusted Access
Manage trusted access for AWS RDS DB Cluster Snapshot [Manual]s.\n\nAWS allows RDS DB Cluster Snapshot [Manual]s to be shared with specific AWS accounts.\nThis control allows you to configure whether such sharing is allowed, and to which accounts.\n\nIf set to Enforce
, access to non-trusted accounts will be removed.\n
AWS > RDS > DB Cluster Snapshot [Manual] > Usage
The Usage control determines whether the number of AWS RDS db cluster snapshot [manual] resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > RDS > DB Cluster Snapshot [Manual] > Usage
policy, and set the limit with the AWS > RDS > DB Cluster Snapshot [Manual] > Usage > Limit
policy.\n
AWS > RDS > DB Instance > Active
Take an action when an AWS RDS db instance is not active based on the\nAWS > RDS > DB Instance > 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 > RDS > DB Instance > 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 > RDS > DB Instance > Approved
Take an action when an AWS RDS db instance is not approved based on AWS > RDS > DB Instance > 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\nSee Approved for more information.\n
AWS > RDS > DB Instance > Auto Minor Version Upgrade
Configure Auto Minor Version Upgrade settings on an AWS > RDS > DB Instance
.\n
AWS > RDS > DB Instance > Backup Retention Period
Raise an alarm if the RDS instance's backup retention period is not configured to meet policy.\n
AWS > RDS > DB Instance > CMDB
Record and synchronize details for the AWS RDS db instance 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 > RDS > DB Instance > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > RDS > DB Instance > Configured
Maintain AWS > RDS > DB Instance configuration\n\nNote: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored\nand inherit from the stack that owns it\n
AWS > RDS > DB Instance > Copy Tags to Snapshot
Configure Copy Tags to Snapshot settings on an AWS > RDS > DB Instance
.\n
AWS > RDS > DB Instance > Deletion Protection
Configure Deletion Protection settings on an AWS > RDS > DB Instance
.\n
AWS > RDS > DB Instance > Discovery
Discover all AWS RDS db instance 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 > RDS > DB Instance > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > RDS > DB Instance > Logs Export Configuration
Configure logs export to CloudWatch for an AWS > RDS > DB Instance
as per the AWS > RDS > DB Instance > Logs Export Configuration > *
policies.\n
AWS > RDS > DB Instance > Multi-AZ
Configure Multi-AZ deployment settings on an AWS > RDS > DB Instance
.\n
AWS > RDS > DB Instance > Parameter Group
Determine whether to check or enforce a specific Parameter Group for this DB Instance.\n\nUse the Parameter Group > Name
sub-policy to set which Parameter Group to configure for this instance.\n
AWS > RDS > DB Instance > Performance Insights
Configure performance insights settings for an AWS > RDS > DB Instance
as per the AWS > RDS > DB Instance > Performance Insights > *
policies.\n
AWS > RDS > DB Instance > Publicly Accessible
Ensure the RDS instance is not publicly accessible.
AWS > RDS > DB Instance > Schedule
Set a schedule for starting and stopping an AWS RDS db instance.\n\nNote If both "Schedule" and "Schedule Tag" are set to enforce and the\ndb instance has a turbot_custom_schedule tag, then the schedule specified by\nthe tag will be in effect.\n
AWS > RDS > DB Instance > Tags
Take an action when an AWS RDS db instance tags is not updated based on the AWS > RDS > DB Instance > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > RDS > DB Instance > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > RDS > DB Instance > Usage
The Usage control determines whether the number of AWS RDS db instance resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > RDS > DB Instance > Usage
policy, and set the limit with the AWS > RDS > DB Instance > Usage > Limit
policy.\n
AWS > RDS > DB Parameter Group > Active
Take an action when an AWS RDS db parameter group is not active based on the\nAWS > RDS > DB Parameter Group > 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 > RDS > DB Parameter Group > 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 > RDS > DB Parameter Group > Approved
Take an action when an AWS RDS db parameter group is not approved based on AWS > RDS > DB Parameter Group > 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 > RDS > DB Parameter Group > CMDB
Record and synchronize details for the AWS RDS db parameter group 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 > RDS > DB Parameter Group > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > RDS > DB Parameter Group > Configured
Maintain AWS > RDS > DB Parameter Group configuration\n\nNote: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored\nand inherit from the stack that owns it\n
AWS > RDS > DB Parameter Group > Discovery
Discover all AWS RDS db parameter group 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 > RDS > DB Parameter Group > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > RDS > DB Parameter Group > Tags
Take an action when an AWS RDS db parameter group tags is not updated based on the AWS > RDS > DB Parameter Group > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > RDS > DB Parameter Group > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > RDS > DB Parameter Group > Usage
The Usage control determines whether the number of AWS RDS db parameter group resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > RDS > DB Parameter Group > Usage
policy, and set the limit with the AWS > RDS > DB Parameter Group > Usage > Limit
policy.\n
AWS > RDS > DB Snapshot [Manual] > Active
Take an action when an AWS RDS db snapshot [manual] is not active based on the\nAWS > RDS > DB Snapshot [Manual] > 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 > RDS > DB Snapshot [Manual] > 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 > RDS > DB Snapshot [Manual] > Approved
Take an action when an AWS RDS db snapshot [manual] is not approved based on AWS > RDS > DB Snapshot [Manual] > 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 > RDS > DB Snapshot [Manual] > CMDB
Record and synchronize details for the AWS RDS db snapshot [manual] 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 > RDS > DB Snapshot [Manual] > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > RDS > DB Snapshot [Manual] > Configured
Maintain AWS > RDS > DB Snapshot [Manual] configuration\n\nNote: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored\nand inherit from the stack that owns it\n
AWS > RDS > DB Snapshot [Manual] > Discovery
Discover all AWS RDS db snapshot [manual] 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 > RDS > DB Snapshot [Manual] > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > RDS > DB Snapshot [Manual] > Tags
Take an action when an AWS RDS db snapshot [manual] tags is not updated based on the AWS > RDS > DB Snapshot [Manual] > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > RDS > DB Snapshot [Manual] > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > RDS > DB Snapshot [Manual] > Trusted Access
Manage trusted access for AWS RDS DB Snapshot [Manual]s.\n\nAWS allows RDS DB Snapshot [Manual]s to be shared with specific AWS accounts.\nThis control allows you to configure whether such sharing is allowed, and to which accounts.\n\nIf set to Enforce
, access to non-trusted accounts will be removed.\n
AWS > RDS > DB Snapshot [Manual] > Usage
The Usage control determines whether the number of AWS RDS db snapshot [manual] resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > RDS > DB Snapshot [Manual] > Usage
policy, and set the limit with the AWS > RDS > DB Snapshot [Manual] > Usage > Limit
policy.\n
AWS > RDS > Global Cluster > Active
Take an action when an AWS RDS global cluster is not active based on the\nAWS > RDS > Global Cluster > 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 > RDS > Global Cluster > 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 > RDS > Global Cluster > Approved
Take an action when an AWS RDS global cluster is not approved based on AWS > RDS > Global Cluster > 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 > RDS > Global Cluster > CMDB
Record and synchronize details for the AWS RDS global cluster 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 > RDS > Global Cluster > Discovery
Discover all AWS RDS global cluster 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 > RDS > Option Group > Active
Take an action when an AWS RDS option group is not active based on the\nAWS > RDS > Option Group > 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 > RDS > Option Group > 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 > RDS > Option Group > Approved
Take an action when an AWS RDS option group is not approved based on AWS > RDS > Option Group > 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 > RDS > Option Group > CMDB
Record and synchronize details for the AWS RDS option group 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 > RDS > Option Group > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > RDS > Option Group > Configured
Maintain AWS > RDS > Option Group configuration\n\nNote: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored\nand inherit from the stack that owns it\n
AWS > RDS > Option Group > Discovery
Discover all AWS RDS option group 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 > RDS > Option Group > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > RDS > Option Group > Tags
Take an action when an AWS RDS option group tags is not updated based on the AWS > RDS > Option Group > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > RDS > Option Group > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > RDS > Option Group > Usage
The Usage control determines whether the number of AWS RDS option group resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > RDS > Option Group > Usage
policy, and set the limit with the AWS > RDS > Option Group > Usage > Limit
policy.\n
AWS > RDS > Stack
Configure a custom stack on AWS, per the custom Stack > Source
.\n\nA Guardrails Stack
is a set of resources configured by Guardrails, as specified\nvia Terraform source. Stacks are responsible for the creation and deletion\nof multiple resources. Once created, stack resources are responsible for\nconfiguring themselves from the stack source via their Configured
control.\n
AWS > RDS > Subnet Group > Active
Take an action when an AWS RDS subnet group is not active based on the\nAWS > RDS > Subnet Group > 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 > RDS > Subnet Group > 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 > RDS > Subnet Group > Approved
Take an action when an AWS RDS subnet group is not approved based on AWS > RDS > Subnet Group > 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 > RDS > Subnet Group > CMDB
Record and synchronize details for the AWS RDS subnet group 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 > RDS > Subnet Group > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)\n
AWS > RDS > Subnet Group > Configured
Maintain AWS > RDS > Subnet Group configuration\n\nNote: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored\nand inherit from the stack that owns it\n
AWS > RDS > Subnet Group > Discovery
Discover all AWS RDS subnet group 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 > RDS > Subnet Group > Regions
policy, the CMDB control will delete the resource from the CMDB.\n
AWS > RDS > Subnet Group > Tags
Take an action when an AWS RDS subnet group tags is not updated based on the AWS > RDS > Subnet Group > Tags > * policies
.\n\nIf the resource is not updated with the tags defined in AWS > RDS > Subnet Group > Tags > Template
, this control raises an alarm and takes the defined enforcement action.\n\nSee Tags for more information.\n
AWS > RDS > Subnet Group > Usage
The Usage control determines whether the number of AWS RDS subnet group resources exceeds the configured usage limit for this region.\n\nYou can configure the behavior of this control with the AWS > RDS > Subnet Group > Usage
policy, and set the limit with the AWS > RDS > Subnet Group > Usage > Limit
policy.\n