Describe the bug
Our application is trying to create bucket dynamically through S3 API with help AWS SDK (v2) . Here we need to create a user , along with access key and secret dynamically as well.
We are using IAM API as well to access creation of user and other credentials.
The response I received while updating bucket ACL through S3 API is the S3Exception. It only works when I set value CannedACL to Private , which is not what we intend. But that's the only workflow that works.
Response received is :
software.amazon.awssdk.services.s3.model.S3Exception: A header you provided implies functionality that is not implemented (Service: S3, Status Code: 501, Request ID: 1704889231403443496)
System Setup
SeaweedFS is deployed on kubernetes
OS version
version 30GB 3.59 linux amd64
if using filer, show the content of filer.toml
[leveldb2]
enabled = true
dir = "/data/filerldb2"
Expected behavior
S3 API call should be able to set ACL for the bucket.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
We are trying to create user dynamically for every bucket we create and have a user only read/write access for the bucket. The user with admin rights will create a bucket and set the ACL the other user should only read/write from/to bucket. We need user to upload/download documents through presigned URL for which a user with only read/write has to be created.
Describe the bug Our application is trying to create bucket dynamically through S3 API with help AWS SDK (v2) . Here we need to create a user , along with access key and secret dynamically as well. We are using IAM API as well to access creation of user and other credentials. The response I received while updating bucket ACL through S3 API is the S3Exception. It only works when I set value CannedACL to Private , which is not what we intend. But that's the only workflow that works.
Response received is : software.amazon.awssdk.services.s3.model.S3Exception: A header you provided implies functionality that is not implemented (Service: S3, Status Code: 501, Request ID: 1704889231403443496)
System Setup
SeaweedFS is deployed on kubernetes OS version version 30GB 3.59 linux amd64 if using filer, show the content of filer.toml [leveldb2] enabled = true dir = "/data/filerldb2"
Expected behavior S3 API call should be able to set ACL for the bucket.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context We are trying to create user dynamically for every bucket we create and have a user only read/write access for the bucket. The user with admin rights will create a bucket and set the ACL the other user should only read/write from/to bucket. We need user to upload/download documents through presigned URL for which a user with only read/write has to be created.