Cloud Computing with Debian and its descendants

This page summaries on what to expect from Debian when it comes to compute clouds, in which virtual machines can be quickly provisioned via service calls, configured and manipulated through various manual or automated means, and terminated when no longer needed.

We support a number of different cloud-oriented use cases:

Starting with bullseye, documentation on the image lifecycle and security support can be found here.

Debian cloud images in the cloud marketplaces

Cloud images have to deviate from the base Debian image due to nature of the environment in which they are running.
On pages listed below we're trying to explain differences between them:

Cloud images requirements

Building cloud images


These clouds don't have Debian images yet, but users of these services are invited to work with the cloud team to add support:

Cloud software already available in Debian

How to contribute

Start by joining the Debian Cloud team and/or the Openstack maintainers mailing list

Note that, especially OpenStack, is BIG. We already have more than 50 binary packages of it in sid. So of course, we'd be more than happy to have help for its packaging/testing.

Reporting bugs

The Debian Cloud team uses the pseudo-package to track issues not bound to a specific package maintained in the team (for example, for the Amazon AWS images).

After reporting a bug against a Debian package, which has an impact on Debian images provided on or for clouds, please mark that the bug affects

Bugs are divided in four categories, by usertagging with the address ?

Bugs related to the images distributed in public clouds (outdatedness, lack of availability in all zones, etc.) can be usertagged ( More names of public clouds can of course be added, please keep the list of control commands below up to date) with:

The user categories were set up with the following control emails:


What is the default user name on the Debian cloud images?

A. The default user name differs based on the cloud environment. Please see for more information. Authentication is via the ssh key installed by cloud-init. There is no password. These accounts may become root by running (no password required):

sudo -i

CategoryPermalink | CategoryVirtualization | CategorySystemAdministration