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.