Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage Lifecycle Service: support new AWS s3 parameter of lifecycle configuration to move files of any sizes #3753

Open
SilinPavel opened this issue Oct 24, 2024 · 0 comments
Labels
kind/enhancement New feature or request

Comments

@SilinPavel
Copy link
Member

SilinPavel commented Oct 24, 2024

Background

Related to #2721

Based on https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-transition-general-considerations.html#lifecycle-configuration-constraints
Starting from September 2024 we can control size of the files which will be moved to archive classes.

Approach

  • Introduce new property minimum_object_size_for_transit of cloud region sls properties.
  • During sls execution cycle support usage of this property:
    • If exists and >= 0 use i as ObjectSizeGreaterThan param value for S3 Bucket LifecycleConfiguration
    • If doesn't exists do not specify ObjectSizeGreaterThan param which effectively leads to effect that files < 128Kb won't be transitioned
@SilinPavel SilinPavel added the kind/enhancement New feature or request label Oct 24, 2024
SilinPavel added a commit that referenced this issue Oct 24, 2024
…rty from sls cloud region config. Expand exception logging.
SilinPavel added a commit that referenced this issue Oct 24, 2024
…rty from sls cloud region config. Expand exception logging.
SilinPavel added a commit that referenced this issue Oct 25, 2024
SilinPavel added a commit that referenced this issue Oct 25, 2024
…lifecycle rule to the list of new rules to apply if it matches a new one
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant