CLOUD / A CONCEPT NOTE
Object Storage
unlimited, highly durable storage for any blob of data
Overview · mechanism
pitfall · examples
01 / THE SHORT VERSION
The idea in a few sentences.
Buckets hold objects (files) at URLs like s3://my-bucket/path/to/file.jpg. Each object has data, metadata, and a unique version ID. Storage classes trade cost for access frequency — Standard, Infrequent Access, Glacier (archive). 11 nines of durability means you can lose two datacenters and still read every object.
02 / FOLLOW THE MECHANISM
How an s3 get request works
Client
sends a GET request to
https://my-bucket.s3.us-east-1.amazonaws.com/file.jpg.S3 endpoint
routes the request to the bucket's region and authenticates via IAM or a presigned URL.
Object store
looks up the object in the bucket's key-value index and retrieves it from replicated storage across >= 3 AZs.
Response
streams the object data + headers (ETag, Content-Type, version ID) back to the client.
04 / COMMAND NOTES
Read the command, then the result.
Inspect the flags and arguments before trying an example. Snippets can need local setup, replacement values, or resources in your own environment.
list objects in a bucket
aws s3 ls s3://my-bucket/upload a file to S3
aws s3 cp file.txt s3://my-bucket/05 / CHECK YOURSELF
Could you explain Object Storage to a teammate?
Try it out loud in two sentences: what it is, and the one detail that changes the picture. If you stall, the gap is the part to reread.
Up next in Cloud architectureVPCyour private network in the cloud