Rotate a leaked key

  • Fix
  • Lock 09

Difficulty 3 of 5

A payment key leaked. The team moved it to the secret store, and checkout now reads it on every request. The store serves 1,000 reads/s. An old key stops working 5 minutes after each rotation. Keep errors under 0.1 percent and p99 under 100 ms. You have 6 edits.

0:00. The leaked payment key now lives in the secret store. Since then, 3 in 4 checkouts fail. Graph: error rate at 75 percent.

Play level

HTTP/2Users1,500 req/sLoad balanc…API serverSecret storeKey-value s…0.5 vCPU · 1 GB
HTTP/2HTTP/2HTTP/2UsersLoad bala…API serverSecret st…Key-value…
The board at the start of the level
One data key seals many recordsTap or press Space to change how records get a key

Envelope keys · < 1 key service calls/s · limit 10,000/s

Goals and limits

Error rate
under 0.1%
p99 latency
under 100 ms
Data age
under 300 s
Monthly cost
under 60 USD/mo
Parts you can add
Local cache, Redis cache, Managed pub/sub, Managed queue, Secret store
Part limit
10
Edit limit
6
Traffic
1,500 req/s

Concepts

How players did

Player results load from the server.