Command Palette

Search for a command to run...

Hectal
Phase 4Intermediate5 of 9 in AWS

Storage & Databases

S3 for objects, EBS and EFS for disks, RDS/Aurora for relational data, DynamoDB and ElastiCache for key-value speed — and when each one is the right answer.

Where your data lives decides your durability, your latency, your scaling ceiling, and a large part of your bill. This phase covers the storage and database services nearly every backend on AWS ends up using, with the operational details — lifecycle rules, Multi-AZ failover, partition-key design, connection limits — that separate a working demo from a production system.

0/4 · 0%
4 topics ~53 min 9 code blocks & diagrams
Start with the first topic
1
4.1

S3: Buckets, Storage Classes, Security & Presigned URLs

S3 stores objects (files plus metadata) in buckets with eleven nines of durability; storage classes and lifecycle rules control cost, Block Public Access and bucket policies control exposure, and presigned URLs let clients upload or download directly without your server in the middle.

14 min 1 diagram 2 code practice

2
4.2

EBS & EFS: Block and File Storage

EBS is a network-attached disk for one instance in one AZ, with snapshots for backup; EFS is a managed NFS filesystem that many instances across AZs can mount at once.

13 min 2 code practice

3
4.3

RDS & Aurora: Managed Relational Databases

RDS runs Postgres/MySQL and others for you with automated backups, patching, and Multi-AZ failover; read replicas scale reads; Aurora is AWS's re-engineered, cluster-based variant with shared storage and faster failover.

13 min 1 diagram 1 code practice

4
4.4

DynamoDB & ElastiCache

DynamoDB is a serverless key-value/document database that delivers single-digit-millisecond reads at any scale if — and only if — you design keys around your access patterns; ElastiCache gives you managed Redis/Valkey or Memcached for caching and fast shared state.

13 min 1 diagram 1 code practice