put_object_acl¶
Operation¶
put_object_acl
async
¶
put_object_acl(input: PutObjectAclInput, plugins: list[Plugin] | None = None) -> PutObjectAclOutput
Warning
End of support notice: As of October 1, 2025, Amazon S3 has discontinued
support for Email Grantee Access Control Lists (ACLs). If you attempt to
use an Email Grantee ACL in a request after October 1, 2025, the request
will receive an HTTP 405 (Method Not Allowed) error.
This change affects 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), and South America (São Paulo).
Note: 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.
Warning
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-aclrequest 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 ofx-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, andx-amz-grant-full-controlheaders. 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 usex-amz-aclheader 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
Note: 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-readheader 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:
<grantee xmlns:xsi="http://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="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><uri><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<>``</uri></grantee> -
By Email address:
<grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><emailaddress><>Grantees@email.com<>``</emailaddress>lt;/Grantee>The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
Note: 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
versionIdsubresource.
The following operations are related to PutObjectAcl:
Warning
You must URL encode any signed header values that contain spaces. For
example, if your header value is my file.txt, containing two spaces
after my, you must URL encode this value to my%20%20file.txt.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
input
|
PutObjectAclInput
|
An instance of |
required |
plugins
|
list[Plugin] | None
|
A list of callables that modify the configuration dynamically. Changes made by these plugins only apply for the duration of the operation execution and will not affect any other operation invocations. |
None
|
Returns:
| Type | Description |
|---|---|
PutObjectAclOutput
|
An instance of |
Input¶
PutObjectAclInput
dataclass
¶
Bases: _SerdeShape
Dataclass for PutObjectAclInput structure.
Attributes¶
access_control_policy
class-attribute
instance-attribute
¶
Contains the elements that set the ACL permissions for an object per grantee.
acl
class-attribute
instance-attribute
¶
acl: str | None = ...
The canned ACL to apply to the object. For more information, see Canned ACL.
bucket
class-attribute
instance-attribute
¶
bucket: str | None = ...
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.
checksum_algorithm
class-attribute
instance-attribute
¶
checksum_algorithm: str | None = ...
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.
content_md5
class-attribute
instance-attribute
¶
content_md5: str | None = ...
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.
expected_bucket_owner
class-attribute
instance-attribute
¶
expected_bucket_owner: str | None = ...
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).
grant_full_control
class-attribute
instance-attribute
¶
grant_full_control: str | None = ...
Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.
This functionality is not supported for Amazon S3 on Outposts.
grant_read
class-attribute
instance-attribute
¶
grant_read: str | None = ...
Allows grantee to list the objects in the bucket.
This functionality is not supported for Amazon S3 on Outposts.
grant_read_acp
class-attribute
instance-attribute
¶
grant_read_acp: str | None = ...
Allows grantee to read the bucket ACL.
This functionality is not supported for Amazon S3 on Outposts.
grant_write
class-attribute
instance-attribute
¶
grant_write: str | None = ...
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.
grant_write_acp
class-attribute
instance-attribute
¶
grant_write_acp: str | None = ...
Allows grantee to write the ACL for the applicable bucket.
This functionality is not supported for Amazon S3 on Outposts.
key
class-attribute
instance-attribute
¶
key: str | None = ...
Key for which the PUT action was initiated.
request_payer
class-attribute
instance-attribute
¶
request_payer: str | None = ...
Confirms that the requester knows that they will be charged for the request. Bucket owners need not specify this parameter in their requests. If either the source or destination S3 bucket has Requester Pays enabled, the requester will pay for the corresponding charges. For information about downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays Buckets in the Amazon S3 User Guide.
Note
This functionality is not supported for directory buckets.
Output¶
PutObjectAclOutput
dataclass
¶
Bases: _SerdeShape
Dataclass for PutObjectAclOutput structure.
Attributes¶
request_charged
class-attribute
instance-attribute
¶
request_charged: str | None = ...
If present, indicates that the requester was successfully charged for the request. For more information, see Using Requester Pays buckets for storage transfers and usage in the Amazon Simple Storage Service user guide.
Note
This functionality is not supported for directory buckets.
response_metadata
class-attribute
instance-attribute
¶
Metadata about the response that produced this output. Use this to recover the request identifiers a service's support team needs in order to investigate a call. Members of the metadata are individually optional.