Close the resource inventory and cost boundary
What This Concept Is
An experiment has a resource lifecycle: create or identify resources, observe them, clean up those owned by the experiment, and independently reconcile what remains. A successful deletion command is one observation, not proof that all related resources or costs disappeared.
Why It Matters Here
The original teardown drill names disks, snapshots, network resources and retained logs. These are easy to omit when concentrating on the main workload. Budget notifications are useful signals, but delayed billing and notification mean they are not hard spend limits. This curriculum extension runs locally and creates no cloud resources.
Concrete Example
A fictional experiment's inventory includes a VM, disk, snapshot and retained log. Deleting the VM leaves three entries to explain. An entry can be removed, deliberately retained with an owner/expiry/cost assumption, or unresolved. Removing it from a spreadsheet without verifying its resource state is not cleanup.
For a teaching estimate, four resource-hours at 0.20 currency units/hour plus ten storage units at 0.03 per unit-month for one whole month gives 1.10 currency units. This is invented arithmetic, not a provider quote; request, egress, tax and retention charges are excluded. Halving runtime does not halve the storage term.
Common Confusion / Misconception
A zero-resource result in one region or account does not prove global absence. Unpaginated listings can omit resources. A retained snapshot may be intentional and valuable; teardown should not delete unrelated or required recovery data. A cost alert may arrive after additional usage has already occurred.
How To Use It
Record scope, owner, identifiers, dependency, retention decision and charge unit before the experiment. For a local substitute, create a manifest of synthetic resources and simulate incomplete listings, permission failures and retained items. Mark those outcomes incomplete rather than clean. For an authorized cloud exercise, use current provider listings across the relevant scopes and document limits; never place secrets in evidence.
Check Yourself
What proves the listing was complete? Which resource outlives compute? Does a budget alert stop usage? What evidence distinguishes intentional retention from an orphan? Who can authorize deletion?
Mini Drill or Application
Produce a before/after manifest with one retained snapshot and one failed query. Your final result must report unresolved inventory, not a clean teardown. Estimate both current and retained costs with explicit units, date and exclusions. Preserve the original budget and teardown requirements if choosing the real-cloud lane later.
Read This Only If Stuck
AWS Budgets documentation explains notification delay. Use official service pricing pages for a real estimate; no subscription or purchase is necessary for this local exercise.
The Linux Command Line is selective prerequisite support for inspecting local processes, network paths and resource inventories. Provider documentation above remains authoritative for cloud behavior.