UPDATE 10th Dec 2023:
Implemented read-check failover. Message: "Read check has failed. S3Drive functionality may not work properly." shall be rendered. We've had to implement specific workaround for Wasabi and Cubbit at least. If you don't find this working for your S3 provider, please contact us so we can assist.
===
We perform https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html on the: .s3drive_bucket_read_test key.
Since some users want to use S3 and drive mount just for listing we should probably allow skipping the read check.
I've tested behavior in our most recent 1.6.1 version.
Given the S3 permissions:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:List*"
],
"Resource": "*"
}
]
}
bucket can be set up without problems despite the read check.
Upload/download naturally wouldn't work, but that's expected. (Please note that these error responses come from 1.6.1 version which is due to be released. In older version errors might be rendered differently).
Drive mount does also seem to mount properly and listing works.