Cost for Cloud Architects
Cost-optimised cloud design means paying only for the value you need. It includes tagging and allocating spend, right-sizing, using reserved capacity or savings plans and spot instances where suitable, choosing storage tiers, shutting off idle resources and setting budgets with alerts so costs stay visible and predictable.
Stage: Cost and Migration · Part of the Cloud Architect roadmap · Last reviewed 19 November 2026
What to learn in Cost
- Tag resources so spend can be attributed to teams and projects
- Right-size an over-provisioned instance using utilisation data
- Compare on-demand, reserved and spot pricing for a workload
- Move cold data to cheaper storage tiers with lifecycle rules
- Set a budget alert before a bill surprises you
Cost interview questions
When are spot instances a good choice?
Spot capacity is discounted but can be reclaimed with short notice, so it suits fault-tolerant, interruptible work such as batch jobs, CI runners and stateless workers. It is a poor fit for stateful systems that cannot tolerate sudden loss.
How do you find cloud waste?
Review utilisation metrics for idle or oversized instances, unattached volumes, old snapshots, unused load balancers and forgotten test environments. Cost explorer reports grouped by tag show where spend is growing and who owns it.
Where Cost fits in the Cloud Architect roadmap
Cost belongs to the Cost and Migration stage (advanced level). Make it practical.
Other units in this stage
Back to the full Cloud Architect roadmap