EBS vs EFS: Differences and Which the AWS Exam Expects (2026)

Illustration comparing storage plugged into one server with a central storage unit cabled to several servers

Amazon EBS is block storage: a virtual disk attached to one EC2 instance in one Availability Zone, ideal for boot volumes and databases. Amazon EFS is a managed network file system that many instances, containers and Lambda functions can mount at the same time, across Availability Zones, and it grows and shrinks automatically. On the exam, “shared by many instances” or “across AZs” points to EFS, and “boot volume”, “database” or “lowest latency for one instance” points to EBS.

Facts verified November 2026 against the Amazon EBS and Amazon EFS user guides.

EBS vs EFS at a glance

In short: EBS is a fast private disk for one instance, and EFS is a shared folder for many.

Amazon EBSAmazon EFS
Storage typeBlock storage (a volume)File storage (NFS file system)
Who can use itOne EC2 instance at a time, in the same AZ. Multi-Attach lets some io1/io2 volumes attach to several Nitro instances in one AZMany clients at once: EC2, Amazon ECS, Amazon EKS, AWS Lambda, and on-premises servers over Direct Connect or VPN
ScopeOne Availability ZoneRegional (data stored across multiple AZs) or One Zone
SizingYou provision a size and can increase itElastic: grows and shrinks with your files, with no provisioning
PricingPay for the provisioned size (and provisioned IOPS or throughput where applicable)Pay for storage used, by storage class
Performance optionsVolume types: gp3 (general SSD), io2 Block Express (high IOPS), st1 (throughput HDD), sc1 (cold HDD)Throughput modes: Elastic, Provisioned, Bursting. Storage classes: Standard, Infrequent Access, Archive
Boot volumeYesNo
Operating systemsAny OS that EC2 supportsLinux clients (NFS). For Windows SMB shares, use Amazon FSx for Windows File Server
BackupsIncremental snapshots, copyable to other RegionsAWS Backup, plus EFS replication to another Region or AZ

Choose EBS when…

  • You need a boot or root volume for an EC2 instance.
  • A single instance needs low-latency block storage, for example a self-managed database such as MySQL or PostgreSQL on EC2.
  • The workload needs high, consistent IOPS. Use io2 Block Express or provisioned gp3.
  • You want point-in-time snapshots of a volume to restore or copy to another AZ or Region.

Choose EFS when…

  • Several instances must read and write the same files at the same time: a shared content directory, user uploads, or home directories.
  • The storage must survive an AZ failure without you managing replication. Regional EFS stores data across AZs.
  • You don’t know how much space you’ll need. EFS grows and shrinks on its own.
  • Containers or Lambda functions need persistent shared storage. Both ECS/EKS tasks and Lambda can mount EFS.
  • Files are rarely accessed after a while. Lifecycle management moves them to cheaper storage classes automatically.

Where do S3 and FSx fit?

The exam often lists all of them, so know the split:

NeedService
Disk for one EC2 instance, boot volume, databaseAmazon EBS
Shared Linux file system (NFS) across instances and AZsAmazon EFS
Shared Windows file system (SMB, Active Directory)Amazon FSx for Windows File Server
High-performance computing, often linked to S3Amazon FSx for Lustre
Objects accessed over HTTP, static websites, data lakes, backupsAmazon S3
Temporary scratch space that can be lost when the instance stopsEC2 instance store

Exam cues: which answer the question wants

Cue in the questionLikely answerExam
“Block storage for EC2”Amazon EBSCLF-C02
“File storage shared by multiple instances”Amazon EFSCLF-C02, SAA-C03
“Linux instances in several AZs must share files”Amazon EFS (Regional)SAA-C03
“Windows instances need a shared file system”FSx for Windows File Server (not EFS)SAA-C03
“Highest IOPS for a database on EC2”EBS io2 Block ExpressSAA-C03
“Cost-effective general-purpose SSD with independent IOPS and throughput settings”EBS gp3SAA-C03, SOA-C03
“Large sequential throughput, lowest cost HDD”EBS st1 (frequent) or sc1 (cold)SAA-C03
“Files rarely accessed after 30 days, reduce cost”EFS lifecycle management to Infrequent AccessSAA-C03, SOA-C03
“Lambda function needs a shared file system”Amazon EFSSAA-C03
“Copy a volume to another Region for DR”EBS snapshot copied cross-RegionSAA-C03, SOA-C03
“Data must persist after the instance stops”EBS (not instance store)SAA-C03

Worked example 1: the shared upload folder

A web application runs on an Auto Scaling group of Linux EC2 instances across three Availability Zones. Users upload files, and every instance must be able to read every uploaded file immediately. The amount of data is growing unpredictably. Which storage should the application use?

Three requirements decide it: many instances, several AZs and unpredictable growth. An EBS volume belongs to one AZ and, in practice, one instance. Even Multi-Attach only works within one AZ and with specific volume types, so EBS fails the multi-AZ requirement. EFS can be mounted by every instance in every AZ at once, stores data across AZs, and grows automatically, so you never resize anything. The answer is a Regional EFS file system mounted on all instances. If the instances ran Windows, the answer would change to FSx for Windows File Server.

Worked example 2: the database on EC2

A company runs a self-managed database on a single EC2 instance. The database needs consistently high IOPS and the lowest possible latency. Which storage option is most suitable?

Only one instance needs the storage, and the priorities are IOPS and latency. A network file system adds latency and isn’t designed for database block I/O, so EFS is the wrong fit. EBS gives the instance a dedicated block device, and the io2 Block Express volume type is built for high, consistent IOPS. If the question said “cost-effective” and the IOPS needs were moderate, gp3 with provisioned IOPS would be the answer instead. Instance store would be fast, but data is lost if the instance stops, so it’s wrong for a database.

Common EBS vs EFS traps

  1. “EBS volumes can be shared across AZs.” They can’t. A volume lives in one AZ. Use a snapshot to move data to another AZ.
  2. Multi-Attach as a file share. Multi-Attach is limited to certain io1/io2 volumes in one AZ, and the application must manage concurrent writes. It isn’t a shared file system.
  3. EFS for Windows. EFS uses NFS for Linux clients. Windows file shares mean FSx for Windows File Server.
  4. EFS as a boot volume. EC2 boots from EBS (or instance store), never from EFS.
  5. Paying for unused EBS space. EBS charges for the size you provision, even if it’s empty. EFS charges for what you store.
  6. Instance store vs EBS. Instance store is temporary. “Data must persist” rules it out.

EBS vs EFS FAQ

Is EFS faster than EBS?

Not for a single instance. EBS usually gives lower latency because it’s block storage attached to the instance. EFS scales throughput across many clients, so it wins for parallel, shared access.

Is EFS more expensive than EBS?

Per GB, EFS Standard usually costs more than EBS gp3. But EFS charges only for what you store, and its Infrequent Access and Archive classes cost much less, so the total depends on the workload.

Can I use EFS with Windows?

No. EFS supports Linux clients over NFS. Use Amazon FSx for Windows File Server for Windows workloads.

Can multiple EC2 instances share one EBS volume?

Only with Multi-Attach, which works with certain io1 and io2 volumes and Nitro instances in the same AZ. For general file sharing, use EFS.

How do I back up EBS and EFS?

EBS uses incremental snapshots. EFS uses AWS Backup and can replicate to another Region. AWS Backup can manage both centrally.

Test yourself

Storage choices appear throughout SAA-C03. Try our free AWS Solutions Architect Associate practice exam, then take a full timed test:

Free mock exam

Take SAA-C03 Mock Exam 1, free

A full-length, timed mock in the real exam format, with every answer explained so you know exactly where you stand.

65

questions

130

minutes

720

to pass

Free account required.

The full set is in our SAA-C03 practice exams.

Read the SAA-C03 exam guide, or compare networking next in NAT gateway vs internet gateway.


AWSBoy is not affiliated with Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates.

Sources (checked November 2026): Amazon EBS User Guide · Amazon EBS volume types · EBS Multi-Attach · Amazon EFS User Guide · EFS storage classes · Amazon FSx for Windows File Server · Amazon EBS pricing · Amazon EFS pricing

Shopping Cart
Scroll to Top