Cloud · AWS

Amazon S3 and storage classes

awsEasyawss3storage classesdata lakelifecycle

Interview question

What is Amazon S3, and what are its main storage classes?

How to answer

The short answer

Amazon S3 (Simple Storage Service) is AWS . You put files (objects) in buckets. Each object has a key (path-like name), data bytes, and metadata. Data engineers use S3 as the landing zone and data lake: raw dumps, Parquet tables, logs, backups.

Problem first. A warehouse of CSV exports and Spark job outputs needs cheap, durable storage that many tools can read. Attaching giant disks to one server does not scale. S3 is shared object storage with 11 nines of durability design.

Core ideas

  • Bucket = top-level container (globally unique name)
  • Object = file + key + metadata
  • No real folders; prefixes like raw/orders/ are a naming convention
  • Access via policies, bucket policies, and (optionally) ACLs

Storage classes (interview table)

ClassWhen to useAccess patternCost shape
S3 StandardHot data, frequent readsMillisecondsHigher storage, low request cost
S3 Intelligent-TieringUnknown / changing accessAuto-moves tiersSmall monitoring fee
S3 Standard-IAInfrequent but quick accessMilliseconds + retrieval feeCheaper storage
S3 One Zone-IARe-creatable infrequent dataOne AZ onlyCheapest IA, less resilient
S3 Glacier Instant RetrievalArchive, rare but need ms accessMillisecondsLow storage, higher retrieval
S3 Glacier Flexible RetrievalCold archive (minutes–hours)Restore then readVery low storage
S3 Glacier Deep ArchiveLong-term complianceHours to restoreLowest storage

Lifecycle example

Keep last 30 days in Standard, move older prefixes to IA, then Glacier after 90 days. Use lifecycle rules so you do not manage this by hand.

Interview tip: Say "S3 = durable object store for lakes," then name 2–3 classes and when you would lifecycle data down. Mention prefixes and IAM, not "folders."