Readonly
configOptional
options: HttpHandlerOptionsOptional
data: CheckBucketNameAvailabilityCommandOutputOptional
data: CheckBucketNameAvailabilityCommandOutputOptional
options: HttpHandlerOptionsOptional
data: CopyObjectCommandOutputOptional
data: CopyObjectCommandOutputOptional
options: HttpHandlerOptionsOptional
data: CreateBucketCommandOutputOptional
data: CreateBucketCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DeleteBucketCommandOutputOptional
data: DeleteBucketCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DeleteObjectCommandOutputOptional
data: DeleteObjectCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DeleteObjectsCommandOutputOptional
data: DeleteObjectsCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeBucketCommandOutputOptional
data: DescribeBucketCommandOutputDestroy underlying resources, like sockets. It's usually not necessary to do this. However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed. Otherwise, sockets might stay open for quite a long time before the server terminates them.
Optional
options: HttpHandlerOptionsOptional
data: GetObjectCommandOutputOptional
data: GetObjectCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListBucketsCommandOutputOptional
data: ListBucketsCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListObjectsCommandOutputOptional
data: ListObjectsCommandOutputOptional
options: HttpHandlerOptionsOptional
data: PutObjectCommandOutputOptional
data: PutObjectCommandOutputOptional
options: HttpHandlerOptionsOptional
data: UpdateBucketCommandOutputOptional
data: UpdateBucketCommandOutput
The resolved configuration of BucketsClient class. This is resolved and normalized from the constructor configuration interface.