Posted on Jun 16 At this point most AWS professionals are familiar with the various options for how to store data in S3, but there is a point of confusion that can be expensive. At a previous company this confusion led them to spend three million dollars a year that they didn't have to.Part of the confusion is understandable as it seem that AWS tweaks the S3 storage options at every re:Invent. Another part of the confusion however comes from thinking that if an answer is too good to be true it must be false.The key distinction lies in a subtlety of Intelligent Tiering. We tend to be familiar with the "normal" storage classes of Standard-Access, Infrequent-Access, and "Glacier". We know the mantra that if you know you will not access an Object much and can tolerate some delay when you do access it you can save money.What is often missed however is that there is a cost to retrieve objects from Infrequent Access. There you are happily saving 50% of the cost after moving your objects to IA when someone accesses all that data, or worse yet accesses it multiple times (think data science jobs). Suddenly the access charges hit you with 100% or 200% of your cost. The sudden giant bill sours you (and your organization) on IA and it becomes a forbidden topic.This is where the subtlety of Intelligent-Tiering (IT)comes in. Objects in the IT storage class are moved between the "normal" storage classes based on usage. When an object is unused it moves 'down' to storage classes and when it is used it moves back to Standard Access. The key point is that there is no access charge for these movements. So if an object in IT-IA is accessed and moved back to SA you do not pay the fee that you would have if the object had been in "normal" IA.So, what's the catch? Well, there is monitoring charge per object in IT. This is not size based but simply based on the number of objects. So, if all of your objects were accessed all of the time IT would not save anything (because the objects would live in IT-SA) and there would in fact be the additional monitoring charge. So, if your objects are all under constant use then IT is not for you.One middle ground that some companies embrace is to only set their largest objects to IT. The large objects are by definition the most expensive ones and so will gain the most from the cost saving of IT while minimizing the relative effect of the monitoring cost. These companies use S3 Lifecyle rules to move objects over a certain size to IT.Another fear factor for companies is retrieval time. When Glacier was first introduced it was understood that not only would retrieval from Glacier be costly, it would also be slow. As more storage options were introduced each had its own retrieval characteristics. Glacier Deep Archive is the slowest and least expensive option (until you retrieve from it) because its basically a tape archive. On the other hand, Glacier Instant Access a bit of a self contradiction. It's glacier so it's "slow" but it's instant access so it's "fast?".If you configure Intelligent Tiering to just use Standard Access, Infrequent Access and the strangely named Glacier Instant Access then you get the performance characteristics of normal Standard Access.Some companies decide this is too good to be true and so assume its false. Other companies run performance tests of their own. These tests confirm that the top three levels of IT have (within 3%) the same first-byte-access times of Standard Access.So, the bottom line is you can save half of your S3 costs with no change to your overall system performance. Once you see it in that light the choice seems clear.If you configure Intelligent Tiering to just use Standard Access, Infrequent Access and the strangely named Glacier Instant Access then you get the performance characteristics of normal Standard Access.Some companies decide this is too good to be true and so assume its false. Other companies run performance tests of their own. These tests confirm that the top three levels of IT have (within 3%) the same first-byte-access times of Standard Access.So, the bottom line is you can save half of your S3 costs with no change to your overall system performance. Once you see it in that light the choice seems clear.Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse David Llerena - May 8 '22 I'm Luis! \^-^/ - Apr 4 '22 Yasunori Kirimoto - Apr 25 '22 Md Mohaymenul Islam (Noyon) - Apr 10 '22 Once suspended, aws-heroes will not be able to comment or publish posts until their suspension is removed. Once unsuspended, aws-heroes will be able to comment and publish posts again. Once unpublished, all posts by aws-heroes will become hidden and only accessible to themselves. If aws-heroes is not suspended, they can still re-publish their posts from their dashboard. Note: Once unpublished, this post will become invisible to the public and only accessible to Brian Tarbox. They can still re-publish the post if they are not suspended. Thanks for keeping DEV Community safe. Here is what you can do to flag aws-heroes: aws-heroes consistently posts content that violates DEV Community's code of conduct because it is harassing, offensive or spammy. Unflagging aws-heroes will restore default visibility to their posts. DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey. Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2023. We're a place where coders share, stay up-to-date and grow their careers.