Table Of Contents


User Guide

First time using the AWS CLI? See the User Guide for help getting started.

[ aws . s3api ]



Sets the permissions on an existing bucket using access control lists (ACL). For more information, see Using ACLs . To set the ACL of a bucket, you must have WRITE_ACP permission.

You can use one of the following two ways to set a bucket's permissions:

  • Specify the ACL in the request body
  • Specify permissions using request headers


You cannot specify access permission using both the body and the request headers.

Depending on your application needs, you may choose to set the ACL on a bucket 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, then 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-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 (AWS accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use the 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-write header grants create, overwrite, and delete objects permission to LogDelivery group predefined by Amazon S3 and two AWS accounts identified by their email addresses.

x-amz-grant-write: uri="", emailAddress="", emailAddress=""

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="" xsi:type="AmazonCustomerByEmail";/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="" xsi:type="CanonicalUser"IDID/IDDisplayNameGranteesEmail/DisplayName /Grantee DisplayName is optional and ignored in the request
  • By URI: Grantee xmlns:xsi="" xsi:type="Group"URI
Related Resources
  • CreateBucket
  • DeleteBucket
  • GetObjectAcl

See also: AWS API Documentation

See 'aws help' for descriptions of global parameters.


[--acl <value>]
[--access-control-policy <value>]
--bucket <value>
[--content-md5 <value>]
[--grant-full-control <value>]
[--grant-read <value>]
[--grant-read-acp <value>]
[--grant-write <value>]
[--grant-write-acp <value>]
[--cli-input-json <value>]
[--generate-cli-skeleton <value>]


--acl (string)

The canned ACL to apply to the bucket.

Possible values:

  • private
  • public-read
  • public-read-write
  • authenticated-read

--access-control-policy (structure)

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

JSON Syntax:

  "Grants": [
      "Grantee": {
        "DisplayName": "string",
        "EmailAddress": "string",
        "ID": "string",
        "Type": "CanonicalUser"|"AmazonCustomerByEmail"|"Group",
        "URI": "string"
      "Permission": "FULL_CONTROL"|"WRITE"|"WRITE_ACP"|"READ"|"READ_ACP"
  "Owner": {
    "DisplayName": "string",
    "ID": "string"

--bucket (string)

The bucket to which to apply the ACL.

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

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

--cli-input-json (string) Performs service operation based on the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally.

--generate-cli-skeleton (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.

See 'aws help' for descriptions of global parameters.


This example grants full control to two AWS users ( and and read permission to everyone:

aws s3api put-bucket-acl --bucket MyBucket --grant-full-control, --grant-read uri=

See for details on custom ACLs (the s3api ACL commands, such as put-bucket-acl, use the same shorthand argument notation).