cache: prevent small objects from transitioning to Glacier#960
Open
cache: prevent small objects from transitioning to Glacier#960
Conversation
Switch transition_default_minimum_object_size from varies_by_storage_class to all_storage_classes_128K, so our bucket behaves as if created today. Because our bucket predates September 2024, it was on the legacy default of varies_by_storage_class. Amazon since September 2024 defaults to all_storage_classes_128K, which prevents objects <128KB from transitioning to any storage class. Note that the legacy behaviour only applies to Glacier and our current lifecycle rule only moves to Infrequent Access, so this has no practical effect today. But aligning with the new defaults avoids footguns if we add Glacier transitions in the future. Source: https://aws.amazon.com/about-aws/whats-new/2024/09/amazon-s3-default-minimum-object-size-lifecycle-transition-rules/
arianvp
force-pushed
the
push-olkuqsupuvpq
branch
from
d1248b6 to
d61f58f
Compare
mweinelt
approved these changes
Feb 20, 2026
Member
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
2 participants
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.
Switch transition_default_minimum_object_size from varies_by_storage_class
to all_storage_classes_128K, so our bucket behaves as if created today.
Because our bucket predates September 2024, it was on the legacy default of
varies_by_storage_class. Amazon since September 2024 defaults to
all_storage_classes_128K, which prevents objects <128KB from transitioning
to any storage class.
Note that the legacy behaviour only applies to Glacier and our current
lifecycle rule only moves to Infrequent Access, so this has no practical
effect today. But aligning with the new defaults avoids footguns if we add
Glacier transitions in the future.
Source: https://aws.amazon.com/about-aws/whats-new/2024/09/amazon-s3-default-minimum-object-size-lifecycle-transition-rules/