Method: Aws::S3::Client#put_object_acl

Defined in:: lib/aws-sdk-s3/client.rb

#put_object_acl(params = {}) ⇒ `Types::PutObjectAclOutput`

Uses the ‘acl` subresource to set the access control list (ACL) permissions for an object that already exists in a bucket. You must have `WRITE_ACP` permission to set the ACL of an object.

Depending on your application needs, you can choose to set the ACL on an object using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, you can continue to use that approach.

**Access Permissions**

You can set access permissions using one of the following methods:

Specify a canned ACL with the ‘x-amz-acl` request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value of `x-amz-ac`l. If you use this header, you cannot use other access control-specific headers in your request. For more information, see [Canned ACL].
Specify access permissions explicitly with the ‘x-amz-grant-read`, `x-amz-grant-read-acp`, `x-amz-grant-write-acp`, and `x-amz-grant-full-control` headers. When using these headers, you specify explicit access permissions and grantees (AWS accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use `x-amz-acl` header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see [Access Control List (ACL) Overview].

You specify each grantee as a type=value pair, where the type is one of the following:
- ‘emailAddress` – if the value specified is the email address of an AWS account
- ‘id` – if the value specified is the canonical user ID of an AWS account
- ‘uri` – if you are granting permissions to a predefined group
For example, the following ‘x-amz-grant-read` header grants list objects permission to the two AWS accounts identified by their email addresses.

‘x-amz-grant-read: emailAddress=“[email protected]”, emailAddress=“[email protected]” `

You can use either a canned ACL or specify access permissions explicitly. You cannot do both.

**Grantee Values**

You can specify the person (grantee) to whom you’re assigning access rights (using request elements) in the following ways:

By Email address:

‘<Grantee xmlns:xsi=“www.w3.org/2001/XMLSchema-instance” xsi:type=“AmazonCustomerByEmail”><EmailAddress><>[email protected]<></EmailAddress>lt;/Grantee>`

The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
By the person’s ID:

‘<Grantee xmlns:xsi=“www.w3.org/2001/XMLSchema-instance” xsi:type=“CanonicalUser”><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>`

DisplayName is optional and ignored in the request.
By URI:

‘<Grantee xmlns:xsi=“www.w3.org/2001/XMLSchema-instance” xsi:type=“Group”><URI><>acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>`

Versioning

The ACL of an object is set at the object version level. By default, PUT sets the ACL of the current version of an object. To set the ACL of a different version, use the ‘versionId` subresource.

**Related Resources**

CopyObject
GetObject

[1]: docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL [2]: docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html

Examples:

Example: To grant permissions using object ACL


# The following example adds grants to an object ACL. The first permission grants user1 and user2 FULL_CONTROL and the
# AllUsers group READ permission.

resp = client.put_object_acl({
  access_control_policy: {
  }, 
  bucket: "examplebucket", 
  grant_full_control: "[email protected],[email protected]", 
  grant_read: "uri=http://acs.amazonaws.com/groups/global/AllUsers", 
  key: "HappyFace.jpg", 
})

resp.to_h outputs the following:
{
}

Request syntax with placeholder values


resp = client.put_object_acl({
  acl: "private", # accepts private, public-read, public-read-write, authenticated-read, aws-exec-read, bucket-owner-read, bucket-owner-full-control
  access_control_policy: {
    grants: [
      {
        grantee: {
          display_name: "DisplayName",
          email_address: "EmailAddress",
          id: "ID",
          type: "CanonicalUser", # required, accepts CanonicalUser, AmazonCustomerByEmail, Group
          uri: "URI",
        },
        permission: "FULL_CONTROL", # accepts FULL_CONTROL, WRITE, WRITE_ACP, READ, READ_ACP
      },
    ],
    owner: {
      display_name: "DisplayName",
      id: "ID",
    },
  },
  bucket: "BucketName", # required
  content_md5: "ContentMD5",
  grant_full_control: "GrantFullControl",
  grant_read: "GrantRead",
  grant_read_acp: "GrantReadACP",
  grant_write: "GrantWrite",
  grant_write_acp: "GrantWriteACP",
  key: "ObjectKey", # required
  request_payer: "requester", # accepts requester
  version_id: "ObjectVersionId",
})

Response structure


resp.request_charged #=> String, one of "requester"

Options Hash (params):

:acl (String) —

The canned ACL to apply to the object. For more information, see [Canned ACL].

[1]: docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL
:access_control_policy (Types::AccessControlPolicy) —

Contains the elements that set the ACL permissions for an object per grantee.
:bucket (required, String) —

The bucket name that contains the object to which you want to attach the ACL.

When using this API with an access point, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using this operation using an access point through the AWS SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see [Using Access Points] in the *Amazon Simple Storage Service Developer Guide*.

[1]: docs.aws.amazon.com/AmazonS3/latest/dev/using-access-points.html
:content_md5 (String) —

The base64-encoded 128-bit MD5 digest of the data. This header must be used as a message integrity check to verify that the request body was not corrupted in transit. For more information, go to [RFC 1864.>]

[1]: www.ietf.org/rfc/rfc1864.txt
:grant_full_control (String) —

Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.
:grant_read (String) —

Allows grantee to list the objects in the bucket.
:grant_read_acp (String) —

Allows grantee to read the bucket ACL.
:grant_write (String) —

Allows grantee to create, overwrite, and delete any object in the bucket.
:grant_write_acp (String) —

Allows grantee to write the ACL for the applicable bucket.
:key (required, String) —

Key for which the PUT operation was initiated.
:request_payer (String) —

Confirms that the requester knows that they will be charged for the request. Bucket owners need not specify this parameter in their requests. For information about downloading objects from requester pays buckets, see [Downloading Objects in Requestor Pays Buckets] in the *Amazon S3 Developer Guide*.

[1]: docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html
:version_id (String) —

VersionId used to reference a specific version of the object.