AWS VPC Terraform module

Upstream version 6.7.3
4 controls from SOC 2 requirements

Terraform Module Source

soc2.compliance.tf/terraform-aws-modules/vpc/aws
ComplianceInputsOutputsResourcesRulesDiff (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/vpc/aws@6.7.32 changes

Variables Changed

2
VariableUpstreamCTFReasonControl
flow_log_cloudwatch_log_group_retention_in_days-365Ensure 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
vpc_block_public_access_options{}{ "internet_gateway_block_mode": "block-bidirectional" }This control checks whether Amazon EC2 VPC Block Public Access (BPA) settings are configured to block internet gateway traffic for all Amazon VPCs in the AWS account. The control fails if VPC BPA settings aren't configured to block internet gateway traffic. For the control to pass, the VPC BPA InternetGatewayBlockMode must be set to block-bidirectional or block-ingress. If the parameter vpcBpaInternetGatewayBlockMode is provided, the control passes only if the VPC BPA value for InternetGatewayBlockMode matches the parameter.vpc_block_public_access_restrict_internet_gateway_traffic