Boto not working mumbai region

[sayatul]

boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request

[klodha]

I am also facing similar error. Actually using s3put CLI utility to push log files to my s3 bucket. I am able to do that fine on Singapore S3 bucket even without specifying region.

However, for Mumbai region, if I skip --region parameter, it gives authentication method V4 error. But if I specify --region, it fails with error raise ValueError('Invalid region %s specified' % a).

Upon checking code of s3put, I found that its calling boto.s3.regions() and compare passed value against that. However, Mumbai region (ap-south-1) is not in the list returned, thus check fails and it raises error.

So for time being, instead of using s3put supplied in AMI (updated to latest version using yum update but with same error), I am using s3cmd. I found s3put easier, so hope Boto's issue get resolved soon.

[checkaayush]

The region names are hardcoded here. Mumbai region, being the one newly established, isn't mentioned there.

Is someone looking into this?

[m-tse]

I am having a similar issue. For me, when I try to establish a connection to an ap-south-1 bucket, it fails and gives me a NoneType object:

bucket = conn.lookup(bucketName, validate=False)
AttributeError: 'NoneType' object has no attribute 'lookup'

Note: I'm using boto 2.38.0.

I have a feeling it has to do with ap-south-1 only supporting Signature Version 4. It looks like there was a similar hotfix to auto detect signature version 4 for ap-northeast-2 here. Do we need to do a similar hotfix here?

I tried forcing use of version 4 by adding the following lines to my ~/.boto config file, but it didn't work:

[s3]
use-sigv4 = True

EDIT: It looks like the feature I was talking about was added in a commit. When I updated to boto 2.42.0, ap-south-1 worked for me.

What version of boto are you guys using? Maybe give 2.42.0 a try?

[jamesls]

Yep, ap-south-1 should be available in 2.42.0. Let me know if anyone's still having issues on the latest version of boto.

[sivacool]

@jamesls am using the latest version(2.48.0) of boto but still am getting the same error