AWS Redshift Terraform module

Upstream version 7.1.1
9 controls from ISO/IEC 27001:2022 requirements

Terraform Module Source

iso27001.compliance.tf/terraform-aws-modules/redshift/aws
ComplianceInputsOutputsResourcesRulesDiff (5)README

Behavioral Summary

This module modifies 5 variable defaults and makes 0 resource changes from the upstream module. All changes are driven by compliance controls and can be reviewed in detail below.

Your Code Impact

If you are migrating from the upstream module, the enforced default changes mean your existing configurations will automatically gain compliance controls. Variables you have explicitly set will continue to use your values. Review the diff below to understand exactly what changes.

Compared to terraform-aws-modules/redshift/aws@7.1.15 changes

Variables Changed

5
VariableUpstreamCTFReasonControl
cloudwatch_log_group_retention_in_days0365Ensure a minimum duration of event log data is retained for your log groups to help with troubleshooting and forensics investigations.cloudwatch_log_group_retention_period_365
encrypted-trueEnsure that your AWS Redshift clusters require TLS/SSL encryption to connect to SQL clients.redshift_cluster_encryption_in_transit_enabled
enhanced_vpc_routing-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'.redshift_cluster_enhanced_vpc_routing_enabled
multi_az-trueThis control checks whether multiple Availability Zones (Multi-AZ) deployments are enabled for an Amazon Redshift cluster. The control fails if Multi-AZ deployments aren't enabled for the Amazon Redshift cluster.redshift_cluster_multiple_az_enabled
publicly_accessible-falseManage access to resources in the AWS Cloud by ensuring that AWS Redshift clusters are not public.redshift_cluster_prohibit_public_access