Submit feedback on
Overprovisioned Throughput in EFS
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Overprovisioned Throughput in EFS
Matt Wilder
Service Category
Storage
Cloud Provider
AWS
Service Name
AWS EFS
Inefficiency Type
Explanation

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 allocated, especially in dev/test environments or during periods of reduced usage. These overprovisioned settings can silently accrue substantial monthly charges that go unnoticed without intentional review.

This inefficiency is not flagged by AWS Trusted Advisor and is easy to miss. Elastic Throughput mode now offers a scalable alternative that automatically adjusts capacity — but isn’t always cheaper, depending on the workload’s sustained throughput.

Relevant Billing Model

Amazon EFS supports three throughput modes:

Bursting Throughput Mode – Default option for General Purpose file systems. Throughput automatically scales with the amount of storage; short bursts above the baseline are supported using a credit system. No separate throughput charge.

Provisioned Throughput Mode – Throughput is explicitly configured in MB/s and billed separately from storage, regardless of actual usage.

Elastic Throughput Mode – Throughput scales automatically to meet demand and is billed based on actual usage above the baseline included with storage.

Provisioned throughput is billed continuously, even if the application’s actual throughput is far below the configured amount. Elastic mode eliminates this fixed cost but can be more expensive if workloads regularly exceed the baseline.

Detection
  • Identify EFS file systems configured with Provisioned Throughput Mode
  • Compare provisioned throughput (MB/s) to actual usage over time
  • Assess whether throughput usage consistently falls below provisioned baseline
  • Flag file systems in dev/test environments that mirror production settings
  • Evaluate whether switching to Elastic Throughput/Bursting Throughput would reduce cost without affecting performance
  • Confirm whether burst patterns might result in higher costs under Elastic mode
Remediation
  • Reconfigure overprovisioned file systems with a reduced Provisioned Throughput value
  • For workloads with low and predictable throughput, consider switching to Elastic Throughput
  • For dev/test systems cloned from production, adjust throughput settings independently
  • Establish a periodic review of throughput configurations as part of FinOps or infrastructure governance
Submit Feedback