Home > Storage > PowerScale (Isilon) > Product Documentation > Protocols > Dell PowerScale: OneFS S3 API Guide > PutObjectAcl
This API sets the permissions on an existing object using ACLs. Table 22 shows the details about the OneFS S3 PutObjectACL API request parameters and request body. If not specified, OneFS silently ignores all unsupported request parameters and the request body, without returning an error code to the 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. Please refer to section 3 for details. |
Key | Yes | Required: Yes This is the key name of the object to set the ACL. |
versionId | No | N/A |
x-amz-acl | Yes | This is the standard ACL to apply to the object. OneFS does not support aws-exec-read and log-delivery-write. Valid values: private | public-read | public-read-write | authenticated-read | bucket-owner-read | bucket-owner-full-control |
x-amz-grant-full-control | Yes | This gives the grantee READ, READ_ACP, and WRITE_ACP permissions on the object. |
x-amz-grant-read | Yes | This allows the grantee to read the object data and its metadata. |
x-amz-grant-read-acp | Yes | This allows the grantee to read the object ACL. |
x-amz-grant-write-acp | Yes | This allows the grantee to write the ACL for the applicable object. |
Note: Amazon S3 allows specifying a grantee using the following headers: email address, id, uri in the x-amz-grant-readx-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.