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 theAWS > RDS > DB 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 > RDS > DB 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.
tmod:@turbot/aws-rds#/control/types/dbClusterActive
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
.
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.
tmod:@turbot/aws-rds#/control/types/dbClusterApproved
AWS > RDS > DB Cluster > Backup Retention Period
Raise an alarm if the RDS cluster's backup retention period is not configured to meet policy.
tmod:@turbot/aws-rds#/control/types/dbClusterBackupRetentionPeriod
AWS > RDS > DB Cluster > CMDB
Record and synchronize details for the AWS RDS db 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 > 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.)
tmod:@turbot/aws-rds#/control/types/dbClusterCmdb
AWS > RDS > DB Cluster > Configured
Maintain AWS > RDS > DB 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.
tmod:@turbot/aws-rds#/control/types/dbClusterConfigured
AWS > RDS > DB Cluster > Copy Tags to Snapshot
Configure Copy Tags to Snapshot settings on an AWS > RDS > DB Cluster
.
tmod:@turbot/aws-rds#/control/types/dbClusterCopyTagsToSnapshot
AWS > RDS > DB Cluster > Deletion Protection
Configure Deletion Protection settings on an AWS > RDS > DB Cluster
.
tmod:@turbot/aws-rds#/control/types/dbClusterDeletionProtection
AWS > RDS > DB Cluster > Discovery
Discover all AWS RDS db 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 > RDS > DB Cluster > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-rds#/control/types/dbClusterDiscovery
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.
tmod:@turbot/aws-rds#/control/types/dbClusterLogsExportConfiguration
AWS > RDS > DB Cluster > Schedule
Set a schedule for starting and stopping an AWS RDS db cluster.
Note If both "Schedule" and "Schedule Tag" are set to enforce and the
db cluster has a turbot_custom_schedule tag, then the schedule specified by
the tag will be in effect.
tmod:@turbot/aws-rds#/control/types/dbClusterSchedule
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
.
If 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.
See Tags for more information.
tmod:@turbot/aws-rds#/control/types/dbClusterTags
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.
You 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.
tmod:@turbot/aws-rds#/control/types/dbClusterUsage
AWS > RDS > DB Cluster Parameter Group > Active
Take an action when an AWS RDS db cluster parameter group is not active based on theAWS > RDS > DB Cluster Parameter Group > 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 > RDS > DB Cluster Parameter Group > 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.
tmod:@turbot/aws-rds#/control/types/dbClusterParameterGroupActive
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
.
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.
tmod:@turbot/aws-rds#/control/types/dbClusterParameterGroupApproved
AWS > RDS > DB Cluster Parameter Group > CMDB
Record and synchronize details for the AWS RDS db cluster parameter group 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 > 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.)
tmod:@turbot/aws-rds#/control/types/dbClusterParameterGroupCmdb
AWS > RDS > DB Cluster Parameter Group > Configured
Maintain AWS > RDS > DB Cluster Parameter Group 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.
tmod:@turbot/aws-rds#/control/types/dbClusterParameterGroupConfigured
AWS > RDS > DB Cluster Parameter Group > Discovery
Discover all AWS RDS db cluster parameter group 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 > RDS > DB Cluster Parameter Group > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-rds#/control/types/dbClusterParameterGroupDiscovery
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
.
If 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.
See Tags for more information.
tmod:@turbot/aws-rds#/control/types/dbClusterParameterGroupTags
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.
You 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.
tmod:@turbot/aws-rds#/control/types/dbClusterParameterGroupUsage
AWS > RDS > DB Cluster Snapshot [Manual] > Active
Take an action when an AWS RDS db cluster snapshot [manual] is not active based on theAWS > RDS > DB Cluster Snapshot [Manual] > 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 > RDS > DB Cluster Snapshot [Manual] > 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.
tmod:@turbot/aws-rds#/control/types/dbClusterSnapshotManualActive
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
.
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.
tmod:@turbot/aws-rds#/control/types/dbClusterSnapshotManualApproved
AWS > RDS > DB Cluster Snapshot [Manual] > CMDB
Record and synchronize details for the AWS RDS db cluster snapshot [manual] 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 > 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.)
tmod:@turbot/aws-rds#/control/types/dbClusterSnapshotManualCmdb
AWS > RDS > DB Cluster Snapshot [Manual] > Configured
Maintain AWS > RDS > DB Cluster Snapshot [Manual] 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.
tmod:@turbot/aws-rds#/control/types/dbClusterSnapshotManualConfigured
AWS > RDS > DB Cluster Snapshot [Manual] > Discovery
Discover all AWS RDS db cluster snapshot [manual] 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 > RDS > DB Cluster Snapshot [Manual] > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-rds#/control/types/dbClusterSnapshotManualDiscovery
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
.
If 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.
See Tags for more information.
tmod:@turbot/aws-rds#/control/types/dbClusterSnapshotManualTags
AWS > RDS > DB Cluster Snapshot [Manual] > Trusted Access
Manage trusted access for AWS RDS DB Cluster Snapshot [Manual]s.
AWS allows RDS DB Cluster Snapshot [Manual]s to be shared with specific AWS accounts.
This control allows you to configure whether such sharing is allowed, and to which accounts.
If set to Enforce
, access to non-trusted accounts will be removed.
tmod:@turbot/aws-rds#/control/types/dbClusterSnapshotManualTrustedAccess
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.
You 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.
tmod:@turbot/aws-rds#/control/types/dbClusterSnapshotManualUsage
AWS > RDS > DB Instance > Active
Take an action when an AWS RDS db instance is not active based on theAWS > RDS > DB 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 > RDS > DB 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.
tmod:@turbot/aws-rds#/control/types/dbInstanceActive
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
.
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.
See Approved for more information.
tmod:@turbot/aws-rds#/control/types/dbInstanceApproved
AWS > RDS > DB Instance > Auto Minor Version Upgrade
Configure Auto Minor Version Upgrade settings on an AWS > RDS > DB Instance
.
tmod:@turbot/aws-rds#/control/types/dbInstanceAutoMinorVersionUpgrade
AWS > RDS > DB Instance > Backup Retention Period
Raise an alarm if the RDS instance's backup retention period is not configured to meet policy.
tmod:@turbot/aws-rds#/control/types/dbInstanceBackupRetentionPeriod
AWS > RDS > DB Instance > CMDB
Record and synchronize details for the AWS RDS db 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 > 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.)
tmod:@turbot/aws-rds#/control/types/dbInstanceCmdb
AWS > RDS > DB Instance > Configured
Maintain AWS > RDS > DB Instance 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.
tmod:@turbot/aws-rds#/control/types/dbInstanceConfigured
AWS > RDS > DB Instance > Copy Tags to Snapshot
Configure Copy Tags to Snapshot settings on an AWS > RDS > DB Instance
.
tmod:@turbot/aws-rds#/control/types/dbInstanceCopyTagsToSnapshot
AWS > RDS > DB Instance > Deletion Protection
Configure Deletion Protection settings on an AWS > RDS > DB Instance
.
tmod:@turbot/aws-rds#/control/types/dbInstanceDeletionProtection
AWS > RDS > DB Instance > Discovery
Discover all AWS RDS db 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 > RDS > DB Instance > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-rds#/control/types/dbInstanceDiscovery
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.
tmod:@turbot/aws-rds#/control/types/dbInstanceLogsExportConfiguration
AWS > RDS > DB Instance > Multi-AZ
Configure Multi-AZ deployment settings on an AWS > RDS > DB Instance
.
tmod:@turbot/aws-rds#/control/types/dbInstanceMultiAz
AWS > RDS > DB Instance > Parameter Group
Determine whether to check or enforce a specific Parameter Group for this DB Instance.
Use the Parameter Group > Name
sub-policy to set which Parameter Group to configure for this instance.
tmod:@turbot/aws-rds#/control/types/dbInstanceParameterGroup
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.
tmod:@turbot/aws-rds#/control/types/dbInstancePerformanceInsights
AWS > RDS > DB Instance > Publicly Accessible
Ensure the RDS instance is not publicly accessible.
tmod:@turbot/aws-rds#/control/types/dbInstancePubliclyAccessible
AWS > RDS > DB Instance > Schedule
Set a schedule for starting and stopping an AWS RDS db instance.
Note If both "Schedule" and "Schedule Tag" are set to enforce and the
db instance has a turbot_custom_schedule tag, then the schedule specified by
the tag will be in effect.
tmod:@turbot/aws-rds#/control/types/instanceSchedule
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
.
If 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.
See Tags for more information.
tmod:@turbot/aws-rds#/control/types/dbInstanceTags
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.
You 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.
tmod:@turbot/aws-rds#/control/types/dbInstanceUsage
AWS > RDS > DB Parameter Group > Active
Take an action when an AWS RDS db parameter group is not active based on theAWS > RDS > DB Parameter Group > 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 > RDS > DB Parameter Group > 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.
tmod:@turbot/aws-rds#/control/types/dbParameterGroupActive
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
.
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.
tmod:@turbot/aws-rds#/control/types/dbParameterGroupApproved
AWS > RDS > DB Parameter Group > CMDB
Record and synchronize details for the AWS RDS db parameter group 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 > 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.)
tmod:@turbot/aws-rds#/control/types/dbParameterGroupCmdb
AWS > RDS > DB Parameter Group > Configured
Maintain AWS > RDS > DB Parameter Group 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.
tmod:@turbot/aws-rds#/control/types/dbParameterGroupConfigured
AWS > RDS > DB Parameter Group > Discovery
Discover all AWS RDS db parameter group 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 > RDS > DB Parameter Group > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-rds#/control/types/dbParameterGroupDiscovery
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
.
If 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.
See Tags for more information.
tmod:@turbot/aws-rds#/control/types/dbParameterGroupTags
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.
You 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.
tmod:@turbot/aws-rds#/control/types/dbParameterGroupUsage
AWS > RDS > DB Snapshot [Manual] > Active
Take an action when an AWS RDS db snapshot [manual] is not active based on theAWS > RDS > DB Snapshot [Manual] > 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 > RDS > DB Snapshot [Manual] > 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.
tmod:@turbot/aws-rds#/control/types/dbSnapshotManualActive
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
.
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.
tmod:@turbot/aws-rds#/control/types/dbSnapshotManualApproved
AWS > RDS > DB Snapshot [Manual] > CMDB
Record and synchronize details for the AWS RDS db snapshot [manual] 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 > 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.)
tmod:@turbot/aws-rds#/control/types/dbSnapshotManualCmdb
AWS > RDS > DB Snapshot [Manual] > Configured
Maintain AWS > RDS > DB Snapshot [Manual] 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.
tmod:@turbot/aws-rds#/control/types/dbSnapshotManualConfigured
AWS > RDS > DB Snapshot [Manual] > Discovery
Discover all AWS RDS db snapshot [manual] 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 > RDS > DB Snapshot [Manual] > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-rds#/control/types/dbSnapshotManualDiscovery
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
.
If 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.
See Tags for more information.
tmod:@turbot/aws-rds#/control/types/dbSnapshotManualTags
AWS > RDS > DB Snapshot [Manual] > Trusted Access
Manage trusted access for AWS RDS DB Snapshot [Manual]s.
AWS allows RDS DB Snapshot [Manual]s to be shared with specific AWS accounts.
This control allows you to configure whether such sharing is allowed, and to which accounts.
If set to Enforce
, access to non-trusted accounts will be removed.
tmod:@turbot/aws-rds#/control/types/dbSnapshotManualTrustedAccess
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.
You 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.
tmod:@turbot/aws-rds#/control/types/dbSnapshotManualUsage
AWS > RDS > Global Cluster > Active
Take an action when an AWS RDS global cluster is not active based on theAWS > RDS > Global 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 > RDS > Global 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.
tmod:@turbot/aws-rds#/control/types/globalClusterActive
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
.
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.
tmod:@turbot/aws-rds#/control/types/globalClusterApproved
AWS > RDS > Global Cluster > CMDB
Record and synchronize details for the AWS RDS global 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".
tmod:@turbot/aws-rds#/control/types/globalClusterCmdb
AWS > RDS > Global Cluster > Discovery
Discover all AWS RDS global 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.
tmod:@turbot/aws-rds#/control/types/globalClusterDiscovery
AWS > RDS > Option Group > Active
Take an action when an AWS RDS option group is not active based on theAWS > RDS > Option Group > 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 > RDS > Option Group > 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.
tmod:@turbot/aws-rds#/control/types/optionGroupActive
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
.
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.
tmod:@turbot/aws-rds#/control/types/optionGroupApproved
AWS > RDS > Option Group > CMDB
Record and synchronize details for the AWS RDS option group 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 > 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.)
tmod:@turbot/aws-rds#/control/types/optionGroupCmdb
AWS > RDS > Option Group > Configured
Maintain AWS > RDS > Option Group 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.
tmod:@turbot/aws-rds#/control/types/optionGroupConfigured
AWS > RDS > Option Group > Discovery
Discover all AWS RDS option group 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 > RDS > Option Group > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-rds#/control/types/optionGroupDiscovery
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
.
If 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.
See Tags for more information.
tmod:@turbot/aws-rds#/control/types/optionGroupTags
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.
You 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.
tmod:@turbot/aws-rds#/control/types/optionGroupUsage
AWS > RDS > Stack
Configure a custom stack on AWS, per the custom Stack > Source
.
A Guardrails Stack
is a set of resources configured by Guardrails, as specified
via Terraform source. Stacks are responsible for the creation and deletion
of multiple resources. Once created, stack resources are responsible for
configuring themselves from the stack source via their Configured
control.
tmod:@turbot/aws-rds#/control/types/rdsStack
AWS > RDS > Subnet Group > Active
Take an action when an AWS RDS subnet group is not active based on theAWS > RDS > Subnet Group > 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 > RDS > Subnet Group > 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.
tmod:@turbot/aws-rds#/control/types/subnetGroupActive
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
.
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.
tmod:@turbot/aws-rds#/control/types/subnetGroupApproved
AWS > RDS > Subnet Group > CMDB
Record and synchronize details for the AWS RDS subnet group 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 > 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.)
tmod:@turbot/aws-rds#/control/types/subnetGroupCmdb
AWS > RDS > Subnet Group > Configured
Maintain AWS > RDS > Subnet Group 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.
tmod:@turbot/aws-rds#/control/types/subnetGroupConfigured
AWS > RDS > Subnet Group > Discovery
Discover all AWS RDS subnet group 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 > RDS > Subnet Group > Regions
policy, the CMDB control will delete the resource from the CMDB.
tmod:@turbot/aws-rds#/control/types/subnetGroupDiscovery
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
.
If 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.
See Tags for more information.
tmod:@turbot/aws-rds#/control/types/subnetGroupTags
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.
You 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.
tmod:@turbot/aws-rds#/control/types/subnetGroupUsage