Thank you so much for that information. I ended up putting in this PR with the changes. This change should allow for full support of most (if not all) other S3 Compatible services like Backblaze & MinIO. I did test this specifically with MinIO & AWS with no issues presenting themselves.

If there needs to be anything else done from my end to perform testing, I would be more than happy to do that to get this over the finish line.

As we are needing to run S3 on Premise, we elected to go with MinIO
So after testing, it looks like there are compatibility issues with the AWS SDK. The issue being the default connector using the AWS SDK is using what is called virtual style rather than path style. In this case, I believe a change would be needed to support path style URL's. eg. with aws, you could use either <bucket name>.s3.amazonaws.com or s3.amazonaws.com/bucket-name. For reference from AWS, here is their documentation on the difference between Virtual Hosted & Path Style Requests.
In the situation of how the SDK works by default, it is using virtual path style which would not work with the implementation style that we have used with MinIO.

From what I can tell, the modification to the AWS SDK should be relatively simple to implement as it is adding another option within the web interface, as well as adding a line in the AmazonS3Config class to "ForcePathStyle" when selected. If it would be easier, I can draft up a PR that can implement those changes, however my C# is a bit rusty.

I will say that by implementing this, it should support the rest of the S3 Compatible providers others have looked at.

I've been looking into ProGet with my company and wanted to see if there was support for MinIO? I know there is AWS S3 storage support, but it looks like the only way is using virtual path support, whereas MinIO requires forcing path style.