- Newest
- Most votes
- Most comments
Could you refer to this documentation :- https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html
Also you can follow these below Viewing and Editing an S3 Lifecycle Policy
Step 1: Access the S3 Console Log in to the AWS Management Console.Navigate to the S3 Service: In the AWS Management Console, type "S3" in the search bar at the top and select "S3" from the dropdown menu.
Step 2: Select Your Bucket Select the Bucket: In the S3 console, you will see a list of your buckets. Click on the name of the bucket you want to manage.
Step 3: Navigate to the Lifecycle Policies Go to the Management Tab: Once you are in your bucket, click on the "Management" tab. View Lifecycle Rules: Under the Management tab, you will see a section for "Lifecycle rules". Here, you can view existing lifecycle rules.
Step 4: Edit an Existing Lifecycle Policy Select the Rule to Edit: In the Lifecycle rules section, you will see a list of your existing rules. Find the rule you want to edit and click on it. Edit the Rule: Click the "Edit" button to modify the rule. You will be taken to the rule editing wizard.
Step 5: Modify the Transition to Glacier Deep Archive Configure Rule Actions: In the rule editing wizard, you will see different rule actions. Find the action related to transitioning objects to Glacier Deep Archive. Change the Interval: Modify the interval (number of days) between object upload and migration to Glacier Deep Archive. For example, you might change it from 30 days to 60 days. Save Changes: After making your changes, continue through the wizard and save the changes.
Step 6: Review and Save Review the Changes: Review the changes you have made to ensure everything is correct. Save the Lifecycle Rule: Click "Save" to apply the changes to your lifecycle policy.
Select your S3 bucket -> Management tab -> Create lifecycle rule
Lifecycle rule name, Apply to all objects in the bucket
Move current versions of objects between storage classes -> Select Storage Class (e.g. Glacier)
Days after object creation - Enter number of days
This rule is missing a minimum size filter. Small objects will cost more if they're transitioned to Glacier Deep Archive, so a minimum size limit should always be applied in transitioning rules.
Relevant content
- asked 9 months ago
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated a year ago- How do I create Amazon Data Lifecycle Manager policies from selected EBS volumes in the EC2 console?AWS OFFICIALUpdated 2 years ago
But importantly, make sure to add a size limit for any rule that transitions objects to any of the Glacier classes, particularly Deep Archive. If you transition small or tiny objects, the 8 kiB of overhead charged at Standard class rates and 32 kiB of overhead charged at the respective Glacier rate will increase costs for small objects, rather than saving a single cent. I would generally recommend setting the transitioning threshold to Deep Archive to 1 MiB or 256 kiB, unless it's certain that there are lots of smaller objects that would benefit from it.