How to delete your CloudStack account

About deleting your CloudStack account

Apache CloudStack is a sophisticated open-source software designed to deploy and manage large networks of virtual machines as a highly available, scalable cloud computing platform. Unlike public SaaS providers, CloudStack is typically deployed by organizations, hosting providers, or individual developers to create their own private or public cloud infrastructure. Because the software is self-managed, 'deleting an account' is not a single click process but rather a complex task of de-provisioning virtual resources, removing user records from the SQL database, and wiping associated storage volumes.

Users often seek to delete their CloudStack presence when migrating to a different orchestrator like OpenStack or when a specific project deployment is finished. Reasons for account removal include:

• Reducing the attack surface of unused or legacy virtual machine instances.
• Reclaiming allocated compute, network, and storage resources from the cloud pool.
• Complying with internal data governance policies regarding inactive virtual environments.
• Removing personal or company-specific configuration data stored within the management server database.

What happens to your data

When you delete an account in CloudStack, the management server executes commands to stop and destroy associated virtual machine (VM) instances and release public IP addresses. However, since the administrator maintains the hardware, data persistence depends on the underlying storage implementation (e.g., Ceph, NFS, or local storage).

Types of data often associated with your CloudStack account include:

• Virtual Machine disk images and snapshots.
• User metadata, SSH public keys, and password hashes stored in the CloudStack database.
• Network configurations, including VPCs, load balancer rules, and firewall ingress/egress policies.
• Usage records and billing data logs if the instance uses a billing integration plugin.

It is vital to note that while the account record is removed from the MySQL database, block storage volumes might persist on your SAN or local storage backend if not explicitly commanded for destruction during the account purge process. You must ensure your storage backends are sanitized to prevent data remnants from being accessed by subsequent users of the same hardware.

Privacy considerations

CloudStack itself does not engage in external ad targeting or third-party data mining, as it is an infrastructure orchestration tool rather than a public service. Privacy concerns are largely dependent on the administrator of your specific CloudStack deployment. If you are using a managed service provider that uses CloudStack, they might log your API interactions or resource utilization metrics.

Privacy tips for CloudStack users:

• Audit your API key usage and revoke any keys that are no longer strictly necessary.
• Ensure your cloud administrator has enabled encryption at rest for your virtual disk volumes.
• Regularly rotate your SSH keys attached to virtual instances.
• Verify if your deployment configuration logs management traffic in plain text within the management server logs.

Frequently Asked Questions

Does deleting my account delete my virtual machines?

By default, CloudStack requires you to destroy the VM instances associated with your account before the account object can be fully removed from the database.

How do I ensure all my data is wiped from storage backends?

You must manually execute the destroy command for all volumes and snapshots via the API or GUI before removing the user account to ensure that the storage backend flags the blocks as available for overwrite.

Can I recover my data after deleting a CloudStack account?

If the storage volumes were marked for destruction and the garbage collector has run on your storage backend, recovery is generally not possible.

Is my usage history deleted when the account is removed?

Usage events stored in the CloudStack database are typically purged, but if your administrator forwards logs to an external SIEM or analysis tool, those records will persist until manually cleared.

What if I am an end-user and not the administrator?

You cannot delete your own account if the administrator has restricted access; you must submit a ticket to the cloud provider to have your identity and associated instances removed.