Control types for @turbot/aws-redshift
- AWS > Redshift > Cluster > Active
- AWS > Redshift > Cluster > Approved
- AWS > Redshift > Cluster > Audit Logging
- AWS > Redshift > Cluster > Backup Retention Period
- AWS > Redshift > Cluster > CMDB
- AWS > Redshift > Cluster > Discovery
- AWS > Redshift > Cluster > Encryption at Rest
- AWS > Redshift > Cluster > Encryption in Transit
- AWS > Redshift > Cluster > Parameter Group
- AWS > Redshift > Cluster > Publicly Accessible
- AWS > Redshift > Cluster > Schedule
- AWS > Redshift > Cluster > Tags
- AWS > Redshift > Cluster > Usage
- AWS > Redshift > Cluster Parameter Group > Active
- AWS > Redshift > Cluster Parameter Group > Approved
- AWS > Redshift > Cluster Parameter Group > CMDB
- AWS > Redshift > Cluster Parameter Group > Discovery
- AWS > Redshift > Cluster Parameter Group > Tags
- AWS > Redshift > Cluster Parameter Group > Usage
- AWS > Redshift > Cluster Subnet Group > Active
- AWS > Redshift > Cluster Subnet Group > Approved
- AWS > Redshift > Cluster Subnet Group > CMDB
- AWS > Redshift > Cluster Subnet Group > Discovery
- AWS > Redshift > Cluster Subnet Group > Tags
- AWS > Redshift > Cluster Subnet Group > Usage
- AWS > Redshift > Manual Cluster Snapshot > Active
- AWS > Redshift > Manual Cluster Snapshot > Approved
- AWS > Redshift > Manual Cluster Snapshot > CMDB
- AWS > Redshift > Manual Cluster Snapshot > Discovery
- AWS > Redshift > Manual Cluster Snapshot > Tags
- AWS > Redshift > Manual Cluster Snapshot > Trusted Access
- AWS > Redshift > Manual Cluster Snapshot > Usage
AWS > Redshift > Cluster > Active
Take an action when an AWS Redshift cluster is not active based on the
AWS > Redshift > 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 > Redshift > Cluster > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved for any reason it will be considered Unapproved.
See Active for more information.
AWS > Redshift > Cluster > Approved
Take an action when an AWS Redshift cluster is not approved based on AWS > Redshift > Cluster > Approved > * policies
.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
AWS > Redshift > Cluster > Audit Logging
Define the Audit Logging settings required for AWS > Redshift > Cluster
.
AWS > Redshift > Cluster
provides detailed audit logs information about connection, user and user activity logs in your database.
These logs help you to monitor the database for security and troubleshooting purposes, which is a process often referred to as database auditing.
The logs are stored in Amazon S3 buckets.
The control changes the audit logging setting of the AWS > Redshift > Cluster
and also changes the enable_user_activity_logging
parameter of the attached parameter group if sub policy AWS > Redshift > Cluster > Audit Logging > User Activity Logging
is set.
Also the control triggers reboot if the attached parameter group is modified.
AWS > Redshift > Cluster > Backup Retention Period
Raise an alarm if the Redshift cluster backup retention period is not configured per policy.
AWS > Redshift > Cluster > CMDB
Record and synchronize details for the AWS Redshift cluster into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot 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 > Redshift > Cluster > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
AWS > Redshift > Cluster > Discovery
Discover all AWS Redshift 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 > Redshift > Cluster > Regions
policy, the CMDB control will delete the resource from the CMDB.
AWS > Redshift > Cluster > Encryption at Rest
Define the Encryption at Rest settings required for AWS > Redshift > Cluster
.
Encryption at Rest refers specifically to the encryption of data when written to an underlying storage system. This control determines whether the resource is encrypted at rest, and sets encryption to your desired level.
The Encryption at Rest
control compares the encryption settings against the encryption policies for the resource
(AWS > Redshift > Cluster > Encryption at Rest > *
),
raises an alarm, and takes the defined enforcement action.
AWS > Redshift > Cluster > Encryption in Transit
Define the Encryption in Transit settings required for AWS > Redshift > Cluster
.
The Encryption in Transit control compares the Encryption in Transit settings against the Encryption in Transit policies for the resource (AWS > Redshift > Cluster > Encryption in Transit), raises an alarm, and takes the defined enforcement action.
The control changes the require_ssl
parameter of the attached parameter group. Also the control triggers reboot when the attached parameter group is modified.
AWS > Redshift > Cluster > Parameter Group
Determine whether to check or enforce a specific parameter group for this AWS > Redshift > Cluster
.
Use the Parameter Group > Name
sub-policy to set which parameter group to configure for this cluster.
When set to Enforce: Set to Parameter Group > Name (Create if missing)
, this control will create a new parameter group, copy the currently attached parameter group's parameter values over, and then attach the new parameter group. Also the control triggers reboot after attaching a new parameter group.
AWS > Redshift > Cluster > Publicly Accessible
Ensure the Redshift cluster is not publicly accessible.
AWS > Redshift > Cluster > Schedule
Set a schedule for starting and stopping an AWS Redshift cluster.
Note If both "Schedule" and "Schedule Tag" are set to enforce and the cluster has a turbot_custom_schedule tag, then the schedule specified by the tag will be in effect.
AWS > Redshift > Cluster > Tags
Take an action when an AWS Redshift cluster tags is not updated based on the AWS > Redshift > Cluster > Tags > * policies
.
If the resource is not updated with the tags defined in AWS > Redshift > Cluster > Tags > Template
, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > Redshift > Cluster > Usage
The Usage control determines whether the number of AWS Redshift cluster resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Redshift > Cluster > Usage
policy, and set the limit with the AWS > Redshift > Cluster > Usage > Limit
policy.
AWS > Redshift > Cluster Parameter Group > Active
Take an action when an AWS Redshift cluster parameter group is not active based on the
AWS > Redshift > 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 > Redshift > 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.
AWS > Redshift > Cluster Parameter Group > Approved
Take an action when an AWS Redshift cluster parameter group is not approved based on AWS > Redshift > 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.
AWS > Redshift > Cluster Parameter Group > CMDB
Record and synchronize details for the AWS Redshift cluster parameter group into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot 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 > Redshift > 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.)
AWS > Redshift > Cluster Parameter Group > Discovery
Discover all AWS Redshift 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 > Redshift > Cluster Parameter Group > Regions
policy, the CMDB control will delete the resource from the CMDB.
AWS > Redshift > Cluster Parameter Group > Tags
Take an action when an AWS Redshift cluster parameter group tags is not updated based on the AWS > Redshift > Cluster Parameter Group > Tags > * policies
.
If the resource is not updated with the tags defined in AWS > Redshift > Cluster Parameter Group > Tags > Template
, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > Redshift > Cluster Parameter Group > Usage
The Usage control determines whether the number of AWS Redshift cluster parameter group resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Redshift > Cluster Parameter Group > Usage
policy, and set the limit with the AWS > Redshift > Cluster Parameter Group > Usage > Limit
policy.
AWS > Redshift > Cluster Subnet Group > Active
Take an action when an AWS Redshift cluster subnet group is not active based on the
AWS > Redshift > Cluster 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 > Redshift > Cluster 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.
AWS > Redshift > Cluster Subnet Group > Approved
Take an action when an AWS Redshift cluster subnet group is not approved based on AWS > Redshift > Cluster 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.
AWS > Redshift > Cluster Subnet Group > CMDB
Record and synchronize details for the AWS Redshift cluster subnet group into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot 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 > Redshift > Cluster Subnet Group > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
AWS > Redshift > Cluster Subnet Group > Discovery
Discover all AWS Redshift cluster 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 > Redshift > Cluster Subnet Group > Regions
policy, the CMDB control will delete the resource from the CMDB.
AWS > Redshift > Cluster Subnet Group > Tags
Take an action when an AWS Redshift cluster subnet group tags is not updated based on the AWS > Redshift > Cluster Subnet Group > Tags > * policies
.
If the resource is not updated with the tags defined in AWS > Redshift > Cluster Subnet Group > Tags > Template
, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > Redshift > Cluster Subnet Group > Usage
The Usage control determines whether the number of AWS Redshift cluster subnet group resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Redshift > Cluster Subnet Group > Usage
policy, and set the limit with the AWS > Redshift > Cluster Subnet Group > Usage > Limit
policy.
AWS > Redshift > Manual Cluster Snapshot > Active
Take an action when an AWS Redshift manual cluster snapshot is not active based on the
AWS > Redshift > Manual Cluster Snapshot > 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 > Redshift > Manual Cluster Snapshot > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved for any reason it will be considered Unapproved.
See Active for more information.
AWS > Redshift > Manual Cluster Snapshot > Approved
Take an action when an AWS Redshift manual cluster snapshot is not approved based on AWS > Redshift > Manual Cluster Snapshot > Approved > * policies
.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
AWS > Redshift > Manual Cluster Snapshot > CMDB
Record and synchronize details for the AWS Redshift manual cluster snapshot into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot 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 > Redshift > Manual Cluster Snapshot > Regions
policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
AWS > Redshift > Manual Cluster Snapshot > Discovery
Discover all AWS Redshift manual cluster snapshot 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 > Redshift > Manual Cluster Snapshot > Regions
policy, the CMDB control will delete the resource from the CMDB.
AWS > Redshift > Manual Cluster Snapshot > Tags
Take an action when an AWS Redshift manual cluster snapshot tags is not updated based on the AWS > Redshift > Manual Cluster Snapshot > Tags > * policies
.
If the resource is not updated with the tags defined in AWS > Redshift > Manual Cluster Snapshot > Tags > Template
, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > Redshift > Manual Cluster Snapshot > Trusted Access
Manage trusted access for AWS Redshift Manual Cluster Snapshots.
AWS allows Redshift Manual Cluster Snapshots 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.
AWS > Redshift > Manual Cluster Snapshot > Usage
The Usage control determines whether the number of AWS Redshift manual cluster snapshot resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Redshift > Manual Cluster Snapshot > Usage
policy, and set the limit with the AWS > Redshift > Manual Cluster Snapshot > Usage > Limit
policy.