Data · Difficulty 5 of 5 · 90 min
The nightly data refresh stalls
Records keep arriving, but the curated area of the data lake has stayed empty since the last nightly run. More than one step between arrival and the catalog has drifted from what was deployed, and security expects records to be protected on the way. Restore the flow end to end.
Where the symptom shows: S3
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
- DataOrder writes cannot reach the databaseLambda · 90 min · level 5
- DataShared file reads fail with permission errorsLambda · 90 min · level 5
- DataStream lag climbs without any outputKinesis · 45 min · level 4
- DataSlow lookups, records that never expireDynamoDB · 20 min · level 3
- DataReads refused and data disappears earlyS3 · 20 min · level 3
- DataThe nightly job reprocesses everythingS3 · 15 min · level 2