Tiered storage lifecycle

beginner

Scenario & brief

A compliance archive keeps 40 TB of rarely-accessed data in S3 Standard — paying hot-storage prices for cold data — behind an oversized, always-on app server.

Targets (relaxed): p99 ≤ 300 ms, 99.0% availability, standard durability, under $400/mo.

Archival data that's almost never read belongs in a colder storage class (Glacier Instant is a fraction of Standard's price). Pick the right storage class for the access pattern and right-size the compute.

500 rps peakp99 ≤ 300ms99% availdurability: standardbudget $400/mo

App Server

Compute

Instance class

Scaling

Instances (static)

2instances

Availability Zones

Purchasing

Running schedule

System health

Overheating · burning cash

/ 100

Score

Meets SLA but over budget

Monthly cost

$2,063

Budget $400/mo · $1,663 over

Metrics

Capacity100

Availability100

Durability100

Cost efficiency0

Requirements

Peak capacity — 13000 rps compute · 0 rps db (need ≥ 500 rps)
p99 latency — ~67 ms (need ≤ 300 ms)
Availability — 99.50% (need ≥ 99.00%)
Durability — protected (need backups)
Budget — $2063/mo (need ≤ $400/mo)

Advisor

Design is sound but $2063/mo blows the $400/mo budget — right-size to cut cost.
Compute capacity is more than 2× peak demand — downsize the class or switch to autoscaling to stop overpaying.

Discussion

No comments yet. Be the first to start the discussion.

For learning purposes only. Costs and capacities are illustrative, not live AWS prices. Not affiliated with or endorsed by Amazon Web Services.