v2.0.0

Two errors when trying to plan 'Invalid count argument' and 'Incorrect attribute value type' @goruha (#121)

## what * Fix

│ Error: Invalid count argument
│
│   on .terraform\modules\foo.vpc_flow_logs.s3_log_storage_bucket.aws_s3_bucket\main.tf line 64, in resource "aws_s3_bucket_logging" "default":
│   64:   count  = local.enabled && var.logging != null ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until
│ apply, so Terraform cannot predict how many instances will be created. To work
│ around this, use the -target argument to first apply only the resources that the
│ count depends on.
╵

references

• cloudposse/terraform-aws-vpc-flow-logs-s3-bucket#66 (comment)

🤖 Automatic Updates

Fix go version in tests @osterman (#127)

## what - Update go `1.24`

why

• Error loading shared library libresolv.so.2 in Go 1.20

References

• https://sweetops.slack.com/archives/G014YEKDH4K/p1746672149263629
• golang/go#59305 (comment)
• cloudposse/terraform-aws-cloudfront-s3-cdn#294

Replace Makefile with atmos.yaml @osterman (#126)

## what - Remove `Makefile` - Add `atmos.yaml`

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

v1.4.5

🚀 Enhancements

fix: remove join calls on bucket arn + id usage @carterdanko-dw (#125)

## what

• Initially put the wrong values for coditions, just needs to be a list
• Bucket should be single resource vs joining on a list.

references

issue #122

🐛 Bug Fixes

fix: remove join calls on bucket arn + id usage @carterdanko-dw (#125)

## what

• Initially put the wrong values for coditions, just needs to be a list
• Bucket should be single resource vs joining on a list.

references

issue #122

v1.4.4

🚀 Enhancements

Issue-122/Values expect list of strings vs string @carterdanko-dw (#123)

## what Updating the sqs iam permissions, as the values expects to be a list of strings vs just the single string arn that is the output of the module.

why

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document#condition-1 expects to be a list of strings, vs just the single string arn of the s3 bucket.

references

Github issue #122

🐛 Bug Fixes

Issue-122/Values expect list of strings vs string @carterdanko-dw (#123)

## what Updating the sqs iam permissions, as the values expects to be a list of strings vs just the single string arn that is the output of the module.

why

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document#condition-1 expects to be a list of strings, vs just the single string arn of the s3 bucket.

references

Github issue #122

🤖 Automatic Updates

Migrate new test account @osterman (#119)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

Update .github/settings.yml @osterman (#118)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#112)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#111)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update release workflow to allow pull-requests: write @osterman (#110)

## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PR

why

• So we can support commenting on PRs with a link to the release

Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#109)

## what - Update workflows (`.github/workflows`) to use shared workflows from `.github` repo

why

• Reduce nested levels of reusable workflows

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#108)

## what - Update workflows (`.github/workflows`) to add `issue: write` permission needed by ReviewDog `tflint` action

why

• The ReviewDog action will comment with line-level suggestions based on linting failures

Update GitHub workflows @osterman (#107)

## what - Update workflows (`.github/workflows/settings.yaml`)

why

• Support new readme generation workflow.
• Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#106)

## what

• Install latest GitHub Action Workflows

why

• Use shared workflows from cldouposse/.github repository
• Simplify management of workflows from centralized hub of configuration

Add GitHub Settings @osterman (#104)

## what - Install a repository config (`.github/settings.yaml`)

why

• Programmatically manage GitHub repo settings

Update README.md and docs @cloudpossebot (#99)

## what This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update Scaffolding @osterman (#100)

## what - Reran `make readme` to rebuild `README.md` from `README.yaml` - Migrate to square badges - Add scaffolding for repo settings and Mergify

why

• Upstream template changed in the .github repo
• Work better with repository rulesets
• Modernize look & feel

v1.4.3

🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.3 (main) @renovate (#95)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	3.1.2 -> 3.1.3

---

Release Notes

cloudposse/terraform-aws-s3-bucket (cloudposse/s3-bucket/aws)

v3.1.3

Compare Source

Unfortunately, this change makes count unknown at plan time in certain situations. In general, you cannot use the output of compact() in count.

The solution is to stop using the deprecated policy input and revert to 3.1.2 or upgrade to 4.0.

🚀 Enhancements

Fix `source_policy_documents` combined with `var.policy` being ignored @​johncblandii (#​201)

what

• Changed var.source_policy_documents to local.source_policy_documents so var.policy usage was still supported

why

• The ternary check uses var,source_policy_documents so var.policy being combined with var.source_policy_documents into local.source_policy_documents does not provide true for the ternary to execute

references

• https://github.com/cloudposse/terraform-aws-config-storage/pull/39

---

Update README.md and docs @cloudpossebot (#94)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v1.4.2

🚀 Enhancements

Add `grants` input @Nuru (#93)

what

• Add grants input

why

• Some AWS services, such at Cloudfront, require specific grants for log delivery

references

• Cloudfront log delivery requirements

v1.4.1

Sync .github @max-lobur (#89)

Rebuild '.github' dir from the template

🚀 Enhancements

Update Terraform cloudposse/s3-bucket/aws to v3.1.2 (main) @renovate (#91)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	3.1.1 -> 3.1.2

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v3.1.2: Fix Public Bucket Creation

Compare Source

What's Changed

• Remove reference to TF_DATA_DIR retained by mistake in #​40 by @​Nuru in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/181
• Sync .github by @​max-lobur in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/183
• Fix linters / Retest on AWS provider V5 by @​max-lobur in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/188
• Fix Public Bucket Creation by @​rankin-tr in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194

New Contributors

• @​rankin-tr made their first contribution in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194

Full Changelog: cloudposse/terraform-aws-s3-bucket@3.1.1...3.1.2

---

🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.2 (main) @renovate (#91)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	3.1.1 -> 3.1.2

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v3.1.2: Fix Public Bucket Creation

Compare Source

What's Changed

• Remove reference to TF_DATA_DIR retained by mistake in #​40 by @​Nuru in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/181
• Sync .github by @​max-lobur in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/183
• Fix linters / Retest on AWS provider V5 by @​max-lobur in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/188
• Fix Public Bucket Creation by @​rankin-tr in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194

New Contributors

• @​rankin-tr made their first contribution in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194

Full Changelog: cloudposse/terraform-aws-s3-bucket@3.1.1...3.1.2

---

v1.4.0

• No changes

v1.3.1

🚀 Enhancements

Update Terraform cloudposse/s3-bucket/aws to v3.1.1 (master) @renovate (#88)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	3.1.0 -> 3.1.1

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v3.1.1

Compare Source

🐛 Bug Fixes

Revert change to Transfer Acceleration from #​178 @​Nuru (#​180)

what

• Revert change to Transfer Acceleration from #​178

why

• Transfer Acceleration is not available in every region, and the change in #​178 (meant to detect and correct drift) does not work (throws API errors) in regions where Transfer Acceleration is not supported

---

🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.1 (master) @renovate (#88)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	3.1.0 -> 3.1.1

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v3.1.1

Compare Source

🐛 Bug Fixes

Revert change to Transfer Acceleration from #​178 @​Nuru (#​180)

what

• Revert change to Transfer Acceleration from #​178

why

• Transfer Acceleration is not available in every region, and the change in #​178 (meant to detect and correct drift) does not work (throws API errors) in regions where Transfer Acceleration is not supported

---

v1.3.0

🚀 Enhancements

Enhance lifecycle object with optionals, limit length of bucket name @Nuru (#87)

what

• Limit length of auto-generated bucket name to match AWS-imposed limit
• Enhance lifecycle_configuration_rules to be fully defined with optional members

why

• Avoid situation where module fails because auto-generated bucket name is too long
• Make it easier to build a list of rules

references

• https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html
• cloudposse/terraform-aws-s3-bucket#167

v1.2.0 Support new AWS S3 defaults (ACL prohibited)

🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.0 @renovate (#85)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	minor	3.0.0 -> 3.1.0

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v3.1.0

Compare Source

Make compatible with new S3 defaults. Add user permissions boundary. @​Nuru (#​178)

what

• Make compatible with new S3 defaults by setting S3 Object Ownership before setting ACL and disabling ACL if Ownership is "BucketOwnerEnforced"
• Add optional permissions boundary input for IAM user created by this module
• Create aws_s3_bucket_accelerate_configuration and aws_s3_bucket_versioning resources even when the feature is disabled, to enable drift detection

why

• S3 buckets with ACLs were failing to be provisioned because the ACL was set before the bucket ownership was changed
• Requested feature
• See #​171

references

• Closes #​174
• Supersedes and closes #​175
• Supersedes and closes #​176

Always include `aws_s3_bucket_versioning` resource @​mviamari (#​172)

what

• Always create an aws_s3_bucket_versioning resource to track changes made to bucket versioning configuration

why

• When there is no aws_s3_bucket_versioning, the expectation is that the bucket versioning is disabled/suspend for the bucket. If bucket versioning is turned on outside of terraform (e.g. through the console), the change is not detected by terraform unless the aws_s3_bucket_versioning resource exists.

references

• Closes #​171

Add support for permission boundaries on replication IAM role @​mchristopher (#​170)

what

• Adds support for assigning permission boundaries to the replication IAM role

why

• Our AWS environment enforces permission boundaries on all IAM roles to follow AWS best practices with security.

references

• AWS IAM Access Policies

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​164)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

---