<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Storage on LeanerCloud</title><link>https://leanercloud.com/tags/storage.html</link><description>Recent content in Storage on LeanerCloud</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 02:08:40 +0200</lastBuildDate><atom:link href="https://leanercloud.com/tags/storage/index.xml" rel="self" type="application/rss+xml"/><item><title>Slashing S3 costs with the right storage class and lifecycle rules</title><link>https://leanercloud.com/blog/2025-05-29-s3-storage-class-and-lifecycle-savings.html</link><pubDate>Thu, 29 May 2025 21:31:47 +0000</pubDate><guid>https://leanercloud.com/blog/2025-05-29-s3-storage-class-and-lifecycle-savings.html</guid><description>&lt;h2 id="most-large-s3-bills-are-old-data-in-the-wrong-tier"&gt;Most large S3 bills are old data in the wrong tier&lt;/h2&gt;
&lt;p&gt;When a client has a large S3 bill, the cause is usually not the data they are actively using. It is data they stopped using years ago and kept paying full price to store, because it is sitting in S3 Standard when it should be in a cheaper tier or deleted outright.&lt;/p&gt;
&lt;p&gt;On one client, the vast majority of their S3 cost came from buckets storing logs. They had many dozens of terabytes of old log files as S3 Standard, spread across multiple buckets, some of it dating back five years. They only needed a few months of retention. They were paying thousands of dollars a month to keep years of logs they would never look at.&lt;/p&gt;</description></item></channel></rss>