v1.5.0

added recording_mode{} attribute @AdamTylerLynch (#87)

what

Added recording_mode block.

Requesting maintainer guidance on properly defining the inputs as a practitioner would expect. The way it is defined now feels odd, requiring a variable assignment and then a list for recording_mode_override.

Example:

##---------------------------------------------------
## AWS Config to monitor compliance
##---------------------------------------------------
module "config" {
  source    = "cloudposse/terraform-aws-config/aws"
  name      = "${local.name}-config-${data.aws_caller_identity.current.account_id}"
  namespace = local.namespace

  s3_bucket_id                     = module.log_storage.bucket_id
  s3_bucket_arn                    = module.log_storage.bucket_arn
  global_resource_collector_region = data.aws_region.current.name

  create_iam_role = true

  recording_mode = {
    recording_frequency = "DAILY"
    recording_mode_override = {
      description         = "Override for specific resource types"
      recording_frequency = "CONTINUOUS"
      resource_types      = ["AWS::EC2::Instance"]
    }
  }
}

why

This feature allows for cost optimization. Adds the ability to leverage Periodic recording VS continious.

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/config_configuration_recorder#periodic-recording
• https://aws.amazon.com/about-aws/whats-new/2023/11/aws-config-periodic-recording/
• https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.38.0

git.io->cloudposse.tools update @dylanbannon (#55)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143