Hue currently uses boto 2.46.1 however there are a few bugs in boto 2.x's handling of SignerTypes. We are interested in using Hue with different S3 end points and the SignerType bugs are a blocker.
boto3 / botocore aren't affected by these bugs. @jennykim, do you think this is ok or is there a blocker preventing us from upgrading? The files that import boto are as follows:
The only risk I see is the django sync_s3 extension. Since boto 2.x and botocore use different package names, the django extension and the filebrowser could use both in the meantime. How do you feel about that change?