v5.0.3

Resolves an error during terraform apply due to AWS changing default functionality of S3 ACLs.

https://aws.amazon.com/blogs/aws/heads-up-amazon-s3-security-changes-are-coming-in-april-of-2023/

v5.0.2

Bump dependency

v5.0.1

Bump dependencies

v5.0.0

Breaking change: we now require Terraform version 1.3.0 or above, and AWS provider version 4.0.0 or above.

This is a continuation of the work done to clean up warnings in #65. We discovered that we had to move to AWS provider 4.0.0 to resolve some remaining warnings.

What's Changed

• Switch from aws_s3_bucket_object to aws_s3_object by @GaryGSC in #66

Full Changelog: v4.0.1...v5.0.0

v4.0.1

What's Changed

• Use newer TF resources for S3 buckets, rather than the now-deprecated resources by @GaryGSC in #65

Note
This update may initially generate some noise in Terraform plans as it "creates" a number of S3 resources. The resources it creates are equivalent to what we were already using, hence the patch release.

Full Changelog: v4.0.0...v4.0.1

v4.0.0

This update primarily bumps the Lambda runtime to nodejs16.x.

It's a major version update due to the requirement that the AWS provider be recent (and by extension, the TF version). Apart from updating those versions, no code changes should be necessary.

Specifically, we require Terraform version 1.0.0 or above, and AWS provider version 3.75.2 or above.

For more details, see #58.

v3.2.4

Apply log_retention_in_days to the S3 logging bucket. (Previously, this variable only applied to the CloudWatch log group. The S3 bucket was hard coded at 120 days.)

v3.2.3

Allow s3 buckets to be emptied.

v3.2.2

• Make it harder to accidentally make the contents of the log bucket public (#44)

v3.2.1

• Use filebase64sha256 to compute source_code_hash (#43)