# Missing Intelligent-Tiering on EFS lifecycle policy Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/missing-intelligent-tiering-on-efs-lifecycle-policy EFS offers lifecycle policies that transition files from the Standard tier to Infrequent Access (IA) based on inactivity, significantly reducing... By: Charles Haile Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Missing Intelligent-Tiering on EFS Lifecycle Policy The short version EFS offers lifecycle policies that transition files from the Standard tier to Infrequent Access (IA) based on inactivity, significantly reducing storage costs for cold data. [Charles Haile](https://www.linkedin.com/in/charles-haile-730a3676/) Procurement and FinOps Manager @ Insurity AWS service [AWS EFS](https://www.pointfive.co/efficiency-hub/cloud-services/aws-efs) Category [Storage](https://www.pointfive.co/efficiency-hub/service-category/storage) Reference CER-0190 Type Excessive Data Retention ## Explanation Why the waste happens and who it affects. When this feature is not enabled, infrequently accessed files remain in the more expensive Standard tier indefinitely. This often occurs when the file system is initially provisioned for performance but long-term access patterns are not reevaluated. File systems created in the console with the recommended settings get a default lifecycle configuration (transition into IA after 30 days and into Archive after 90 days since last access), so this mainly applies to file systems created without a lifecycle configuration, for example through the API, CLI, or infrastructure-as-code, or where lifecycle management was turned off. The Archive storage class is available only for file systems that use the Elastic throughput mode. ## Billing model The pricing dimensions that drive this cost. Billed per GB-month based on storage class (e.g., Standard, Infrequent Access); access and metadata requests may incur additional charges ## How to detect 5 checks to find it in your estate. - Review if lifecycle management is disabled or not set to transition files after an appropriate period of inactivity - Evaluate the proportion of files that are infrequently accessed yet stored in the Standard tier - Check whether the file system is used by workloads with predictable cold data patterns (e.g., logs, archive, ML input files) - Determine if storage costs are dominated by data that has not been accessed in weeks or months - Confirm whether business requirements permit longer access latencies for cold data ## How to fix 3 ways to remove the waste. - Enable EFS lifecycle management with a transition period (e.g., 7, 14, 30 days) aligned to actual data access patterns - Monitor and periodically review access logs or file activity metrics to refine lifecycle timing - If access latency is not a concern, consider more aggressive transitions to IA for archival-type data ## Documentation Vendor references for pricing and configuration. - [Managing storage lifecycle docs.aws.amazon.com](https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html) - [Configuring lifecycle policies docs.aws.amazon.com](https://docs.aws.amazon.com/efs/latest/ug/enable-lifecycle-management.html) - [EFS Pricing aws.amazon.com](https://aws.amazon.com/efs/pricing/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS EFS CER-0198 ### [Suboptimal Use of EFS Storage Classes](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-efs-storage-classes) Many organizations default to storing all EFS data in the Standard class, regardless of how frequently data is accessed. This results in inefficient spend for workloads with significant portions of data that are rarely read. EFS IA and... Storage - AWS EFS CER-0123 ### [Overprovisioned Throughput in EFS](https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-throughput-in-efs) When file systems are launched with Provisioned Throughput, teams often overestimate future demand - especially in environments cloned from production or sized "just to be safe." Over time, many workloads consume far less throughput than... Storage - AWS EFS CER-0143 ### [Missing Lifecycle Policy on Replicated EFS File System](https://www.pointfive.co/efficiency-hub/inefficiencies/missing-lifecycle-policy-on-replicated-efs-file-system) When replicating an EFS file system across AWS regions (e.g., for disaster recovery), the destination file system does not automatically inherit the source's lifecycle policy. As a result, files replicated to the destination will remain in... Storage --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.