Decommissioning a Cloud Account Cleanly
Closing down costs more attention than starting up. Data extraction, dependency checks and billing closure each have a failure mode.
Winding an account down is treated as an afterthought and quietly causes more damage than setting one up. The failure modes are losing something you needed, breaking something that still depended on it, and continuing to be billed for something you thought was gone.
Extract before you delete
Work out what has to survive and get it out first:
- Databases, exported and verified by restoring the export somewhere else.
- Object storage contents.
- Configuration that exists only on the servers.
- Logs you may need for audit or compliance reasons.
- TLS certificates and keys still in use elsewhere.
Verification matters. An export nobody has restored is a hope, not a backup.
Find what still points at it
Things outside the account may depend on it:
- DNS records pointing at its addresses.
- Webhooks from third-party services.
- CI pipelines deploying into it.
- Monitoring checks that will alarm when it disappears.
- Other applications calling its APIs.
Stop before deleting
Turn things off and wait. A week of silence is strong evidence nothing needed them. Deletion is irreversible; stopping is not. This single habit prevents most decommissioning incidents.
Delete in dependency order
Compute first, then the storage attached to it, then networking, then supporting identities and keys. Deleting out of order leaves orphans that are harder to find later.
Close the billing loop
Deleting resources is not the same as ending the billing relationship. Confirm the final invoice, remove the payment method where appropriate, and check the following month’s statement rather than assuming. Reserved addresses and snapshots are the usual survivors.
If the account is being transferred rather than closed
Different job. Instead of deleting, you are handing over: remove your own credentials and keys, clear your recovery paths, document the state, and let the new owner run their own first-hour sequence. The receiving side of that process is covered in the first hour after taking over a cloud account.
Cloud accounts on OldCloudShop
Ten providers, every configuration and the starting price for each.
Continue in the library
Other entries covering account structure, billing, security and provider infrastructure.