-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is s3 secret enabed? #70
Comments
Yes, you can. But (as far as I know), you have to add it manually by running something like:
in the Source: https://github.com/seaweedfs/seaweedfs/wiki/Amazon-S3-API#s3-authentication |
Thanks, I've done this in one of master nodes, but I can still access filer nodes without using accessKey/secretKey, did I miss something ? |
I am by no means knowledgeable regarding filer, but my guess would be that the accessKey/secretKey is only mandatory for the specific bucket and not the filer as a whole. If you want to secure your whole filer instance, my guess would be, that you had to configure But as I said, I'm only guessing here. But even if I was right, a new property needs to be added to the Seaweed Custom Resource Definition, so that users would be able to set security.toml options. Input from someone more knowleadgable would be highly appreciated. |
Can I enable accessKey/secretKey for s3 now ?
The text was updated successfully, but these errors were encountered: