Learning bite
Account for resources and cost
Cost control needs an inventory, ownership, and a retirement procedure.
AWS
Predict before you try
Does deleting the application workload prove the experiment no longer incurs cost?
Try it: Work through the MicroBank example →On this page
The operating question
A resource can keep creating cost after the application experiment ends. Record the owner, purpose, lifetime, and cleanup evidence for compute, storage, network, logs, and backups. AWS Budgets can track spending and send notifications, but billing and notifications have delay; an alert is not an immediate universal spending cap. Retained data and shared resources need an explicit lifecycle decision.
Work through the MicroBank example
Use an empty inventory template or a sanitized real export. For each proposed resource, name the owner, cleanup trigger, evidence of removal, and any retained data. Leave prices and savings blank until supported by the selected region, configuration, and observation window.
Use a lifecycle inventory before filling in prices:
| Resource family | Cleanup question | Retention decision |
|---|---|---|
| Compute | Was the owned workload and its dedicated capacity removed? | Keep only deliberately shared capacity |
| Data and backups | Which volumes, databases, snapshots, and backups remain? | Name the owner, reason, and expiry for retained data |
| Network | Which dedicated entry, address, and network resources remain? | Record shared dependencies before removing anything |
| Telemetry | Which logs, metrics, and exports continue collecting or retaining data? | Define the observation and retention window |
A resource marked “retained” needs an owner and a follow-up decision. Do not describe a budget notification as an immediate spending stop.
Keep the selected source revision and distinguish an illustrative design from actual environment evidence. The teaching reference is MicroBank f75da68 from the implementation guide. Inspect newer application branches before carrying version-specific findings forward.
Compare your reasoning
Does deleting the application workload prove the experiment no longer incurs cost? No. Inspect its separate storage, networking, telemetry, backup, and managed-service resources.
Checkpoint
Save your diagram or decision record, its assumptions, and the next missing verification. No cloud account or provisioning is required for this design bite. Any later cloud run needs its own approved sandbox, scoped identity, cost boundaries, and cleanup evidence.
Read further
Prove what you learned
Inspect the result
Save the component/owner decision, a denied or failed path, and the missing verification.
Explain it in your own words
Explain why your observation supports the stated outcome, and name one thing it does not prove.
Try a small variation
Change one design requirement and revise only the affected decisions; state the trade-off.
Your evidence should show
- Record the context/revision or label the work as a paper or prepared fixture.
- Compare the prediction with the actual result from “Work through the MicroBank example”.
- Save the component/owner decision, a denied or failed path, and the missing verification.
- Explain the transfer challenge and retain the same verification question.
Hint
Separate runtime, identity, network, data, messaging and recovery ownership.
Answer guide: compare after predicting
No. Inspect its separate storage, networking, telemetry, backup, and managed-service resources.
Compare this with your actual observation. A paper answer is useful reasoning practice; record execution separately.
Recall the source-derived MicroBank component map and cloud service responsibility model. Revisit the previous lesson.
Save the prediction, result and explanation ↓Your notes and evidence
Record observations, questions, or links to your work. Keep credentials out of your notes.
Back up or restore this path
Progress and notes stay in this browser. A backup contains only this learning path.