You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will allow having a per-user access-control, managed directly by Seaweedfs. That way, I can rely on the Seaweedfs IAM implementation to do access control, instead of doing it in my app.
What is the feature you are proposing to solve the problem?
Adding a new container running an API of the AWS IAM service (weed iam), so that one can configure ACLs for the S3 API for seaweedfs.
Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.
Name and Version
bitnami/seaweedfs
What is the problem this feature will solve?
This will allow having a per-user access-control, managed directly by Seaweedfs. That way, I can rely on the Seaweedfs IAM implementation to do access control, instead of doing it in my app.
What is the feature you are proposing to solve the problem?
Adding a new container running an API of the AWS IAM service (
weed iam
), so that one can configure ACLs for the S3 API for seaweedfs.See here for the links:
What alternatives have you considered?
Expose the
-iam
option to start the the IAM server in the same container as the filer withweed filer -iam
.See other options here (mainly ip and port):
https://github.com/seaweedfs/seaweedfs/blob/master/weed/command/filer.go#L137
The text was updated successfully, but these errors were encountered: