Storage selection starts with the interface. S3 is object storage accessed by API. EBS is block storage attached within an AZ. EFS is a regional shared POSIX file system. FSx supplies managed file systems for Windows, Lustre, ONTAP, or OpenZFS requirements.
| Signal in the question | Likely choice |
|---|---|
| Static assets, data lake, durable objects | S3 |
| Boot volume or low-latency block device | EBS |
| Shared Linux files across AZs | EFS |
| SMB/Windows integration | FSx for Windows |
| HPC scratch tightly integrated with S3 | FSx for Lustre |
| Temporary highest-speed local data | Instance Store |
S3 design is policy plus lifecycle
Versioning protects against overwrite and is required for replication. CRR crosses Regions; SRR stays in one Region. Lifecycle transitions objects according to access age; Intelligent-Tiering fits changing or unknown access patterns. Glacier choices trade retrieval time and cost.
SSE-S3 uses S3-managed keys; SSE-KMS adds KMS control and audit; SSE-C leaves key delivery to the client. Block Public Access is a guardrail, while bucket policies express resource access. OAC is the preferred way for CloudFront to access a private S3 origin.
Backup is not availability
EBS snapshots and S3 versioning help recovery, but do not create a live standby. EBS moves across AZs through snapshot/restore. AWS Backup centralizes policies and vault controls. Object Lock or Vault Lock addresses immutability requirements.
For hybrid transfer, DataSync moves online datasets, Storage Gateway exposes familiar file/volume/tape interfaces, Transfer Family provides managed SFTP/FTPS/FTP, and Snow Family handles constrained networks or edge processing.
Exam lens: identify interface, sharing scope, latency, durability, recovery time, and access frequency—in that order.
Review card
- S3 object, EBS block, EFS/FSx file.
- EBS is AZ-scoped; EFS is regional.
- Replication requires versioning and does not retroactively copy everything by default.
- Lifecycle is a cost policy, not a backup strategy.
- Select migration tools by network availability and required protocol.
儲存選型先看 interface。S3 是 API 存取的 object storage；EBS 是 AZ 內 attach 的 block storage；EFS 是 regional shared POSIX file system；FSx 處理 Windows、Lustre、ONTAP 或 OpenZFS 需求。
| 題目訊號 | 可能選擇 |
|---|---|
| Static asset、data lake、durable object | S3 |
| Boot volume、low-latency block | EBS |
| 跨 AZ 共用 Linux file | EFS |
| SMB/Windows integration | FSx for Windows |
| 與 S3 整合的 HPC scratch | FSx for Lustre |
| 可遺失的極速 local data | Instance Store |
S3 設計是 policy 加 lifecycle
Versioning 防 overwrite，也是 replication 前提。CRR 跨 Region；SRR 在同 Region。Lifecycle 依 access age transition；access pattern 會變或不明時用 Intelligent-Tiering。Glacier 選項是 retrieval time 與 cost 交換。
SSE-S3 用 S3-managed keys；SSE-KMS 多 KMS control/audit；SSE-C 由 client 提供 key。Block Public Access 是 guardrail；bucket policy 表達 resource access。CloudFront 存取 private S3 origin 優先 OAC。
Backup 不是 availability
EBS snapshot 與 S3 versioning 幫助 recovery，不會建立 live standby。EBS 要透過 snapshot/restore 跨 AZ。AWS Backup 中央管 policy/vault；Object Lock 或 Vault Lock 應對 immutability。
Hybrid transfer 中，DataSync 搬 online dataset；Storage Gateway 提供 file/volume/tape interface；Transfer Family 提供 managed SFTP/FTPS/FTP；Snow Family 處理 network 受限或 edge processing。
考試視角： 依序確認 interface、sharing scope、latency、durability、recovery time、access frequency。
複習卡
- S3 object、EBS block、EFS/FSx file。
- EBS 屬 AZ；EFS 屬 Region。
- Replication 需 versioning，且預設不會回頭複製所有既有 object。
- Lifecycle 是 cost policy，不是 backup strategy。
- Migration tool 要看 network 條件與 protocol。