Changes from upstream
Compared to terraform-aws-modules/redshift/aws@7.1.1, this version has 6 variable changes and 0 resource changes. Each change below names the control it comes from.
Your code impact
If you are migrating from the upstream module, review each change below before you switch. A changed default applies only where your configuration does not set that variable; values you set keep taking effect.
Defaults changed 6
- allow_version_upgradeupstream null, compliance.tf trueThis control checks whether automatic major version upgrades are enabled for the AWS Redshift cluster.Control redshift_cluster_automatic_upgrade_major_versions_enabled
- automated_snapshot_retention_periodupstream null, compliance.tf 7This control checks whether AWS Redshift clusters have automated snapshots enabled. It also checks whether the snapshot retention period is greater than or equal to seven.Control redshift_cluster_automatic_snapshots_min_7_days
- cloudwatch_log_group_retention_in_daysupstream 0, compliance.tf 365Ensure a minimum duration of event log data is retained for your log groups to help with troubleshooting and forensics investigations.Control cloudwatch_log_group_retention_period_365
- encryptedupstream null, compliance.tf trueEnsure that your AWS Redshift clusters require TLS/SSL encryption to connect to SQL clients.Control redshift_cluster_encryption_in_transit_enabled
- enhanced_vpc_routingupstream null, compliance.tf trueEnsure that AWS Redshift cluster has 'enhancedVpcRouting' enabled. The rule is non-compliant if 'enhancedVpcRouting' is not enabled or if the configuration.enhancedVpcRouting field is 'false'.Control redshift_cluster_enhanced_vpc_routing_enabled
- publicly_accessibleupstream null, compliance.tf falseManage access to resources in the AWS Cloud by ensuring that AWS Redshift clusters are not public.Control redshift_cluster_prohibit_public_access