1.5.0

Warning!

This release removes moved blocks from the Terraform configuration of the region-level module.

Previously, these moved blocks were used to simplify module usage by automatically relocating resources without requiring any action from the user. However, we have encountered drawbacks when using moved blocks inside a module. If a resource is moved within the module, it becomes impossible to move that resource later in the root configuration. Therefore, it was decided to remove these moved blocks.

• If you are using version 1.2.0 or higher, no action is required.
• If you are using versions prior to 1.2.0, please update to version 1.2.0 first and then to the latest version to avoid any errors.

Alternatively, you can manually add moved blocks to your root configuration, enabling you to update directly to version 1.4.4. Example:

# move to s3 baseline bucket
moved {
  from = module.<name_of_root_module>.module.access_logs_bucket[0]
  to   = module.<name_of_root_module>.module.logs_bucket.module.bucket_baseline[0]
}

moved {
  from = module.<name_of_root_module>.module.access_logs_bucket.module.bucket_baseline[0]
  to   = module.<name_of_root_module>.module.access_logs_bucket[0]
}

#Refactor dynamodb state lock to use dynamodb module
moved {
  from = module.<name_of_root_module>.module.dynanodb_tf_state_lock_[0].aws_dynamodb_table.this[0]
  to   = module.<name_of_root_module>.module.dynanodb_tf_state_lock[0].aws_dynamodb_table.this[0]
}

moved {
  from = module.<name_of_root_module>.module.dynanodb_tf_state_lock[0].aws_dynamodb_table.this[0]
  to   = module.<name_of_root_module>.module.dynamodb_tf_state_lock[0].aws_dynamodb_table.this[0]
}

Full Changelog: 1.4.4...1.5.0

1.4.4

Warning!

This release fixes a path issue in the terraform-aws-naming-conventions module.
In previous versions, pipelines that are use the athena-regional-baseline module would break during terraform init because the old path for the terraform-aws-naming-conventions module is no longer accessible.

Full Changelog: 1.4.3...1.4.4

1.4.3

What's Changed

• build(deps): bump terraform-aws-modules/iam/aws from 5.39.0 to 5.47.1 in /modules/account_level by @dependabot in #91
• build(deps): bump terraform-aws-modules/dynamodb-table/aws from 4.0.1 to 4.2.0 in /modules/region_level by @dependabot in #90
• build(deps): bump terraform-aws-modules/s3-bucket/aws from 4.1.2 to 4.2.1 in /modules/region_level by @dependabot in #88
• build(deps): bump terraform-aws-modules/s3-bucket/aws from 4.1.2 to 4.2.1 in /modules/s3_baseline by @dependabot in #87

Full Changelog: 1.4.2...1.4.3

1.4.2

• allow overriding of athena results bucket name

Full Changelog: 1.4.1...1.4.2

1.4.1

fix: rename README.MD to README.md so terraform registry will not count athena baseline module as internal

Full Changelog: 1.4.0...1.4.1

1.4.0

Terraform AWS Athena regional baseline module

This release adds Athena regional baseline module. This module sets up a baseline configuration for AWS Athena in your account. It follows best practices for security and reliability.

Full Changelog: 1.3.7...1.4.0

1.3.7

Fix:

• Fix the Unsupported argument bug.

Full Changelog: 1.3.6...1.3.7

1.3.6

Fixes:

• If either the denyIncorrectEncryptionHeaders or denyUnencryptedObjectUploads policy is present on the S3 access logs bucket, S3 access logs from other buckets will not be delivered. So in this release, we are turning off the creation of those policies for S3 access logs buckets by default.
• Guess the attach_policy variable's boolean status by the persistence of the policy variable. So now you don't need to provide the attach_policy variable manually.

Full Changelog: 1.3.5...1.3.6

1.3.5

Fix:

If you're using the terraform-aws-account-baseline S3 baseline module with the policy variable, or managing regional-level Terraform state or access logs S3 buckets with the policy variable, please update to this release. The previous version did not attach any custom policy provided by the policy var to your bucket because the attach_policy variable was missing from the module.

To fix this, update to the latest version of the S3 baseline module and set the attach_policy variable to true.

Full Changelog: 1.3.4...1.3.5

1.3.4

Fix: add attach_policy variable, so policy var would work.

Full Changelog: 1.3.3...1.3.4