Data · Difficulty 1 of 5 · 5 min
Query results land in the wrong place
The approved location for query results has received nothing new, while another location fills with output from recent ad hoc queries. Find out why, and make every future query respect the approved location.
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
- DataBooking emails are never loggedDynamoDB · 4 min · level 1
- DataThe nightly job reprocesses everythingS3 · 15 min · level 2
- DataSlow lookups, records that never expireDynamoDB · 20 min · level 3
- DataReads refused and data disappears earlyS3 · 20 min · level 3
- DataStream lag climbs without any outputKinesis · 45 min · level 4
- DataThe nightly data refresh stallsS3 · 90 min · level 5