MushyBook
All challenges

Trim the idle dev/test bill

beginner

Scenario & brief

This is a non-production environment: light traffic, only used during business hours, and the SLA is relaxed. Yet it runs 2× m5.4xlarge on-demand, 24×7, plus an oversized database — around $1,500/mo for almost nothing.

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

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

App Server

Compute

2instances

System health

Erupting · SLA breach

28

/ 100

Score

SLA not met yet

Monthly cost

$1,472

Budget $200/mo · $1,272 over

Metrics

Capacity100
Availability100
Durability25
Cost efficiency0

Requirements

  • Peak capacity — 13000 rps compute · 3400 rps db (need ≥ 300 rps)
  • p99 latency — ~74 ms (need ≤ 300 ms)
  • Availability — 99.00% (need ≥ 99.00%)
  • Durability — at risk (need backups)
  • Budget — $1472/mo (need ≤ $200/mo)

Advisor

  • The database has no Multi-AZ standby or replica — a failure risks data loss. Enable Multi-AZ and backups.

Discussion

Sign in to join the 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.