Document Minio issue with multipart + direct AWS deployment using non us-east-1 region (cantaloupe)

[DiegoPino]

What?

We need to document a production deployment without minio and make sure Cantaloupe can connect to a different Bucket.
Why?

So far on Archipelago 1.3.0 with Cantaloupe 6.0.1 I can only make Cantaloupe talk to EAST-1. I thought the issue was DNS resolving but it's not that. On EAST one or using minio as in-between (any region) it works

Maybe it is just my Dec 24th distraction, but I will try to make some test with small test AWS/EC2 machines in other regions and see what I come with up

This is related to the 5GBytes limit that requires multipart copies and puts, for which MIN.IO adds an invalid header that breaks the API calls

For this week I will run Minio only for IIIF and Repo directly connected to S3 (that works on us-west)

[DiegoPino]

Some stuff I found in Cantaloupe's code:

• https://github.com/cantaloupe-project/cantaloupe/blob/21057cf72071840e2a984450bf8845c6e6490ec9/src/main/java/edu/illinois/library/cantaloupe/util/S3ClientBuilder.java#L152
• I will try forcing an endpoint from https://docs.aws.amazon.com/general/latest/gr/s3.html to use an us-west bucked bc something tells me the AWS S3 API is not tested well enough