Rotate a leaked key
Lock 09Fix the board. Turn every goal green.
- Traffic
- 1,500 req/s · reads only
- Limit
- API server answers about 10,000 req/s
- Bill
- Load balancer (L7)2 USD/mo
- API server12 USD/mo
- Secret store2 USD/mo
- Key-value store4 USD/mo
20 of 60 USD/mo
Goals
Not tested yet
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.
Envelope keys · < 1 key service calls/s · limit 10,000/s
Parts you can add: Local cache, Redis cache, Managed pub/sub, Managed queue, Secret store. At most 10 parts. Budget: 60 USD/mo.
Tap a part to add it, or drag it onto a trace.Click a part to add it, or drag it onto a trace.