This page contains link to the latest stable release of Libcloud. If you are interested in an older release, please visit the archive page.

Libcloud 0.17.0 (stable) - Released on February 18th, 2015


Upgrade notes: Click

You are strongly encouraged to verify those packages using the Apache Libcloud developers KEYS. You can find information on how to do that in the "Quick package verification guide" section bellow.

Distribution specific packages

Libcloud is also available in standard repositories of many popular Linux distributions.

Ubuntu, Debian (apt)

Package name: python-libcloud

apt-get install python-libcloud

Fedora, RedHat (yum)

Package name: python-libcloud

yum install python-libcloud

Arch Linux (pacman)

Package name: apache-libcloud

pacman -S apache-libcloud

FreeBSD (ports, packages)

Port name: ports/net/py-libcloud

cd /usr/ports/net/py-libcloud
make install clean

Package name: py-libcloud

pkg_add -r py27-libcloud

OpenBSD (ports)

cd /usr/ports/net/py-libcloud
make install clean

OS X (MacPorts)

Port name: py-libcloud Installation:

port installl py-libcloud

Keep in mind that distribution packages may be out of date. If you want to make sure that you are using the latest version, you should install it by downloading the archive from this page or using pip.

PyPi Package

The Python Package Index or PyPI is the official third-party software repository for the Python programming language.

We push all the releases to PyPi so you can also download and install the latest release using pip:

pip install apache-libcloud

Keep in mind that pip install command doesn't verify the package signatures, so if you are worried about that, you should manually download the package and verify the signature using the steps described bellow.

Old releases

Old releases can be found in the archive at We strongly recommend to not use those releases, but upgrade to the latest release available.

Source code

Source code can be found in our Git repository at

Read only mirror is also available on Github at

Quick package verification guide

This section contains quick instructions on how to validate the release PGP signatures.

1.. Download the KEYS file from the Apache website


It is very important to only download KEYS file from the Apache server which is mentioned above.

2.. Import KEYS file

   gpg --import KEYS
   gpg: key 42721F00: public key "Paul Querna <...>" imported
   gpg: Total number processed: 1
   gpg:               imported: 1
   gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
   gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
   gpg: next trustdb check due at 2011-10-30</pre>

3.. Verify package with .asc signature file

gpg --verify apache-libcloud-0.17.0.tar.bz2.asc
gpg: Signature made Wed Oct  6 15:31:35 2010 CDT using DSA key ID 42721F00
gpg: Good signature from "Paul Querna <...>"
gpg:                 aka "Paul Querna <...>"
gpg:                 ...</span>
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 39F6 691A 0ECF 0C50 E8BB  849C F788 75F6 4272 1F00

Example of a bad signature:

gpg --verify apache-libcloud-0.17.0.tar.bz2.asc
gpg: Signature made Wed Oct  6 15:31:35 2010 CDT using DSA key ID 42721F00
gpg: BAD signature from "Paul Querna <...>"