<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS S3 on Mexicali IT</title><link>https://mxlit.com/technologies/aws-s3/</link><description>Recent content in AWS S3 on Mexicali IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Mar 2026 03:00:00 -0700</lastBuildDate><atom:link href="https://mxlit.com/technologies/aws-s3/index.xml" rel="self" type="application/rss+xml"/><item><title>Isilon OneFS: Transparent Cloud Tiering &amp; Cost Optimization with CloudPools (AWS S3)</title><link>https://mxlit.com/kb-00086/</link><pubDate>Sun, 22 Mar 2026 03:00:00 -0700</pubDate><guid>https://mxlit.com/kb-00086/</guid><description>&lt;p&gt;As data volumes continue to grow explosively, a significant percentage inevitably becomes &amp;ldquo;cold data&amp;rdquo;—historical files that are rarely accessed. Keeping this inactive data sitting on high-performance primary storage is extremely cost-inefficient.&lt;/p&gt;
&lt;p&gt;To solve this, OneFS integrates &lt;strong&gt;CloudPools&lt;/strong&gt;, a powerful tiering feature that allows you to seamlessly move inactive data blocks to an external object storage platform like Amazon S3, Azure Blob, or a local ECS. When data is tiered, OneFS leaves behind a reference file (a SmartLink, or &lt;em&gt;stub&lt;/em&gt;) on the local file system. To end-users connected via SMB or NFS, the file still appears in its original location as normal; however, when they try to open it, the cluster retrieves the payload from the cloud transparently.&lt;/p&gt;</description></item></channel></rss>