While tinkering with wal-e, postgres and minio, I found a bug in boto in which the region name is inferred by the hostname with the v4 signature authentication handler, which is required by minio. boto2 hardcodes their region name with this authentication handler which makes it a non starter. However, boto3 allows us to configure the region name. Since boto3 is now considered stable, it would make sense to rebase wal-e on top of boto3 so that we can use wal-e with minio.
While tinkering with wal-e, postgres and minio, I found a bug in boto in which the region name is inferred by the hostname with the v4 signature authentication handler, which is required by minio. boto2 hardcodes their region name with this authentication handler which makes it a non starter. However, boto3 allows us to configure the region name. Since boto3 is now considered stable, it would make sense to rebase wal-e on top of boto3 so that we can use wal-e with minio.
See https://github.com/wal-e/wal-e/issues/197#issuecomment-170655919 for more information.