Generalize S3 allow-all documentation

Chris Lu committed 2026-01-14 12:46:37 -08:00
1 parent 8b2965e6d2
commit 235c242e59
2 files changed
+3 -3

No files matched your search

+1 -1
@@ -81,7 +81,7 @@ The initial IAM config will be created automatically for the `mini` user with th
## Default S3 Access
By default, `weed mini` starts in **"Allow All" mode** if no S3 credentials are configured. This is designed for maximum ease of use in development and testing environments.
By default, the SeaweedFS S3 gateway starts in **"Allow All" mode** if no S3 credentials are configured. This is designed for maximum ease of use in development and testing environments, and it applies to all S3 instances, including `weed mini`.
- **No credentials configured**: All S3 operations are allowed without authentication.
- **Credentials added**: As soon as *any* credentials are configured (either initially via flags/env vars or dynamically via the Admin UI/Shell), **authentication is automatically enabled** and all requests will then require valid credentials.
+2 -2
@@ -323,11 +323,11 @@ Environment variables create global admin access and cannot be scoped to specifi
By default, the SeaweedFS S3 gateway handles anonymous access differently depending on whether any credentials have been configured:
### Allow-All Mode (Default for `weed mini`)
### Allow-All Mode
If no S3 credentials have been configured through any of the methods above (config files, filer, or environment variables), the S3 gateway defaults to **Allow-All Mode**. In this mode:
- All S3 operations are permitted without authentication.
- This is the default state when starting `weed mini` without any flags or environment variables.
- This is the default state for `weed mini` (and `weed s3`) when starting without any flags or environment variables.
### Authentication Required Mode