Access · Difficulty 3 of 5 · 20 min
Approved senders rejected at intake
Every attempt by producers to send new work to the intake line fails, while consumers sit idle. A compliance check separately flagged that stored data is not protected the way policy requires, and a look-alike sender exists. Let authorised senders enqueue work again, with the data kept protected.
Where the symptom shows: SQS
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
- AccessA service can no longer read its secretLambda · 20 min · level 3
- AccessEvery booking stops at the availability checkStep Functions · 7 min · level 3
- AccessWorkflow that stops at step oneStep Functions · 15 min · level 2
- DeliveryDeployment that never landedElastic Load Balancing · 20 min · level 3
- ResilienceBad messages with nowhere to goSQS · 25 min · level 3
- DataSlow lookups, records that never expireDynamoDB · 20 min · level 3