Although it is inconsistent, this behavior is intentional and follows the AWS S3 API specification.
Our solution was to examine the URL and prepend 'https://' if required.
Please see this issue in aws-sdk-js
- https://github.com/aws/aws-sdk-js/issues/4636