kodebeat / papers / cost
Stopping an AWS account's spend without losing anything
A reversible spend killswitch with a recorded restore path.
Halts spend by cutting ingress first and then draining compute, deleting nothing and recording exactly how to put it all back. plan is read-only and safe against production, restore replays the snapshot, and verify fires, reads the account back, restores and reads it back again, because the API returning no error is not evidence that anything stopped.
What is in it
- The problem — what goes unanswered without it, and who notices first.
- Why the obvious alternative falls short — stated plainly, including where it is the better choice.
- How it works — the method, not a feature list.
- Concrete use cases — with console output quoted from the repository, never reconstructed.
- The methodology behind any number it emits — every term shown, so the figure survives a question.
- What it deliberately does not do — the section most papers leave out.
Part of the Cost & FinOps theme.
Get the PDF
One email with the download link, and this paper already selected. No follow-up sequence.