Home > Storage > PowerScale (Isilon) > Product Documentation > Protocols > Dell PowerScale: OneFS S3 API Guide > PutBucketAcl
This API sets the permissions on an existing bucket using access control lists (ACLs). Table 10 shows the details about the OneFS S3 PutBucketACL API request parameters and request body. If not specified, all unsupported request parameters and request body are silently ignored by OneFS without an error code being returned to client.
Request parameters/body | Supported | Description |
Bucket | Yes | Required: Yes This is the name of the bucket containing the objects. |
Content-MD5 | Yes | This is the base64-encoded, 128-bit MD5 digest of the data. |
x-amz-acl | Yes | This is the canned ACL to apply to the bucket. Valid values: private | public-read | public-read-write | authenticated-read |
x-amz-grant-full-control | Yes | This allows the grantee the read, write, read ACP, and write ACP permissions on the bucket. |
x-amz-grant-read | Yes | This allows the grantee to list the objects in the bucket. |
x-amz-grant-read-acp | Yes | This allows the grantee to read the bucket ACL. |
x-amz-grant-write | Yes | This allows the grantee to create, overwrite, and delete any object in the bucket. |
x-amz-grant-write-acp | Yes | This allows the grantee to write the ACL for the applicable bucket. |
Note: Amazon S3 allows specifying a grantee using the following headers: email address, id, uri in the x-amz-grant-read, x-amz-grant-write, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control. OneFS does not support an email address to specify a grantee, and a 501 NotImplemented code is returned.