[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-log-storage/aws (source)	module	major	1.4.5 → 2.1.0

---

Release Notes

cloudposse/terraform-aws-s3-log-storage (cloudposse/s3-log-storage/aws)

v2.1.0

Compare Source

✨ Features

feat: add object_lock_enabled passthrough @​Benbentwo (#​141)

what

• Bump cloudposse/s3-bucket/aws from 4.10.0 to 4.15.0.
• Expose that module's object_lock_enabled input as a variable on this module.
• Raise the AWS provider floor from >= 4.9.0 to >= 6.37.0, which s3-bucket 4.15.0 requires.

why

object_lock_configuration is the only Object Lock knob this module exposes, and it is a bucket-wide default retention
rule — mode plus days or years, both required. There is no way to ask for "Object Lock enabled, nothing locked by
default", which is what you want when objects are protected individually with a retention period or a legal hold.

That matters for log buckets specifically. A default retention rule interacts badly with lifecycle expiration: S3 cannot
delete an object still under retention, so a retention period longer than the expiration deadlocks the lifecycle rule.
Callers who want the WORM capability without that coupling currently have no option.

cloudposse/terraform-aws-s3-bucket already solved this in
v4.15.0 by adding a bare
object_lock_enabled bool alongside object_lock_configuration. This PR just carries that input up one layer. The
variable description is copied verbatim from the child module so the two stay consistent.

references

• Child module input: object_lock_enabled in cloudposse/terraform-aws-s3-bucket v4.15.0
• Configuring S3 Object Lock

note on the provider floor

The provider bump is the part worth a second look — it comes along with s3-bucket 4.15.0 rather than from this change
itself, and it is a large jump for consumers still on provider v4 or v5. Happy to split it out or gate it differently if
you would rather land the passthrough separately.

🤖 Automatic Updates

chore(deps): bump github.com/ulikunitz/xz from 0.5.10 to 0.5.14 in /test/src @​[dependabot[bot]](https://redirect.github.com/apps/dependabot) (#​131)

Bumps [github.com/ulikunitz/xz](https://redirect.github.com/ulikunitz/xz) from 0.5.10 to 0.5.14.

Commits

• 7184815 Preparation of release v0.5.14
• 88ddf1d Address Security Issue GHSA-jc7w-c686-c4v9
• c8314b8 Add new package xio with WriteCloserStack
• 4f11dce Update README.md and SECURITY.md to address security questions
• f56ebbf TODO.md: fix a typo
• 9d122a6 release version v0.5.11
• 4ce6f08 lzma: fix handling of small dictionary sizes
• 0b7c695 xz: add reader benchmark
• 5535077 xz: add compression reate to Writer benchmark
• 886dc9a xz: add benchmark for Writer
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

v2.0.0

Compare Source

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
• https://github.com/golang/go/issues/59305#issuecomment-1488478737
• https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/pull/294/#issuecomment-2859195553

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[mergify]

/terratest

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (3)

• Bump
• chore(deps)
• WIP

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.