Skip to content

/AWS1/CL_S3=>PUTOBJECTACL()

About PutObjectAcl

This operation is not supported for directory buckets.

Uses the acl subresource to set the access control list (ACL) permissions for a new or existing object in an S3 bucket. You must have the WRITE_ACP permission to set the ACL of an object. For more information, see What permissions can I grant? in the Amazon S3 User Guide.

This functionality is not supported for Amazon S3 on Outposts.

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. For more information, see Access Control List (ACL) Overview in the Amazon S3 User Guide.

If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions. You must use policies to grant access to your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return the AccessControlListNotSupported error code. Requests to read ACLs are still supported. For more information, see Controlling object ownership in the Amazon S3 User Guide.

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-acl. 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 (Amazon Web Services 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:

    • id – if the value specified is the canonical user ID of an Amazon Web Services account

    • uri – if you are granting permissions to a predefined group

    • emailAddress – if the value specified is the email address of an Amazon Web Services account

      Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:

      • US East (N. Virginia)

      • US West (N. California)

      • US West (Oregon)

      • Asia Pacific (Singapore)

      • Asia Pacific (Sydney)

      • Asia Pacific (Tokyo)

      • Europe (Ireland)

      • South America (São Paulo)

      For a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.

    For example, the following x-amz-grant-read header grants list objects permission to the two Amazon Web Services accounts identified by their email addresses.

    x-amz-grant-read: emailAddress="xyz@amazon.com", emailAddress="abc@amazon.com"

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. For examples of how to specify these grantee values in JSON format, see the Amazon Web Services CLI example in Enabling Amazon S3 server access logging in the Amazon S3 User Guide.

  • By the person's ID:

    <>ID<><>GranteesEmail<>

    DisplayName is optional and ignored in the request.

  • By URI:

    <>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<>

  • By Email address:

    <>Grantees@email.com<>lt;/Grantee>

    The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.

    Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:

    • US East (N. Virginia)

    • US West (N. California)

    • US West (Oregon)

    • Asia Pacific (Singapore)

    • Asia Pacific (Sydney)

    • Asia Pacific (Tokyo)

    • Europe (Ireland)

    • South America (São Paulo)

    For a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
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.

The following operations are related to PutObjectAcl:

Method Signature

IMPORTING

Required arguments:

iv_bucket TYPE /AWS1/S3_BUCKETNAME /AWS1/S3_BUCKETNAME

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

Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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 action with an access point through the Amazon Web Services 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 S3 User Guide.

S3 on Outposts - When you use this action with S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. When you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.

iv_key TYPE /AWS1/S3_OBJECTKEY /AWS1/S3_OBJECTKEY

Key for which the PUT action was initiated.

Optional arguments:

iv_acl TYPE /AWS1/S3_OBJECTCANNEDACL /AWS1/S3_OBJECTCANNEDACL

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

io_accesscontrolpolicy TYPE REF TO /AWS1/CL_S3_ACCESSCTLPOLICY /AWS1/CL_S3_ACCESSCTLPOLICY

Contains the elements that set the ACL permissions for an object per grantee.

iv_contentmd5 TYPE /AWS1/S3_CONTENTMD5 /AWS1/S3_CONTENTMD5

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.>

For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.

iv_checksumalgorithm TYPE /AWS1/S3_CHECKSUMALGORITHM /AWS1/S3_CHECKSUMALGORITHM

Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more information, see Checking object integrity in the Amazon S3 User Guide.

If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm parameter.

iv_grantfullcontrol TYPE /AWS1/S3_GRANTFULLCONTROL /AWS1/S3_GRANTFULLCONTROL

Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.

This functionality is not supported for Amazon S3 on Outposts.

iv_grantread TYPE /AWS1/S3_GRANTREAD /AWS1/S3_GRANTREAD

Allows grantee to list the objects in the bucket.

This functionality is not supported for Amazon S3 on Outposts.

iv_grantreadacp TYPE /AWS1/S3_GRANTREADACP /AWS1/S3_GRANTREADACP

Allows grantee to read the bucket ACL.

This functionality is not supported for Amazon S3 on Outposts.

iv_grantwrite TYPE /AWS1/S3_GRANTWRITE /AWS1/S3_GRANTWRITE

Allows grantee to create new objects in the bucket.

For the bucket and object owners of existing objects, also allows deletions and overwrites of those objects.

iv_grantwriteacp TYPE /AWS1/S3_GRANTWRITEACP /AWS1/S3_GRANTWRITEACP

Allows grantee to write the ACL for the applicable bucket.

This functionality is not supported for Amazon S3 on Outposts.

iv_requestpayer TYPE /AWS1/S3_REQUESTPAYER /AWS1/S3_REQUESTPAYER

RequestPayer

iv_versionid TYPE /AWS1/S3_OBJECTVERSIONID /AWS1/S3_OBJECTVERSIONID

Version ID used to reference a specific version of the object.

This functionality is not supported for directory buckets.

iv_expectedbucketowner TYPE /AWS1/S3_ACCOUNTID /AWS1/S3_ACCOUNTID

The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).

RETURNING

oo_output TYPE REF TO /aws1/cl_s3_putobjectacloutput /AWS1/CL_S3_PUTOBJECTACLOUTPUT

Domain /AWS1/RT_ACCOUNT_ID
Primitive Type NUMC

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->/aws1/if_s3~putobjectacl(
  io_accesscontrolpolicy = new /aws1/cl_s3_accessctlpolicy(
    io_owner = new /aws1/cl_s3_owner(
      iv_displayname = |string|
      iv_id = |string|
    )
    it_grants = VALUE /aws1/cl_s3_grant=>tt_grants(
      (
        new /aws1/cl_s3_grant(
          io_grantee = new /aws1/cl_s3_grantee(
            iv_displayname = |string|
            iv_emailaddress = |string|
            iv_id = |string|
            iv_type = |string|
            iv_uri = |string|
          )
          iv_permission = |string|
        )
      )
    )
  )
  iv_acl = |string|
  iv_bucket = |string|
  iv_checksumalgorithm = |string|
  iv_contentmd5 = |string|
  iv_expectedbucketowner = |string|
  iv_grantfullcontrol = |string|
  iv_grantread = |string|
  iv_grantreadacp = |string|
  iv_grantwrite = |string|
  iv_grantwriteacp = |string|
  iv_key = |string|
  iv_requestpayer = |string|
  iv_versionid = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_requestcharged = lo_result->get_requestcharged( ).
ENDIF.

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.

DATA(lo_result) = lo_client->/aws1/if_s3~putobjectacl(
  io_accesscontrolpolicy = new /aws1/cl_s3_accessctlpolicy( )
  iv_bucket = |examplebucket|
  iv_grantfullcontrol = |emailaddress=user1@example.com,emailaddress=user2@example.com|
  iv_grantread = |uri=http://acs.amazonaws.com/groups/global/AllUsers|
  iv_key = |HappyFace.jpg|
).