Skip to content
Cloud Efficiency Hub

Suboptimal Use of EFS Storage Classes

The short version

Many organizations default to storing all EFS data in the Standard class, regardless of how frequently data is accessed.

Amay Chandravanshi

Cloud FinOps Engineer @ Syngenta Group

AWS service
AWS EFS
Category
Storage
Reference
CER-0198
Type
Suboptimal Tier or SKU

Explanation

Why the waste happens and who it affects.

This results in inefficient spend for workloads with significant portions of data that are rarely read. EFS IA and Archive tiers offer lower-cost alternatives for data with low or near-zero access, while Intelligent Tiering can automate placement decisions. Failing to leverage these options wastes storage spend and reduces cost efficiency.

Billing model

The pricing dimensions that drive this cost.

EFS charges separately for data stored in each class. Standard storage is priced highest, while IA and Archive offer lower storage costs but charge per GB for reads and for tiering data into and out of those classes. Both bill a minimum of 128 KiB per file, and Archive has a 90-day minimum storage duration and is supported only on file systems using Elastic throughput. Intelligent Tiering automatically transitions data between classes based on access patterns. Placing all data in Standard when much of it is infrequently accessed leads to unnecessary cost.

How to detect

4 checks to find it in your estate.

  • Review whether large EFS volumes are configured entirely in Standard storage class without considering access frequency
  • Assess whether filesystems contain long-lived data with little or no recent access
  • Evaluate if Intelligent Tiering could automate tier placement in cases where access patterns are unpredictable
  • Compare storage distribution across Standard, IA, and Archive tiers to workload access requirements

How to fix

4 ways to remove the waste.

  • Transition infrequently accessed data to EFS IA or Archive storage classes to reduce cost
  • Enable Intelligent Tiering for workloads where access frequency is variable or difficult to predict
  • Maintain Standard storage only for data that requires frequent or high-performance access
  • Periodically review access patterns and adjust lifecycle policies to align with current workload usage

Documentation

Vendor references for pricing and configuration.