Consider providing an actual S3 account for S3 AWSS3IntegrationSpec CI

[mdedetrich]

Short description

Currently the problem is that Alpakka CI only does S3 tests against Minio. While for basic usage of the S3 client this may have been appropriate, when using Alpakka for a project I came across many discrepancies using the S3 client with a real AWS S3 account. Details of these discrepancies can be found at

• S3: Add MultiPartUpload and ListParts APIs #2730
• S3: Allow bucket creation besides us-east-1 for AWS #2742

As can be seen, these differences are starting to pile up and because of this there is a real risk that regressions can be created due to the fact that CI is currently only testing against Minio (which is not a full S3 implementation and they haven't ever claimed to be). Currently some tests in S3IntegrationSpec either are deliberately skipped in Minio (because there is no such functionality) or AWS S3 requires additional context for specific requests (i.e. make buckets in non default regions) which Minio doesn't require but AWS S3 does.

Details

Would it be possible for Lightbend to start investigating providing an actual S3 account so that the CI can run S3IntegrationSpec? Do note that its possible to apply for promotional credits at https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects to reduce the cost of maintaining such an account