gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Amazon S3 API (markdown)

Chris Lu 2020-02-17 12:53:18 -08:00
parent 00a9888a01
commit c7b2cb630f
1 changed files with 60 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

63
Amazon-S3-API.md

@ -33,8 +33,65 @@ Currently, the following APIs are supported.
* CopyObjectPart
```
Not planned:
* ACL
Not included:
* Policy
The major difference with Amazon S3 is that the permission and access control are not implemented yet.
# Authentication
By default, the access key and secret key to access `weed s3` is not authenticated. To To enable credential based access, create a config.json file similar to the example below, and specify it via `weed s3 -config=config.json`.
## Configuration Example
You just need to create a user with all "Admin", "Read", "Write" actions.
You can create as many users as needed. Each user can have multiple credentials.
* The "Admin" action is needed to list, create, and delete buckets.
* The "Write" action allows uploading files within a bucket. // TODO limit Write operations to a specific bucket.
* The "Read" action allows reading and listing files within a bucket.// TODO limit Read operations to a specific bucket.
```
{
"identities": [
{
"name": "some_name",
"credentials": [
{
"accessKey": "some_access_key1",
"secretKey": "some_secret_key2"
}
],
"actions": [
"Admin",
"Read",
"Write"
]
},
{
"name": "some_read_only_user",
"credentials": [
{
"accessKey": "some_access_key1",
"secretKey": "some_secret_key1"
}
],
"actions": [
"Read"
]
},
{
"name": "some_normal_user",
"credentials": [
{
"accessKey": "some_access_key2",
"secretKey": "some_secret_key2"
}
],
"actions": [
"Read",
"Write"
]
}
]
}
```