Found a great walkthrough on setting up WAL-E to use python-swiftclient for storage in Rackspace Cloud Files: https://developer.rackspace.com/blog/postgresql-plus-wal-e-plus-cloudfiles-equals-awesome/
Unfortunately by default, your backups use the public URL for Cloud Files and eat into metered public bandwidth.
The way to work around this is to set the endpoint_type to internalURL instead of the default publicURL.
You do that by setting the following environment variable:
SWIFT_ENDPOINT_TYPE='internalURL'
That allows WAL-E to use Servicenet for base backups and WAL archiving which will be much faster and not eat into your metered public bandwidth.
Unfortunately by default, your backups use the public URL for Cloud Files and eat into metered public bandwidth.
The way to work around this is to set the endpoint_type to internalURL instead of the default publicURL.
You do that by setting the following environment variable:
SWIFT_ENDPOINT_TYPE='internalURL'
That allows WAL-E to use Servicenet for base backups and WAL archiving which will be much faster and not eat into your metered public bandwidth.