Study guide
3.4 Block and File Storage - EBS, EFS, and FSx
AWS Solutions Architect Associate SAA-C03
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework
2 Domain 1: Design Secure Architectures (30%)
1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services
3 Domain 2: Design Resilient Architectures (26%)
2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration
4 Domain 3: Design High-Performing Architectures (24%)
3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR
5 Domain 4: Design Cost-Optimized Architectures (20%)
4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools
6 VPC and Networking Deep Dive
5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services
7 Migration, Transfer, and Hybrid Services
6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family
8 Serverless Architecture and Application Services
7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR
9 Advanced Topics and Exam Scenarios
8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together
3.4 Block and File Storage - EBS, EFS, and FSx
Key Takeaways Explain This Topic AI
EBS is single-AZ block storage attached to one EC2 instance (io2/io2 Block Express support Multi-Attach to up to 16 instances in the same AZ).
gp3 baselines at 3,000 IOPS / 125 MB/s independent of size and can be provisioned up to 80,000 IOPS and 2,000 MB/s; io2 Block Express reaches 256,000 IOPS and 4,000 MB/s for the largest databases.
EFS is fully managed NFS shared across thousands of Linux instances and multiple AZs; FSx for Windows is SMB with Active Directory.
FSx for Lustre is a parallel POSIX file system for HPC/ML that integrates natively with S3 (read from and write back to a linked bucket).
Pick by protocol and sharing: single instance block -> EBS; shared Linux NFS -> EFS; Windows SMB -> FSx for Windows; HPC/ML scratch -> FSx for Lustre.
Last updated: October 2026
Quick Answer: EBS = single-AZ block volume for one instance. EFS = elastic shared NFS for many Linux instances across AZs. FSx for Windows = managed SMB with Active Directory. FSx for Lustre = high-throughput parallel file system for HPC/ML with native S3 integration. Choose on protocol, sharing scope, and performance target.
Amazon EBS (Elastic Block Store)
EBS volumes are network-attached virtual disks bound to a single Availability Zone . They persist independently of the instance lifecycle, support encryption with KMS (no measurable performance hit), and back up via incremental snapshots stored in S3 (which can be copied cross-Region for DR).
- Volume type API name Max IOPS Max throughput Use case
- General Purpose SSD gp3 80,000 2,000 MB/s Default for most workloads, boot, mid DBs
- General Purpose SSD gp2 16,000 250 MB/s Legacy; migrate to gp3
- Provisioned IOPS SSD io2 64,000 1,000 MB/s Critical Oracle/SQL Server/SAP
- Provisioned IOPS SSD io2 Block Express 256,000 4,000 MB/s Largest, most I/O-intensive databases
- Throughput HDD st1 500 500 MB/s Big data, log warehouses, streaming reads
- Cold HDD sc1 250 250 MB/s Infrequent access, lowest-cost HDD
- gp3 vs gp2 (a frequent exam contrast)
- Feature gp3 gp2
- Baseline IOPS 3,000 at any size 3 IOPS/GB (burst to 3,000)
- Baseline throughput 125 MB/s at any size scales with size
- Max IOPS 80,000 (provisioned independently) 16,000
- Performance vs capacity Decoupled - pay only for IOPS you need Coupled - must oversize disk for IOPS
- Price ~20% cheaper than gp2 Legacy pricing
The key gp3 advantage is decoupling performance from capacity : with gp2 you had to grow the volume to 5,334 GB just to hit 16,000 IOPS, but gp3 lets you keep a small disk and dial IOPS/throughput up independently. Choose io2 / io2 Block Express when you need provisioned IOPS above gp3's range, the highest durability (99.999%), sub-millisecond latency, or Multi-Attach to up to 16 instances in the same AZ.
Amazon EFS (Elastic File System)
EFS is fully managed NFS v4.1 that grows and shrinks automatically and mounts simultaneously on thousands of Linux instances across multiple AZs - the answer whenever multiple instances need a shared POSIX file system. It is Linux-only (no Windows/SMB).
- Setting Options
- Performance mode General Purpose (low latency, default) or Max I/O (higher aggregate throughput)
- Throughput mode Elastic (recommended), Provisioned, or Bursting
- Storage classes Standard, Standard-IA, One Zone, One Zone-IA (lifecycle moves cold files to IA)
- Encryption At rest (KMS) and in transit (TLS)
- Amazon FSx Family
Variant Protocol Signature strength Use case
FSx for Windows File Server SMB Active Directory, DFS, shadow copies, quotas Windows apps, SharePoint, home directories
FSx for Lustre POSIX (Lustre) Hundreds of GB/s, native S3 import/export HPC, ML training, media, financial modeling
FSx for NetApp ONTAP NFS, SMB, iSCSI Dedup, compression, snapshots, multi-protocol NetApp migrations, mixed-OS access
FSx for OpenZFS NFS Up to 1M IOPS, sub-ms latency, snapshots High-performance Linux, ZFS migrations
FSx for Lustre deploys as Scratch (temporary, highest performance, no replication) or Persistent (replicated, durable) and can transparently link to an S3 bucket so jobs read input from S3 and write results back - the standard HPC/ML answer.
Storage Comparison
- EBS EFS FSx for Lustre
- Type Block File (NFS) File (parallel POSIX)
- Sharing 1 instance (io2 Multi-Attach up to 16, same AZ) Thousands, multi-AZ Thousands
- AZ scope Single AZ Multi-AZ Single or Multi-AZ
- OS Linux + Windows Linux only Linux only
- Peak performance 256K IOPS / 4 GB/s 10+ GB/s Hundreds of GB/s
- Best for Databases, boot volumes Shared Linux storage HPC, ML, media
On the Exam: "Many Linux instances across AZs need one shared file system" -> EFS. "Windows SMB with Active Directory" -> FSx for Windows. "ML training reading training data from S3 at high throughput" -> FSx for Lustre. "Single high-IOPS database volume" -> io2 / io2 Block Express.
Worked Scenario: Right-Sizing EBS Performance
A reporting database on a gp2 volume needs a steady 10,000 IOPS but currently underperforms because gp2 delivers only 3 IOPS per GB - reaching 10,000 baseline IOPS would force the volume to roughly 3,334 GB even if the data is far smaller. The cost-optimal fix is to convert to gp3 and provision 10,000 IOPS independently of capacity, keeping the disk sized to the data and paying only for the performance needed. Reserve io2 / io2 Block Express for the cases gp3 cannot serve: more than 80,000 IOPS, 99.999% durability, single-digit-microsecond-class latency, or Multi-Attach across up to 16 instances in one AZ.
Decoupling performance from capacity is the key gp3 concept.
Common Traps to Avoid
EBS Multi-Attach across AZs. Multi-Attach (io2 only) shares a volume with up to 16 instances, but they must all be in the same AZ . If the question needs cross-AZ sharing, the answer is EFS, not EBS.
EFS for Windows. EFS is NFS and Linux-only; a Windows SMB requirement points to FSx for Windows File Server.
Oversizing gp2 for IOPS. Growing a gp2 volume purely to gain IOPS wastes money; gp3 provisions IOPS separately and is about 20% cheaper at baseline.
Confusing st1 with high-IOPS needs. st1 is throughput-optimized HDD for large sequential reads (logs, big data); it caps near 500 IOPS and is wrong for random-access databases.
FSx for Lustre durability. Lustre Scratch deployments are not replicated - they are for temporary, highest-performance scratch space; use Persistent deployments when the data must survive.