Skip to content
Draft: this topic has not been reviewed yet. Check facts against the linked AWS documentation before relying on them.

Storage types compared — block, file and object storage on AWS

Solutions Architect – Associate · Domain 3 · Design High-Performing ArchitecturesTask 3.1: Determine high-performing and/or scalable storage solutionsLevel 120 minComparisonDraft
Difficulty
Confidence

AWS has storage for every kind of need. The trick is to recognize how the data is used, because that decides the kind of storage:

  • Block storage: a disk for one server, divided into blocks the operating system manages.
  • File storage: a shared drive with folders that many servers use at once.
  • Object storage: a store of whole files reached over the web by any client.
Block — Amazon EBSEC2 instanceOne instance, one AZ,like a hard driveFile — Amazon EFSEC2EC2EC2File systemMany instances sharethe same filesObject — Amazon S3AppBrowserServiceHTTPS (API)BucketAny client, from anywhere,any amount of data
Block storage is a disk for one server, file storage is a shared drive, and object storage is a web-accessible store for any client.

Block storage: disks for EC2

Amazon Elastic Block Store (Amazon EBS)

An EBS volume is a network-attached disk for an EC2 instance, like a hard drive.

  • It lives in one Availability Zone and attaches to an instance in that AZ (normally one instance at a time).
  • Data persists when the instance stops; the volume can be detached and attached to another instance.
  • Snapshots back up a volume to S3 behind the scenes, and can be copied to other Regions.
  • You choose the size and type (for example general purpose SSD, or high-performance SSD for databases) and pay for what you provision.

Typical uses: the boot disk of an instance, and databases running on EC2.

Instance store

Some instance types include an instance store: disks physically attached to the host computer.

  • Very fast, and included in the instance price.
  • Temporary: the data is lost when the instance stops, hibernates or terminates, or if the underlying hardware fails.

Typical uses: caches, buffers and scratch data you can afford to lose.

File storage: shared file systems

Amazon Elastic File System (Amazon EFS)

EFS is a shared file system for Linux workloads that many instances can use at the same time, across multiple Availability Zones.

  • It grows and shrinks automatically as you add and remove files; there is no size to choose.
  • You pay for the storage you use.

Typical uses: shared content for a fleet of web servers, home directories, shared files for containers.

Amazon FSx

FSx gives you fully managed file systems built on popular file system software:

FSx option Use it for
FSx for Windows File Server Windows applications and shared drives that use the SMB protocol and Active Directory
FSx for Lustre High-performance computing and machine learning that need very fast file access
FSx for NetApp ONTAP Moving NetApp-based storage to AWS with the same features
FSx for OpenZFS Moving ZFS-based or Linux file servers to AWS

A simple rule: Linux shared files → EFS; Windows shared files → FSx for Windows File Server.

Object storage: Amazon S3

S3 stores objects in buckets, reached over HTTPS by any application, browser or service. It scales without limits, is designed for eleven nines of durability, and offers cheaper storage classes for rarely used data. See Amazon S3 basics.

Side by side

Amazon EBS Instance store Amazon EFS Amazon FSx Amazon S3
Type Block Block File File Object
Used by One EC2 instance The one instance on that host Many Linux instances Many instances (Windows, Linux, HPC) Any client over HTTPS
Scope One AZ That host Regional Depends on deployment Regional
Survives stop Yes No Yes Yes Yes
Size You choose Fixed by instance type Grows automatically You choose Grows automatically
Typical use Boot disks, databases on EC2 Caches, scratch data Shared Linux files Windows shares, HPC Backups, media, data lakes, websites

Hybrid storage: AWS Storage Gateway

AWS Storage Gateway connects your on-premises applications to storage in AWS. It runs as a virtual or hardware appliance in your data center and keeps recently used data in a local cache, so access is fast while the full data lives in AWS.

Gateway type What on-premises systems see Data stored in
Amazon S3 File Gateway A file share (NFS or SMB) Amazon S3
Amazon FSx File Gateway A Windows file share FSx for Windows File Server
Tape Gateway A virtual tape library for backup software S3 and Glacier storage classes
Volume Gateway Block storage volumes (iSCSI) AWS, with EBS snapshots

This is what the exam means by a cached file system: local speed, cloud capacity.

Protecting data: AWS Backup

AWS Backup manages backups centrally across many services: EBS volumes, EC2 instances, RDS and Aurora databases, DynamoDB tables, EFS and FSx file systems, S3 and more.

  • You create a backup plan: how often to back up, how long to keep backups, and whether to copy them to another Region or account.
  • It replaces many separate backup scripts with one policy, which also helps prove compliance.

Putting it together: a media company

  • Video editors on Windows share project files on FSx for Windows File Server.
  • The rendering farm, on Linux EC2 instances, reads shared assets from EFS, and uses instance store for temporary render files.
  • Finished videos are stored and served from S3, and old projects move to Glacier with lifecycle rules.
  • The office’s old tape backups are replaced by Tape Gateway, which stores virtual tapes in AWS.
  • AWS Backup runs nightly backups of all EBS volumes and databases and copies them to a second Region.

Common mix-ups

  • EBS vs instance store. Both are block storage, but EBS persists when the instance stops; instance store does not.
  • EFS vs FSx. EFS is for Linux; FSx offers Windows, Lustre, NetApp ONTAP and OpenZFS file systems.
  • EBS vs EFS. One instance’s disk vs a file system shared by many instances.
  • Storage Gateway vs Backup. Storage Gateway connects on-premises systems to AWS storage; AWS Backup schedules and manages backups.

Check yourself

Many Linux web servers need to read and write the same files at once. Which service fits?

Amazon EFS.

A Windows application needs a shared drive with Active Directory integration. Which service?

Amazon FSx for Windows File Server.

What happens to instance store data when you stop the instance?

It is lost. Instance store is temporary storage.

An on-premises backup system writes to tapes. How can it store backups in AWS without changing the software?

AWS Storage Gateway – Tape Gateway, which presents a virtual tape library backed by AWS storage.

A company wants one place to schedule and manage backups of EBS, RDS and DynamoDB. Which service?

AWS Backup.

Exam tip for Cloud Practitioner

“Attach a disk to my EC2 instance” → EBS. “Temporary, very fast local storage” → instance store. “Many servers share files” → EFS (Linux) or FSx (Windows). “Store and serve any number of files from anywhere” → S3. “On-premises access to cloud storage with a local cache” → Storage Gateway. “Centralized backup across services” → AWS Backup.

Key takeaways

  • Block (EBS, instance store), file (EFS, FSx) and object (S3) storage serve different access patterns.
  • EBS persists; instance store is temporary; EFS and FSx are shared; S3 is for any client over the web.
  • Storage Gateway links on-premises systems to AWS storage; AWS Backup manages backups centrally.

Cloud Study Lab is an independent study site. It is not affiliated with or endorsed by Amazon Web Services. AWS and the names of AWS certifications are trademarks of Amazon.com, Inc. or its affiliates.