Merged
Conversation
cdaniluk
approved these changes
Feb 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Breaking Changes
kms_key_idoption, due to its incompatibility with ALB logging. Existing buckets will have their encryption settings changed to SSE-S3. Users of previous versions of this module should evaluate their existing configuration for any negative impact of this change before upgrading.aws_s3_bucket_lifecycle_configurationresource. Existing deployments will need to explicitly import the lifecycle configuration into state when upgrading using an import block:source_accountsoptions is to restrict bucket access to the same account. Set this to an empty list to revert to the old behavior.Features
use_legacy_elb_policyoption.source_accountsorsource_organizationslist. Defaults to the current account, following AWS security best practices.Changes