rename_object
async
¶
rename_object(
bucket: BucketName,
key: ObjectKey,
rename_source: RenameSource,
*,
config_overrides: Optional[AsyncS3ClientConfig] = None,
destination_if_match: Optional[IfMatch] = None,
destination_if_none_match: Optional[IfNoneMatch] = None,
destination_if_modified_since: Optional[IfModifiedSince] = None,
destination_if_unmodified_since: Optional[IfUnmodifiedSince] = None,
source_if_match: Optional[RenameSourceIfMatch] = None,
source_if_none_match: Optional[RenameSourceIfNoneMatch] = None,
source_if_modified_since: Optional[RenameSourceIfModifiedSince] = None,
source_if_unmodified_since: Optional[RenameSourceIfUnmodifiedSince] = None,
client_token: Optional[ClientToken] = None,
) -> RenameObjectOutput
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.
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-Matchconditional header with the value‘*’in theRenameObjectrequest. Amazon S3 then returns a412 Precondition Failederror if the object with the specified name already exists. For more information, see RFC 7232.
- Permissions
-
To grant access to the
RenameObjectoperation on a directory bucket, we recommend that you use theCreateSessionoperation for session-based authorization. Specifically, you grant thes3express:CreateSessionpermission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make theCreateSessionAPI 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 anotherCreateSessionAPI 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:SessionModecondition key to control who can create aReadWriteorReadOnlysession. AReadWritesession is required for executing all the Zonal endpoint API operations, includingRenameObject. For more information about authorization, seeCreateSession. To learn more about Zonal endpoint API 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.
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:
-
bucket(BucketName) –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(ObjectKey) –Key name of the object to rename.
-
rename_source(RenameSource) –Specifies the source for the rename operation. The value must be URL encoded.
-
destination_if_match(Optional[IfMatch], default:None) –Renames the object only if the ETag (entity tag) value provided during the operation matches the ETag of the object in S3. The
If-Matchheader field makes the request method conditional on ETags. If the ETag values do not match, the operation returns a412 Precondition Failederror.Expects the ETag value as a string.
-
destination_if_none_match(Optional[IfNoneMatch], default:None) –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 Failederror, preventing an overwrite. TheIf-None-Matchheader 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). -
destination_if_modified_since(Optional[IfModifiedSince], default:None) –Renames the object if the destination exists and if it has been modified since the specified time.
-
destination_if_unmodified_since(Optional[IfUnmodifiedSince], default:None) –Renames the object if it hasn't been modified since the specified time.
-
source_if_match(Optional[RenameSourceIfMatch], default:None) –Renames the object if the source exists and if its entity tag (ETag) matches the specified ETag.
-
source_if_none_match(Optional[RenameSourceIfNoneMatch], default:None) –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 Failederror. -
source_if_modified_since(Optional[RenameSourceIfModifiedSince], default:None) –Renames the object if the source exists and if it has been modified since the specified time.
-
source_if_unmodified_since(Optional[RenameSourceIfUnmodifiedSince], default:None) –Renames the object if the source exists and hasn't been modified since the specified time.
-
client_token(Optional[ClientToken], default:None) –A unique string with a max of 64 ASCII characters in the ASCII range of 33 - 126.
RenameObjectsupports 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 anIdempotentParameterMismatcherror is returned.
Raises:
-
IdempotencyParameterMismatch–Parameters on this idempotent request are inconsistent with parameters used in previous request(s).
For a list of error codes and more information on Amazon S3 errors, see Error codes.
Idempotency ensures that an API request completes no more than one time. With an idempotent request, if the original request completes successfully, any subsequent retries complete successfully without performing any further actions.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_s3/_services/async_s3.py
9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 9187 9188 9189 9190 9191 9192 9193 9194 9195 9196 9197 9198 9199 9200 9201 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218 9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 9230 9231 9232 9233 9234 9235 9236 9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272 9273 | |