Skip to content

v2.0.0

Latest

Choose a tag to compare

@cloudposse-releaser cloudposse-releaser released this 04 Jun 16:48
340908e
feat: upgrade AWS provider to v6 and update all module dependencies Miguel Zablah (@MrZablah) (#141) ## what
  • Bump AWS provider constraint from >= 5.x to >= 6.0.0 across all versions.tf files (root, both submodules, all four examples)
  • Bump Terraform minimum version from >= 1.0 to >= 1.3 across all versions.tf files to formally align with optional() object type usage already present in the codebase
  • Fix breaking change: rename region → authorized_aws_region on both aws_config_aggregate_authorization resources (child and central)
  • Fix breaking change: replace removed data.aws_region.*.name attribute with .region in examples/hipaa/main.tf and modules/cis-1-2-rules/main.tf
  • Add s3_kms_key_arn argument to aws_config_delivery_channel and expose it as an optional variable for KMS encryption of delivered Config snapshots
  • Add evaluation_mode dynamic block to all three aws_config_config_rule resources (managed, custom Lambda, custom policy) and expose it as an optional variable
  • Add enable_debug_log_delivery to custom_policy_details block and expose it as an optional variable on custom_policy_rules
  • Update cloudposse/sns-topic/aws: 0.20.1 → 1.2.0
  • Update cloudposse/iam-role/aws: 0.19.0 → 1.0.0
  • Update cloudposse/config-storage/aws: 1.0.0 → 1.0.2 (all examples)
  • Update cloudposse/utils/aws: 1.0.0 → 1.4.0
  • Update cloudposse/label/null: 0.22.1 → 0.25.0 in examples/cis (was the only stale reference)

why

  • AWS provider v6 removed the region argument on aws_config_aggregate_authorization and the name attribute on the aws_region data source — both are hard failures without this fix
  • Terraform >= 1.3 is the correct minimum since optional() in object type constraints (already used in variables.tf) was stabilized in that release
  • evaluation_mode enables opt-in proactive evaluation of Config rules before resources are deployed, a significant compliance feature added in recent provider versions
  • s3_kms_key_arn closes a gap where Config delivery to an encrypted S3 bucket had no native KMS argument wired through
  • enable_debug_log_delivery makes CFN Guard policy rule development easier by surfacing evaluation logs in CloudWatch
  • Module bumps bring in AWS provider v6 compatibility fixes and new features (SNS delivery status, IAM role managed policy ARN maps) from upstream CloudPosse modules

references