Make the assumptions visible
Write the Region, instance configuration and expected running hours. Add disk capacity, traffic and other services. I would keep these assumptions next to the estimate so another person can understand what the number actually represents.
Compare two scenarios
Estimate an ordinary lab session and an extended run. This shows the cost impact of forgetting cleanup. Use current pricing instead of treating a historical video figure as today’s quote. Include resources that remain after the instance stops.
Check actual usage afterwards
The estimate is your plan; billing shows actual usage. Investigate differences and update the next estimate. Review resource lists after cleanup because an unused volume or address can be easy to overlook when you focus only on servers.
Try it yourself
Estimate a short lab and an accidentally extended run. Mark every resource that could remain after compute stops.
A common question
Is the hourly instance price enough?
No. Include the other services and resources used by the configuration, together with their usage assumptions.
References & video notes
Use the video to follow the topic with me. Console screens and older offers can change, so check the current AWS documentation before performing a lab.
Keep learning
- What is Amazon EC2? A beginner’s guide
- What is an AMI? Understanding EC2 machine images
- Plan and launch your first EC2 instance