minio client API

[JayaChandra03]

can minio client API (mc) communicate with zenko s3 compatible server except that admin APIs?

[harshavardhana]

@JayaChandra03 we do not know how S3 compatible Zenko is ? - we did some similar testing with GCP's S3 compatibility claim and here are some results..

API	AWS S3	MinIO	GCS (S3 compatibility)
ListObjectVersions	✔️	✔️	❗

GCS fails in this manner while they succeed on AWS S3 and MinIO fine.

~ mc ls --versions gcs/harshavardhana
mc: <ERROR> Unable to list folder. unrecognized option:Marker

API	AWS S3	MinIO	GCS (S3 compatibility)
GetBucketEncryption	✔️	✔️	❗

GCS fails in this manner while they succeed on AWS S3 and MinIO fine.

~  mc encrypt info gcs/harshavardhana
mc: <ERROR> Unable to get encryption info: 503 Service Unavailable.

API	AWS S3	MinIO	GCS (S3 compatibility)
PutBucketLifecycle	✔️	✔️	❗

GCS fails in this manner while they succeed on AWS S3 and MinIO fine.

~ mc ilm add gcs/harshavardhana --expiry-days 365
mc: <ERROR> Unable to set new lifecycle rules. The XML you provided was not well-formed or did not validate against our published schema.

API	AWS S3	MinIO	GCS (S3 compatibility)
SelectObjectContent	✔️	✔️	❗

GCS fails in this manner while they succeed on AWS S3 and MinIO fine.

~ mc sql gcs/harshavardhana/hosts.csv
mc: <ERROR> Unable to run sql Invalid argument.

API	AWS S3	MinIO	GCS (S3 compatibility)
MultiObjectDelete	✔️	✔️	❗

GCS fails in this manner while they succeed on AWS S3 and MinIO fine.

~ mc rm gcs/harshavardhana/hosts
Removing `gcs/harshavardhana/hosts`.
mc: <ERROR> Failed to remove `gcs/harshavardhana/hosts`. Invalid argument.

API	AWS S3	MinIO	GCS (S3 compatibility)
PutObjectTags	✔️	✔️	❗

GCS fails in this manner while they succeed on AWS S3 and MinIO fine.

~ mc tag set gcs/harshavardhana/hosts "key1=value1&key2=value2&key3=value3"
mc: <ERROR> Failed to set tags for https://storage.googleapis.com/harshavardhana/hosts: 503 Service Unavailable.

Summary

AWS S3 API Compatibility is quite limited, since few basic APIs do not work well. Other APIs that are not mentioned are not part of GCS S3 compatibility layer implementation are

• Multipart Uploads.
• Multiple Destination Bucket Replication
• Event Notifications
• Object Locking and Legal Hold