Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

UploadPartRequest

import type { UploadPartRequest } from "https://aws-api.deno.dev/v0.4/services/s3.ts?docs=full";
interface UploadPartRequest {
Body?: Uint8Array | string | null;
Bucket: string;
ChecksumAlgorithm?: ChecksumAlgorithm | null;
ChecksumCRC32?: string | null;
ChecksumCRC32C?: string | null;
ChecksumSHA1?: string | null;
ChecksumSHA256?: string | null;
ContentLength?: number | null;
ContentMD5?: string | null;
ExpectedBucketOwner?: string | null;
Key: string;
PartNumber: number;
RequestPayer?: RequestPayer | null;
SSECustomerAlgorithm?: string | null;
SSECustomerKey?: Uint8Array | string | null;
SSECustomerKeyMD5?: string | null;
UploadId: string;
}

§Properties

§
Body?: Uint8Array | string | null
[src]

Object data.

§
Bucket: string
[src]

The name of the bucket to which the multipart upload was initiated.

When using this action with an access point, 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.

When using this action with Amazon 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 using this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts bucket ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.

§
ChecksumAlgorithm?: ChecksumAlgorithm | null
[src]

Indicates the algorithm used to create the checksum for the object when using the SDK. This header will not provide any additional functionality if not using the SDK. When sending 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.

This checksum algorithm must be the same for all parts and it match the checksum value supplied in the CreateMultipartUpload request.

§
ChecksumCRC32?: string | null
[src]

This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the base64-encoded, 32-bit CRC32 checksum of the object. For more information, see Checking object integrity in the Amazon S3 User Guide.

§
ChecksumCRC32C?: string | null
[src]

This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the base64-encoded, 32-bit CRC32C checksum of the object. For more information, see Checking object integrity in the Amazon S3 User Guide.

§
ChecksumSHA1?: string | null
[src]

This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the base64-encoded, 160-bit SHA-1 digest of the object. For more information, see Checking object integrity in the Amazon S3 User Guide.

§
ChecksumSHA256?: string | null
[src]

This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the base64-encoded, 256-bit SHA-256 digest of the object. For more information, see Checking object integrity in the Amazon S3 User Guide.

§
ContentLength?: number | null
[src]

Size of the body in bytes. This parameter is useful when the size of the body cannot be determined automatically.

§
ContentMD5?: string | null
[src]

The base64-encoded 128-bit MD5 digest of the part data. This parameter is auto-populated when using the command from the CLI. This parameter is required if object lock parameters are specified.

§
ExpectedBucketOwner?: string | null
[src]

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).

§
Key: string
[src]

Object key for which the multipart upload was initiated.

§
PartNumber: number
[src]

Part number of part being uploaded. This is a positive integer between 1 and 10,000.

§
RequestPayer?: RequestPayer | null
[src]
§
SSECustomerAlgorithm?: string | null
[src]

Specifies the algorithm to use to when encrypting the object (for example, AES256).

§
SSECustomerKey?: Uint8Array | string | null
[src]

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-encryption-customer-algorithm header. This must be the same encryption key specified in the initiate multipart upload request.

§
SSECustomerKeyMD5?: string | null
[src]

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.

§
UploadId: string
[src]

Upload ID identifying the multipart upload whose part is being uploaded.