5.63 How to clean your instance group
This short lesson wraps up section IV with a reminder: clean up after every lab. Many of the resources you created in the previous lessons — EC2 instances, EBS volumes, EFS file systems, snapshots — keep billing as long as they exist on your AWS account. Even a forgotten t2.micro running outside the free tier can rack up unexpected costs over time, and EBS storage keeps charging by the gigabyte even when no instance is attached.
Cleanup checklist
- EC2 instances: in the Instances view, select every running or stopped instance and choose Terminate.
- EBS volumes: open the Volumes view and delete any leftover volume not destroyed automatically when terminating its instance.
- EBS snapshots: open the Snapshots view and remove the snapshots you created during the EBS lessons.
- EFS file systems: from the EFS console, remove any file system created during the labs.
- Security groups: not billed, but a good idea to clean up to avoid clutter.
The general principle is simple: every paid resource you created since the beginning of this training should be removed as soon as you are done with the labs. AWS bills you per second of usage, so even a few hours of idle instances cost real money. A clean account also helps you find your way around the console next time you start an experiment.
Take a few minutes after each major lab to walk through the EC2 dashboard top-down — Instances, Volumes, Snapshots, Load Balancers, Auto Scaling Groups, EFS — and confirm everything you created has been removed. With that habit in place, you can practice freely without surprises on your next billing statement.
Summary
This lesson demonstrates how to clean up and delete AWS resources created during the training to avoid unnecessary charges. The instructor walks through the process of removing EC2 instances, storage volumes, and snapshots that are no longer needed, emphasizing the importance of resource cleanup to prevent ongoing billing. By systematically deleting payable resources through the AWS console, learners can ensure they only incur costs for resources currently in use.
Key points
- Delete unused EC2 instances and auto-scaling groups once they have finished running to stop incurring charges
- Remove all storage volumes and snapshots created during the training that are no longer needed
- Access and manage resource deletion through the corresponding AWS console sections
- Verify that all payable resources have been properly removed to avoid unexpected billing
- Resource cleanup is a best practice to maintain cost control and security in AWS environments
FAQ
Why is cleaning up AWS resources important after completing a training course?
Cleaning up resources is crucial because AWS charges for many resources including EC2 instances, storage volumes, and snapshots. By deleting unused resources immediately after they serve their purpose, you avoid incurring unnecessary ongoing costs.
What resources should be deleted when cleaning up an AWS instance group?
You should delete EC2 instances, storage volumes, snapshots, and any other payable resources that were created during the training but are no longer in use. Check the AWS console to verify all resources have been properly removed.
How can I verify that all my AWS resources have been deleted?
Review the relevant AWS console sections (EC2, Volumes, Snapshots) to confirm that no resources remain. Once all payable resources are removed, your AWS account will no longer incur charges for those resources.