Night 36 — Keywords: storage + hybrid
~2 hr. $0 AWS spend. Apply Night 35’s method to storage stems. These dominated several Practice Exam 1 misses when “just use S3” felt right.
Plain language first
S3 is default for objects. The stem tells you when it is not.
Underline interface words first:
object / URL / bucket / lifecycle / Glacier
block / volume / boot / iSCSI (block over the network)
POSIX / mount / concurrent Linux
SMB / Windows file share / Active Directory
SFTP / managed transfer
local cache + on-prem protocol
Block 1 (~30 min) — Force-word → service map
| Force words in stem | Pick | Near-miss kill |
|---|---|---|
| object, unlimited, static site, analytics files, lifecycle to Glacier | S3 | EBS, EFS |
| boot volume, single-instance DB disk, persistent block for one EC2 | EBS | Instance Store (dies with the instance), S3 |
| POSIX, shared, many EC2, Multi-AZ Linux | EFS | bigger EBS, S3 “as filesystem” |
| Windows SMB, Active Directory integration, file share migrate | FSx Windows | EFS (Linux), EBS |
| Windows + block / iSCSI + Multi-AZ high availability | FSx NetApp ONTAP | FSx Windows (file only) |
| parallel high-performance / ML hot scratch | FSx Lustre (+ S3 cold) | EFS “good enough” |
| on-prem SMB/NFS + local cache + objects in AWS | File Gateway | DataSync (no cache), Tape Gateway |
| SFTP + encrypt + high availability + delete after N days + least operational work | Transfer Family → S3 + lifecycle expire | EC2+SFTP; EFS lifecycle (does not delete); Transfer “retention policy” |
| write-once timed lock + even root | Object Lock compliance + retention | governance; legal hold “for 1 year” |
| accidental delete, still allow deletes | Versioning + MFA Delete | Deny Delete policy |
| restrict S3 access to one VPC | S3 Access Point (VPC) | Network Firewall on bucket |
| many private files, don’t change URLs | CloudFront signed cookies | signed URL |
| fastest long-haul upload to a Region bucket | Transfer Acceleration + multipart | Cross-Region Replication (slower), Site-to-Site VPN |
Soft rules
- EFS lifecycle transitions to Infrequent Access — it does not delete files.
- Legal hold has no duration — never pair with “for one year.”
- Instance Store dies with the instance — never “mission-critical persistent.”
- One Zone Infrequent Access is not “archival.”
Block 2 (~60 min) — Stem drills (write force words → pick)
Do these without options first (10), then take the quiz.
- Content management system on Auto Scaling EC2; uploads on one EBS; need scalable high-availability POSIX shared store.
- Trading app on Windows; Multi-AZ; low-latency shared block.
- Confidential docs via SFTP; encrypt; high availability; auto-delete at 30 days; least operational work.
- On-prem corporate docs over SMB; local cache; Glacier after months.
- Clinical data; no overwrite/delete for 1 year including root.
- Junior deleted S3 objects; prevent accident; allow intentional delete.
- Tax docs; write-once lock; requests only from one VPC.
- Member-only media library; many files; keep current URLs.
- Global weather sites; one-time 500 GB each → us-east-1 ASAP (no Direct Connect partner).
- Persistent block for EC2; object backups; after 30 days to archival storage.
- EFS
- FSx ONTAP iSCSI
- Transfer Family → S3 + lifecycle expire
- File Gateway + S3 lifecycle → Glacier
- Object Lock compliance + retention
- Versioning + MFA Delete
- Access Point (VPC) + Object Lock
- Signed cookies
- Transfer Acceleration + multipart
- EBS + S3 + lifecycle → Glacier Flexible Retrieval
Block 3 (~30 min) — Quiz
night-36-quiz.json (20 questions). Margin: interface force word before answering.
Tomorrow
Databases: Multi-AZ vs read replica vs Aurora Global vs DynamoDB; Database Migration Service vs refactor; custom endpoints; IAM database authentication.