AWS: When would you pick S3 over EBS?
The right answer shows you understand *access patterns*, not just storage products.
Question
When would you choose AWS S3 over EBS?
Answer
Pick **S3** when you have **objects** (files, images, logs, backups) that are accessed independently, from many places, over HTTP, and where high durability (11 nines) matters more than millisecond latency. S3 is virtually unlimited, pay-per-GB, and multi-AZ by default. Pick **EBS** when you need a **block device** attached to one EC2 instance at a time — a database's data files, an application's local disk, low-latency random reads/writes, or anything that expects a POSIX filesystem. EBS is bound to a single AZ, sized in fixed GB, and its price includes provisioned IOPS. **In short: S3 for files, EBS for disks.**
See the question and answer above.
Keep reading
You may also like
interview
How does Terraform know what already exists?
The most missed Terraform interview follow-up. Explain state files and how they work.
interview
Explain the Kafka message flow end-to-end
A crisp walkthrough of what happens between a producer's `send()` call and a consumer's `poll()` receiving the message.
interview
Difference between Docker and Kubernetes
One of the most common early-career interview questions. Nail the answer in 3 sentences.
Discussion (0)
No comments yet. Be the first to weigh in.