In this article
Removing compute may leave independent resources behind; every retained object needs a purpose, owner and review date.
At the end of a GPU pilot, inspect disks, snapshots, addresses and network components as well as instances. Every retained resource needs a purpose, owner and retention period. Deleting the compute instance may close only one part of the project, so use an inventory and verify the documented final states.
Inventory before removing the environment
While relationships are still visible in the control panel, record each resource ID, region, project, purpose and decision: remove, retain for the next stage or transfer to an owner. Labels such as test or backup become ambiguous without a short explanation and review date.
Confirm that results and the launch recipe have been preserved first. Read a small control sample from the retained archive and ensure another responsible person knows its location. Cost cleanup should not destroy the only useful outcome of the experiment. Keep the acceptance record outside the temporary instance.
Verify the compute state
Azure’s states and billing documentation distinguishes Stopped from Deallocated. Other products have their own lifecycle operations. Saying the server is switched off does not establish the intended billing state, and a closed SSH session says little about the service’s resource allocation.
Record the final state and action time for each VM or container resource. If the operation remains pending, wait for its documented completion before marking the task finished. Preserve a resource identifier so that later usage can be associated with the correct environment rather than an informal nickname.
Review independent objects
AWS documents EBS retention through deletion attributes and Elastic IP addresses as separately managed resources. These examples explain why the compute list alone is insufficient.
| Resource group | Cleanup question |
|---|---|
| Compute | Did every unnecessary instance reach the intended state? |
| Volumes | Are any unattached disks still needed? |
| Snapshots and images | Who owns each retained copy? |
| Public addresses | Does every address still have a purpose? |
| Network services | Are temporary gateways or load balancers required? |
| Data storage | Are uploads complete and retention dates assigned? |
Check every region and project used during the pilot. An empty list under the current filter does not establish that the account contains no remaining resources.
Reconcile charges and hand over
For a one-week experiment, a team might keep one result archive and one tested image while removing temporary copies. It records their owners and review dates, then updates the restart instructions. A second reviewer can catch a forgotten region or snapshot without repeating every operational action.
After an appropriate accounting interval, compare reported usage with that expected remainder. Investigate identifiable resources or completed billing periods rather than deleting objects at random because totals did not immediately fall to zero. Revoke unused credentials and check automation.
Official references: learn.microsoft.com — states billing, docs.aws.amazon.com — preserving volumes on termination, docs.aws.amazon.com — elastic ip addresses eip.
Related guides: GPU powered off, public IP retained: audit the network resource, GPU cloud team access: API keys and SSH keys have different jobs.