Apa kemampuan storage sing beda-beda ing AWS (S3, EBS, EFS)?

Question

Accepted Answer

AWS nawakake pirang-pirang **tipe storage** kanggo kabutuhan sing beda-beda — **S3** (object storage), **EBS** (block storage / disk kanggo EC2), lan **EFS** (shared file storage). Ngerti prabedane lan use case-ne membantu milih storage sing tepat kanggo saben workload.

## Telu tipe storage utama

```text
S3 (OBJECT storage) → files/objects accessed via API, virtually unlimited, durable:
  → for: files, backups, static assets, data lakes, anything accessed as whole objects
  → NOT a filesystem (no in-place edits; access by key); accessed over HTTP/API

EBS (BLOCK storage) → virtual disks ATTACHED to a single EC2 instance:
  → like a hard drive for an instance (boot volumes, databases, app data)
  → attached to ONE instance at a time (in one AZ); persists independently of the instance
  → for: an instance's filesystem, databases needing low-latency block storage

EFS (FILE storage) → a shared filesystem mountable by MANY instances simultaneously:
  → NFS file system; multiple EC2 instances mount it concurrently (shared access)
  → scales automatically; for: shared files across instances, content management, etc.
```

## Perbandingan lan pemilihan

```text
                S3 (Object)        EBS (Block)         EFS (File)
Access          API/HTTP (key)     attached disk       mounted filesystem (NFS)
Attached to     accessed by URL    ONE instance        MANY instances (shared)
Use for         files, backups,    instance disks,     shared files across
                static assets,     databases, boot     multiple instances
                data lakes         volumes
Scale           unlimited          fixed size (resize) auto-scaling
```

```text
CHOOSE: S3 for objects/files/backups/static content (most common general storage)
        EBS for an instance's disk / database storage (block, single instance)
        EFS for shared filesystem access across multiple instances
```

## Kenapa iki penting

Ngerti pilihan storage AWS iki berharga amarga milih tipe storage sing tepat kanggo saben workload iku penting kanggo fungsi lan biaya, mula mangkono pengetahuan AWS sing praktis.

Telu tipe utama iki nuduhake tujuan sing beda-beda: **S3** (object storage) kanggo file, backup, static asset, lan data lake — diakses minangka object lengkap via API, praktis unlimited lan durable, storage umum sing paling umum; **EBS** (block storage) menyediakake **disk virtual sing kapisahan menyang sawijining EC2 instance** — kaya hard drive, dikarepake kanggo filesystem instance, boot volume, lan database sing butuh block storage low-latency; lan **EFS** (file storage) menyediakake **shared filesystem sing bisa dipasang dening pirang-pirang instance bebarengan** — kanggo shared file sadurunge pirang-pirang instance.

Ngerti prabedane kunci — cara diakses (S3 via API/key, EBS minangka disk sing kapisahan, EFS minangka mounted filesystem), apa sing kapisahan (S3 diakses via URL, EBS menyang sawijining instance, EFS dibagekake sadurunge akeh), lan use case-ne — iku perlu kanggo milih kanthi bener.

Milih **tipe storage sing salah** nyebabake masalah nyata: nyoba ngibagi EBS volume sadurunge instance (ora bisa), nganggo S3 kanggo block storage low-latency sing database butuh (model salah), utawa nganggo EFS nalika object storage luwih murah lan gampang — mula kepancet storage menyang workload iku penting kanggo fungsi (nganggo tipe sing mampu aksès pattern) lan biaya (tipe sing pas asring luwih murah).

Ngerti **kapan nganggo saben tipe** (S3 kanggo object/file/backup, EBS kanggo disk instance lan database, EFS kanggo akses shared filesystem) nggambarake keputusan arsitektur sing apik.

Amarga aplikasi AWS nduweni kabutuhan storage sing beda-beda (object storage kanggo file, block storage kanggo database lan disk, shared file storage sadurunge instance) lan milih tipe sing tepat mengaruh fungsi lan biaya, ngerti pilihan storage AWS (S3, EBS, EFS) lan use case sing pas kanggo saben tipe iku pengetahuan AWS sing berharga, praktis-relevan kanggo ndesain aplikasi kanthi storage sing tepat kanggo saben workload, sawijining pertimbangan arsitektur sing umum lan penting.