Data · Difficulty 4 of 5 · 45 min
Stream lag climbs without any output
Records enter the stream, but processing lag climbs without limit and no transformed output lands in storage. A second job definition sits idle. Trace the live path and restore continuous processing.
Where the symptom shows: Kinesis
Take this challenge on a live account
A live AWS account, already broken, and a clock. You fix it with the provider's own console and command line, then read a report of how you worked. We host the cloud account. Nothing lands on your bill.
More challenges
- DataSlow lookups, records that never expireDynamoDB · 20 min · level 3
- DataThe nightly data refresh stallsS3 · 90 min · level 5
- DataOrder writes cannot reach the databaseLambda · 90 min · level 5
- DataShared file reads fail with permission errorsLambda · 90 min · level 5
- DataReads refused and data disappears earlyS3 · 20 min · level 3
- DataThe nightly job reprocesses everythingS3 · 15 min · level 2