Access · Difficulty 3 of 5 · 20 min
A service can no longer read its secret
A service that loads a configuration secret on every request has failed every call since this morning with a generic error. The secret has not moved and its value is unchanged. Restore exactly what the service needs to read that one secret, and nothing more.
Where the symptom shows: Lambda
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
- AccessApproved senders rejected at intakeSQS · 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