Longship Logistics · Cloud Platform · us-east-1 · Night shift

CloudOutage

You're the on-call AWS engineer. Something in production just broke. Investigate with the aws CLI, watch the architecture react, find the root cause and fix it before the pager goes off again.

Case board

How to play

You get paged. Each case opens with an alert at 02:47. Acknowledge it, then read the ticket on the left.
Investigate like it's real. The terminal is a bastion host with a simulated aws CLI v2. Output follows the real JSON shapes, and --query, --output text|table, jq, curl, dig and aws ssm start-session all work.
Watch the architecture. The diagram on the right is live. Boxes turn red, gold or green as the account changes. Click a box to load the command behind it.
Fix the cause, not the symptom. Objectives tick off only when the system is actually healthy. Destructive shortcuts get flagged or blocked by MUNIN, the incident bot, and cost points.
Close the case. The debrief explains the root cause and the real-world lesson, and adds a cheat-sheet card to your Field manual.

Scoring

Case closed	1000
Over par time	−1 per 2 s (max −300)
Hints 1 / 2 / 3	−50 / −100 / −200
Mistakes MUNIN catches	−10 to −200
Commands over the case's par	−5 each (max −100)
All bonus objectives	+100

★★★ at 850+ · ★★ at 600+ · ★ for closing the case. help, ticket, objectives and hint don't count as commands. The case closes the moment the last required objective is met, so finish bonus work first.

Keys

Tab: complete services, operations, --flags and resource IDs (twice lists options)
↑ ↓: command history
Ctrl+C: stop a waiter or logs tail --follow
Ctrl+L: clear the screen
Esc: pause menu
M: sound on or off

Good first commands

help
aws help
aws ec2 describe-instances --output table
aws cloudtrail lookup-events --max-results 5
aws ec2 describe-route-tables | jq '.RouteTables[].Routes'

Write files with edit policy.json, then pass them as file://policy.json.

Fine print

Everything is simulated and fictional: the account 123456789012, Longship Logistics, every name, key and IP. No request ever leaves your browser and nothing touches a real AWS account. Your progress is saved only in this browser (localStorage). An unfinished case isn't saved; only closed cases are.

Field manual

Every case you close adds a cheat-sheet card here. These are the commands real cloud on-call engineers reach for first.

05:00

1000pts

try