INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Inventory resources across every Region used and identify the information needed for retain/stop/delete decisions and follow-up verification.

Prerequisite

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.

Fields to record for each learning resource
RecordWhat to establish
Resource and locationService, Region and identifiable resource name/ID
Owner and purposeWhether it is exclusive learning use or supports other people/services
DataWhat must remain, what may be removed and the recovery requirement
Dependencies and controllerReferences from elsewhere and automation that could recreate it
Decision and operatorReason for retention/stop/deletion, authorization scope and verification owner

Inventory → retention decision → action → follow-up

Establish the resource scope before authorized cleanup
Establish the resource scope before authorized cleanup1: Inventory — A resource you discover is not automatically a deletion target. — Retention and impact. 2: Retention and impact — Identify what must remain, what is unnecessary, authorization and impact. — Authorized action. 3: Authorized action — Verify the action, then recheck retained resources and charges for past use. — Resource/cost review123InventoryRetention andimpactAuthorized actionResource/costreviewEstablish the resource scope before authorized cleanup1: Inventory — A resource you discover is not automatically a deletion target. — Retention and impact. 2: Retention and impact — Identify what must remain, what is unnecessary, authorization and impact. — Authorized action. 3: Authorized action — Verify the action, then recheck retained resources and charges for past use. — Resource/cost review123InventoryRetention andimpactAuthorizedactionResource/costreview
  1. Inventory → Retention and impactA resource you discover is not automatically a deletion target.
  2. Retention and impact → Authorized actionIdentify what must remain, what is unnecessary, authorization and impact.
  3. 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

Common checks; adapt them to the actual scope used
ResourceKey checks
EBS and snapshotsPer-volume termination deletion settings, retention purpose and other consumers
Elastic IP and related addressesDisassociation versus release, retention purpose and charging terms
NAT, load balancers and similar componentsIndependent lifecycle, dependencies and automated creation
S3 and other stored dataData owner, consumers and retention/deletion conditions
Purchasing commitments and subscriptionsTerm 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

Turn each observed state into the next decision
ObservationNext check
EC2 is stoppedWhether it will be restarted or may be terminated; inspect non-compute resources too
An EBS volume remainsRequired data, owner, other consumers and retention purpose
An Elastic IP is unassociatedReuse, dependencies and charges; consider release only if authorized as unnecessary
Charges still appear the day after cleanupSeparate the charged period, past use, reporting delay and other retained resources

Choose an option to see the result and explanation.

The EC2 list is empty. Is cleanup complete across every Region?
Read the answer and reason

Answer: No, inspect other resources and locations too · One resource list does not cover the account’s entire inventory. Review used Regions, storage, addresses, associated functions, commitments and billing.

Record retained resources, reasons and verification

  1. Record each retention reason or authorized action in the inventory.
  2. Use resource-specific official procedures and verify the result and remaining dependencies.
  3. Recheck retained resources across all Regions used.
  4. Read the billing period and update state; distinguish past use from continuing cost.
  5. 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

  1. Inventory all used Regions and associated resources.
  2. Establish owners, data and dependencies before deciding.
  3. 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.