AWS EBS Support

Amazon EFS throughput modes and cost: Elastic, Provisioned or Bursting.

EFS performance and price depend on the throughput mode and on which storage class your files live in. A file system on Bursting mode can run out of credits, Provisioned mode can pay for unused throughput, and unused data can sit in expensive storage. We measure and choose.

ElasticPay per data read and written
ProvisionedPay for set throughput
BurstingScales with stored size
IA / ArchiveCheaper classes for cold files

When You Need This

The situations where this work pays for itself.

Signs it is time

  • Applications on EFS slow down under load
  • BurstCreditBalance is falling or at zero
  • You pay for provisioned throughput that is mostly idle
  • Most files are rarely read and the storage bill is high
  • WordPress, shared content or container workloads see slow file access

What you get

  • Throughput and cost analysis for each file system
  • Recommended throughput mode with cost model
  • Lifecycle policy and storage class settings
  • Mount configuration guidance and alarms

How we do it

A clear, safe process you can follow along with.

1. Measure current behavior

In CloudWatch we review PermittedThroughput, MeteredIOBytes, TotalIOBytes, PercentIOLimit and, for Bursting mode, BurstCreditBalance. This shows whether you are throttled or paying for headroom you do not use.

2. Understand the modes

Elastic throughput scales automatically with the workload and bills for data transferred, which suits spiky or unpredictable use. Provisioned throughput sets a fixed rate you pay for regardless of use. Bursting ties baseline throughput to the amount stored and uses credits above it.

3. Choose and change the mode

For variable workloads Elastic is usually simplest. For a steady high throughput relative to size, Provisioned can cost less. We model the monthly cost with your measured numbers, then change the mode, noting that there are limits on how often a mode change can be made.

4. Use lifecycle management for storage cost

We enable lifecycle policies to move files not accessed for a set period to Infrequent Access or Archive classes, with intelligent tiering back on access, and check the retrieval charges for your read patterns. One Zone classes suit data that does not need multi-AZ resilience.

5. Fix client and mount settings

We mount using the EFS mount helper from amazon-efs-utils, with TLS where required, use the mount target in the same Availability Zone to avoid cross-AZ latency, and review NFS options. Small-file workloads suffer from per-operation latency, so parallelism and caching in the application matter.

6. Review architecture fit

If the workload needs very low latency or heavy random I/O, EBS or instance storage may suit better. We also check for log or temp files written to EFS that could be moved off it.

7. Verify

We compare throughput, latency and the monthly bill before and after, and set alarms on burst credits, PercentIOLimit and throughput.

Mistakes we help you avoid

Common ways this goes wrong, and what we do instead.

Staying on Bursting with a small file system

Baseline is tied to size, so a small system can starve under load.

Provisioning for the peak

You pay for the full rate all month for a short spike.

Moving hot files to Infrequent Access

Access charges can exceed the saving. Check access patterns first.

Mounting a target in another Availability Zone

It adds latency and cross-AZ data transfer.

Frequently Asked Questions

Which EFS throughput mode should I use?

Elastic suits spiky or unknown workloads, Provisioned suits steady high throughput relative to stored data, and Bursting suits workloads whose throughput needs fit the size-based baseline. We decide from your CloudWatch data.

Why is my EFS slow?

Common causes are exhausted burst credits, reaching the throughput limit, many small file operations, cross-AZ mounts or a mismatch between workload and NFS. Metrics tell which.

How can I reduce EFS cost?

Use lifecycle management to move cold data to cheaper storage classes, pick the right throughput mode, and remove data that should not be on a shared file system.

Want Help With Amazon EFS throughput modes and cost: Elastic, Provisioned or Bursting?

Schedule an appointment. Tell us about your environment and we will outline the safest, highest-value approach.

Schedule Appointment › No commitment required