OC-1026: Configure intelligent tiering for S3 buckets #781
Conversation
This file contains 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.
The purpose of this PR was to make use of the intelligent tiering storage class for AWS S3 that intelligently moves objects into a different archival class based on the frequency of their retrieval for a small management fee.
I've applied it to the buckets that I expect to have lots of files and variable rates of retrieval.
Acceptance Criteria:
Intelligent tiering is used where beneficial.
Checklist:
Screenshots:
The lifecycle rules have moved items above 128KB to intelligent tiering. Any smaller file doesn't qualify for it. This transition happens overnight each day.