S3 / Client / rename_object
rename_object¶
- S3.Client.rename_object(**kwargs)¶
Renames an existing object in a directory bucket that uses the S3 Express One Zone storage class. You can use
RenameObject
by specifying an existing object’s name as the source and the new name of the object as the destination within the same directory bucket.Note
RenameObject
is only supported for objects stored in the S3 Express One Zone storage class.To prevent overwriting an object, you can use the
If-None-Match
conditional header.If-None-Match - Renames the object only if an object with the specified name does not already exist in the directory bucket. If you don’t want to overwrite an existing object, you can add the
If-None-Match
conditional header with the value‘*’
in theRenameObject
request. Amazon S3 then returns a412 Precondition Failed
error if the object with the specified name already exists. For more information, see RFC 7232.Permissions
To grant access to the
RenameObject
operation on a directory bucket, we recommend that you use theCreateSession
operation for session-based authorization. Specifically, you grant thes3express:CreateSession
permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make theCreateSession
API call on the directory bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make anotherCreateSession
API call to generate a new session token for use. The Amazon Web Services CLI and SDKs will create and manage your session including refreshing the session token automatically to avoid service interruptions when a session expires. In your bucket policy, you can specify thes3express:SessionMode
condition key to control who can create aReadWrite
orReadOnly
session. AReadWrite
session is required for executing all the Zonal endpoint API operations, includingRenameObject
. For more information about authorization, see CreateSession. To learn more about Zonal endpoint APT operations, see Authorizing Zonal endpoint API operations with CreateSession in the Amazon S3 User Guide.HTTP Host header syntax
Directory buckets - The HTTP Host header syntax is
Bucket-name.s3express-zone-id.region-code.amazonaws.com
.See also: AWS API Documentation
Request Syntax
response = client.rename_object( Bucket='string', Key='string', RenameSource='string', DestinationIfMatch='string', DestinationIfNoneMatch='string', DestinationIfModifiedSince=datetime(2015, 1, 1), DestinationIfUnmodifiedSince=datetime(2015, 1, 1), SourceIfMatch='string', SourceIfNoneMatch='string', SourceIfModifiedSince=datetime(2015, 1, 1), SourceIfUnmodifiedSince=datetime(2015, 1, 1), ClientToken='string' )
- Parameters:
Bucket (string) –
[REQUIRED]
The bucket name of the directory bucket containing the object.
You must use virtual-hosted-style requests in the format
Bucket-name.s3express-zone-id.region-code.amazonaws.com
. Path-style requests are not supported. Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the formatbucket-base-name--zone-id--x-s3
(for example,amzn-s3-demo-bucket--usw2-az1--x-s3
). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide.Key (string) –
[REQUIRED]
Key name of the object to rename.
RenameSource (string) –
[REQUIRED]
Specifies the source for the rename operation. The value must be URL encoded.
DestinationIfMatch (string) –
Renames the object only if the ETag (entity tag) value provided during the operation matches the ETag of the object in S3. The
If-Match
header field makes the request method conditional on ETags. If the ETag values do not match, the operation returns a412 Precondition Failed
error.Expects the ETag value as a string.
DestinationIfNoneMatch (string) –
Renames the object only if the destination does not already exist in the specified directory bucket. If the object does exist when you send a request with
If-None-Match:*
, the S3 API will return a412 Precondition Failed
error, preventing an overwrite. TheIf-None-Match
header prevents overwrites of existing data by validating that there’s not an object with the same key name already in your directory bucket.Expects the
*
character (asterisk).DestinationIfModifiedSince (datetime) – Renames the object if the destination exists and if it has been modified since the specified time.
DestinationIfUnmodifiedSince (datetime) – Renames the object if it hasn’t been modified since the specified time.
SourceIfMatch (string) – Renames the object if the source exists and if its entity tag (ETag) matches the specified ETag.
SourceIfNoneMatch (string) – Renames the object if the source exists and if its entity tag (ETag) is different than the specified ETag. If an asterisk (
*
) character is provided, the operation will fail and return a412 Precondition Failed
error.SourceIfModifiedSince (datetime) – Renames the object if the source exists and if it has been modified since the specified time.
SourceIfUnmodifiedSince (datetime) – Renames the object if the source exists and hasn’t been modified since the specified time.
ClientToken (string) –
A unique string with a max of 64 ASCII characters in the ASCII range of 33 - 126.
RenameObject
supports idempotency using a client token. To make an idempotent API request usingRenameObject
, specify a client token in the request. You should not reuse the same client token for other API requests. If you retry a request that completed successfully using the same client token and the same parameters, the retry succeeds without performing any further actions. If you retry a successful request using the same client token, but one or more of the parameters are different, the retry fails and anIdempotentParameterMismatch
error is returned.This field is autopopulated if not provided.
- Return type:
dict
- Returns:
Response Syntax
{}
Response Structure
(dict) –
Exceptions