Skip to content

Instantly share code, notes, and snippets.

@jflasher
Created February 1, 2019 15:21
Show Gist options
  • Select an option

  • Save jflasher/1a97b9f3f7e2bbf232086e3ca31119e1 to your computer and use it in GitHub Desktop.

Select an option

Save jflasher/1a97b9f3f7e2bbf232086e3ca31119e1 to your computer and use it in GitHub Desktop.
Instructions for setting up a lifecycle policy for S3 Intelligent-Tiering

Amazon S3 now supports a new storage class called Intelligent Tiering. This will be a very attractive option for many customers who have datasets that are accessed in unpredictable patterns. You can set this storage class when uploading any new data. However, the below instructions will allow you to set up a lifecycle policy that will change the storage class of data that already exists in your bucket.

To set up a lifecycle policy to change the storage class of the data currently stored in your Amazon S3 bucket, follow the below steps.

  1. Visit the S3 console and go to your bucket of interest.

  2. Click on the Management tab at the top and select + Add lifecycle rule.

  3. Enter a rule name of your choice (e.g., Convert to Intelligent Tiering storage class). Unless you want to filter which data is converted to the new storage class, you can leave the prefix/tag filter field empty.

  4. Click Next.

  5. Select the Current Version checkbox unless you have previously enabled versioning. Click the + Add transition link that appears.

  6. Select Transition to Intelligent-Tiering after in the dropdown box. You can leave the Days after creation value at its default of 0.

  7. Click Next.

  8. We do not need to set any expirations at this time. Click Next.

  9. You can review your settings and if all looks well, click Save.

You now have a lifecycle policy in place that will move any existing data (and new data that comes in) to the Intelligent-Tiering storage class.

@MrCsabaToth
Copy link

Is it possible to configure Intelligent Tiering to only go as far as Archive Instant Access (AIA) and don't move stuff to higher latency Archive tiers? If yes where?

@jflasher
Copy link
Author

jflasher commented Mar 5, 2024

Hi @MrCsabaToth I'd recommend checking out the docs or re:Post. This is not something I've looked into for quite some time at this point.

@99702
Copy link

99702 commented Nov 27, 2025

@jflasher , in 5th section, there is no such current version rather there is a list containing:
a. Transition current versions of objects between storage classes
b. Transition noncurrent versions of objects between storage classes
c. Expire current versions of objects
d. Permanently delete noncurrent versions of objects
e. Delete expired object delete markers or incomplete multipart uploads

If we choose a. , I get

Transitions are charged per request
For a lifecycle transition action, each request corresponds to an object transition. For details on lifecycle transition pricing, see requests pricing info on the Storage & requests tab of the [Amazon S3 pricing page ](https://aws.amazon.com/s3/pricing).

Does this mean , like if we have alot of pdf , then for each pdf to transition into intelligent tiering will take additional cost .
Is it ok if i have small objects currently so transition will not take much charge?

Thanks for help .

@jflasher
Copy link
Author

Hi @99702, please see the previous comment for suggestions on where to find updated info. This is not something I have looked at for quite some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment