AWS MSK Kafka Cluster Terraform module

Upstream version 3.3.0
3 controls from NIST Cybersecurity Framework v2.0 requirements

Terraform Module Source

nistcsf.compliance.tf/terraform-aws-modules/msk-kafka-cluster/aws
ComplianceInputsOutputsResourcesDiff (2)README

Behavioral Summary

This module modifies 2 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/msk-kafka-cluster/aws@3.3.02 changes

Variables Changed

2
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
encryption_in_transit_in_cluster-trueThis controls checks if an Amazon MSK cluster is encrypted in transit with HTTPS (TLS) among the broker nodes of the cluster. The control fails if plain text communication is enabled for a cluster broker node connection.msk_cluster_encryption_in_transit_with_tls_enabled