AbortMultipartUpload
This action aborts a multipart upload
After a multipart upload is aborted, no additional parts can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be freed. However, if any part uploads are currently in progress, those part uploads might or might not succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to completely free all storage consumed by all parts.
To verify that all parts have been removed, so you don't get charged for the part storage, you should call the ListParts action and ensure that the parts list is empty.
Request Syntax
URI Request Parameters
The request uses the following URI parameters.
Bucket
The bucket name to which the upload was taking place.
Required: Yes
Key
Key of the object for which the multipart upload was initiated.
Length Constraints: Minimum length of 1.
Required: Yes
uploadId
Upload ID that identifies the multipart upload.
Required: Yes
x-amz-expected-bucket-owner
The account ID of the expected bucket owner. If the bucket is owned by a different account, the request fails with the HTTP status code 403 Forbidden (access denied).
x-amz-request-payer
Confirms that the requester knows that they will be charged for the request. Bucket owners need not specify this parameter in their requests.
Valid Values: requester
Request Body
The request does not have a request body.
Response Syntax
Response Elements
If the action is successful, the service sends back an HTTP 204 response.
The response returns the following HTTP headers.
x-amz-request-charged
If present, indicates that the requester was successfully charged for the request.
Valid Values: requester
Examples
Sample Request
The following request aborts a multipart upload identified by its upload ID.
Sample Response
This example illustrates one usage of AbortMultipartUpload.
Last updated