RunbookGuard
Stop discovering stale runbooks at 2 a.m. RunbookGuard cross-checks your Confluence runbooks against live AWS inventory and tells you which references no longer point at anything real.
Visit runbookguard.comThe problem it solves
Runbooks are written once, during or just after an incident, and then trusted for years. Meanwhile the infrastructure underneath them keeps moving — instances are replaced, buckets renamed, queues retired, accounts reorganized. The document still reads as though everything is fine.
The gap usually surfaces at the worst possible moment: an engineer is paged, opens the runbook, and the resource it tells them to check does not exist. RunbookGuard closes that gap by checking continuously, in daylight, before anyone is paged.
How it works
Read-only, inside Atlassian, with nothing to run yourself.
Scans your runbooks
Reads the Confluence pages you point it at and extracts every AWS resource reference it finds — instance IDs, bucket names, ARNs, queues, and more.
Checks live AWS inventory
Cross-references each one against what actually exists in your AWS account right now, and flags what has gone missing.
Reports what is stale
You get a clear list of which runbooks reference resources that no longer exist, so they can be fixed before the next incident.
Why teams pick it
- Read-only by design. It never modifies your pages or your infrastructure.
- Five minutes to first finding. Install, connect, scan — no pipeline work, no agents to deploy.
- Runs on Atlassian Forge. It lives inside Atlassian's platform rather than on servers you have to operate.
- Built for the person who owns both. Made for engineers who own the runbook and the AWS account it describes.
See the full site
Install instructions, security details, pricing, and the full FAQ are all on the RunbookGuard site.
Go to runbookguard.com