feat(transform): Add Storage Class Support to AWS S3 #189
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.
Description
Motivation and Context
This makes it possible to upload objects with unique storage class settings directly to an S3 bucket, which is useful if the transform is being used for the purpose of archiving data.
Another way to do this is with a lifecycle rule, but there are caveats to using that method, such as the object needing to stay in Standard storage for a minimum number of days and the additional cost of transitioning objects between storage classes.
The list of valid storage class strings is here.
How Has This Been Tested?
This has been E2E tested in a production environment for multiple days.
Types of changes
Checklist: