Availability · Difficulty 4 of 5 · 45 min
Outbound traffic reaches nothing
A function attached to a private network can no longer reach outside interfaces or the internal resources it used to. Nothing about its setup looks obviously empty, and a wide-open alternative sits nearby. Restore its outbound reach without giving it more than it is meant to have.
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
- AvailabilityFailover that never fails overRoute 53 · 45 min · level 4
- AvailabilityThe fleet never replaces a dead nodeEC2 · 40 min · level 4
- AvailabilityPower loss in one availability zoneEC2 · 45 min · level 4
- AvailabilityContainers lose connectivity mid-requestElastic Load Balancing · 45 min · level 4
- AvailabilityConnections drop when the writer changesRDS · 45 min · level 4
- AvailabilityCallers turned away at trivial trafficAPI Gateway · 20 min · level 3