Uploads a part by copying data from an existing object as data source.
You specify the data source by adding the request header
x-amz-copy-source in your request and a byte range by adding the
request header x-amz-copy-source-range in your request.
s3_upload_part_copy(Bucket, CopySource, CopySourceIfMatch,
CopySourceIfModifiedSince, CopySourceIfNoneMatch,
CopySourceIfUnmodifiedSince, CopySourceRange, Key, PartNumber, UploadId,
SSECustomerAlgorithm, SSECustomerKey, SSECustomerKeyMD5,
CopySourceSSECustomerAlgorithm, CopySourceSSECustomerKey,
CopySourceSSECustomerKeyMD5, RequestPayer)[required] The bucket name.
[required] The name of the source bucket and key name of the source object, separated by a slash (/). Must be URL-encoded.
Copies the object if its entity tag (ETag) matches the specified tag.
Copies the object if it has been modified since the specified time.
Copies the object if its entity tag (ETag) is different than the specified ETag.
Copies the object if it hasn\'t been modified since the specified time.
The range of bytes to copy from the source object. The range value must use the form bytes=first-last, where the first and last are the zero-based byte offsets to copy. For example, bytes=0-9 indicates that you want to copy the first 10 bytes of the source. You can copy a range only if the source object is greater than 5 MB.
[required] Object key for which the multipart upload was initiated.
[required] Part number of part being copied. This is a positive integer between 1 and 10,000.
[required] Upload ID identifying the multipart upload whose part is being copied.
Specifies the algorithm to use to when encrypting the object (for example, AES256).
Specifies the customer-provided encryption key for Amazon S3 to use in
encrypting data. This value is used to store the object and then it is
discarded; Amazon S3 does not store the encryption key. The key must be
appropriate for use with the algorithm specified in the
x-amz-server-side<U+00E2><U+20AC><U+2039>-encryption<U+00E2><U+20AC><U+2039>-customer-algorithm header. This must be
the same encryption key specified in the initiate multipart upload
request.
Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption key was transmitted without error.
Specifies the algorithm to use when decrypting the source object (for example, AES256).
Specifies the customer-provided encryption key for Amazon S3 to use to decrypt the source object. The encryption key provided in this header must be one that was used when the source object was created.
Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption key was transmitted without error.
svc$upload_part_copy(
Bucket = "string",
CopySource = "string",
CopySourceIfMatch = "string",
CopySourceIfModifiedSince = as.POSIXct(
"2015-01-01"
),
CopySourceIfNoneMatch = "string",
CopySourceIfUnmodifiedSince = as.POSIXct(
"2015-01-01"
),
CopySourceRange = "string",
Key = "string",
PartNumber = 123,
UploadId = "string",
SSECustomerAlgorithm = "string",
SSECustomerKey = raw,
SSECustomerKeyMD5 = "string",
CopySourceSSECustomerAlgorithm = "string",
CopySourceSSECustomerKey = raw,
CopySourceSSECustomerKeyMD5 = "string",
RequestPayer = "requester"
)
The minimum allowable part size for a multipart upload is 5 MB. For more information about multipart upload limits, go to Quick Facts in the Amazon Simple Storage Service Developer Guide.
Instead of using an existing object as part data, you might use the UploadPart operation and provide data in your request.
You must initiate a multipart upload before you can upload any part. In response to your initiate request. Amazon S3 returns a unique identifier, the upload ID, that you must include in your upload part request.
For more information about using the UploadPartCopy operation, see the
following:
For conceptual information about multipart uploads, see Uploading Objects Using Multipart Upload in the Amazon Simple Storage Service Developer Guide.
For information about permissions required to use the multipart upload API, see Multipart Upload API and Permissions in the Amazon Simple Storage Service Developer Guide.
For information about copying objects using a single atomic operation vs. the multipart upload, see Operations on Objects in the Amazon Simple Storage Service Developer Guide.
For information about using server-side encryption with customer-provided encryption keys with the UploadPartCopy operation, see CopyObject and UploadPart.
Note the following additional considerations about the request headers
x-amz-copy-source-if-match, x-amz-copy-source-if-none-match,
x-amz-copy-source-if-unmodified-since, and
x-amz-copy-source-if-modified-since:
Consideration 1 - If both of the x-amz-copy-source-if-match
and x-amz-copy-source-if-unmodified-since headers are present in
the request as follows:
x-amz-copy-source-if-match condition evaluates to true, and;
x-amz-copy-source-if-unmodified-since condition evaluates to
false;
Amazon S3 returns 200 OK and copies the data.
Consideration 2 - If both of the
x-amz-copy-source-if-none-match and
x-amz-copy-source-if-modified-since headers are present in the
request as follows:
x-amz-copy-source-if-none-match condition evaluates to false,
and;
x-amz-copy-source-if-modified-since condition evaluates to true;
Amazon S3 returns 412 Precondition Failed response code.
Versioning
If your bucket has versioning enabled, you could have multiple versions
of the same object. By default, x-amz-copy-source identifies the
current version of the object to copy. If the current version is a
delete marker and you don\'t specify a versionId in the
x-amz-copy-source, Amazon S3 returns a 404 error, because the object
does not exist. If you specify versionId in the x-amz-copy-source and
the versionId is a delete marker, Amazon S3 returns an HTTP 400 error,
because you are not allowed to specify a delete marker as a version for
the x-amz-copy-source.
You can optionally specify a specific version of the source object to
copy by adding the versionId subresource as shown in the following
example:
x-amz-copy-source: /bucket/object?versionId=version id
Special Errors
- *Code: NoSuchUpload*- *Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.*
- *HTTP Status Code: 404 Not Found*
- *Code: InvalidRequest*- *Cause: The specified copy source is not supported as a byte-range copy source.*
- *HTTP Status Code: 400 Bad Request*
Related Resources
CreateMultipartUpload
UploadPart
CompleteMultipartUpload
AbortMultipartUpload
ListParts
ListMultipartUploads
# NOT RUN {
# The following example uploads a part of a multipart upload by copying
# data from an existing object as data source.
svc$upload_part_copy(
Bucket = "examplebucket",
CopySource = "/bucketname/sourceobjectkey",
Key = "examplelargeobject",
PartNumber = "1",
UploadId = "exampleuoh_10OhKhT7YukE9bjzTPRiuaCotmZM_pFngJFir9OZNrSr5cWa3cq3LZSUsfjI4FI7PkP..."
)
# The following example uploads a part of a multipart upload by copying a
# specified byte range from an existing object as data source.
svc$upload_part_copy(
Bucket = "examplebucket",
CopySource = "/bucketname/sourceobjectkey",
CopySourceRange = "bytes=1-100000",
Key = "examplelargeobject",
PartNumber = "2",
UploadId = "exampleuoh_10OhKhT7YukE9bjzTPRiuaCotmZM_pFngJFir9OZNrSr5cWa3cq3LZSUsfjI4FI7PkP..."
)
# }
# NOT RUN {
# }
Run the code above in your browser using DataLab