Topic lessonTopic: Account protection and resource cleanup
AWS cleanup after learning: review retained resources, data and costs
After learning, inspect stored data, retained IP addresses, networking resources and commitments, not just the instance you created. Do not start with bulk deletion. Establish ownership, purpose, dependencies and retention needs, then work within the authorized scope. Afterwards, separate charges for past use from continuing costs.
Inventory resources across every Region used and identify the information needed for retain/stop/delete decisions and follow-up verification.
Know the roles of EC2, EBS and S3 and the difference between stopping and terminating. Only an owner-authorized operator performs real actions.
Start with an inventory, not a delete button
List the accounts, Regions and services used. An empty EC2 list does not establish that EBS, snapshots, IP addresses or S3 are empty too. Inspect associated resources created by other services and resources in other Regions. Disabling a Region is not a substitute for deleting resources.
| Record | What to establish |
|---|---|
| Resource and location | Service, Region and identifiable resource name/ID |
| Owner and purpose | Whether it is exclusive learning use or supports other people/services |
| Data | What must remain, what may be removed and the recovery requirement |
| Dependencies and controller | References from elsewhere and automation that could recreate it |
| Decision and operator | Reason for retention/stop/deletion, authorization scope and verification owner |
Inventory → retention decision → action → follow-up
- Inventory → Retention and impactA resource you discover is not automatically a deletion target.
- Retention and impact → Authorized actionIdentify what must remain, what is unnecessary, authorization and impact.
- Authorized action → Resource/cost reviewVerify the action, then recheck retained resources and charges for past use.
- Inventory
- List all used locations and associated resources.
- Retention and impact
- Establish ownership, required data and dependencies.
- Authorized action
- Use the official procedure for that resource.
- Resource/cost review
- Separate retained resources from delayed charges for earlier use.
Look beyond the instance for retained resources
| Resource | Key checks |
|---|---|
| EBS and snapshots | Per-volume termination deletion settings, retention purpose and other consumers |
| Elastic IP and related addresses | Disassociation versus release, retention purpose and charging terms |
| NAT, load balancers and similar components | Independent lifecycle, dependencies and automated creation |
| S3 and other stored data | Data owner, consumers and retention/deletion conditions |
| Purchasing commitments and subscriptions | Term and obligations separate from stopping or removing a resource |
For EBS termination behavior, inspect each volume’s DeleteOnTermination setting. Do not rely on “root means deleted” or “data means retained.” Establish both the data that must survive and the cost of retained storage.
Worked example: EC2 is stopped but storage and an IP remain
| Observation | Next check |
|---|---|
| EC2 is stopped | Whether it will be restarted or may be terminated; inspect non-compute resources too |
| An EBS volume remains | Required data, owner, other consumers and retention purpose |
| An Elastic IP is unassociated | Reuse, dependencies and charges; consider release only if authorized as unnecessary |
| Charges still appear the day after cleanup | Separate the charged period, past use, reporting delay and other retained resources |
Choose an option to see the result and explanation.
Record retained resources, reasons and verification
- Record each retention reason or authorized action in the inventory.
- Use resource-specific official procedures and verify the result and remaining dependencies.
- Recheck retained resources across all Regions used.
- Read the billing period and update state; distinguish past use from continuing cost.
- Take unresolved charges or anomalies to the billing administrator or the official AWS support route.
Cleanup does not necessarily make the bill immediately zero. Earlier usage and contractual obligations remain separate, and billing updates take time. Aim for an evidence-backed explanation of what was checked and what remains.
Check, then explain in your own words
- Inventory all used Regions and associated resources.
- Establish owners, data and dependencies before deciding.
- Verify action results, retained resources and billing separately.
Check your understanding: Should you immediately delete every billed resource to reduce cost?
No. Establish its purpose, owner, required data and dependencies first.
A charge alone does not authorize deletion that could damage other users or data. A past-usage item may not even describe a currently existing resource.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- Understanding unexpected chargesChecked:
Scope and conditionsResources in all Regions; deletion and data retention need review
Used in this lessonStart with an inventory, not a delete button Look beyond the instance for retained resources Worked example: EC2 is stopped but storage and an IP remain Record retained resources, reasons and verification
- EC2 instance state changesChecked:
Scope and conditionsEBS-backed stop/start, hibernation and termination differ
Used in this lessonWorked example: EC2 is stopped but storage and an IP remain
- Understanding your billChecked:
Scope and conditionsBilling period, service/Region breakdown and estimated charges
Used in this lessonWorked example: EC2 is stopped but storage and an IP remain Record retained resources, reasons and verification
Scope and conditionsData loss and persistence; DeleteOnTermination is evaluated for each EBS volume, not assumed from instance state.
Used in this lessonLook beyond the instance for retained resources
- Amazon EBS pricingChecked:
Scope and conditionsProvisioned capacity, additional performance and snapshots; no unit rate or price quote is embedded.
Used in this lessonLook beyond the instance for retained resources
- Amazon VPC pricingChecked:
Scope and conditionsPublic IPv4 and NAT gateway pricing dimensions, including retained/idle addresses; no unit-rate quote.
Used in this lessonLook beyond the instance for retained resources Worked example: EC2 is stopped but storage and an IP remain