- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
- * General purpose bucket permissions - For
- * information about permissions required to use the multipart upload, see
- * Multipart Upload and
- * Permissions in the Amazon S3 User Guide.
+ * General purpose bucket permissions - For information
+ * about permissions required to use the multipart upload, see Multipart Upload and Permissions in
+ * the Amazon S3 User Guide.
*
Completes a multipart upload by assembling previously uploaded parts.
- *
You first initiate the multipart upload and then upload all parts using the UploadPart
- * operation or the UploadPartCopy operation.
- * After successfully uploading all relevant parts of an upload, you call this
- * CompleteMultipartUpload operation to complete the upload. Upon receiving
- * this request, Amazon S3 concatenates all the parts in ascending order by part number to create a
- * new object. In the CompleteMultipartUpload request, you must provide the parts list and
- * ensure that the parts list is complete. The CompleteMultipartUpload API operation
- * concatenates the parts that you provide in the list. For each part in the list, you must
- * provide the PartNumber value and the ETag value that are returned
- * after that part was uploaded.
- *
The processing of a CompleteMultipartUpload request could take several minutes to
- * finalize. After Amazon S3 begins processing the request, it sends an HTTP response header that
- * specifies a 200 OK response. While processing is in progress, Amazon S3
- * periodically sends white space characters to keep the connection from timing out. A request
- * could fail after the initial 200 OK response has been sent. This means that a
- * 200 OK response can contain either a success or an error. The error
- * response might be embedded in the 200 OK response. If you call this API
- * operation directly, make sure to design your application to parse the contents of the
- * response and handle it appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition.
- * The SDKs detect the embedded error and apply error handling per your configuration settings
- * (including automatically retrying the request as appropriate). If the condition persists,
- * the SDKs throw an exception (or, for the SDKs that don't use exceptions, they return an
- * error).
- *
Note that if CompleteMultipartUpload fails, applications should be prepared
- * to retry any failed requests (including 500 error responses). For more information, see
- * Amazon S3 Error
- * Best Practices.
+ *
You first initiate the multipart upload and then upload all parts using the UploadPart operation or the
+ * UploadPartCopy
+ * operation. After successfully uploading all relevant parts of an upload, you call this
+ * CompleteMultipartUpload operation to complete the upload. Upon receiving this request,
+ * Amazon S3 concatenates all the parts in ascending order by part number to create a new object. In the
+ * CompleteMultipartUpload request, you must provide the parts list and ensure that the parts list is
+ * complete. The CompleteMultipartUpload API operation concatenates the parts that you provide in the list.
+ * For each part in the list, you must provide the PartNumber value and the ETag
+ * value that are returned after that part was uploaded.
+ *
The processing of a CompleteMultipartUpload request could take several minutes to finalize. After
+ * Amazon S3 begins processing the request, it sends an HTTP response header that specifies a 200
+ * OK response. While processing is in progress, Amazon S3 periodically sends white space characters to
+ * keep the connection from timing out. A request could fail after the initial 200 OK response
+ * has been sent. This means that a 200 OK response can contain either a success or an error.
+ * The error response might be embedded in the 200 OK response. If you call this API operation
+ * directly, make sure to design your application to parse the contents of the response and handle it
+ * appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the embedded error and
+ * apply error handling per your configuration settings (including automatically retrying the request as
+ * appropriate). If the condition persists, the SDKs throw an exception (or, for the SDKs that don't use
+ * exceptions, they return an error).
+ *
Note that if CompleteMultipartUpload fails, applications should be prepared to retry
+ * any failed requests (including 500 error responses). For more information, see Amazon S3 Error Best
+ * Practices.
*
*
You can't use Content-Type: application/x-www-form-urlencoded for the
- * CompleteMultipartUpload requests. Also, if you don't provide a Content-Type
- * header, CompleteMultipartUpload can still return a 200 OK
- * response.
+ * CompleteMultipartUpload requests. Also, if you don't provide a Content-Type header,
+ * CompleteMultipartUpload can still return a 200 OK response.
*
- *
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
- * General purpose bucket permissions - For
- * information about permissions required to use the multipart upload API, see
- * Multipart Upload and
- * Permissions in the Amazon S3 User Guide.
- *
If you provide an additional checksum
- * value in your MultipartUpload requests and the
- * object is encrypted with Key Management Service, you must have permission to use the
- * kms:Decrypt action for the
- * CompleteMultipartUpload request to succeed.
+ * General purpose bucket permissions - For information
+ * about permissions required to use the multipart upload API, see Multipart Upload and Permissions in
+ * the Amazon S3 User Guide.
+ *
If you provide an additional checksum value in your MultipartUpload requests and the
+ * object is encrypted with Key Management Service, you must have permission to use the
+ * kms:Decrypt action for the CompleteMultipartUpload request to
+ * succeed.
If the object is encrypted with SSE-KMS, you must also have the
- * kms:GenerateDataKey and kms:Decrypt permissions
- * in IAM identity-based policies and KMS key policies for the KMS
- * key.
+ * kms:GenerateDataKey and kms:Decrypt permissions in IAM
+ * identity-based policies and KMS key policies for the KMS key.
*
Description: Your proposed upload is smaller than the minimum
- * allowed object size. Each part must be at least 5 MB in size, except
- * the last part.
+ *
Description: Your proposed upload is smaller than the minimum allowed object size.
+ * Each part must be at least 5 MB in size, except the last part.
Description: One or more of the specified parts could not be found.
- * The part might not have been uploaded, or the specified ETag might not
- * have matched the uploaded part's ETag.
+ *
Description: One or more of the specified parts could not be found. The part might not
+ * have been uploaded, or the specified ETag might not have matched the uploaded part's
+ * ETag.
Description: The specified multipart upload does not exist. The
- * upload ID might be invalid, or the multipart upload might have been
- * aborted or completed.
+ *
Description: The specified multipart upload does not exist. The upload ID might be
+ * invalid, or the multipart upload might have been aborted or completed.
Creates a copy of an object that is already stored in Amazon S3.
*
- *
You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your
- * object up to 5 GB in size in a single atomic action using this API. However, to copy an
- * object greater than 5 GB, you must use the multipart upload Upload Part - Copy
- * (UploadPartCopy) API. For more information, see Copy Object Using the
- * REST Multipart Upload API.
+ *
You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your object up to 5
+ * GB in size in a single atomic action using this API. However, to copy an object greater than 5 GB, you
+ * must use the multipart upload Upload Part - Copy (UploadPartCopy) API. For more information, see
+ * Copy Object
+ * Using the REST Multipart Upload API.
*
- *
You can copy individual objects between general purpose buckets, between directory buckets,
- * and between general purpose buckets and directory buckets.
+ *
You can copy individual objects between general purpose buckets, between directory buckets, and between
+ * general purpose buckets and directory buckets.
*
*
*
- *
Amazon S3 supports copy operations using Multi-Region Access Points only as a
- * destination when using the Multi-Region Access Point ARN.
+ *
Amazon S3 supports copy operations using Multi-Region Access Points only as a destination when
+ * using the Multi-Region Access Point ARN.
*
*
*
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
*
*
- *
VPC endpoints don't support cross-Region requests (including copies). If you're
- * using VPC endpoints, your source and destination buckets should be in the same
- * Amazon Web Services Region as your VPC endpoint.
+ *
VPC endpoints don't support cross-Region requests (including copies). If you're using VPC
+ * endpoints, your source and destination buckets should be in the same Amazon Web Services Region as your VPC
+ * endpoint.
*
*
*
- *
Both the Region that you want to copy the object from and the Region that you want to
- * copy the object to must be enabled for your account. For more information about how to
- * enable a Region for your account, see Enable or disable a Region for standalone accounts in the Amazon Web Services
- * Account Management Guide.
+ *
Both the Region that you want to copy the object from and the Region that you want to copy the
+ * object to must be enabled for your account. For more information about how to enable a Region for your
+ * account, see Enable
+ * or disable a Region for standalone accounts in the Amazon Web Services Account Management
+ * Guide.
*
- *
Amazon S3 transfer acceleration does not support cross-Region copies. If you request a
- * cross-Region copy using a transfer acceleration endpoint, you get a 400 Bad
- * Request error. For more information, see Transfer
- * Acceleration.
+ *
Amazon S3 transfer acceleration does not support cross-Region copies. If you request a cross-Region
+ * copy using a transfer acceleration endpoint, you get a 400 Bad Request error. For more
+ * information, see Transfer Acceleration.
*
*
*
Authentication and authorization
*
- *
All CopyObject requests must be authenticated and signed by using
- * IAM credentials (access key ID and secret access key for the IAM identities).
- * All headers with the x-amz- prefix, including
- * x-amz-copy-source, must be signed. For more information, see
- * REST Authentication.
+ *
All CopyObject requests must be authenticated and signed by using IAM
+ * credentials (access key ID and secret access key for the IAM identities). All headers with the
+ * x-amz- prefix, including x-amz-copy-source, must be signed. For more
+ * information, see REST Authentication.
*
- * Directory buckets - You must use the
- * IAM credentials to authenticate and authorize your access to the
- * CopyObject API operation, instead of using the temporary security
- * credentials through the CreateSession API operation.
- *
Amazon Web Services CLI or SDKs handles authentication and authorization on your
- * behalf.
+ * Directory buckets - You must use the IAM
+ * credentials to authenticate and authorize your access to the CopyObject API
+ * operation, instead of using the temporary security credentials through the
+ * CreateSession API operation.
+ *
Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.
*
*
Permissions
*
*
You must have read access to the source object and
- * write access to the destination bucket.
+ * write access to the destination bucket.
*
*
*
- * General purpose bucket permissions - You
- * must have permissions in an IAM policy based on the source and destination
- * bucket types in a CopyObject operation.
+ * General purpose bucket permissions - You must have
+ * permissions in an IAM policy based on the source and destination bucket types in a
+ * CopyObject operation.
*
*
- *
If the source object is in a general purpose bucket, you must have
- *
+ *
If the source object is in a general purpose bucket, you must have
* s3:GetObject
- *
- * permission to read the source object that is being copied.
+ * permission to read the source object that is
+ * being copied.
*
*
- *
If the destination bucket is a general purpose bucket, you must have
- *
+ *
If the destination bucket is a general purpose bucket, you must have
* s3:PutObject
- *
- * permission to write the object copy to the destination bucket.
+ * permission to write the object copy to the
+ * destination bucket.
*
*
*
*
*
- * Directory bucket permissions -
- * You must have permissions in a bucket policy or an IAM identity-based policy based on the
- * source and destination bucket types in a CopyObject
- * operation.
+ * Directory bucket permissions - You must have
+ * permissions in a bucket policy or an IAM identity-based policy based on the source and destination bucket types
+ * in a CopyObject operation.
*
*
- *
If the source object that you want to copy is in a
- * directory bucket, you must have the
+ *
If the source object that you want to copy is in a directory bucket, you must have
+ * the
* s3express:CreateSession
* permission in
- * the Action element of a policy to read the object. By
- * default, the session is in the ReadWrite mode. If you
- * want to restrict the access, you can explicitly set the
- * s3express:SessionMode condition key to
- * ReadOnly on the copy source bucket.
+ * the Action element of a policy to read the object. By default, the session is
+ * in the ReadWrite mode. If you want to restrict the access, you can explicitly
+ * set the s3express:SessionMode condition key to ReadOnly on the
+ * copy source bucket.
*
*
- *
If the copy destination is a directory bucket, you must have the
- *
+ *
If the copy destination is a directory bucket, you must have the
* s3express:CreateSession
* permission in the
- * Action element of a policy to write the object to the
- * destination. The s3express:SessionMode condition key
- * can't be set to ReadOnly on the copy destination bucket.
- *
+ * Action element of a policy to write the object to the destination. The
+ * s3express:SessionMode condition key can't be set to ReadOnly
+ * on the copy destination bucket.
*
*
*
If the object is encrypted with SSE-KMS, you must also have the
- * kms:GenerateDataKey and kms:Decrypt permissions
- * in IAM identity-based policies and KMS key policies for the KMS
- * key.
When the request is an HTTP 1.1 request, the response is chunk encoded. When
- * the request is not an HTTP 1.1 request, the response would not contain the
- * Content-Length. You always need to read the entire response body
- * to check if the copy succeeds.
+ *
When the request is an HTTP 1.1 request, the response is chunk encoded. When the request is
+ * not an HTTP 1.1 request, the response would not contain the Content-Length. You
+ * always need to read the entire response body to check if the copy succeeds.
*
*
- *
If the copy is successful, you receive a response with information about
- * the copied object.
+ *
If the copy is successful, you receive a response with information about the copied
+ * object.
*
*
- *
A copy request might return an error when Amazon S3 receives the copy request
- * or while Amazon S3 is copying the files. A 200 OK response can
- * contain either a success or an error.
+ *
A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3 is
+ * copying the files. A 200 OK response can contain either a success or an
+ * error.
*
*
- *
If the error occurs before the copy action starts, you receive a
- * standard Amazon S3 error.
+ *
If the error occurs before the copy action starts, you receive a standard Amazon S3
+ * error.
*
*
- *
If the error occurs during the copy operation, the error response
- * is embedded in the 200 OK response. For example, in a
- * cross-region copy, you may encounter throttling and receive a
- * 200 OK response. For more information, see Resolve the Error 200 response when copying objects to
- * Amazon S3. The 200 OK status code means the copy
- * was accepted, but it doesn't mean the copy is complete. Another
- * example is when you disconnect from Amazon S3 before the copy is complete,
- * Amazon S3 might cancel the copy and you may receive a 200 OK
- * response. You must stay connected to Amazon S3 until the entire response is
- * successfully received and processed.
- *
If you call this API operation directly, make sure to design your
- * application to parse the content of the response and handle it
- * appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The
- * SDKs detect the embedded error and apply error handling per your
- * configuration settings (including automatically retrying the request
- * as appropriate). If the condition persists, the SDKs throw an
- * exception (or, for the SDKs that don't use exceptions, they return an
- * error).
+ *
If the error occurs during the copy operation, the error response is embedded in the
+ * 200 OK response. For example, in a cross-region copy, you may encounter
+ * throttling and receive a 200 OK response. For more information, see Resolve the Error
+ * 200 response when copying objects to Amazon S3. The 200 OK status code
+ * means the copy was accepted, but it doesn't mean the copy is complete. Another example is
+ * when you disconnect from Amazon S3 before the copy is complete, Amazon S3 might cancel the copy and
+ * you may receive a 200 OK response. You must stay connected to Amazon S3 until the
+ * entire response is successfully received and processed.
+ *
If you call this API operation directly, make sure to design your application to parse
+ * the content of the response and handle it appropriately. If you use Amazon Web Services SDKs, SDKs
+ * handle this condition. The SDKs detect the embedded error and apply error handling per
+ * your configuration settings (including automatically retrying the request as appropriate).
+ * If the condition persists, the SDKs throw an exception (or, for the SDKs that don't use
+ * exceptions, they return an error).
The copy request charge is based on the storage class and Region that you
- * specify for the destination object. The request can also result in a data
- * retrieval charge for the source if the source storage class bills for data
- * retrieval. If the copy source is in a different region, the data transfer is
- * billed to the copy source account. For pricing information, see Amazon S3 pricing.
+ *
The copy request charge is based on the storage class and Region that you specify for the
+ * destination object. The request can also result in a data retrieval charge for the source if the
+ * source storage class bills for data retrieval. If the copy source is in a different region, the
+ * data transfer is billed to the copy source account. For pricing information, see Amazon S3 pricing.
- * Amazon S3 on Outposts - When you use this action with S3 on Outposts through the REST API, 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. The hostname isn't required when you use the Amazon Web Services CLI or SDKs.
+ * Amazon S3 on Outposts - When you use this action with
+ * S3 on Outposts through the REST API, 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.
+ * The hostname isn't required when you use the Amazon Web Services CLI or SDKs.
*
Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a valid Amazon Web Services
- * Access Key ID to authenticate requests. Anonymous requests are never allowed to create
- * buckets. By creating the bucket, you become the bucket owner.
Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a valid Amazon Web Services Access Key
+ * ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the
+ * bucket, you become the bucket owner.
* General purpose buckets - If you send your
- * CreateBucket request to the s3.amazonaws.com global
- * endpoint, the request goes to the us-east-1 Region. So the signature
- * calculations in Signature Version 4 must use us-east-1 as the Region,
- * even if the location constraint in the request specifies another Region where the
- * bucket is to be created. If you create a bucket in a Region other than US East (N.
- * Virginia), your application must be able to handle 307 redirect. For more
- * information, see Virtual hosting of
- * buckets in the Amazon S3 User Guide.
+ * CreateBucket request to the s3.amazonaws.com global endpoint, the
+ * request goes to the us-east-1 Region. So the signature calculations in Signature
+ * Version 4 must use us-east-1 as the Region, even if the location constraint in the
+ * request specifies another Region where the bucket is to be created. If you create a bucket in a
+ * Region other than US East (N. Virginia), your application must be able to handle 307 redirect. For
+ * more information, see Virtual hosting of buckets in the Amazon S3 User Guide.
*
- * General purpose bucket permissions - In
- * addition to the s3:CreateBucket permission, the following
- * permissions are required in a policy when your CreateBucket
- * request includes specific headers:
+ * General purpose bucket permissions - In addition to the
+ * s3:CreateBucket permission, the following permissions are required in a policy
+ * when your CreateBucket request includes specific headers:
*
*
*
- * Access control lists (ACLs)
- * - In your CreateBucket request, if you specify an
- * access control list (ACL) and set it to public-read,
- * public-read-write, authenticated-read, or
- * if you explicitly specify any other custom ACLs, both
- * s3:CreateBucket and s3:PutBucketAcl
- * permissions are required. In your CreateBucket request,
- * if you set the ACL to private, or if you don't specify
- * any ACLs, only the s3:CreateBucket permission is
- * required.
+ * Access control lists (ACLs) - In your
+ * CreateBucket request, if you specify an access control list (ACL) and set
+ * it to public-read, public-read-write,
+ * authenticated-read, or if you explicitly specify any other custom ACLs,
+ * both s3:CreateBucket and s3:PutBucketAcl permissions are
+ * required. In your CreateBucket request, if you set the ACL to
+ * private, or if you don't specify any ACLs, only the
+ * s3:CreateBucket permission is required.
*
*
*
* Object Lock - In your
- * CreateBucket request, if you set
- * x-amz-bucket-object-lock-enabled to true, the
- * s3:PutBucketObjectLockConfiguration and
- * s3:PutBucketVersioning permissions are
- * required.
+ * CreateBucket request, if you set
+ * x-amz-bucket-object-lock-enabled to true, the
+ * s3:PutBucketObjectLockConfiguration and s3:PutBucketVersioning
+ * permissions are required.
*
*
*
- * S3 Object Ownership - If
- * your CreateBucket request includes the
- * x-amz-object-ownership header, then the
- * s3:PutBucketOwnershipControls permission is
- * required.
+ * S3 Object Ownership - If your
+ * CreateBucket request includes the x-amz-object-ownership
+ * header, then the s3:PutBucketOwnershipControls permission is required.
*
- *
To set an ACL on a bucket as part of a
- * CreateBucket request, you must explicitly set S3
- * Object Ownership for the bucket to a different value than the
- * default, BucketOwnerEnforced. Additionally, if your
- * desired bucket ACL grants public access, you must first create the
- * bucket (without the bucket ACL) and then explicitly disable Block
- * Public Access on the bucket before using PutBucketAcl
- * to set the ACL. If you try to create a bucket with a public ACL,
- * the request will fail.
To set an ACL on a bucket as part of a CreateBucket request, you must
+ * explicitly set S3 Object Ownership for the bucket to a different value than the default,
+ * BucketOwnerEnforced. Additionally, if your desired bucket ACL grants
+ * public access, you must first create the bucket (without the bucket ACL) and then
+ * explicitly disable Block Public Access on the bucket before using
+ * PutBucketAcl to set the ACL. If you try to create a bucket with a public
+ * ACL, the request will fail.
- * Directory bucket permissions -
- * You must have the s3express:CreateBucket permission in
- * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ * Directory bucket permissions - You must have the
+ * s3express:CreateBucket permission in an IAM identity-based policy instead of a bucket policy.
+ * Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource. For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
*
- *
The permissions for ACLs, Object Lock, S3 Object Ownership, and S3
- * Block Public Access are not supported for directory buckets. For
- * directory buckets, all Block Public Access settings are enabled at the
- * bucket level and S3 Object Ownership is set to Bucket owner enforced
- * (ACLs disabled). These settings can't be modified.
- *
For more information about permissions for creating and working with
- * directory buckets, see Directory buckets in the
- * Amazon S3 User Guide. For more information about
- * supported S3 features for directory buckets, see Features of S3 Express One Zone in the
- * Amazon S3 User Guide.
+ *
The permissions for ACLs, Object Lock, S3 Object Ownership, and S3 Block Public Access
+ * are not supported for directory buckets. For directory buckets, all Block Public Access
+ * settings are enabled at the bucket level and S3 Object Ownership is set to Bucket owner
+ * enforced (ACLs disabled). These settings can't be modified.
+ *
For more information about permissions for creating and working with directory buckets,
+ * see Directory buckets
+ * in the Amazon S3 User Guide. For more information about supported S3
+ * features for directory buckets, see Features of
+ * S3 Express One Zone in the Amazon S3 User Guide.
The bucket you tried to create already exists, and you own it. Amazon S3 returns this error
- * in all Amazon Web Services Regions except in the North Virginia Region. For legacy compatibility, if you
- * re-create an existing bucket that you already own in the North Virginia Region, Amazon S3
- * returns 200 OK and resets the bucket access control lists (ACLs).
+ *
The bucket you tried to create already exists, and you own it. Amazon S3 returns this error in all Amazon Web Services
+ * Regions except in the North Virginia Region. For legacy compatibility, if you re-create an existing
+ * bucket that you already own in the North Virginia Region, Amazon S3 returns 200 OK and resets the bucket
+ * access control lists (ACLs).
*
* @throws {@link S3ServiceException}
*
Base exception class for all service exceptions from S3 service.
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateBucketMetadataConfigurationCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateBucketMetadataConfigurationCommand.d.ts
new file mode 100644
index 00000000..b061898c
--- /dev/null
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateBucketMetadataConfigurationCommand.d.ts
@@ -0,0 +1,182 @@
+import { Command as $Command } from "@smithy/smithy-client";
+import { MetadataBearer as __MetadataBearer } from "@smithy/types";
+import { CreateBucketMetadataConfigurationRequest } from "../models/models_0";
+import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
+/**
+ * @public
+ */
+export type { __MetadataBearer };
+export { $Command };
+/**
+ * @public
+ *
+ * The input for {@link CreateBucketMetadataConfigurationCommand}.
+ */
+export interface CreateBucketMetadataConfigurationCommandInput extends CreateBucketMetadataConfigurationRequest {
+}
+/**
+ * @public
+ *
+ * The output of {@link CreateBucketMetadataConfigurationCommand}.
+ */
+export interface CreateBucketMetadataConfigurationCommandOutput extends __MetadataBearer {
+}
+declare const CreateBucketMetadataConfigurationCommand_base: {
+ new (input: CreateBucketMetadataConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl;
+ new (input: CreateBucketMetadataConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl;
+ getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+};
+/**
+ *
If you want to encrypt your metadata tables with server-side encryption with Key Management Service
+ * (KMS) keys (SSE-KMS), you need additional permissions in your KMS key policy. For more
+ * information, see
+ * Setting up permissions for configuring metadata tables in the
+ * Amazon S3 User Guide.
+ * We recommend that you create your S3 Metadata configurations by using the V2
+ * CreateBucketMetadataConfiguration API operation. We no longer recommend using the V1
+ * CreateBucketMetadataTableConfiguration API operation.
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
If you also want to integrate your table bucket with Amazon Web Services analytics services so that you
- * can query your metadata table, you need additional permissions. For more information, see
- *
- * Integrating Amazon S3 Tables with Amazon Web Services analytics services in the
- * Amazon S3 User Guide.
If you want to encrypt your metadata tables with server-side encryption with Key Management Service
+ * (KMS) keys (SSE-KMS), you need additional permissions. For more
+ * information, see
+ * Setting up permissions for configuring metadata tables in the
+ * Amazon S3 User Guide.
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region,
* Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (São Paulo) Region.
*
- *
This action initiates a multipart upload and returns an upload ID. This upload ID is
- * used to associate all of the parts in the specific multipart upload. You specify this
- * upload ID in each of your subsequent upload part requests (see UploadPart). You also include this
- * upload ID in the final request to either complete or abort the multipart upload request.
- * For more information about multipart uploads, see Multipart Upload Overview in the
- * Amazon S3 User Guide.
+ *
This action initiates a multipart upload and returns an upload ID. This upload ID is used to
+ * associate all of the parts in the specific multipart upload. You specify this upload ID in each of your
+ * subsequent upload part requests (see UploadPart). You also include this upload ID in
+ * the final request to either complete or abort the multipart upload request. For more information about
+ * multipart uploads, see Multipart
+ * Upload Overview in the Amazon S3 User Guide.
*
- *
After you initiate a multipart upload and upload one or more parts, to stop being
- * charged for storing the uploaded parts, you must either complete or abort the multipart
- * upload. Amazon S3 frees up the space used to store the parts and stops charging you for
- * storing them only after you either complete or abort a multipart upload.
+ *
After you initiate a multipart upload and upload one or more parts, to stop being charged for
+ * storing the uploaded parts, you must either complete or abort the multipart upload. Amazon S3 frees up the
+ * space used to store the parts and stops charging you for storing them only after you either complete
+ * or abort a multipart upload.
*
- *
If you have configured a lifecycle rule to abort incomplete multipart uploads, the
- * created multipart upload must be completed within the number of days specified in the
- * bucket lifecycle configuration. Otherwise, the incomplete multipart upload becomes eligible
- * for an abort action and Amazon S3 aborts the multipart upload. For more information, see Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle
- * Configuration.
+ *
If you have configured a lifecycle rule to abort incomplete multipart uploads, the created multipart
+ * upload must be completed within the number of days specified in the bucket lifecycle configuration.
+ * Otherwise, the incomplete multipart upload becomes eligible for an abort action and Amazon S3 aborts the
+ * multipart upload. For more information, see Aborting
+ * Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration.
*
*
*
*
* Directory buckets -
- * S3 Lifecycle is not supported by directory buckets.
+ * S3 Lifecycle is not supported by directory buckets.
*
*
*
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
For request signing, multipart upload is just a series of regular requests. You
- * initiate a multipart upload, send one or more requests to upload parts, and then
- * complete the multipart upload process. You sign each request individually. There
- * is nothing special about signing multipart upload requests. For more information
- * about signing, see Authenticating
- * Requests (Amazon Web Services Signature Version 4) in the
- * Amazon S3 User Guide.
+ *
For request signing, multipart upload is just a series of regular requests. You initiate a
+ * multipart upload, send one or more requests to upload parts, and then complete the multipart
+ * upload process. You sign each request individually. There is nothing special about signing
+ * multipart upload requests. For more information about signing, see Authenticating Requests (Amazon Web Services
+ * Signature Version 4) in the Amazon S3 User Guide.
*
*
Permissions
*
*
*
*
- * General purpose bucket permissions - To
- * perform a multipart upload with encryption using an Key Management Service (KMS)
- * KMS key, the requester must have permission to the
- * kms:Decrypt and kms:GenerateDataKey actions on
- * the key. The requester must also have permissions for the
- * kms:GenerateDataKey action for the
- * CreateMultipartUpload API. Then, the requester needs
- * permissions for the kms:Decrypt action on the
- * UploadPart and UploadPartCopy APIs. These
- * permissions are required because Amazon S3 must decrypt and read data from the
- * encrypted file parts before it completes the multipart upload. For more
- * information, see Multipart upload API and permissions and Protecting data
- * using server-side encryption with Amazon Web Services KMS in the
- * Amazon S3 User Guide.
+ * General purpose bucket permissions - To perform a
+ * multipart upload with encryption using an Key Management Service (KMS) KMS key, the requester must have
+ * permission to the kms:Decrypt and kms:GenerateDataKey actions on the
+ * key. The requester must also have permissions for the kms:GenerateDataKey action
+ * for the CreateMultipartUpload API. Then, the requester needs permissions for the
+ * kms:Decrypt action on the UploadPart and
+ * UploadPartCopy APIs. These permissions are required because Amazon S3 must decrypt
+ * and read data from the encrypted file parts before it completes the multipart upload. For more
+ * information, see Multipart upload API and
+ * permissions and Protecting data using server-side
+ * encryption with Amazon Web Services KMS in the Amazon S3 User Guide.
*
- * General purpose buckets - Server-side
- * encryption is for data encryption at rest. Amazon S3 encrypts your data as it
- * writes it to disks in its data centers and decrypts it when you access it.
- * Amazon S3 automatically encrypts all new objects that are uploaded to an S3
- * bucket. When doing a multipart upload, if you don't specify encryption
- * information in your request, the encryption setting of the uploaded parts is
- * set to the default encryption configuration of the destination bucket. By
- * default, all buckets have a base level of encryption configuration that uses
- * server-side encryption with Amazon S3 managed keys (SSE-S3). If the destination
- * bucket has a default encryption configuration that uses server-side
- * encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided
- * encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a
- * customer-provided key to encrypt the uploaded parts. When you perform a
- * CreateMultipartUpload operation, if you want to use a different type of
- * encryption setting for the uploaded parts, you can request that Amazon S3
- * encrypts the object with a different encryption key (such as an Amazon S3 managed
- * key, a KMS key, or a customer-provided key). When the encryption setting
- * in your request is different from the default encryption configuration of
- * the destination bucket, the encryption setting in your request takes
- * precedence. If you choose to provide your own encryption key, the request
- * headers you provide in UploadPart and
- * UploadPartCopy
- * requests must match the headers you used in the
- * CreateMultipartUpload request.
+ * General purpose buckets - Server-side encryption is for
+ * data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers
+ * and decrypts it when you access it. Amazon S3 automatically encrypts all new objects that are
+ * uploaded to an S3 bucket. When doing a multipart upload, if you don't specify encryption
+ * information in your request, the encryption setting of the uploaded parts is set to the
+ * default encryption configuration of the destination bucket. By default, all buckets have a
+ * base level of encryption configuration that uses server-side encryption with Amazon S3 managed keys
+ * (SSE-S3). If the destination bucket has a default encryption configuration that uses
+ * server-side encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided
+ * encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a customer-provided key to
+ * encrypt the uploaded parts. When you perform a CreateMultipartUpload operation, if you want to
+ * use a different type of encryption setting for the uploaded parts, you can request that Amazon S3
+ * encrypts the object with a different encryption key (such as an Amazon S3 managed key, a KMS key,
+ * or a customer-provided key). When the encryption setting in your request is different from the
+ * default encryption configuration of the destination bucket, the encryption setting in your
+ * request takes precedence. If you choose to provide your own encryption key, the request
+ * headers you provide in UploadPart and UploadPartCopy requests must match the headers you used in the
+ * CreateMultipartUpload request.
*
*
- *
Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key
- * (aws/s3) and KMS customer managed keys stored in Key Management Service
- * (KMS) – If you want Amazon Web Services to manage the keys used to encrypt data,
- * specify the following headers in the request.
+ *
Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key (aws/s3) and
+ * KMS customer managed keys stored in Key Management Service (KMS) – If you want Amazon Web Services to manage the keys used
+ * to encrypt data, specify the following headers in the request.
If you specify
- * x-amz-server-side-encryption:aws:kms, but
- * don't provide
- * x-amz-server-side-encryption-aws-kms-key-id,
- * Amazon S3 uses the Amazon Web Services managed key (aws/s3 key) in
- * KMS to protect the data.
+ *
If you specify x-amz-server-side-encryption:aws:kms, but don't
+ * provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the
+ * Amazon Web Services managed key (aws/s3 key) in KMS to protect the data.
*
*
- *
To perform a multipart upload with encryption by using an
- * Amazon Web Services KMS key, the requester must have permission to the
- * kms:Decrypt and
- * kms:GenerateDataKey* actions on the key.
- * These permissions are required because Amazon S3 must decrypt and
- * read data from the encrypted file parts before it completes
- * the multipart upload. For more information, see Multipart upload API and permissions and Protecting data using server-side encryption with Amazon Web Services
- * KMS in the
- * Amazon S3 User Guide.
+ *
To perform a multipart upload with encryption by using an Amazon Web Services KMS key, the
+ * requester must have permission to the kms:Decrypt and
+ * kms:GenerateDataKey* actions on the key. These permissions are
+ * required because Amazon S3 must decrypt and read data from the encrypted file parts
+ * before it completes the multipart upload. For more information, see Multipart
+ * upload API and permissions and Protecting data using
+ * server-side encryption with Amazon Web Services KMS in the
+ * Amazon S3 User Guide.
*
*
- *
If your Identity and Access Management (IAM) user or role is in the same
- * Amazon Web Services account as the KMS key, then you must have these
- * permissions on the key policy. If your IAM user or role is
- * in a different account from the key, then you must have the
- * permissions on both the key policy and your IAM user or
- * role.
+ *
If your Identity and Access Management (IAM) user or role is in the same Amazon Web Services account as the
+ * KMS key, then you must have these permissions on the key policy. If your IAM
+ * user or role is in a different account from the key, then you must have the
+ * permissions on both the key policy and your IAM user or role.
*
*
- *
All GET and PUT requests for an
- * object protected by KMS fail if you don't make them by
- * using Secure Sockets Layer (SSL), Transport Layer Security
- * (TLS), or Signature Version 4. For information about
- * configuring any of the officially supported Amazon Web Services SDKs and
- * Amazon Web Services CLI, see Specifying the Signature Version in
- * Request Authentication in the
- * Amazon S3 User Guide.
+ *
All GET and PUT requests for an object protected by
+ * KMS fail if you don't make them by using Secure Sockets Layer (SSL), Transport
+ * Layer Security (TLS), or Signature Version 4. For information about configuring any
+ * of the officially supported Amazon Web Services SDKs and Amazon Web Services CLI, see Specifying the Signature Version in Request
+ * Authentication in the Amazon S3 User Guide.
Use customer-provided encryption keys (SSE-C) – If you want to
- * manage your own encryption keys, provide all the following headers in
- * the request.
+ *
Use customer-provided encryption keys (SSE-C) – If you want to manage your own
+ * encryption keys, provide all the following headers in the request.
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+ * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
* CreateSession requests or PUT object requests. Then, new objects
* are automatically encrypted with the desired encryption settings. For more
* information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
For directory buckets, when you perform a
- * CreateMultipartUpload operation and an
- * UploadPartCopy operation, the request headers you provide
- * in the CreateMultipartUpload request must match the default
- * encryption configuration of the destination bucket.
+ *
For directory buckets, when you perform a CreateMultipartUpload operation
+ * and an UploadPartCopy operation, the request headers you provide in the
+ * CreateMultipartUpload request must match the default encryption configuration
+ * of the destination bucket.
Creates a session that establishes temporary security credentials to support fast
- * authentication and authorization for the Zonal endpoint API operations on directory buckets. For more
- * information about Zonal endpoint API operations that include the Availability Zone in the request endpoint, see S3 Express One Zone
- * APIs in the Amazon S3 User Guide.
- *
To make Zonal endpoint API requests on a directory bucket, use the CreateSession
- * API operation. Specifically, you grant s3express:CreateSession permission to a
- * bucket in a bucket policy or an IAM identity-based policy. Then, you use IAM credentials to make the
- * CreateSession API request on the bucket, which returns temporary security
- * credentials that include the access key ID, secret access key, session token, and
- * expiration. These credentials have associated permissions to access the Zonal endpoint API operations. After
- * the session is created, you don’t need to use other policies to grant permissions to each
- * Zonal endpoint API individually. Instead, in your Zonal endpoint API requests, you sign your requests by
- * applying the temporary security credentials of the session to the request headers and
- * following the SigV4 protocol for authentication. You also apply the session token to the
- * x-amz-s3session-token request header for authorization. Temporary security
- * credentials are scoped to the bucket and expire after 5 minutes. After the expiration time,
- * any calls that you make with those credentials will fail. You must use IAM credentials
- * again to make a CreateSession API request that generates a new set of
- * temporary credentials for use. Temporary credentials cannot be extended or refreshed beyond
- * the original specified interval.
- *
If you use Amazon Web Services SDKs, SDKs handle the session token refreshes automatically to avoid
- * service interruptions when a session expires. We recommend that you use the Amazon Web Services SDKs to
- * initiate and manage requests to the CreateSession API. For more information, see Performance guidelines and design patterns in the
- * Amazon S3 User Guide.
+ *
Creates a session that establishes temporary security credentials to support fast authentication and
+ * authorization for the Zonal endpoint API operations on directory buckets. For more information about Zonal endpoint API operations that
+ * include the Availability Zone in the request endpoint, see S3 Express One Zone APIs in the
+ * Amazon S3 User Guide.
+ *
To make Zonal endpoint API requests on a directory bucket, use the CreateSession API
+ * operation. Specifically, you grant s3express:CreateSession permission to a bucket in
+ * a bucket policy or an IAM identity-based policy. Then, you use IAM credentials to make the CreateSession
+ * API request on the bucket, which returns temporary security credentials that include the access key ID,
+ * secret access key, session token, and expiration. These credentials have associated permissions to
+ * access the Zonal endpoint API operations. After the session is created, you don’t need to use other policies to grant
+ * permissions to each Zonal endpoint API individually. Instead, in your Zonal endpoint API requests, you sign your
+ * requests by applying the temporary security credentials of the session to the request headers and
+ * following the SigV4 protocol for authentication. You also apply the session token to the
+ * x-amz-s3session-token request header for authorization. Temporary security credentials
+ * are scoped to the bucket and expire after 5 minutes. After the expiration time, any calls that you make
+ * with those credentials will fail. You must use IAM credentials again to make a
+ * CreateSession API request that generates a new set of temporary credentials for use.
+ * Temporary credentials cannot be extended or refreshed beyond the original specified interval.
+ *
If you use Amazon Web Services SDKs, SDKs handle the session token refreshes automatically to avoid service
+ * interruptions when a session expires. We recommend that you use the Amazon Web Services SDKs to initiate and manage
+ * requests to the CreateSession API. For more information, see Performance guidelines and design patterns in the
+ * Amazon S3 User Guide.
*
- * CopyObject API operation -
- * Unlike other Zonal endpoint API operations, the CopyObject API operation doesn't use
- * the temporary security credentials returned from the CreateSession
- * API operation for authentication and authorization. For information about
- * authentication and authorization of the CopyObject API operation on
- * directory buckets, see CopyObject.
+ * CopyObject API operation - Unlike other
+ * Zonal endpoint API operations, the CopyObject API operation doesn't use the temporary security
+ * credentials returned from the CreateSession API operation for authentication and
+ * authorization. For information about authentication and authorization of the
+ * CopyObject API operation on directory buckets, see CopyObject.
*
*
*
*
- * HeadBucket API operation -
- * Unlike other Zonal endpoint API operations, the HeadBucket API operation doesn't use
- * the temporary security credentials returned from the CreateSession
- * API operation for authentication and authorization. For information about
- * authentication and authorization of the HeadBucket API operation on
- * directory buckets, see HeadBucket.
+ * HeadBucket API operation - Unlike other
+ * Zonal endpoint API operations, the HeadBucket API operation doesn't use the temporary security
+ * credentials returned from the CreateSession API operation for authentication and
+ * authorization. For information about authentication and authorization of the
+ * HeadBucket API operation on directory buckets, see HeadBucket.
*
*
*
*
*
Permissions
*
- *
To obtain temporary security credentials, you must create
- * a bucket policy or an IAM identity-based policy that grants s3express:CreateSession
- * permission to the bucket. In a policy, you can have the
- * s3express:SessionMode condition key to control who can create a
- * ReadWrite or ReadOnly session. For more information
- * about ReadWrite or ReadOnly sessions, see
+ *
To grant cross-account access to Zonal endpoint API operations, the bucket policy should also
- * grant both accounts the s3express:CreateSession permission.
To grant cross-account access to Zonal endpoint API operations, the bucket policy should also grant both
+ * accounts the s3express:CreateSession permission.
*
If you want to encrypt objects with SSE-KMS, you must also have the
- * kms:GenerateDataKey and the kms:Decrypt permissions
- * in IAM identity-based policies and KMS key policies for the target KMS
- * key.
+ * kms:GenerateDataKey and the kms:Decrypt permissions in IAM
+ * identity-based policies and KMS key policies for the target KMS key.
*
Deletes the S3 bucket. All objects (including all object versions and delete markers) in
- * the bucket must be deleted before the bucket itself can be deleted.
+ *
Deletes the S3 bucket. All objects (including all object versions and delete markers) in the bucket
+ * must be deleted before the bucket itself can be deleted.
*
*
*
*
- * Directory buckets - If multipart
- * uploads in a directory bucket are in progress, you can't delete the bucket until
- * all the in-progress multipart uploads are aborted or completed.
+ * Directory buckets - If multipart uploads in a
+ * directory bucket are in progress, you can't delete the bucket until all the in-progress multipart
+ * uploads are aborted or completed.
*
- * General purpose bucket permissions - You
- * must have the s3:DeleteBucket permission on the specified
- * bucket in a policy.
+ * General purpose bucket permissions - You must have the
+ * s3:DeleteBucket permission on the specified bucket in a policy.
*
*
*
- * Directory bucket permissions -
- * You must have the s3express:DeleteBucket permission in
- * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ * Directory bucket permissions - You must have the
+ * s3express:DeleteBucket permission in an IAM identity-based policy instead of a bucket policy.
+ * Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource. For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
*
This operation is not supported for directory buckets.
*
*
Deletes the cors configuration information set for the bucket.
- *
To use this operation, you must have permission to perform the
- * s3:PutBucketCORS action. The bucket owner has this permission by default
- * and can grant this permission to others.
To use this operation, you must have permission to perform the s3:PutBucketCORS action.
+ * The bucket owner has this permission by default and can grant this permission to others.
This implementation of the DELETE action resets the default encryption for the bucket as
- * server-side encryption with Amazon S3 managed keys (SSE-S3).
+ *
This implementation of the DELETE action resets the default encryption for the bucket as server-side
+ * encryption with Amazon S3 managed keys (SSE-S3).
*
*
*
*
- * General purpose buckets - For information
- * about the bucket default encryption feature, see Amazon S3 Bucket Default
- * Encryption in the Amazon S3 User Guide.
+ * General purpose buckets - For information about the bucket
+ * default encryption feature, see Amazon S3 Bucket Default Encryption in the
+ * Amazon S3 User Guide.
*
*
*
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption
- * configuration in directory buckets, see Setting
- * default server-side encryption behavior for directory buckets.
- * Directory bucket permissions -
- * To grant access to this API operation, you must have the
- * s3express:PutEncryptionConfiguration permission in
- * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ * Directory bucket permissions - To grant access to
+ * this API operation, you must have the s3express:PutEncryptionConfiguration
+ * permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
*
Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the
- * lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your
- * objects never expire, and Amazon S3 no longer automatically deletes any objects on the basis of
- * rules contained in the deleted lifecycle configuration.
+ *
Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the lifecycle
+ * configuration rules in the lifecycle subresource associated with the bucket. Your objects never expire,
+ * and Amazon S3 no longer automatically deletes any objects on the basis of rules contained in the deleted
+ * lifecycle configuration.
*
*
Permissions
*
*
*
*
- * General purpose bucket permissions - By
- * default, all Amazon S3 resources are private, including buckets, objects, and
- * related subresources (for example, lifecycle configuration and website
- * configuration). Only the resource owner (that is, the Amazon Web Services account that
- * created it) can access the resource. The resource owner can optionally grant
- * access permissions to others by writing an access policy. For this
- * operation, a user must have the s3:PutLifecycleConfiguration
- * permission.
+ * General purpose bucket permissions - By default, all Amazon S3
+ * resources are private, including buckets, objects, and related subresources (for example,
+ * lifecycle configuration and website configuration). Only the resource owner (that is, the
+ * Amazon Web Services account that created it) can access the resource. The resource owner can optionally
+ * grant access permissions to others by writing an access policy. For this operation, a user
+ * must have the s3:PutLifecycleConfiguration permission.
+ *
- * Directory bucket permissions -
- * You must have the s3express:PutLifecycleConfiguration
- * permission in an IAM identity-based policy to use this operation.
- * Cross-account access to this API operation isn't supported. The resource
- * owner can optionally grant access permissions to others by creating a role
- * or user for them as long as they are within the same account as the owner
- * and resource.
+ * Directory bucket permissions - You must have the
+ * s3express:PutLifecycleConfiguration permission in an IAM identity-based policy
+ * to use this operation. Cross-account access to this API operation isn't supported. The
+ * resource owner can optionally grant access permissions to others by creating a role or user
+ * for them as long as they are within the same account as the owner and resource.
+ *
* Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name
@@ -78,12 +73,12 @@ declare const DeleteBucketLifecycleCommand_base: {
*
HTTP Host header syntax
*
*
- * Directory buckets - The HTTP Host
- * header syntax is
- * s3express-control.region.amazonaws.com.
+ * Directory buckets - The HTTP Host header syntax is
+ * s3express-control.region.amazonaws.com.
You can use the V2 DeleteBucketMetadataConfiguration API operation with V1 or V2
+ * metadata configurations. However, if you try to use the V1
+ * DeleteBucketMetadataTableConfiguration API operation with V2 configurations, you
+ * will receive an HTTP 405 Method Not Allowed error.
+ *
+ *
+ *
Permissions
+ *
+ *
To use this operation, you must have the
+ * s3:DeleteBucketMetadataTableConfiguration permission. For more information, see
+ * Setting up permissions for configuring metadata tables in the
+ * Amazon S3 User Guide.
+ *
+ *
The IAM policy action name is the same for the V1 and V2 API operations.
+ *
+ *
+ *
+ *
The following operations are related to DeleteBucketMetadataConfiguration:
+ * We recommend that you delete your S3 Metadata configurations by using the V2
+ * DeleteBucketMetadataTableConfiguration API operation. We no longer recommend using
+ * the V1 DeleteBucketMetadataTableConfiguration API operation.
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
You can use the V2 DeleteBucketMetadataConfiguration API operation with V1 or V2
+ * metadata table configurations. However, if you try to use the V1
+ * DeleteBucketMetadataTableConfiguration API operation with V2 configurations, you
+ * will receive an HTTP 405 Method Not Allowed error.
+ *
Make sure that you update your processes to use the new V2 API operations
+ * (CreateBucketMetadataConfiguration, GetBucketMetadataConfiguration, and
+ * DeleteBucketMetadataConfiguration) instead of the V1 API operations.
To use this operation, you must have the
+ * s3:DeleteBucketMetadataTableConfiguration permission. For more information, see
+ * Setting up permissions for configuring metadata tables in the
+ * Amazon S3 User Guide.
*
*
*
The following operations are related to DeleteBucketMetadataTableConfiguration:
This operation is not supported for directory buckets.
*
- *
Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the
- * metrics configuration ID) from the bucket. Note that this doesn't include the daily storage
- * metrics.
+ *
Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the metrics
+ * configuration ID) from the bucket. Note that this doesn't include the daily storage metrics.
This operation is not supported for directory buckets.
*
- *
Removes OwnershipControls for an Amazon S3 bucket. To use this operation, you
- * must have the s3:PutBucketOwnershipControls permission. For more information
- * about Amazon S3 permissions, see Specifying Permissions in a
- * Policy.
+ *
Removes OwnershipControls for an Amazon S3 bucket. To use this operation, you must have the
+ * s3:PutBucketOwnershipControls permission. For more information about Amazon S3 permissions,
+ * see Specifying
+ * Permissions in a Policy.
If you are using an identity other than the root user of the Amazon Web Services account that
- * owns the bucket, the calling identity must both have the
- * DeleteBucketPolicy permissions on the specified bucket and belong
- * to the bucket owner's account in order to use this operation.
- *
If you don't have DeleteBucketPolicy permissions, Amazon S3 returns a
- * 403 Access Denied error. If you have the correct permissions, but
- * you're not using an identity that belongs to the bucket owner's account, Amazon S3
- * returns a 405 Method Not Allowed error.
+ *
If you are using an identity other than the root user of the Amazon Web Services account that owns the
+ * bucket, the calling identity must both have the DeleteBucketPolicy permissions on the
+ * specified bucket and belong to the bucket owner's account in order to use this operation.
+ *
If you don't have DeleteBucketPolicy permissions, Amazon S3 returns a 403 Access
+ * Denied error. If you have the correct permissions, but you're not using an identity that
+ * belongs to the bucket owner's account, Amazon S3 returns a 405 Method Not Allowed
+ * error.
*
- *
To ensure that bucket owners don't inadvertently lock themselves out of
- * their own buckets, the root principal in a bucket owner's Amazon Web Services account can
- * perform the GetBucketPolicy, PutBucketPolicy, and
- * DeleteBucketPolicy API actions, even if their bucket policy
- * explicitly denies the root principal's access. Bucket owner root principals can
- * only be blocked from performing these API actions by VPC endpoint policies and
- * Amazon Web Services Organizations policies.
+ *
To ensure that bucket owners don't inadvertently lock themselves out of their own buckets,
+ * the root principal in a bucket owner's Amazon Web Services account can perform the
+ * GetBucketPolicy, PutBucketPolicy, and
+ * DeleteBucketPolicy API actions, even if their bucket policy explicitly denies the
+ * root principal's access. Bucket owner root principals can only be blocked from performing these
+ * API actions by VPC endpoint policies and Amazon Web Services Organizations policies.
*
*
*
*
* General purpose bucket permissions - The
- * s3:DeleteBucketPolicy permission is required in a policy.
- * For more information about general purpose buckets bucket policies, see Using Bucket Policies and User Policies in the
- * Amazon S3 User Guide.
+ * s3:DeleteBucketPolicy permission is required in a policy. For more information
+ * about general purpose buckets bucket policies, see Using Bucket Policies and User
+ * Policies in the Amazon S3 User Guide.
*
*
*
- * Directory bucket permissions -
- * To grant access to this API operation, you must have the
- * s3express:DeleteBucketPolicy permission in
- * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ * Directory bucket permissions - To grant access to
+ * this API operation, you must have the s3express:DeleteBucketPolicy permission in
+ * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
*
This operation is not supported for directory buckets.
*
*
Deletes the tags from the bucket.
- *
To use this operation, you must have permission to perform the
- * s3:PutBucketTagging action. By default, the bucket owner has this
- * permission and can grant this permission to others.
+ *
To use this operation, you must have permission to perform the s3:PutBucketTagging
+ * action. By default, the bucket owner has this permission and can grant this permission to others.
*
The following operations are related to DeleteBucketTagging:
This operation is not supported for directory buckets.
*
- *
This action removes the website configuration for a bucket. Amazon S3 returns a 200
- * OK response upon successfully deleting a website configuration on the specified
- * bucket. You will get a 200 OK response if the website configuration you are
- * trying to delete does not exist on the bucket. Amazon S3 returns a 404 response if
- * the bucket specified in the request does not exist.
- *
This DELETE action requires the S3:DeleteBucketWebsite permission. By
- * default, only the bucket owner can delete the website configuration attached to a bucket.
- * However, bucket owners can grant other users permission to delete the website configuration
- * by writing a bucket policy granting them the S3:DeleteBucketWebsite
- * permission.
+ *
This action removes the website configuration for a bucket. Amazon S3 returns a 200 OK
+ * response upon successfully deleting a website configuration on the specified bucket. You will get a
+ * 200 OK response if the website configuration you are trying to delete does not exist on
+ * the bucket. Amazon S3 returns a 404 response if the bucket specified in the request does not
+ * exist.
+ *
This DELETE action requires the S3:DeleteBucketWebsite permission. By default, only the
+ * bucket owner can delete the website configuration attached to a bucket. However, bucket owners can grant
+ * other users permission to delete the website configuration by writing a bucket policy granting them the
+ * S3:DeleteBucketWebsite permission.
If bucket versioning is not enabled, the operation permanently deletes the object.
*
*
- *
If bucket versioning is enabled, the operation inserts a delete marker, which becomes the current version of the object. To permanently delete an object in a versioned bucket, you must include the object’s versionId in the request. For more information about versioning-enabled buckets, see Deleting object versions from a versioning-enabled bucket.
+ *
If bucket versioning is enabled, the operation inserts a delete marker, which becomes the
+ * current version of the object. To permanently delete an object in a versioned bucket, you must
+ * include the object’s versionId in the request. For more information about
+ * versioning-enabled buckets, see Deleting object versions from a
+ * versioning-enabled bucket.
*
*
- *
If bucket versioning is suspended, the operation removes the object that has a null versionId, if there is one, and inserts a delete marker that becomes the current version of the object. If there isn't an object with a null versionId, and all versions of the object have a versionId, Amazon S3 does not remove the object and only inserts a delete marker. To permanently delete an object that has a versionId, you must include the object’s versionId in the request. For more information about versioning-suspended buckets, see Deleting objects from versioning-suspended buckets.
+ *
If bucket versioning is suspended, the operation removes the object that has a null
+ * versionId, if there is one, and inserts a delete marker that becomes the current
+ * version of the object. If there isn't an object with a null versionId, and all versions
+ * of the object have a versionId, Amazon S3 does not remove the object and only inserts a
+ * delete marker. To permanently delete an object that has a versionId, you must include
+ * the object’s versionId in the request. For more information about versioning-suspended
+ * buckets, see Deleting
+ * objects from versioning-suspended buckets.
*
*
*
*
*
*
- * Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null
- * to the versionId query parameter in the request.
+ * Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets.
+ * You can only specify null to the versionId query parameter in the
+ * request.
*
To remove a specific version, you must use the versionId query parameter. Using this
- * query parameter permanently deletes the version. If the object deleted is a delete marker, Amazon S3
- * sets the response header x-amz-delete-marker to true.
- *
If the object you want to delete is in a bucket where the bucket versioning
- * configuration is MFA Delete enabled, you must include the x-amz-mfa request
- * header in the DELETE versionId request. Requests that include
- * x-amz-mfa must use HTTPS. For more information about MFA Delete, see Using MFA Delete in the Amazon S3
- * User Guide. To see sample
- * requests that use versioning, see Sample
- * Request.
+ * query parameter permanently deletes the version. If the object deleted is a delete marker, Amazon S3 sets the
+ * response header x-amz-delete-marker to true.
+ *
If the object you want to delete is in a bucket where the bucket versioning configuration is MFA
+ * Delete enabled, you must include the x-amz-mfa request header in the DELETE
+ * versionId request. Requests that include x-amz-mfa must use HTTPS. For more
+ * information about MFA Delete, see Using MFA Delete in the Amazon S3 User
+ * Guide. To see sample requests that use versioning, see Sample Request.
*
*
* Directory buckets - MFA delete is not supported by directory buckets.
*
- *
You can delete objects by explicitly calling DELETE Object or calling
- * (PutBucketLifecycle) to enable Amazon S3 to remove them for you. If you want to block
- * users or accounts from removing or deleting objects from your bucket, you must deny them
- * the s3:DeleteObject, s3:DeleteObjectVersion, and
- * s3:PutLifeCycleConfiguration actions.
+ *
You can delete objects by explicitly calling DELETE Object or calling (PutBucketLifecycle) to enable Amazon S3 to
+ * remove them for you. If you want to block users or accounts from removing or deleting objects from your
+ * bucket, you must deny them the s3:DeleteObject, s3:DeleteObjectVersion, and
+ * s3:PutLifeCycleConfiguration actions.
*
*
- * Directory buckets - S3 Lifecycle is not supported by directory buckets.
+ * Directory buckets -
+ * S3 Lifecycle is not supported by directory buckets.
*
*
- * General purpose bucket permissions - The following permissions are required in your policies when your
- * DeleteObjects request includes specific headers.
+ * General purpose bucket permissions - The following
+ * permissions are required in your policies when your DeleteObjects request
+ * includes specific headers.
*
*
*
*
* s3:DeleteObject
- * - To delete an object from a bucket, you must always have the s3:DeleteObject permission.
+ * - To delete an
+ * object from a bucket, you must always have the s3:DeleteObject
+ * permission.
*
*
*
*
* s3:DeleteObjectVersion
- * - To delete a specific version of an object from a versioning-enabled bucket, you must have the s3:DeleteObjectVersion permission.
+ * - To delete a specific version of an object from a versioning-enabled
+ * bucket, you must have the s3:DeleteObjectVersion permission.
*
This operation is not supported for directory buckets.
*
- *
Removes the entire tag set from the specified object. For more information about
- * managing object tags, see Object Tagging.
- *
To use this operation, you must have permission to perform the
- * s3:DeleteObjectTagging action.
- *
To delete tags of a specific object version, add the versionId query
- * parameter in the request. You will need permission for the
- * s3:DeleteObjectVersionTagging action.
+ *
Removes the entire tag set from the specified object. For more information about managing object
+ * tags, see Object
+ * Tagging.
+ *
To use this operation, you must have permission to perform the s3:DeleteObjectTagging
+ * action.
+ *
To delete tags of a specific object version, add the versionId query parameter in the
+ * request. You will need permission for the s3:DeleteObjectVersionTagging action.
*
The following operations are related to DeleteObjectTagging:
This operation enables you to delete multiple objects from a bucket using a single HTTP
- * request. If you know the object keys that you want to delete, then this operation provides
- * a suitable alternative to sending individual delete requests, reducing per-request
- * overhead.
- *
The request can contain a list of up to 1,000 keys that you want to delete. In the XML, you
- * provide the object key names, and optionally, version IDs if you want to delete a specific
- * version of the object from a versioning-enabled bucket. For each key, Amazon S3 performs a
- * delete operation and returns the result of that delete, success or failure, in the response.
- * If the object specified in the request isn't found, Amazon S3 confirms the deletion by returning the result as deleted.
+ *
This operation enables you to delete multiple objects from a bucket using a single HTTP request. If
+ * you know the object keys that you want to delete, then this operation provides a suitable alternative to
+ * sending individual delete requests, reducing per-request overhead.
+ *
The request can contain a list of up to 1,000 keys that you want to delete. In the XML, you provide
+ * the object key names, and optionally, version IDs if you want to delete a specific version of the object
+ * from a versioning-enabled bucket. For each key, Amazon S3 performs a delete operation and returns the result
+ * of that delete, success or failure, in the response. If the object specified in the request isn't found,
+ * Amazon S3 confirms the deletion by returning the result as deleted.
*
*
*
*
* Directory buckets -
- * S3 Versioning isn't enabled and supported for directory buckets.
+ * S3 Versioning isn't enabled and supported for directory buckets.
*
*
*
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
*
*
*
- *
The operation supports two modes for the response: verbose and quiet. By default, the
- * operation uses verbose mode in which the response includes the result of deletion of each
- * key in your request. In quiet mode the response includes only keys where the delete
- * operation encountered an error. For a successful deletion in a quiet mode, the operation
- * does not return any information about the delete in the response body.
- *
When performing this action on an MFA Delete enabled bucket, that attempts to delete any
- * versioned objects, you must include an MFA token. If you do not provide one, the entire
- * request will fail, even if there are non-versioned objects you are trying to delete. If you
- * provide an invalid token, whether there are versioned keys in the request or not, the
- * entire Multi-Object Delete request will fail. For information about MFA Delete, see MFA
- * Delete in the Amazon S3 User Guide.
+ *
The operation supports two modes for the response: verbose and quiet. By default, the operation uses
+ * verbose mode in which the response includes the result of deletion of each key in your request. In quiet
+ * mode the response includes only keys where the delete operation encountered an error. For a successful
+ * deletion in a quiet mode, the operation does not return any information about the delete in the response
+ * body.
+ *
When performing this action on an MFA Delete enabled bucket, that attempts to delete any versioned
+ * objects, you must include an MFA token. If you do not provide one, the entire request will fail, even if
+ * there are non-versioned objects you are trying to delete. If you provide an invalid token, whether there
+ * are versioned keys in the request or not, the entire Multi-Object Delete request will fail. For
+ * information about MFA Delete, see MFA Delete in the
+ * Amazon S3 User Guide.
*
*
- * Directory buckets -
- * MFA delete is not supported by directory buckets.
+ * Directory buckets - MFA delete is not supported by directory buckets.
*
*
- * General purpose bucket permissions - The
- * following permissions are required in your policies when your
- * DeleteObjects request includes specific headers.
+ * General purpose bucket permissions - The following
+ * permissions are required in your policies when your DeleteObjects request
+ * includes specific headers.
*
*
*
*
* s3:DeleteObject
- *
- * - To delete an object from a bucket, you must always specify
- * the s3:DeleteObject permission.
+ * - To delete an
+ * object from a bucket, you must always specify the s3:DeleteObject
+ * permission.
*
*
*
*
* s3:DeleteObjectVersion
- * - To delete a specific version of an object from a
- * versioning-enabled bucket, you must specify the
- * s3:DeleteObjectVersion permission.
+ * - To delete a specific version of an object from a versioning-enabled
+ * bucket, you must specify the s3:DeleteObjectVersion permission.
*
- * General purpose bucket - The Content-MD5
- * request header is required for all Multi-Object Delete requests. Amazon S3 uses
- * the header value to ensure that your request body has not been altered in
- * transit.
+ * General purpose bucket - The Content-MD5 request header
+ * is required for all Multi-Object Delete requests. Amazon S3 uses the header value to ensure that
+ * your request body has not been altered in transit.
*
*
*
- * Directory bucket - The
- * Content-MD5 request header or a additional checksum request header
- * (including x-amz-checksum-crc32,
- * x-amz-checksum-crc32c, x-amz-checksum-sha1, or
- * x-amz-checksum-sha256) is required for all Multi-Object
- * Delete requests.
+ * Directory bucket - The Content-MD5 request header
+ * or a additional checksum request header (including x-amz-checksum-crc32,
+ * x-amz-checksum-crc32c, x-amz-checksum-sha1, or
+ * x-amz-checksum-sha256) is required for all Multi-Object Delete requests.
*
This operation is not supported for directory buckets.
*
- *
This implementation of the GET action uses the accelerate subresource to
- * return the Transfer Acceleration state of a bucket, which is either Enabled or
- * Suspended. Amazon S3 Transfer Acceleration is a bucket-level feature that
- * enables you to perform faster data transfers to and from Amazon S3.
+ *
This implementation of the GET action uses the accelerate subresource to return the
+ * Transfer Acceleration state of a bucket, which is either Enabled or Suspended.
+ * Amazon S3 Transfer Acceleration is a bucket-level feature that enables you to perform faster data transfers
+ * to and from Amazon S3.
You set the Transfer Acceleration state of an existing bucket to Enabled or
- * Suspended by using the PutBucketAccelerateConfiguration operation.
- *
A GET accelerate request does not return a state value for a bucket that
- * has no transfer acceleration state. A bucket has no Transfer Acceleration state if a state
- * has never been set on the bucket.
- *
For more information about transfer acceleration, see Transfer Acceleration in
- * the Amazon S3 User Guide.
- *
The following operations are related to
- * GetBucketAccelerateConfiguration:
A GET accelerate request does not return a state value for a bucket that has no
+ * transfer acceleration state. A bucket has no Transfer Acceleration state if a state has never been set
+ * on the bucket.
+ *
For more information about transfer acceleration, see Transfer Acceleration in the
+ * Amazon S3 User Guide.
+ *
The following operations are related to GetBucketAccelerateConfiguration:
This operation is not supported for directory buckets.
*
- *
This implementation of the GET action uses the acl subresource
- * to return the access control list (ACL) of a bucket. To use GET to return the
- * ACL of the bucket, you must have the READ_ACP access to the bucket. If
- * READ_ACP permission is granted to the anonymous user, you can return the
- * ACL of the bucket without using an authorization header.
+ *
This implementation of the GET action uses the acl subresource to return
+ * the access control list (ACL) of a bucket. To use GET to return the ACL of the bucket, you
+ * must have the READ_ACP access to the bucket. If READ_ACP permission is granted
+ * to the anonymous user, you can return the ACL of the bucket without using an authorization
+ * header.
*
When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
*
When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name.
* If the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned.
* For more information about InvalidAccessPointAliasError, see List of
* Error Codes.
*
- *
If your bucket uses the bucket owner enforced setting for S3 Object Ownership,
- * requests to read ACLs are still supported and return the
- * bucket-owner-full-control ACL with the owner being the account that
- * created the bucket. For more information, see Controlling object
- * ownership and disabling ACLs in the
- * Amazon S3 User Guide.
+ *
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, requests to read
+ * ACLs are still supported and return the bucket-owner-full-control ACL with the owner
+ * being the account that created the bucket. For more information, see Controlling object ownership and
+ * disabling ACLs in the Amazon S3 User Guide.
*
*
The following operations are related to GetBucketAcl:
This operation is not supported for directory buckets.
*
*
Returns the Cross-Origin Resource Sharing (CORS) configuration information set for the
- * bucket.
- *
To use this operation, you must have permission to perform the
- * s3:GetBucketCORS action. By default, the bucket owner has this permission
- * and can grant it to others.
+ * bucket.
+ *
To use this operation, you must have permission to perform the s3:GetBucketCORS
+ * action. By default, the bucket owner has this permission and can grant it to others.
*
When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
*
When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name.
* If the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned.
* For more information about InvalidAccessPointAliasError, see List of
* Error Codes.
Returns the default encryption configuration for an Amazon S3 bucket. By default, all buckets
- * have a default encryption configuration that uses server-side encryption with Amazon S3 managed
- * keys (SSE-S3).
+ *
Returns the default encryption configuration for an Amazon S3 bucket. By default, all buckets have a
+ * default encryption configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3).
*
*
*
*
- * General purpose buckets - For information
- * about the bucket default encryption feature, see Amazon S3 Bucket Default
- * Encryption in the Amazon S3 User Guide.
+ * General purpose buckets - For information about the bucket
+ * default encryption feature, see Amazon S3 Bucket Default Encryption in the
+ * Amazon S3 User Guide.
*
*
*
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption
- * configuration in directory buckets, see Setting
- * default server-side encryption behavior for directory buckets.
- * Directory bucket permissions -
- * To grant access to this API operation, you must have the
- * s3express:GetEncryptionConfiguration permission in
- * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ * Directory bucket permissions - To grant access to
+ * this API operation, you must have the s3express:GetEncryptionConfiguration
+ * permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
*
Returns the lifecycle configuration information set on the bucket. For information about
- * lifecycle configuration, see Object Lifecycle
- * Management.
- *
Bucket lifecycle configuration now supports specifying a lifecycle rule using an object
- * key name prefix, one or more object tags, object size, or any combination of these.
- * Accordingly, this section describes the latest API, which is compatible with the new
- * functionality. The previous version of the API supported filtering based only on an object
- * key name prefix, which is supported for general purpose buckets for backward compatibility.
- * For the related API description, see GetBucketLifecycle.
+ *
Returns the lifecycle configuration information set on the bucket. For information about lifecycle
+ * configuration, see Object Lifecycle Management.
+ *
Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name
+ * prefix, one or more object tags, object size, or any combination of these. Accordingly, this section
+ * describes the latest API, which is compatible with the new functionality. The previous version of the
+ * API supported filtering based only on an object key name prefix, which is supported for general purpose
+ * buckets for backward compatibility. For the related API description, see GetBucketLifecycle.
*
- *
Lifecyle configurations for directory buckets only support expiring objects and
- * cancelling multipart uploads. Expiring of versioned objects, transitions and tag filters
- * are not supported.
+ *
Lifecyle configurations for directory buckets only support expiring objects and cancelling
+ * multipart uploads. Expiring of versioned objects, transitions and tag filters are not
+ * supported.
- * General purpose bucket permissions - By
- * default, all Amazon S3 resources are private, including buckets, objects, and
- * related subresources (for example, lifecycle configuration and website
- * configuration). Only the resource owner (that is, the Amazon Web Services account that
- * created it) can access the resource. The resource owner can optionally grant
- * access permissions to others by writing an access policy. For this
- * operation, a user must have the s3:GetLifecycleConfiguration
- * permission.
+ * General purpose bucket permissions - By default, all Amazon S3
+ * resources are private, including buckets, objects, and related subresources (for example,
+ * lifecycle configuration and website configuration). Only the resource owner (that is, the
+ * Amazon Web Services account that created it) can access the resource. The resource owner can optionally
+ * grant access permissions to others by writing an access policy. For this operation, a user
+ * must have the s3:GetLifecycleConfiguration permission.
+ *
- * Directory bucket permissions -
- * You must have the s3express:GetLifecycleConfiguration
- * permission in an IAM identity-based policy to use this operation.
- * Cross-account access to this API operation isn't supported. The resource
- * owner can optionally grant access permissions to others by creating a role
- * or user for them as long as they are within the same account as the owner
- * and resource.
+ * Directory bucket permissions - You must have the
+ * s3express:GetLifecycleConfiguration permission in an IAM identity-based policy
+ * to use this operation. Cross-account access to this API operation isn't supported. The
+ * resource owner can optionally grant access permissions to others by creating a role or user
+ * for them as long as they are within the same account as the owner and resource.
+ *
* Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name
@@ -86,9 +79,8 @@ declare const GetBucketLifecycleConfigurationCommand_base: {
*
HTTP Host header syntax
*
*
- * Directory buckets - The HTTP Host
- * header syntax is
- * s3express-control.region.amazonaws.com.
+ * Directory buckets - The HTTP Host header syntax is
+ * s3express-control.region.amazonaws.com.
This operation is not supported for directory buckets.
*
*
Returns the Region the bucket resides in. You set the bucket's Region using the
- * LocationConstraint request parameter in a CreateBucket
- * request. For more information, see CreateBucket.
+ * LocationConstraint request parameter in a CreateBucket request. For more
+ * information, see CreateBucket.
*
When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
*
When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name.
* If the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned.
* For more information about InvalidAccessPointAliasError, see List of
* Error Codes.
*
- *
We recommend that you use HeadBucket to return the Region
- * that a bucket resides in. For backward compatibility, Amazon S3 continues to support
- * GetBucketLocation.
+ *
We recommend that you use HeadBucket to return the Region that a bucket
+ * resides in. For backward compatibility, Amazon S3 continues to support GetBucketLocation.
*
*
The following operations are related to GetBucketLocation:
You can use the V2 GetBucketMetadataConfiguration API operation with V1 or V2
+ * metadata configurations. However, if you try to use the V1
+ * GetBucketMetadataTableConfiguration API operation with V2 configurations, you
+ * will receive an HTTP 405 Method Not Allowed error.
+ * We recommend that you retrieve your S3 Metadata configurations by using the V2
+ * GetBucketMetadataTableConfiguration API operation. We no longer recommend using the V1
+ * GetBucketMetadataTableConfiguration API operation.
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
You can use the V2 GetBucketMetadataConfiguration API operation with V1 or V2
+ * metadata table configurations. However, if you try to use the V1
+ * GetBucketMetadataTableConfiguration API operation with V2 configurations, you
+ * will receive an HTTP 405 Method Not Allowed error.
+ *
Make sure that you update your processes to use the new V2 API operations
+ * (CreateBucketMetadataConfiguration, GetBucketMetadataConfiguration, and
+ * DeleteBucketMetadataConfiguration) instead of the V1 API operations.
This operation is not supported for directory buckets.
*
- *
Gets a metrics configuration (specified by the metrics configuration ID) from the
- * bucket. Note that this doesn't include the daily storage metrics.
+ *
Gets a metrics configuration (specified by the metrics configuration ID) from the bucket. Note that
+ * this doesn't include the daily storage metrics.
Returns the notification configuration of a bucket.
*
If notifications are not enabled on the bucket, the action returns an empty
- * NotificationConfiguration element.
- *
By default, you must be the bucket owner to read the notification configuration of a
- * bucket. However, the bucket owner can use a bucket policy to grant permission to other
- * users to read this configuration with the s3:GetBucketNotification
- * permission.
+ * NotificationConfiguration element.
+ *
By default, you must be the bucket owner to read the notification configuration of a bucket.
+ * However, the bucket owner can use a bucket policy to grant permission to other users to read this
+ * configuration with the s3:GetBucketNotification permission.
*
When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.
*
When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name.
* If the Object Lambda access point alias in a request is not valid, the error code InvalidAccessPointAliasError is returned.
* For more information about InvalidAccessPointAliasError, see List of
* Error Codes.
This operation is not supported for directory buckets.
*
- *
Retrieves OwnershipControls for an Amazon S3 bucket. To use this operation, you
- * must have the s3:GetBucketOwnershipControls permission. For more information
- * about Amazon S3 permissions, see Specifying permissions in a
- * policy.
+ *
Retrieves OwnershipControls for an Amazon S3 bucket. To use this operation, you must have
+ * the s3:GetBucketOwnershipControls permission. For more information about Amazon S3 permissions,
+ * see Specifying
+ * permissions in a policy.
*
*
A bucket doesn't have OwnershipControls settings in the following cases:
*
*
- *
The bucket was created before the BucketOwnerEnforced ownership setting was introduced and you've never explicitly applied this value
+ *
The bucket was created before the BucketOwnerEnforced ownership setting was
+ * introduced and you've never explicitly applied this value
*
*
- *
You've manually deleted the bucket ownership control value using the DeleteBucketOwnershipControls API operation.
+ *
You've manually deleted the bucket ownership control value using the
+ * DeleteBucketOwnershipControls API operation.
*
*
*
By default, Amazon S3 sets OwnershipControls for all newly created buckets.
If you are using an identity other than the root user of the Amazon Web Services account that
- * owns the bucket, the calling identity must both have the
- * GetBucketPolicy permissions on the specified bucket and belong to
- * the bucket owner's account in order to use this operation.
- *
If you don't have GetBucketPolicy permissions, Amazon S3 returns a
- * 403 Access Denied error. If you have the correct permissions, but
- * you're not using an identity that belongs to the bucket owner's account, Amazon S3
- * returns a 405 Method Not Allowed error.
+ *
If you are using an identity other than the root user of the Amazon Web Services account that owns the
+ * bucket, the calling identity must both have the GetBucketPolicy permissions on the
+ * specified bucket and belong to the bucket owner's account in order to use this operation.
+ *
If you don't have GetBucketPolicy permissions, Amazon S3 returns a 403 Access
+ * Denied error. If you have the correct permissions, but you're not using an identity that
+ * belongs to the bucket owner's account, Amazon S3 returns a 405 Method Not Allowed
+ * error.
*
- *
To ensure that bucket owners don't inadvertently lock themselves out of
- * their own buckets, the root principal in a bucket owner's Amazon Web Services account can
- * perform the GetBucketPolicy, PutBucketPolicy, and
- * DeleteBucketPolicy API actions, even if their bucket policy
- * explicitly denies the root principal's access. Bucket owner root principals can
- * only be blocked from performing these API actions by VPC endpoint policies and
- * Amazon Web Services Organizations policies.
+ *
To ensure that bucket owners don't inadvertently lock themselves out of their own buckets,
+ * the root principal in a bucket owner's Amazon Web Services account can perform the
+ * GetBucketPolicy, PutBucketPolicy, and
+ * DeleteBucketPolicy API actions, even if their bucket policy explicitly denies the
+ * root principal's access. Bucket owner root principals can only be blocked from performing these
+ * API actions by VPC endpoint policies and Amazon Web Services Organizations policies.
*
*
*
*
* General purpose bucket permissions - The
- * s3:GetBucketPolicy permission is required in a policy. For
- * more information about general purpose buckets bucket policies, see Using Bucket Policies and User Policies in the
- * Amazon S3 User Guide.
+ * s3:GetBucketPolicy permission is required in a policy. For more information
+ * about general purpose buckets bucket policies, see Using Bucket Policies and User
+ * Policies in the Amazon S3 User Guide.
*
*
*
- * Directory bucket permissions -
- * To grant access to this API operation, you must have the
- * s3express:GetBucketPolicy permission in
- * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ * Directory bucket permissions - To grant access to
+ * this API operation, you must have the s3express:GetBucketPolicy permission in
+ * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
*
*
*
*
Example bucket policies
*
*
- * General purpose buckets example bucket policies
- * - See Bucket policy
- * examples in the Amazon S3 User Guide.
+ * General purpose buckets example bucket policies - See Bucket policy
+ * examples in the Amazon S3 User Guide.
*
This operation is not supported for directory buckets.
*
- *
Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public.
- * In order to use this operation, you must have the s3:GetBucketPolicyStatus
- * permission. For more information about Amazon S3 permissions, see Specifying Permissions in a
- * Policy.
+ *
Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public. In order to
+ * use this operation, you must have the s3:GetBucketPolicyStatus permission. For more
+ * information about Amazon S3 permissions, see Specifying Permissions in a
+ * Policy.
*
For more information about when Amazon S3 considers a bucket public, see The Meaning of "Public".
*
The following operations are related to GetBucketPolicyStatus:
Returns the replication configuration of a bucket.
*
- *
It can take a while to propagate the put or delete a replication configuration to
- * all Amazon S3 systems. Therefore, a get request soon after put or delete can return a wrong
- * result.
+ *
It can take a while to propagate the put or delete a replication configuration to all Amazon S3
+ * systems. Therefore, a get request soon after put or delete can return a wrong result.
*
*
For information about replication configuration, see Replication in the
- * Amazon S3 User Guide.
- *
This action requires permissions for the s3:GetReplicationConfiguration
- * action. For more information about permissions, see Using Bucket Policies and User
- * Policies.
- *
If you include the Filter element in a replication configuration, you must
- * also include the DeleteMarkerReplication and Priority elements.
- * The response also returns those elements.
This action requires permissions for the s3:GetReplicationConfiguration action. For
+ * more information about permissions, see Using Bucket Policies and User
+ * Policies.
+ *
If you include the Filter element in a replication configuration, you must also include
+ * the DeleteMarkerReplication and Priority elements. The response also returns
+ * those elements.
This operation is not supported for directory buckets.
*
- *
Returns the request payment configuration of a bucket. To use this version of the
- * operation, you must be the bucket owner. For more information, see Requester Pays
- * Buckets.
+ *
Returns the request payment configuration of a bucket. To use this version of the operation, you
+ * must be the bucket owner. For more information, see Requester Pays Buckets.
*
The following operations are related to GetBucketRequestPayment:
This operation is not supported for directory buckets.
*
*
Returns the tag set associated with the bucket.
- *
To use this operation, you must have permission to perform the
- * s3:GetBucketTagging action. By default, the bucket owner has this
- * permission and can grant this permission to others.
+ *
To use this operation, you must have permission to perform the s3:GetBucketTagging
+ * action. By default, the bucket owner has this permission and can grant this permission to others.
*
* GetBucketTagging has the following special error:
To retrieve the versioning state of a bucket, you must be the bucket owner.
- *
This implementation also returns the MFA Delete status of the versioning state. If the
- * MFA Delete status is enabled, the bucket owner must use an authentication
- * device to change the versioning state of the bucket.
+ *
This implementation also returns the MFA Delete status of the versioning state. If the MFA Delete
+ * status is enabled, the bucket owner must use an authentication device to change the
+ * versioning state of the bucket.
*
The following operations are related to GetBucketVersioning:
This operation is not supported for directory buckets.
*
- *
Returns the website configuration for a bucket. To host website on Amazon S3, you can
- * configure a bucket as website by adding a website configuration. For more information about
- * hosting websites, see Hosting Websites on Amazon S3.
- *
This GET action requires the S3:GetBucketWebsite permission. By default,
- * only the bucket owner can read the bucket website configuration. However, bucket owners can
- * allow other users to read the website configuration by writing a bucket policy granting
- * them the S3:GetBucketWebsite permission.
+ *
Returns the website configuration for a bucket. To host website on Amazon S3, you can configure a bucket
+ * as website by adding a website configuration. For more information about hosting websites, see Hosting Websites on Amazon S3.
+ *
This GET action requires the S3:GetBucketWebsite permission. By default, only the
+ * bucket owner can read the bucket website configuration. However, bucket owners can allow other users to
+ * read the website configuration by writing a bucket policy granting them the
+ * S3:GetBucketWebsite permission.
*
The following operations are related to GetBucketWebsite:
This functionality is not supported for Amazon S3 on Outposts.
- *
By default, GET returns ACL information about the current version of an object. To
- * return ACL information about a different version, use the versionId subresource.
+ *
By default, GET returns ACL information about the current version of an object. To return ACL
+ * information about a different version, use the versionId subresource.
*
- *
If your bucket uses the bucket owner enforced setting for S3 Object Ownership,
- * requests to read ACLs are still supported and return the
- * bucket-owner-full-control ACL with the owner being the account that
- * created the bucket. For more information, see Controlling object
- * ownership and disabling ACLs in the
- * Amazon S3 User Guide.
+ *
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, requests to read
+ * ACLs are still supported and return the bucket-owner-full-control ACL with the owner
+ * being the account that created the bucket. For more information, see Controlling object ownership and
+ * disabling ACLs in the Amazon S3 User Guide.
*
*
The following operations are related to GetObjectAcl:
Retrieves all of the metadata from an object without returning the object itself. This
- * operation is useful if you're interested only in an object's metadata.
+ *
Retrieves all of the metadata from an object without returning the object itself. This operation is
+ * useful if you're interested only in an object's metadata.
*
- * GetObjectAttributes combines the functionality of HeadObject
- * and ListParts. All of the data returned with both of those individual calls
- * can be returned with a single call to GetObjectAttributes.
+ * GetObjectAttributes combines the functionality of HeadObject and
+ * ListParts. All of the data returned with both of those individual calls can be returned
+ * with a single call to GetObjectAttributes.
*
*
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
- * General purpose bucket permissions - To
- * use GetObjectAttributes, you must have READ access to the object.
- *
The other permissions that you need to use this operation depend on
- * whether the bucket is versioned and if a version ID is passed in the GetObjectAttributes request.
+ * General purpose bucket permissions - To use
+ * GetObjectAttributes, you must have READ access to the object.
+ *
The other permissions that you need to use this operation depend on whether the bucket is
+ * versioned and if a version ID is passed in the GetObjectAttributes request.
*
*
- *
If you pass a version ID in your request, you need both the s3:GetObjectVersion and
- * s3:GetObjectVersionAttributes permissions.
+ *
If you pass a version ID in your request, you need both the
+ * s3:GetObjectVersion and s3:GetObjectVersionAttributes
+ * permissions.
*
*
*
If you do not pass a version ID in your request, you need the
- * s3:GetObject and s3:GetObjectAttributes
- * permissions.
+ * s3:GetObject and s3:GetObjectAttributes permissions.
*
If
- * the
- * object is encrypted with SSE-KMS, you must also have the
- * kms:GenerateDataKey and kms:Decrypt permissions
- * in IAM identity-based policies and KMS key policies for the KMS
- * key.
+ * the
+ * object is encrypted with SSE-KMS, you must also have the kms:GenerateDataKey and
+ * kms:Decrypt permissions in IAM identity-based policies and KMS key policies
+ * for the KMS key.
*
*
*
*
Encryption
*
*
- *
Encryption request headers, like x-amz-server-side-encryption,
- * should not be sent for HEAD requests if your object uses
- * server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer
- * server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side
- * encryption with Amazon S3 managed encryption keys (SSE-S3). The
- * x-amz-server-side-encryption header is used when you
- * PUT an object to S3 and want to specify the encryption method.
- * If you include this header in a GET request for an object that
- * uses these types of keys, you’ll get an HTTP 400 Bad Request
- * error. It's because the encryption method can't be changed when you retrieve
- * the object.
+ *
Encryption request headers, like x-amz-server-side-encryption, should not be
+ * sent for HEAD requests if your object uses server-side encryption with Key Management Service
+ * (KMS) keys (SSE-KMS), dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or
+ * server-side encryption with Amazon S3 managed encryption keys (SSE-S3). The
+ * x-amz-server-side-encryption header is used when you PUT an object
+ * to S3 and want to specify the encryption method. If you include this header in a
+ * GET request for an object that uses these types of keys, you’ll get an HTTP
+ * 400 Bad Request error. It's because the encryption method can't be changed when
+ * you retrieve the object.
*
- *
If you encrypted an object when you stored the object in Amazon S3 by using server-side encryption with customer-provided
- * encryption keys (SSE-C), then when you retrieve
- * the metadata from the object, you must use the following headers. These headers provide the
- * server with the encryption key required to retrieve the object's metadata. The
- * headers are:
+ *
If you encrypted an object when you stored the object in Amazon S3 by using server-side encryption
+ * with customer-provided encryption keys (SSE-C), then when you retrieve the metadata from the
+ * object, you must use the following headers. These headers provide the server with the encryption
+ * key required to retrieve the object's metadata. The headers are:
* Directory bucket permissions -
- * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+ * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
* CreateSession requests or PUT object requests. Then, new objects
* are automatically encrypted with the desired encryption settings. For more
* information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
- * Directory buckets -
- * S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null to the
- * versionId query parameter in the request.
+ * Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets.
+ * You can only specify null to the versionId query parameter in the
+ * request.
*
*
Conditional request headers
*
*
Consider the following when using request headers:
*
*
- *
If both of the If-Match and If-Unmodified-Since
- * headers are present in the request as follows, then Amazon S3 returns the HTTP
- * status code 200 OK and the data requested:
+ *
If both of the If-Match and If-Unmodified-Since headers are
+ * present in the request as follows, then Amazon S3 returns the HTTP status code 200 OK
+ * and the data requested:
*
*
*
- * If-Match condition evaluates to
- * true.
+ * If-Match condition evaluates to true.
*
*
*
- * If-Unmodified-Since condition evaluates to
- * false.
+ * If-Unmodified-Since condition evaluates to false.
*
*
*
For more information about conditional requests, see RFC 7232.
*
*
- *
If both of the If-None-Match and
- * If-Modified-Since headers are present in the request as
- * follows, then Amazon S3 returns the HTTP status code 304 Not
- * Modified:
+ *
If both of the If-None-Match and If-Modified-Since headers are
+ * present in the request as follows, then Amazon S3 returns the HTTP status code 304 Not
+ * Modified:
*
*
*
- * If-None-Match condition evaluates to
- * false.
+ * If-None-Match condition evaluates to false.
*
*
*
- * If-Modified-Since condition evaluates to
- * true.
+ * If-Modified-Since condition evaluates to true.
*
*
*
For more information about conditional requests, see RFC 7232.
In the GetObject request, specify the full key name for the object.
*
- * General purpose buckets - Both the virtual-hosted-style
- * requests and the path-style requests are supported. For a virtual hosted-style request
- * example, if you have the object photos/2006/February/sample.jpg, specify the
- * object key name as /photos/2006/February/sample.jpg. For a path-style request
- * example, if you have the object photos/2006/February/sample.jpg in the bucket
- * named examplebucket, specify the object key name as
- * /examplebucket/photos/2006/February/sample.jpg. For more information about
- * request types, see HTTP Host
- * Header Bucket Specification in the Amazon S3 User Guide.
+ * General purpose buckets - Both the virtual-hosted-style requests
+ * and the path-style requests are supported. For a virtual hosted-style request example, if you have the
+ * object photos/2006/February/sample.jpg, specify the object key name as
+ * /photos/2006/February/sample.jpg. For a path-style request example, if you have the
+ * object photos/2006/February/sample.jpg in the bucket named examplebucket,
+ * specify the object key name as /examplebucket/photos/2006/February/sample.jpg. For more
+ * information about request types, see HTTP Host Header Bucket
+ * Specification in the Amazon S3 User Guide.
*
* Directory buckets -
- * Only virtual-hosted-style requests are supported. For a virtual hosted-style request example, if you have the object photos/2006/February/sample.jpg in the bucket named amzn-s3-demo-bucket--usw2-az1--x-s3, specify the object key name as /photos/2006/February/sample.jpg. Also, when you make requests to this API operation, your requests are sent to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://bucket-name.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Only virtual-hosted-style requests are supported. For a virtual hosted-style request example, if you have the object photos/2006/February/sample.jpg in the bucket named amzn-s3-demo-bucket--usw2-az1--x-s3, specify the object key name as /photos/2006/February/sample.jpg. Also, when you make requests to this API operation, your requests are sent to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://bucket-name.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
- * General purpose bucket permissions - You
- * must have the required permissions in a policy. To use
- * GetObject, you must have the READ access to the
- * object (or version). If you grant READ access to the anonymous
- * user, the GetObject operation returns the object without using
- * an authorization header. For more information, see Specifying permissions in a policy in the
- * Amazon S3 User Guide.
- *
If you include a versionId in your request header, you must
- * have the s3:GetObjectVersion permission to access a specific
- * version of an object. The s3:GetObject permission is not
- * required in this scenario.
- *
If you request the current version of an object without a specific
- * versionId in the request header, only the
- * s3:GetObject permission is required. The
- * s3:GetObjectVersion permission is not required in this
- * scenario.
- *
If the object that you request doesn’t exist, the error that Amazon S3 returns
- * depends on whether you also have the s3:ListBucket
- * permission.
+ * General purpose bucket permissions - You must have the
+ * required permissions in a policy. To use GetObject, you must have the
+ * READ access to the object (or version). If you grant READ access
+ * to the anonymous user, the GetObject operation returns the object without using
+ * an authorization header. For more information, see Specifying permissions in a
+ * policy in the Amazon S3 User Guide.
+ *
If you include a versionId in your request header, you must have the
+ * s3:GetObjectVersion permission to access a specific version of an object. The
+ * s3:GetObject permission is not required in this scenario.
+ *
If you request the current version of an object without a specific versionId
+ * in the request header, only the s3:GetObject permission is required. The
+ * s3:GetObjectVersion permission is not required in this scenario.
+ *
If the object that you request doesn’t exist, the error that Amazon S3 returns depends on
+ * whether you also have the s3:ListBucket permission.
*
*
- *
If you have the s3:ListBucket permission on the
- * bucket, Amazon S3 returns an HTTP status code 404 Not Found
- * error.
+ *
If you have the s3:ListBucket permission on the bucket, Amazon S3 returns an
+ * HTTP status code 404 Not Found error.
*
*
- *
If you don’t have the s3:ListBucket permission, Amazon S3
- * returns an HTTP status code 403 Access Denied
- * error.
+ *
If you don’t have the s3:ListBucket permission, Amazon S3 returns an HTTP
+ * status code 403 Access Denied error.
*
*
*
@@ -92,60 +84,54 @@ declare const GetObjectCommand_base: {
* Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see
* CreateSession
* .
- *
If
- * the
- * object is encrypted using SSE-KMS, you must also have the
- * kms:GenerateDataKey and kms:Decrypt permissions
- * in IAM identity-based policies and KMS key policies for the KMS
- * key.
+ *
If the object is
+ * encrypted using SSE-KMS, you must also have the kms:GenerateDataKey and
+ * kms:Decrypt permissions in IAM identity-based policies and KMS key policies
+ * for the KMS key.
*
*
*
*
Storage classes
*
- *
If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval
- * storage class, the S3 Glacier Deep Archive storage class, the
- * S3 Intelligent-Tiering Archive Access tier, or the S3 Intelligent-Tiering Deep Archive Access tier,
- * before you can retrieve the object you must first restore a copy using RestoreObject. Otherwise, this operation returns an
- * InvalidObjectState error. For information about restoring archived
- * objects, see Restoring Archived
- * Objects in the Amazon S3 User Guide.
+ *
If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class,
+ * the S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the
+ * S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a
+ * copy using RestoreObject. Otherwise, this operation returns an InvalidObjectState
+ * error. For information about restoring archived objects, see Restoring Archived Objects in the
+ * Amazon S3 User Guide.
*
* Directory buckets -
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
* Unsupported storage class values won't write a destination object and will respond with the HTTP status code 400 Bad Request.
*
*
Encryption
*
- *
Encryption request headers, like x-amz-server-side-encryption,
- * should not be sent for the GetObject requests, if your object uses
- * server-side encryption with Amazon S3 managed encryption keys (SSE-S3), server-side
- * encryption with Key Management Service (KMS) keys (SSE-KMS), or dual-layer server-side
- * encryption with Amazon Web Services KMS keys (DSSE-KMS). If you include the header in your
- * GetObject requests for the object that uses these types of keys,
- * you’ll get an HTTP 400 Bad Request error.
+ *
Encryption request headers, like x-amz-server-side-encryption, should not be sent
+ * for the GetObject requests, if your object uses server-side encryption with Amazon S3
+ * managed encryption keys (SSE-S3), server-side encryption with Key Management Service (KMS) keys (SSE-KMS), or
+ * dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS). If you include the header in
+ * your GetObject requests for the object that uses these types of keys, you’ll get an
+ * HTTP 400 Bad Request error.
*
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more
+ * For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more
* information, see Protecting data with server-side encryption in the Amazon S3 User Guide.
*
*
Overriding response header values through the request
*
*
There are times when you want to override certain response header values of a
- * GetObject response. For example, you might override the
- * Content-Disposition response header value through your
- * GetObject request.
- *
You can override values for a set of response headers. These modified response
- * header values are included only in a successful response, that is, when the HTTP
- * status code 200 OK is returned. The headers you can override using
- * the following query parameters in the request are a subset of the headers that
- * Amazon S3 accepts when you create an object.
- *
The response headers that you can override for the GetObject
- * response are Cache-Control, Content-Disposition,
- * Content-Encoding, Content-Language,
- * Content-Type, and Expires.
- *
To override values for a set of response headers in the GetObject
- * response, you can use the following query parameters in the request.
+ * GetObject response. For example, you might override the
+ * Content-Disposition response header value through your GetObject
+ * request.
+ *
You can override values for a set of response headers. These modified response header values
+ * are included only in a successful response, that is, when the HTTP status code 200 OK
+ * is returned. The headers you can override using the following query parameters in the request are
+ * a subset of the headers that Amazon S3 accepts when you create an object.
+ *
The response headers that you can override for the GetObject response are
+ * Cache-Control, Content-Disposition, Content-Encoding,
+ * Content-Language, Content-Type, and Expires.
+ *
To override values for a set of response headers in the GetObject response, you
+ * can use the following query parameters in the request.
When you use these parameters, you must sign the request by using either an
- * Authorization header or a presigned URL. These parameters cannot be used with
- * an unsigned (anonymous) request.
+ *
When you use these parameters, you must sign the request by using either an Authorization
+ * header or a presigned URL. These parameters cannot be used with an unsigned (anonymous)
+ * request.
Object is archived and inaccessible until restored.
- *
If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage
- * class, the S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access
- * tier, or the S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you
- * must first restore a copy using RestoreObject. Otherwise, this
- * operation returns an InvalidObjectState error. For information about restoring
- * archived objects, see Restoring Archived Objects in
- * the Amazon S3 User Guide.
+ *
If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class, the
+ * S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the
+ * S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a copy
+ * using RestoreObject. Otherwise, this operation returns an InvalidObjectState error. For
+ * information about restoring archived objects, see Restoring Archived Objects in the
+ * Amazon S3 User Guide.
This operation is not supported for directory buckets.
*
- *
Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock
- * configuration will be applied by default to every new object placed in the specified
- * bucket. For more information, see Locking Objects.
+ *
Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock configuration
+ * will be applied by default to every new object placed in the specified bucket. For more information, see
+ * Locking Objects.
*
The following action is related to GetObjectLockConfiguration:
This operation is not supported for directory buckets.
*
- *
Returns the tag-set of an object. You send the GET request against the tagging
- * subresource associated with the object.
- *
To use this operation, you must have permission to perform the
- * s3:GetObjectTagging action. By default, the GET action returns information
- * about current version of an object. For a versioned bucket, you can have multiple versions
- * of an object in your bucket. To retrieve tags of any other version, use the versionId query
- * parameter. You also need permission for the s3:GetObjectVersionTagging
- * action.
- *
By default, the bucket owner has this permission and can grant this permission to
- * others.
+ *
Returns the tag-set of an object. You send the GET request against the tagging subresource
+ * associated with the object.
+ *
To use this operation, you must have permission to perform the s3:GetObjectTagging
+ * action. By default, the GET action returns information about current version of an object. For a
+ * versioned bucket, you can have multiple versions of an object in your bucket. To retrieve tags of any
+ * other version, use the versionId query parameter. You also need permission for the
+ * s3:GetObjectVersionTagging action.
+ *
By default, the bucket owner has this permission and can grant this permission to others.
*
For information about the Amazon S3 object tagging feature, see Object Tagging.
*
The following actions are related to GetObjectTagging:
This operation is not supported for directory buckets.
*
- *
Returns torrent files from a bucket. BitTorrent can save you bandwidth when you're
- * distributing large files.
+ *
Returns torrent files from a bucket. BitTorrent can save you bandwidth when you're distributing
+ * large files.
*
- *
You can get torrent only for objects that are less than 5 GB in size, and that are
- * not encrypted using server-side encryption with a customer-provided encryption
- * key.
+ *
You can get torrent only for objects that are less than 5 GB in size, and that are not encrypted
+ * using server-side encryption with a customer-provided encryption key.
*
*
To use GET, you must have READ access to the object.
*
This functionality is not supported for Amazon S3 on Outposts.
This operation is not supported for directory buckets.
*
- *
Retrieves the PublicAccessBlock configuration for an Amazon S3 bucket. To use
- * this operation, you must have the s3:GetBucketPublicAccessBlock permission.
- * For more information about Amazon S3 permissions, see Specifying Permissions in a
- * Policy.
+ *
Retrieves the PublicAccessBlock configuration for an Amazon S3 bucket. To use this
+ * operation, you must have the s3:GetBucketPublicAccessBlock permission. For more information
+ * about Amazon S3 permissions, see Specifying Permissions in a
+ * Policy.
*
- *
When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or
- * an object, it checks the PublicAccessBlock configuration for both the
- * bucket (or the bucket that contains the object) and the bucket owner's account. If the
- * PublicAccessBlock settings are different between the bucket and the
- * account, Amazon S3 uses the most restrictive combination of the bucket-level and
- * account-level settings.
+ *
When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or an object, it
+ * checks the PublicAccessBlock configuration for both the bucket (or the bucket that
+ * contains the object) and the bucket owner's account. If the PublicAccessBlock settings
+ * are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the
+ * bucket-level and account-level settings.
*
*
For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of "Public".
*
The following operations are related to GetPublicAccessBlock:
You can use this operation to determine if a bucket exists and if you have permission to
- * access it. The action returns a 200 OK if the bucket exists and you have
- * permission to access it.
+ *
You can use this operation to determine if a bucket exists and if you have permission to access it.
+ * The action returns a 200 OK if the bucket exists and you have permission to access
+ * it.
*
- *
If the bucket does not exist or you do not have permission to access it, the
- * HEAD request returns a generic 400 Bad Request, 403
- * Forbidden or 404 Not Found code. A message body is not included,
- * so you cannot determine the exception beyond these HTTP response codes.
+ *
If the bucket does not exist or you do not have permission to access it, the HEAD
+ * request returns a generic 400 Bad Request, 403 Forbidden or 404 Not
+ * Found code. A message body is not included, so you cannot determine the exception beyond
+ * these HTTP response codes.
*
*
*
Authentication and authorization
*
*
- * General purpose buckets - Request to public
- * buckets that grant the s3:ListBucket permission publicly do not need to be signed.
- * All other HeadBucket requests must be authenticated and signed by
- * using IAM credentials (access key ID and secret access key for the IAM
- * identities). All headers with the x-amz- prefix, including
- * x-amz-copy-source, must be signed. For more information, see
- * REST Authentication.
+ * General purpose buckets - Request to public buckets that
+ * grant the s3:ListBucket permission publicly do not need to be signed. All other
+ * HeadBucket requests must be authenticated and signed by using IAM credentials
+ * (access key ID and secret access key for the IAM identities). All headers with the
+ * x-amz- prefix, including x-amz-copy-source, must be signed. For more
+ * information, see REST Authentication.
*
- * Directory buckets - You must use IAM
- * credentials to authenticate and authorize your access to the
- * HeadBucket API operation, instead of using the temporary security
- * credentials through the CreateSession API operation.
- *
Amazon Web Services CLI or SDKs handles authentication and authorization on your
- * behalf.
+ * Directory buckets - You must use IAM credentials to
+ * authenticate and authorize your access to the HeadBucket API operation, instead of
+ * using the temporary security credentials through the CreateSession API
+ * operation.
+ *
Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.
- * General purpose bucket permissions - To
- * use this operation, you must have permissions to perform the
- * s3:ListBucket action. The bucket owner has this permission
- * by default and can grant this permission to others. For more information
- * about permissions, see Managing access
- * permissions to your Amazon S3 resources in the
- * Amazon S3 User Guide.
+ * General purpose bucket permissions - To use this
+ * operation, you must have permissions to perform the s3:ListBucket action. The
+ * bucket owner has this permission by default and can grant this permission to others. For more
+ * information about permissions, see Managing access permissions to your
+ * Amazon S3 resources in the Amazon S3 User Guide.
*
*
*
- * Directory bucket permissions -
- * You must have the
+ * Directory bucket permissions - You must have the
+ *
* s3express:CreateSession
* permission in the
- * Action element of a policy. By default, the session is in
- * the ReadWrite mode. If you want to restrict the access, you can
- * explicitly set the s3express:SessionMode condition key to
- * ReadOnly on the bucket.
+ * Action element of a policy. By default, the session is in the
+ * ReadWrite mode. If you want to restrict the access, you can explicitly set the
+ * s3express:SessionMode condition key to ReadOnly on the
+ * bucket.
+ *
The HEAD operation retrieves metadata from an object without returning the
- * object itself. This operation is useful if you're interested only in an object's
- * metadata.
+ *
The HEAD operation retrieves metadata from an object without returning the object
+ * itself. This operation is useful if you're interested only in an object's metadata.
*
- *
A HEAD request has the same options as a GET operation on
- * an object. The response is identical to the GET response except that there
- * is no response body. Because of this, if the HEAD request generates an
- * error, it returns a generic code, such as 400 Bad Request, 403
- * Forbidden, 404 Not Found, 405 Method Not Allowed,
- * 412 Precondition Failed, or 304 Not Modified. It's not
- * possible to retrieve the exact exception of these error codes.
+ *
A HEAD request has the same options as a GET operation on an object. The
+ * response is identical to the GET response except that there is no response body. Because
+ * of this, if the HEAD request generates an error, it returns a generic code, such as
+ * 400 Bad Request, 403 Forbidden, 404 Not Found, 405
+ * Method Not Allowed, 412 Precondition Failed, or 304 Not Modified.
+ * It's not possible to retrieve the exact exception of these error codes.
- * General purpose bucket permissions - To
- * use HEAD, you must have the s3:GetObject
- * permission. You need the relevant read object (or version) permission for
- * this operation. For more information, see Actions, resources, and
- * condition keys for Amazon S3 in the Amazon S3 User
- * Guide. For more information about the permissions to S3 API
- * operations by S3 resource types, see Required permissions for Amazon S3 API operations in the
- * Amazon S3 User Guide.
- *
If the object you request doesn't exist, the error that Amazon S3 returns
- * depends on whether you also have the s3:ListBucket
- * permission.
+ * General purpose bucket permissions - To use
+ * HEAD, you must have the s3:GetObject permission. You need the
+ * relevant read object (or version) permission for this operation. For more information, see
+ * Actions, resources,
+ * and condition keys for Amazon S3 in the Amazon S3 User Guide. For more
+ * information about the permissions to S3 API operations by S3 resource types, see Required permissions for
+ * Amazon S3 API operations in the Amazon S3 User Guide.
+ *
If the object you request doesn't exist, the error that Amazon S3 returns depends on whether
+ * you also have the s3:ListBucket permission.
*
*
- *
If you have the s3:ListBucket permission on the
- * bucket, Amazon S3 returns an HTTP status code 404 Not Found
- * error.
+ *
If you have the s3:ListBucket permission on the bucket, Amazon S3 returns an
+ * HTTP status code 404 Not Found error.
*
*
- *
If you don’t have the s3:ListBucket permission, Amazon S3
- * returns an HTTP status code 403 Forbidden error.
+ *
If you don’t have the s3:ListBucket permission, Amazon S3 returns an HTTP
+ * status code 403 Forbidden error.
*
*
*
@@ -79,34 +73,31 @@ declare const HeadObjectCommand_base: {
* Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see
* CreateSession
* .
- *
If you enable x-amz-checksum-mode in the request and the
- * object is encrypted with Amazon Web Services Key Management Service (Amazon Web Services KMS), you must
- * also have the kms:GenerateDataKey and kms:Decrypt
- * permissions in IAM identity-based policies and KMS key policies for the
- * KMS key to retrieve the checksum of the object.
+ *
If you enable x-amz-checksum-mode in the request and the object is encrypted
+ * with Amazon Web Services Key Management Service (Amazon Web Services KMS), you must also have the
+ * kms:GenerateDataKey and kms:Decrypt permissions in IAM
+ * identity-based policies and KMS key policies for the KMS key to retrieve the checksum of
+ * the object.
*
*
*
*
Encryption
*
*
- *
Encryption request headers, like x-amz-server-side-encryption,
- * should not be sent for HEAD requests if your object uses
- * server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer
- * server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side
- * encryption with Amazon S3 managed encryption keys (SSE-S3). The
- * x-amz-server-side-encryption header is used when you
- * PUT an object to S3 and want to specify the encryption method.
- * If you include this header in a HEAD request for an object that
- * uses these types of keys, you’ll get an HTTP 400 Bad Request
- * error. It's because the encryption method can't be changed when you retrieve
- * the object.
+ *
Encryption request headers, like x-amz-server-side-encryption, should not be
+ * sent for HEAD requests if your object uses server-side encryption with Key Management Service
+ * (KMS) keys (SSE-KMS), dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or
+ * server-side encryption with Amazon S3 managed encryption keys (SSE-S3). The
+ * x-amz-server-side-encryption header is used when you PUT an object
+ * to S3 and want to specify the encryption method. If you include this header in a
+ * HEAD request for an object that uses these types of keys, you’ll get an HTTP
+ * 400 Bad Request error. It's because the encryption method can't be changed when
+ * you retrieve the object.
*
- *
If you encrypt an object by using server-side encryption with customer-provided
- * encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve
- * the metadata from the object, you must use the following headers to provide the
- * encryption key for the server to be able to retrieve the object's metadata. The
- * headers are:
+ *
If you encrypt an object by using server-side encryption with customer-provided encryption
+ * keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the metadata from the
+ * object, you must use the following headers to provide the encryption key for the server to be able
+ * to retrieve the object's metadata. The headers are:
* Directory bucket -
- * For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more
+ * For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more
* information, see Protecting data with server-side encryption in the Amazon S3 User Guide.
If the current version of the object is a delete marker, Amazon S3 behaves as
- * if the object was deleted and includes x-amz-delete-marker:
- * true in the response.
+ *
If the current version of the object is a delete marker, Amazon S3 behaves as if the object was
+ * deleted and includes x-amz-delete-marker: true in the response.
*
*
- *
If the specified version is a delete marker, the response returns a
- * 405 Method Not Allowed error and the Last-Modified:
- * timestamp response header.
+ *
If the specified version is a delete marker, the response returns a 405 Method Not
+ * Allowed error and the Last-Modified: timestamp response header.
* Directory buckets -
- * Delete marker is not supported for directory buckets.
+ * Delete marker is not supported for directory buckets.
*
*
*
* Directory buckets -
- * S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null
- * to the versionId query parameter in the request.
+ * S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null to the
+ * versionId query parameter in the request.
*
This operation is not supported for directory buckets.
*
- *
Lists the analytics configurations for the bucket. You can have up to 1,000 analytics
- * configurations per bucket.
- *
This action supports list pagination and does not return more than 100 configurations at
- * a time. You should always check the IsTruncated element in the response. If
- * there are no more configurations to list, IsTruncated is set to false. If
- * there are more configurations to list, IsTruncated is set to true, and there
- * will be a value in NextContinuationToken. You use the
- * NextContinuationToken value to continue the pagination of the list by
- * passing the value in continuation-token in the request to GET the next
- * page.
+ *
Lists the analytics configurations for the bucket. You can have up to 1,000 analytics configurations
+ * per bucket.
+ *
This action supports list pagination and does not return more than 100 configurations at a time. You
+ * should always check the IsTruncated element in the response. If there are no more
+ * configurations to list, IsTruncated is set to false. If there are more configurations to
+ * list, IsTruncated is set to true, and there will be a value in
+ * NextContinuationToken. You use the NextContinuationToken value to continue
+ * the pagination of the list by passing the value in continuation-token in the request to GET
+ * the next page.
This operation is not supported for directory buckets.
*
- *
Returns a list of inventory configurations for the bucket. You can have up to 1,000
- * analytics configurations per bucket.
- *
This action supports list pagination and does not return more than 100 configurations at
- * a time. Always check the IsTruncated element in the response. If there are no
- * more configurations to list, IsTruncated is set to false. If there are more
- * configurations to list, IsTruncated is set to true, and there is a value in
- * NextContinuationToken. You use the NextContinuationToken value
- * to continue the pagination of the list by passing the value in continuation-token in the
- * request to GET the next page.
+ *
Returns a list of S3 Inventory configurations for the bucket. You can have up to 1,000 analytics
+ * configurations per bucket.
+ *
This action supports list pagination and does not return more than 100 configurations at a time.
+ * Always check the IsTruncated element in the response. If there are no more configurations
+ * to list, IsTruncated is set to false. If there are more configurations to list,
+ * IsTruncated is set to true, and there is a value in NextContinuationToken.
+ * You use the NextContinuationToken value to continue the pagination of the list by passing
+ * the value in continuation-token in the request to GET the next page.
This operation is not supported for directory buckets.
*
- *
Lists the metrics configurations for the bucket. The metrics configurations are only for
- * the request metrics of the bucket and do not provide information on daily storage metrics.
- * You can have up to 1,000 configurations per bucket.
- *
This action supports list pagination and does not return more than 100 configurations at
- * a time. Always check the IsTruncated element in the response. If there are no
- * more configurations to list, IsTruncated is set to false. If there are more
- * configurations to list, IsTruncated is set to true, and there is a value in
- * NextContinuationToken. You use the NextContinuationToken value
- * to continue the pagination of the list by passing the value in
- * continuation-token in the request to GET the next page.
+ *
Lists the metrics configurations for the bucket. The metrics configurations are only for the request
+ * metrics of the bucket and do not provide information on daily storage metrics. You can have up to 1,000
+ * configurations per bucket.
+ *
This action supports list pagination and does not return more than 100 configurations at a time.
+ * Always check the IsTruncated element in the response. If there are no more configurations
+ * to list, IsTruncated is set to false. If there are more configurations to list,
+ * IsTruncated is set to true, and there is a value in NextContinuationToken.
+ * You use the NextContinuationToken value to continue the pagination of the list by passing
+ * the value in continuation-token in the request to GET the next page.
This operation is not supported for directory buckets.
*
- *
Returns a list of all buckets owned by the authenticated sender of the request. To grant IAM permission to use
- * this operation, you must add the s3:ListAllMyBuckets policy action.
Returns a list of all buckets owned by the authenticated sender of the request. To grant IAM
+ * permission to use this operation, you must add the s3:ListAllMyBuckets policy action.
We strongly recommend using only paginated ListBuckets requests. Unpaginated ListBuckets requests are only supported for
- * Amazon Web Services accounts set to the default general purpose bucket quota of 10,000. If you have an approved
- * general purpose bucket quota above 10,000, you must send paginated ListBuckets requests to list your account’s buckets.
- * All unpaginated ListBuckets requests will be rejected for Amazon Web Services accounts with a general purpose bucket quota
- * greater than 10,000.
+ *
We strongly recommend using only paginated ListBuckets requests. Unpaginated
+ * ListBuckets requests are only supported for Amazon Web Services accounts set to the default general
+ * purpose bucket quota of 10,000. If you have an approved general purpose bucket quota above 10,000, you
+ * must send paginated ListBuckets requests to list your account’s buckets. All unpaginated
+ * ListBuckets requests will be rejected for Amazon Web Services accounts with a general purpose bucket
+ * quota greater than 10,000.
*
* @example
* Use a bare-bones client and the command you need to make an API call.
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListDirectoryBucketsCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListDirectoryBucketsCommand.d.ts
index 676c5b77..b0e0c5c4 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListDirectoryBucketsCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListDirectoryBucketsCommand.d.ts
@@ -27,8 +27,9 @@ declare const ListDirectoryBucketsCommand_base: {
getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
};
/**
- *
Returns a list of all Amazon S3 directory buckets owned by the authenticated sender of the
- * request. For more information about directory buckets, see Directory buckets in the Amazon S3 User Guide.
+ *
Returns a list of all Amazon S3 directory buckets owned by the authenticated sender of the request. For
+ * more information about directory buckets, see Directory buckets in the
+ * Amazon S3 User Guide.
*
*
* Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name
@@ -40,21 +41,20 @@ declare const ListDirectoryBucketsCommand_base: {
*
*
Permissions
*
- *
You must have the s3express:ListAllMyDirectoryBuckets permission
- * in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ *
You must have the s3express:ListAllMyDirectoryBuckets permission in
+ * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
*
*
HTTP Host header syntax
*
*
- * Directory buckets - The HTTP Host
- * header syntax is
- * s3express-control.region.amazonaws.com.
+ * Directory buckets - The HTTP Host header syntax is
+ * s3express-control.region.amazonaws.com.
*
*
*
*
The BucketRegion response element is not part of the
- * ListDirectoryBuckets Response Syntax.
+ * ListDirectoryBuckets Response Syntax.
*
* @example
* Use a bare-bones client and the command you need to make an API call.
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListMultipartUploadsCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListMultipartUploadsCommand.d.ts
index da8588ff..a5dacdce 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListMultipartUploadsCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListMultipartUploadsCommand.d.ts
@@ -34,47 +34,41 @@ declare const ListMultipartUploadsCommand_base: {
*
This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region,
* Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (São Paulo) Region.
*
- *
This operation lists in-progress multipart uploads in a bucket. An in-progress multipart
- * upload is a multipart upload that has been initiated by the
- * CreateMultipartUpload request, but has not yet been completed or
- * aborted.
+ *
This operation lists in-progress multipart uploads in a bucket. An in-progress multipart upload is a
+ * multipart upload that has been initiated by the CreateMultipartUpload request, but has not
+ * yet been completed or aborted.
*
*
- * Directory buckets - If multipart uploads in
- * a directory bucket are in progress, you can't delete the bucket until all the
- * in-progress multipart uploads are aborted or completed. To delete these in-progress
- * multipart uploads, use the ListMultipartUploads operation to list the
- * in-progress multipart uploads in the bucket and use the
- * AbortMultipartUpload operation to abort all the in-progress multipart
- * uploads.
+ * Directory buckets - If multipart uploads in a
+ * directory bucket are in progress, you can't delete the bucket until all the in-progress multipart
+ * uploads are aborted or completed. To delete these in-progress multipart uploads, use the
+ * ListMultipartUploads operation to list the in-progress multipart uploads in the bucket
+ * and use the AbortMultipartUpload operation to abort all the in-progress multipart
+ * uploads.
*
- *
The ListMultipartUploads operation returns a maximum of 1,000 multipart
- * uploads in the response. The limit of 1,000 multipart uploads is also the default value.
- * You can further limit the number of uploads in a response by specifying the
- * max-uploads request parameter. If there are more than 1,000 multipart
- * uploads that satisfy your ListMultipartUploads request, the response returns
- * an IsTruncated element with the value of true, a
- * NextKeyMarker element, and a NextUploadIdMarker element. To
- * list the remaining multipart uploads, you need to make subsequent
- * ListMultipartUploads requests. In these requests, include two query
- * parameters: key-marker and upload-id-marker. Set the value of
- * key-marker to the NextKeyMarker value from the previous
- * response. Similarly, set the value of upload-id-marker to the
- * NextUploadIdMarker value from the previous response.
+ *
The ListMultipartUploads operation returns a maximum of 1,000 multipart uploads in the
+ * response. The limit of 1,000 multipart uploads is also the default value. You can further limit the
+ * number of uploads in a response by specifying the max-uploads request parameter. If there
+ * are more than 1,000 multipart uploads that satisfy your ListMultipartUploads request, the
+ * response returns an IsTruncated element with the value of true, a
+ * NextKeyMarker element, and a NextUploadIdMarker element. To list the
+ * remaining multipart uploads, you need to make subsequent ListMultipartUploads requests. In
+ * these requests, include two query parameters: key-marker and upload-id-marker.
+ * Set the value of key-marker to the NextKeyMarker value from the previous
+ * response. Similarly, set the value of upload-id-marker to the
+ * NextUploadIdMarker value from the previous response.
*
*
- * Directory buckets - The
- * upload-id-marker element and the NextUploadIdMarker element
- * aren't supported by directory buckets. To list the additional multipart uploads, you
- * only need to set the value of key-marker to the NextKeyMarker
- * value from the previous response.
+ * Directory buckets - The upload-id-marker
+ * element and the NextUploadIdMarker element aren't supported by directory buckets. To
+ * list the additional multipart uploads, you only need to set the value of key-marker to
+ * the NextKeyMarker value from the previous response.
*
- *
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
- * General purpose bucket permissions - For
- * information about permissions required to use the multipart upload API, see
- * Multipart Upload and
- * Permissions in the Amazon S3 User Guide.
+ * General purpose bucket permissions - For information
+ * about permissions required to use the multipart upload API, see Multipart Upload and Permissions in
+ * the Amazon S3 User Guide.
*
* General purpose bucket - In the
- * ListMultipartUploads response, the multipart uploads are
- * sorted based on two criteria:
+ * ListMultipartUploads response, the multipart uploads are sorted based on two
+ * criteria:
*
*
- *
Key-based sorting - Multipart uploads are initially sorted
- * in ascending order based on their object keys.
+ *
Key-based sorting - Multipart uploads are initially sorted in ascending order
+ * based on their object keys.
*
*
- *
Time-based sorting - For uploads that share the same object
- * key, they are further sorted in ascending order based on the upload
- * initiation time. Among uploads with the same key, the one that was
- * initiated first will appear before the ones that were initiated
- * later.
+ *
Time-based sorting - For uploads that share the same object key, they are
+ * further sorted in ascending order based on the upload initiation time. Among uploads with
+ * the same key, the one that was initiated first will appear before the ones that were
+ * initiated later.
*
*
*
*
*
* Directory bucket - In the
- * ListMultipartUploads response, the multipart uploads aren't
- * sorted lexicographically based on the object keys.
+ * ListMultipartUploads response, the multipart uploads aren't sorted
+ * lexicographically based on the object keys.
*
- *
+ *
*
*
*
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectVersionsCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectVersionsCommand.d.ts
index b1e57826..383d108b 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectVersionsCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectVersionsCommand.d.ts
@@ -1,6 +1,6 @@
import { Command as $Command } from "@smithy/smithy-client";
import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { ListObjectVersionsOutput, ListObjectVersionsRequest } from "../models/models_0";
+import { ListObjectVersionsOutput, ListObjectVersionsRequest } from "../models/models_1";
import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
/**
* @public
@@ -37,17 +37,15 @@ declare const ListObjectVersionsCommand_base: {
*
*
This operation is not supported for directory buckets.
*
- *
Returns metadata about all versions of the objects in a bucket. You can also use request
- * parameters as selection criteria to return metadata about a subset of all the object
- * versions.
+ *
Returns metadata about all versions of the objects in a bucket. You can also use request parameters
+ * as selection criteria to return metadata about a subset of all the object versions.
*
- *
To use this operation, you must have permission to perform the
- * s3:ListBucketVersions action. Be aware of the name difference.
+ *
To use this operation, you must have permission to perform the s3:ListBucketVersions
+ * action. Be aware of the name difference.
*
*
- *
A 200 OK response can contain valid or invalid XML. Make sure to design
- * your application to parse the contents of the response and handle it
- * appropriately.
+ *
A 200 OK response can contain valid or invalid XML. Make sure to design your
+ * application to parse the contents of the response and handle it appropriately.
*
*
To use this operation, you must have READ access to the bucket.
*
The following operations are related to ListObjectVersions:
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectsCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectsCommand.d.ts
index 6d558490..9af088b2 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectsCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectsCommand.d.ts
@@ -1,6 +1,6 @@
import { Command as $Command } from "@smithy/smithy-client";
import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { ListObjectsOutput, ListObjectsRequest } from "../models/models_0";
+import { ListObjectsOutput, ListObjectsRequest } from "../models/models_1";
import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
/**
* @public
@@ -37,13 +37,14 @@ declare const ListObjectsCommand_base: {
*
*
This operation is not supported for directory buckets.
*
- *
Returns some or all (up to 1,000) of the objects in a bucket. You can use the request
- * parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK
- * response can contain valid or invalid XML. Be sure to design your application to parse the
- * contents of the response and handle it appropriately.
+ *
Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as
+ * selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or
+ * invalid XML. Be sure to design your application to parse the contents of the response and handle it
+ * appropriately.
*
- *
This action has been revised. We recommend that you use the newer version, ListObjectsV2, when developing applications. For backward compatibility,
- * Amazon S3 continues to support ListObjects.
+ *
This action has been revised. We recommend that you use the newer version, ListObjectsV2, when
+ * developing applications. For backward compatibility, Amazon S3 continues to support
+ * ListObjects.
*
*
The following operations are related to ListObjects:
*
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectsV2Command.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectsV2Command.d.ts
index e65cd65e..3058214b 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectsV2Command.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListObjectsV2Command.d.ts
@@ -1,6 +1,6 @@
import { Command as $Command } from "@smithy/smithy-client";
import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { ListObjectsV2Output, ListObjectsV2Request } from "../models/models_0";
+import { ListObjectsV2Output, ListObjectsV2Request } from "../models/models_1";
import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
/**
* @public
@@ -27,31 +27,30 @@ declare const ListObjectsV2Command_base: {
getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
};
/**
- *
Returns some or all (up to 1,000) of the objects in a bucket with each request. You can
- * use the request parameters as selection criteria to return a subset of the objects in a
- * bucket. A 200 OK response can contain valid or invalid XML. Make sure to
- * design your application to parse the contents of the response and handle it appropriately.
- * For more information about listing objects, see Listing object keys
- * programmatically in the Amazon S3 User Guide. To get a list of
- * your buckets, see ListBuckets.
+ *
Returns some or all (up to 1,000) of the objects in a bucket with each request. You can use the
+ * request parameters as selection criteria to return a subset of the objects in a bucket. A 200
+ * OK response can contain valid or invalid XML. Make sure to design your application to parse the
+ * contents of the response and handle it appropriately. For more information about listing objects, see
+ * Listing object
+ * keys programmatically in the Amazon S3 User Guide. To get a list of your
+ * buckets, see ListBuckets.
*
*
*
*
* General purpose bucket - For general purpose buckets,
- * ListObjectsV2 doesn't return prefixes that are related only to
- * in-progress multipart uploads.
+ * ListObjectsV2 doesn't return prefixes that are related only to in-progress
+ * multipart uploads.
*
*
*
- * Directory buckets - For
- * directory buckets, ListObjectsV2 response includes the prefixes that
- * are related only to in-progress multipart uploads.
+ * Directory buckets - For directory buckets,
+ * ListObjectsV2 response includes the prefixes that are related only to in-progress
+ * multipart uploads.
*
*
*
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
- * General purpose bucket permissions - To
- * use this operation, you must have READ access to the bucket. You must have
- * permission to perform the s3:ListBucket action. The bucket
- * owner has this permission by default and can grant this permission to
- * others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access
- * Permissions to Your Amazon S3 Resources in the
- * Amazon S3 User Guide.
+ * General purpose bucket permissions - To use this
+ * operation, you must have READ access to the bucket. You must have permission to perform the
+ * s3:ListBucket action. The bucket owner has this permission by default and can
+ * grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access
+ * Permissions to Your Amazon S3 Resources in the
+ * Amazon S3 User Guide.
*
This section describes the latest revision of this action. We recommend that you use
- * this revised API operation for application development. For backward compatibility, Amazon S3
- * continues to support the prior version of this API operation, ListObjects.
+ *
This section describes the latest revision of this action. We recommend that you use this revised
+ * API operation for application development. For backward compatibility, Amazon S3 continues to support the
+ * prior version of this API operation, ListObjects.
*
*
The following operations are related to ListObjectsV2:
*
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListPartsCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListPartsCommand.d.ts
index 7a020bf2..ed246ba4 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListPartsCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/ListPartsCommand.d.ts
@@ -1,6 +1,6 @@
import { Command as $Command } from "@smithy/smithy-client";
import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { ListPartsOutput, ListPartsRequest } from "../models/models_0";
+import { ListPartsOutput, ListPartsRequest } from "../models/models_1";
import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
/**
* @public
@@ -35,22 +35,21 @@ declare const ListPartsCommand_base: {
* Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (São Paulo) Region.
*
*
Lists the parts that have been uploaded for a specific multipart upload.
- *
To use this operation, you must provide the upload ID in the request. You
- * obtain this uploadID by sending the initiate multipart upload request through CreateMultipartUpload.
- *
The ListParts request returns a maximum of 1,000 uploaded parts. The limit
- * of 1,000 parts is also the default value. You can restrict the number of parts in a
- * response by specifying the max-parts request parameter. If your multipart
- * upload consists of more than 1,000 parts, the response returns an IsTruncated
- * field with the value of true, and a NextPartNumberMarker element.
- * To list remaining uploaded parts, in subsequent ListParts requests, include
- * the part-number-marker query string parameter and set its value to the
- * NextPartNumberMarker field value from the previous response.
To use this operation, you must provide the upload ID in the request. You obtain this
+ * uploadID by sending the initiate multipart upload request through CreateMultipartUpload.
+ *
The ListParts request returns a maximum of 1,000 uploaded parts. The limit of 1,000
+ * parts is also the default value. You can restrict the number of parts in a response by specifying the
+ * max-parts request parameter. If your multipart upload consists of more than 1,000 parts,
+ * the response returns an IsTruncated field with the value of true, and a
+ * NextPartNumberMarker element. To list remaining uploaded parts, in subsequent
+ * ListParts requests, include the part-number-marker query string parameter
+ * and set its value to the NextPartNumberMarker field value from the previous
+ * response.
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
- * General purpose bucket permissions - For
- * information about permissions required to use the multipart upload API, see
- * Multipart Upload and
- * Permissions in the Amazon S3 User Guide.
- *
If the upload was created using server-side encryption with Key Management Service
- * (KMS) keys (SSE-KMS) or dual-layer server-side encryption with
- * Amazon Web Services KMS keys (DSSE-KMS), you must have permission to the
- * kms:Decrypt action for the ListParts request to
- * succeed.
+ * General purpose bucket permissions - For information
+ * about permissions required to use the multipart upload API, see Multipart Upload and Permissions in
+ * the Amazon S3 User Guide.
+ *
If the upload was created using server-side encryption with Key Management Service (KMS) keys
+ * (SSE-KMS) or dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), you must have
+ * permission to the kms:Decrypt action for the ListParts request to
+ * succeed.
*
*
*
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAccelerateConfigurationCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAccelerateConfigurationCommand.d.ts
index 24700fec..837763a3 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAccelerateConfigurationCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAccelerateConfigurationCommand.d.ts
@@ -1,6 +1,6 @@
import { Command as $Command } from "@smithy/smithy-client";
import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketAccelerateConfigurationRequest } from "../models/models_0";
+import { PutBucketAccelerateConfigurationRequest } from "../models/models_1";
import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
/**
* @public
@@ -31,14 +31,12 @@ declare const PutBucketAccelerateConfigurationCommand_base: {
*
This operation is not supported for directory buckets.
*
*
Sets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a
- * bucket-level feature that enables you to perform faster data transfers to Amazon S3.
+ * bucket-level feature that enables you to perform faster data transfers to Amazon S3.
*
After setting the Transfer Acceleration state of a bucket to Enabled, it might take up
- * to thirty minutes before the data transfer rates to the bucket increase.
- *
The name of the bucket used for Transfer Acceleration must be DNS-compliant and must
- * not contain periods (".").
After setting the Transfer Acceleration state of a bucket to Enabled, it might take up to thirty
+ * minutes before the data transfer rates to the bucket increase.
+ *
The name of the bucket used for Transfer Acceleration must be DNS-compliant and must not contain
+ * periods (".").
The following operations are related to PutBucketAccelerateConfiguration:
*
*
*
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAclCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAclCommand.d.ts
index 41e077e3..a55e8af4 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAclCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAclCommand.d.ts
@@ -1,6 +1,6 @@
import { Command as $Command } from "@smithy/smithy-client";
import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketAclRequest } from "../models/models_0";
+import { PutBucketAclRequest } from "../models/models_1";
import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
/**
* @public
@@ -38,9 +38,9 @@ declare const PutBucketAclCommand_base: {
*
*
This operation is not supported for directory buckets.
*
- *
Sets the permissions on an existing bucket using access control lists (ACL). For more
- * information, see Using ACLs. To set the ACL of a
- * bucket, you must have the WRITE_ACP permission.
+ *
Sets the permissions on an existing bucket using access control lists (ACL). For more information,
+ * see Using ACLs. To
+ * set the ACL of a bucket, you must have the WRITE_ACP permission.
*
You can use one of the following two ways to set a bucket's permissions:
You cannot specify access permission using both the body and the request
- * headers.
+ *
You cannot specify access permission using both the body and the request headers.
*
- *
Depending on your application needs, you may choose to set the ACL on a bucket using
- * either the request body or the headers. For example, if you have an existing application
- * that updates a bucket ACL using the request body, then you can continue to use that
- * approach.
+ *
Depending on your application needs, you may choose to set the ACL on a bucket using either the
+ * request body or the headers. For example, if you have an existing application that updates a bucket ACL
+ * using the request body, then you can continue to use that approach.
*
- *
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs
- * are disabled and no longer affect permissions. You must use policies to grant access to
- * your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return
- * the AccessControlListNotSupported error code. Requests to read ACLs are
- * still supported. For more information, see Controlling object
- * ownership in the Amazon S3 User Guide.
+ *
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled
+ * and no longer affect permissions. You must use policies to grant access to your bucket and the objects
+ * in it. Requests to set ACLs or update ACLs fail and return the
+ * AccessControlListNotSupported error code. Requests to read ACLs are still supported.
+ * For more information, see Controlling object ownership in
+ * the Amazon S3 User Guide.
You can set access permissions by using one of the following methods:
*
*
- *
Specify a canned ACL with the x-amz-acl request header. Amazon S3
- * supports a set of predefined ACLs, known as canned
- * ACLs. Each canned ACL has a predefined set of grantees and
- * permissions. Specify the canned ACL name as the value of
- * x-amz-acl. If you use this header, you cannot use other
- * access control-specific headers in your request. For more information, see
- * Canned
- * ACL.
+ *
Specify a canned ACL with the x-amz-acl request header. Amazon S3 supports a set
+ * of predefined ACLs, known as canned ACLs. Each canned ACL has a
+ * predefined set of grantees and permissions. Specify the canned ACL name as the value of
+ * x-amz-acl. If you use this header, you cannot use other access control-specific
+ * headers in your request. For more information, see Canned ACL.
*
*
- *
Specify access permissions explicitly with the
- * x-amz-grant-read, x-amz-grant-read-acp,
- * x-amz-grant-write-acp, and
- * x-amz-grant-full-control headers. When using these headers,
- * you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3
- * groups) who will receive the permission. If you use these ACL-specific
- * headers, you cannot use the x-amz-acl header to set a canned
- * ACL. These parameters map to the set of permissions that Amazon S3 supports in an
- * ACL. For more information, see Access Control List (ACL)
- * Overview.
- *
You specify each grantee as a type=value pair, where the type is one of
- * the following:
+ *
Specify access permissions explicitly with the x-amz-grant-read,
+ * x-amz-grant-read-acp, x-amz-grant-write-acp, and
+ * x-amz-grant-full-control headers. When using these headers, you specify
+ * explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who will receive the
+ * permission. If you use these ACL-specific headers, you cannot use the x-amz-acl
+ * header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports
+ * in an ACL. For more information, see Access Control List (ACL)
+ * Overview.
+ *
You specify each grantee as a type=value pair, where the type is one of the
+ * following:
*
*
*
- * id – if the value specified is the canonical user ID
- * of an Amazon Web Services account
+ * id – if the value specified is the canonical user ID of an
+ * Amazon Web Services account
*
*
*
- * uri – if you are granting permissions to a predefined
- * group
+ * uri – if you are granting permissions to a predefined group
*
*
*
- * emailAddress – if the value specified is the email
- * address of an Amazon Web Services account
+ * emailAddress – if the value specified is the email address of an
+ * Amazon Web Services account
*
*
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
For example, the following x-amz-grant-write header grants
- * create, overwrite, and delete objects permission to LogDelivery group
- * predefined by Amazon S3 and two Amazon Web Services accounts identified by their email
- * addresses.
+ *
For example, the following x-amz-grant-write header grants create, overwrite,
+ * and delete objects permission to LogDelivery group predefined by Amazon S3 and two Amazon Web Services accounts
+ * identified by their email addresses.
You can use either a canned ACL or specify access permissions explicitly. You
- * cannot do both.
+ *
You can use either a canned ACL or specify access permissions explicitly. You cannot do
+ * both.
*
*
Grantee Values
*
- *
You can specify the person (grantee) to whom you're assigning access rights
- * (using request elements) in the following ways. For examples of how to specify these
- * grantee values in JSON format, see the Amazon Web Services CLI example in
- * Enabling Amazon S3 server access logging in the
- * Amazon S3 User Guide.
+ *
You can specify the person (grantee) to whom you're assigning access rights (using request
+ * elements) in the following ways. For examples of how to specify these grantee values in JSON
+ * format, see the Amazon Web Services CLI example in Enabling Amazon S3 server
+ * access logging in the Amazon S3 User Guide.
The grantee is resolved to the CanonicalUser and, in a response to a GET
- * Object acl request, appears as the CanonicalUser.
+ *
The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl
+ * request, appears as the CanonicalUser.
*
*
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
*
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAnalyticsConfigurationCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAnalyticsConfigurationCommand.d.ts
index ab244f7d..e96236dc 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAnalyticsConfigurationCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutBucketAnalyticsConfigurationCommand.d.ts
@@ -1,6 +1,6 @@
import { Command as $Command } from "@smithy/smithy-client";
import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketAnalyticsConfigurationRequest } from "../models/models_0";
+import { PutBucketAnalyticsConfigurationRequest } from "../models/models_1";
import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
/**
* @public
@@ -30,26 +30,25 @@ declare const PutBucketAnalyticsConfigurationCommand_base: {
*
*
This operation is not supported for directory buckets.
*
- *
Sets an analytics configuration for the bucket (specified by the analytics configuration
- * ID). You can have up to 1,000 analytics configurations per bucket.
- *
You can choose to have storage class analysis export analysis reports sent to a
- * comma-separated values (CSV) flat file. See the DataExport request element.
- * Reports are updated daily and are based on the object filters that you configure. When
- * selecting data export, you specify a destination bucket and an optional destination prefix
- * where the file is written. You can export the data to a destination bucket in a different
- * account. However, the destination bucket must be in the same Region as the bucket that you
- * are making the PUT analytics configuration to. For more information, see Amazon S3
- * Analytics – Storage Class Analysis.
+ *
Sets an analytics configuration for the bucket (specified by the analytics configuration ID). You
+ * can have up to 1,000 analytics configurations per bucket.
+ *
You can choose to have storage class analysis export analysis reports sent to a comma-separated
+ * values (CSV) flat file. See the DataExport request element. Reports are updated daily and
+ * are based on the object filters that you configure. When selecting data export, you specify a
+ * destination bucket and an optional destination prefix where the file is written. You can export the data
+ * to a destination bucket in a different account. However, the destination bucket must be in the same
+ * Region as the bucket that you are making the PUT analytics configuration to. For more information, see
+ * Amazon S3 Analytics –
+ * Storage Class Analysis.
- * Cause: You are attempting to create a new configuration but have
- * already reached the 1,000-configuration limit.
+ * Cause: You are attempting to create a new configuration but have already reached
+ * the 1,000-configuration limit.
*
- * Cause: You are not the owner of the specified bucket, or you do
- * not have the s3:PutAnalyticsConfiguration bucket permission to set the
- * configuration on the bucket.
+ * Cause: You are not the owner of the specified bucket, or you do not have the
+ * s3:PutAnalyticsConfiguration bucket permission to set the configuration on the
+ * bucket.
*
*
*
*
*
- *
The following operations are related to
- * PutBucketAnalyticsConfiguration:
+ *
The following operations are related to PutBucketAnalyticsConfiguration:
This operation is not supported for directory buckets.
*
- *
Sets the cors configuration for your bucket. If the configuration exists,
- * Amazon S3 replaces it.
- *
To use this operation, you must be allowed to perform the s3:PutBucketCORS
- * action. By default, the bucket owner has this permission and can grant it to others.
- *
You set this configuration on a bucket so that the bucket can service cross-origin
- * requests. For example, you might want to enable a request whose origin is
- * http://www.example.com to access your Amazon S3 bucket at
- * my.example.bucket.com by using the browser's XMLHttpRequest
- * capability.
- *
To enable cross-origin resource sharing (CORS) on a bucket, you add the
- * cors subresource to the bucket. The cors subresource is an XML
- * document in which you configure rules that identify origins and the HTTP methods that can
- * be executed on your bucket. The document is limited to 64 KB in size.
- *
When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a
- * bucket, it evaluates the cors configuration on the bucket and uses the first
- * CORSRule rule that matches the incoming browser request to enable a
- * cross-origin request. For a rule to match, the following conditions must be met:
+ *
Sets the cors configuration for your bucket. If the configuration exists, Amazon S3 replaces
+ * it.
+ *
To use this operation, you must be allowed to perform the s3:PutBucketCORS action. By
+ * default, the bucket owner has this permission and can grant it to others.
+ *
You set this configuration on a bucket so that the bucket can service cross-origin requests. For
+ * example, you might want to enable a request whose origin is http://www.example.com to
+ * access your Amazon S3 bucket at my.example.bucket.com by using the browser's
+ * XMLHttpRequest capability.
+ *
To enable cross-origin resource sharing (CORS) on a bucket, you add the cors
+ * subresource to the bucket. The cors subresource is an XML document in which you configure
+ * rules that identify origins and the HTTP methods that can be executed on your bucket. The document is
+ * limited to 64 KB in size.
+ *
When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a bucket, it
+ * evaluates the cors configuration on the bucket and uses the first CORSRule
+ * rule that matches the incoming browser request to enable a cross-origin request. For a rule to match,
+ * the following conditions must be met:
*
*
- *
The request's Origin header must match AllowedOrigin
- * elements.
+ *
The request's Origin header must match AllowedOrigin elements.
*
*
*
The request method (for example, GET, PUT, HEAD, and so on) or the
- * Access-Control-Request-Method header in case of a pre-flight
- * OPTIONS request must be one of the AllowedMethod
- * elements.
+ * Access-Control-Request-Method header in case of a pre-flight OPTIONS
+ * request must be one of the AllowedMethod elements.
*
*
- *
Every header specified in the Access-Control-Request-Headers request
- * header of a pre-flight request must match an AllowedHeader element.
- *
+ *
Every header specified in the Access-Control-Request-Headers request header of a
+ * pre-flight request must match an AllowedHeader element.
This operation configures default encryption and Amazon S3 Bucket Keys for an existing
- * bucket.
+ *
This operation configures default encryption and Amazon S3 Bucket Keys for an existing bucket.
*
*
* Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name
@@ -37,8 +36,8 @@ declare const PutBucketEncryptionCommand_base: {
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
*
- *
By default, all buckets have a default encryption configuration that uses server-side
- * encryption with Amazon S3 managed keys (SSE-S3).
+ *
By default, all buckets have a default encryption configuration that uses server-side encryption
+ * with Amazon S3 managed keys (SSE-S3).
You can optionally configure default encryption for a bucket by using
- * server-side encryption with Key Management Service (KMS) keys (SSE-KMS) or dual-layer
- * server-side encryption with Amazon Web Services KMS keys (DSSE-KMS). If you specify
- * default encryption by using SSE-KMS, you can also configure Amazon S3
- * Bucket Keys. For information about the bucket default encryption
- * feature, see Amazon S3 Bucket Default
- * Encryption in the Amazon S3 User Guide.
+ *
You can optionally configure default encryption for a bucket by using server-side
+ * encryption with Key Management Service (KMS) keys (SSE-KMS) or dual-layer server-side encryption with
+ * Amazon Web Services KMS keys (DSSE-KMS). If you specify default encryption by using SSE-KMS, you can also
+ * configure Amazon S3 Bucket
+ * Keys. For information about the bucket default encryption feature, see Amazon S3 Bucket Default
+ * Encryption in the Amazon S3 User Guide.
*
*
- *
If you use PutBucketEncryption to set your default bucket
- * encryption to SSE-KMS, you should verify that your KMS key ID
- * is correct. Amazon S3 doesn't validate the KMS key ID provided in
- * PutBucketEncryption requests.
+ *
If you use PutBucketEncryption to set your default bucket encryption to
+ * SSE-KMS, you should verify that your KMS key ID is correct. Amazon S3 doesn't validate the
+ * KMS key ID provided in PutBucketEncryption requests.
*
*
*
*
*
- * Directory buckets - You can
- * optionally configure default encryption for a bucket by using server-side
- * encryption with Key Management Service (KMS) keys (SSE-KMS).
+ * Directory buckets - You can optionally configure
+ * default encryption for a bucket by using server-side encryption with Key Management Service (KMS) keys
+ * (SSE-KMS).
*
*
- *
We recommend that the bucket's default encryption uses the desired
- * encryption configuration and you don't override the bucket default
- * encryption in your CreateSession requests or PUT
- * object requests. Then, new objects are automatically encrypted with the
- * desired encryption settings.
- * For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
+ *
We recommend that the bucket's default encryption uses the desired encryption
+ * configuration and you don't override the bucket default encryption in your
+ * CreateSession requests or PUT object requests. Then, new objects
+ * are automatically encrypted with the desired encryption settings.
+ * For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
*
*
*
Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime.
@@ -91,21 +87,21 @@ declare const PutBucketEncryptionCommand_base: {
*
When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.
*
*
- *
For directory buckets, if you use PutBucketEncryption to set your default bucket encryption to SSE-KMS, Amazon S3 validates the
- * KMS key ID provided in PutBucketEncryption requests.
+ *
For directory buckets, if you use PutBucketEncryption to set your default bucket
+ * encryption to SSE-KMS, Amazon S3 validates the KMS key ID provided in
+ * PutBucketEncryption requests.
*
*
*
*
*
*
- *
If you're specifying a customer managed KMS key, we recommend using a fully
- * qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the
- * key within the requester’s account. This behavior can result in data that's encrypted
- * with a KMS key that belongs to the requester, and not the bucket owner.
If you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key
+ * ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester’s account.
+ * This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and
+ * not the bucket owner.
* General purpose bucket permissions - The
- * s3:PutEncryptionConfiguration permission is required in a
- * policy. The bucket owner has this permission by default. The bucket owner
- * can grant this permission to others. For more information about permissions,
- * see Permissions Related to Bucket Operations and Managing Access
- * Permissions to Your Amazon S3 Resources in the
- * Amazon S3 User Guide.
- * Directory bucket permissions -
- * To grant access to this API operation, you must have the
- * s3express:PutEncryptionConfiguration permission in
- * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
- *
To set a directory bucket default encryption with SSE-KMS, you must also
- * have the kms:GenerateDataKey and the kms:Decrypt
- * permissions in IAM identity-based policies and KMS key policies for the
- * target KMS key.
+ * Directory bucket permissions - To grant access to
+ * this API operation, you must have the s3express:PutEncryptionConfiguration
+ * permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ *
To set a directory bucket default encryption with SSE-KMS, you must also have the
+ * kms:GenerateDataKey and the kms:Decrypt permissions in IAM
+ * identity-based policies and KMS key policies for the target KMS key.
This operation is not supported for directory buckets.
*
- *
Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to
- * 1,000 S3 Intelligent-Tiering configurations per bucket.
+ *
Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to 1,000
+ * S3 Intelligent-Tiering configurations per bucket.
*
The S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without performance impact or operational overhead. S3 Intelligent-Tiering delivers automatic cost savings in three low latency and high throughput access tiers. To get the lowest storage cost on data that can be accessed in minutes to hours, you can choose to activate additional archiving capabilities.
*
The S3 Intelligent-Tiering storage class is the ideal storage class for data with unknown, changing, or unpredictable access patterns, independent of object size or retention period. If the size of an object is less than 128 KB, it is not monitored and not eligible for auto-tiering. Smaller objects can be stored, but they are always charged at the Frequent Access tier rates in the S3 Intelligent-Tiering storage class.
You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically
- * move objects stored in the S3 Intelligent-Tiering storage class to the Archive Access
- * or Deep Archive Access tier.
+ *
You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically move objects
+ * stored in the S3 Intelligent-Tiering storage class to the Archive Access or Deep Archive Access
+ * tier.
*
*
- * PutBucketIntelligentTieringConfiguration has the following special
- * errors:
+ * PutBucketIntelligentTieringConfiguration has the following special errors:
*
- * Cause: You are attempting to create a new configuration
- * but have already reached the 1,000-configuration limit.
+ * Cause: You are attempting to create a new configuration but have already
+ * reached the 1,000-configuration limit.
*
*
HTTP 403 Forbidden Error
*
*
- * Cause: You are not the owner of the specified bucket, or
- * you do not have the s3:PutIntelligentTieringConfiguration bucket
- * permission to set the configuration on the bucket.
+ * Cause: You are not the owner of the specified bucket, or you do not have
+ * the s3:PutIntelligentTieringConfiguration bucket permission to set the configuration
+ * on the bucket.
*
This operation is not supported for directory buckets.
*
- *
This implementation of the PUT action adds an inventory configuration
- * (identified by the inventory ID) to the bucket. You can have up to 1,000 inventory
- * configurations per bucket.
- *
Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly
- * basis, and the results are published to a flat file. The bucket that is inventoried is
- * called the source bucket, and the bucket where the inventory flat file
- * is stored is called the destination bucket. The
- * destination bucket must be in the same Amazon Web Services Region as the
- * source bucket.
- *
When you configure an inventory for a source bucket, you specify
- * the destination bucket where you want the inventory to be stored, and
- * whether to generate the inventory daily or weekly. You can also configure what object
- * metadata to include and whether to inventory all object versions or only current versions.
- * For more information, see Amazon S3 Inventory in the
- * Amazon S3 User Guide.
+ *
This implementation of the PUT action adds an S3 Inventory configuration (identified by
+ * the inventory ID) to the bucket. You can have up to 1,000 inventory configurations per bucket.
+ *
Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly basis, and
+ * the results are published to a flat file. The bucket that is inventoried is called the
+ * source bucket, and the bucket where the inventory flat file is stored is called
+ * the destination bucket. The destination bucket must be in the
+ * same Amazon Web Services Region as the source bucket.
+ *
When you configure an inventory for a source bucket, you specify the
+ * destination bucket where you want the inventory to be stored, and whether to
+ * generate the inventory daily or weekly. You can also configure what object metadata to include and
+ * whether to inventory all object versions or only current versions. For more information, see Amazon S3 Inventory in the
+ * Amazon S3 User Guide.
To use this operation, you must have permission to perform the
- * s3:PutInventoryConfiguration action. The bucket owner has this
- * permission by default and can grant this permission to others.
- *
The s3:PutInventoryConfiguration permission allows a user to
- * create an S3 Inventory
- * report that includes all object metadata fields available and to specify the
- * destination bucket to store the inventory. A user with read access to objects in
- * the destination bucket can also access all object metadata fields that are
- * available in the inventory report.
+ * s3:PutInventoryConfiguration action. The bucket owner has this permission by
+ * default and can grant this permission to others.
+ *
The s3:PutInventoryConfiguration permission allows a user to create an S3 Inventory
+ * report that includes all object metadata fields available and to specify the destination bucket to
+ * store the inventory. A user with read access to objects in the destination bucket can also access
+ * all object metadata fields that are available in the inventory report.
- * Cause: You are attempting to create a new configuration
- * but have already reached the 1,000-configuration limit.
+ * Cause: You are attempting to create a new configuration but have already
+ * reached the 1,000-configuration limit.
*
*
HTTP 403 Forbidden Error
*
*
- * Cause: You are not the owner of the specified bucket, or
- * you do not have the s3:PutInventoryConfiguration bucket permission to
- * set the configuration on the bucket.
+ * Cause: You are not the owner of the specified bucket, or you do not have
+ * the s3:PutInventoryConfiguration bucket permission to set the configuration on the
+ * bucket.
*
*
- *
The following operations are related to
- * PutBucketInventoryConfiguration:
+ *
The following operations are related to PutBucketInventoryConfiguration:
Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle
- * configuration. Keep in mind that this will overwrite an existing lifecycle configuration,
- * so if you want to retain any configuration details, they must be included in the new
- * lifecycle configuration. For information about lifecycle configuration, see Managing
- * your storage lifecycle.
+ * configuration. Keep in mind that this will overwrite an existing lifecycle configuration, so if you want
+ * to retain any configuration details, they must be included in the new lifecycle configuration. For
+ * information about lifecycle configuration, see Managing your storage
+ * lifecycle.
*
- *
Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, object size, or any combination of these. Accordingly, this section describes the latest API. The previous version of the API supported filtering based only on an object key name prefix, which is supported for backward compatibility.
- * For the related API description, see PutBucketLifecycle.
+ *
Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name
+ * prefix, one or more object tags, object size, or any combination of these. Accordingly, this section
+ * describes the latest API. The previous version of the API supported filtering based only on an object
+ * key name prefix, which is supported for backward compatibility. For the related API description, see
+ * PutBucketLifecycle.
*
*
*
Rules
*
Permissions
*
HTTP Host header syntax
*
- *
You specify the lifecycle configuration in your request body. The lifecycle
- * configuration is specified as XML consisting of one or more rules. An Amazon S3
- * Lifecycle configuration can have up to 1,000 rules. This limit is not
- * adjustable.
- *
Bucket lifecycle configuration supports specifying a lifecycle rule using an
- * object key name prefix, one or more object tags, object size, or any combination
- * of these. Accordingly, this section describes the latest API. The previous version
- * of the API supported filtering based only on an object key name prefix, which is
- * supported for backward compatibility for general purpose buckets. For the related
- * API description, see PutBucketLifecycle.
+ *
You specify the lifecycle configuration in your request body. The lifecycle configuration is
+ * specified as XML consisting of one or more rules. An Amazon S3 Lifecycle configuration can have up to
+ * 1,000 rules. This limit is not adjustable.
+ *
Bucket lifecycle configuration supports specifying a lifecycle rule using an object key name
+ * prefix, one or more object tags, object size, or any combination of these. Accordingly, this
+ * section describes the latest API. The previous version of the API supported filtering based only
+ * on an object key name prefix, which is supported for backward compatibility for general purpose
+ * buckets. For the related API description, see PutBucketLifecycle.
*
- *
Lifecyle configurations for directory buckets only support expiring objects and
- * cancelling multipart uploads. Expiring of versioned objects,transitions and tag
- * filters are not supported.
+ *
Lifecyle configurations for directory buckets only support expiring objects and cancelling
+ * multipart uploads. Expiring of versioned objects,transitions and tag filters are not
+ * supported.
*
*
A lifecycle rule consists of the following:
*
*
- *
A filter identifying a subset of objects to which the rule applies. The
- * filter can be based on a key name prefix, object tags, object size, or any
- * combination of these.
+ *
A filter identifying a subset of objects to which the rule applies. The filter can be
+ * based on a key name prefix, object tags, object size, or any combination of these.
*
*
*
A status indicating whether the rule is in effect.
*
*
- *
One or more lifecycle transition and expiration actions that you want
- * Amazon S3 to perform on the objects identified by the filter. If the state of
- * your bucket is versioning-enabled or versioning-suspended, you can have many
- * versions of the same object (one current version and zero or more noncurrent
- * versions). Amazon S3 provides predefined actions that you can specify for current
- * and noncurrent object versions.
+ *
One or more lifecycle transition and expiration actions that you want Amazon S3 to perform on
+ * the objects identified by the filter. If the state of your bucket is versioning-enabled or
+ * versioning-suspended, you can have many versions of the same object (one current version and
+ * zero or more noncurrent versions). Amazon S3 provides predefined actions that you can specify for
+ * current and noncurrent object versions.
- * General purpose bucket permissions - By
- * default, all Amazon S3 resources are private, including buckets, objects, and
- * related subresources (for example, lifecycle configuration and website
- * configuration). Only the resource owner (that is, the Amazon Web Services account that
- * created it) can access the resource. The resource owner can optionally grant
- * access permissions to others by writing an access policy. For this
- * operation, a user must have the s3:PutLifecycleConfiguration
- * permission.
- *
You can also explicitly deny permissions. An explicit deny also
- * supersedes any other permissions. If you want to block users or accounts
- * from removing or deleting objects from your bucket, you must deny them
- * permissions for the following actions:
+ * General purpose bucket permissions - By default, all Amazon S3
+ * resources are private, including buckets, objects, and related subresources (for example,
+ * lifecycle configuration and website configuration). Only the resource owner (that is, the
+ * Amazon Web Services account that created it) can access the resource. The resource owner can optionally
+ * grant access permissions to others by writing an access policy. For this operation, a user
+ * must have the s3:PutLifecycleConfiguration permission.
+ *
You can also explicitly deny permissions. An explicit deny also supersedes any other
+ * permissions. If you want to block users or accounts from removing or deleting objects from
+ * your bucket, you must deny them permissions for the following actions:
- * Directory bucket permissions -
- * You must have the s3express:PutLifecycleConfiguration
- * permission in an IAM identity-based policy to use this operation.
- * Cross-account access to this API operation isn't supported. The resource
- * owner can optionally grant access permissions to others by creating a role
- * or user for them as long as they are within the same account as the owner
- * and resource.
+ * Directory bucket permissions - You must have the
+ * s3express:PutLifecycleConfiguration permission in an IAM identity-based policy
+ * to use this operation. Cross-account access to this API operation isn't supported. The
+ * resource owner can optionally grant access permissions to others by creating a role or user
+ * for them as long as they are within the same account as the owner and resource.
+ *
* Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name
@@ -142,11 +135,9 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
*
*
*
- * Directory buckets - The HTTP Host
- * header syntax is
- * s3express-control.region.amazonaws.com.
- *
The following operations are related to
- * PutBucketLifecycleConfiguration:
+ * Directory buckets - The HTTP Host header syntax is
+ * s3express-control.region.amazonaws.com.
+ *
The following operations are related to PutBucketLifecycleConfiguration:
This operation is not supported for directory buckets.
*
- *
Set the logging parameters for a bucket and to specify permissions for who can view and
- * modify the logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as
- * the source bucket. To set the logging status of a bucket, you must be the bucket
- * owner.
- *
The bucket owner is automatically granted FULL_CONTROL to all logs. You use the
- * Grantee request element to grant access to other people. The
- * Permissions request element specifies the kind of access the grantee has to
- * the logs.
+ *
Set the logging parameters for a bucket and to specify permissions for who can view and modify the
+ * logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as the source bucket. To set
+ * the logging status of a bucket, you must be the bucket owner.
+ *
The bucket owner is automatically granted FULL_CONTROL to all logs. You use the Grantee
+ * request element to grant access to other people. The Permissions request element specifies
+ * the kind of access the grantee has to the logs.
*
- *
If the target bucket for log delivery uses the bucket owner enforced setting for S3
- * Object Ownership, you can't use the Grantee request element to grant access
- * to others. Permissions can only be granted using policies. For more information, see
- * Permissions for server access log delivery in the
- * Amazon S3 User Guide.
+ *
If the target bucket for log delivery uses the bucket owner enforced setting for S3 Object
+ * Ownership, you can't use the Grantee request element to grant access to others.
+ * Permissions can only be granted using policies. For more information, see Permissions for server access log delivery in the
+ * Amazon S3 User Guide.
*
*
*
Grantee Values
*
- *
You can specify the person (grantee) to whom you're assigning access rights (by
- * using request elements) in the following ways. For examples of how to specify these
- * grantee values in JSON format, see the Amazon Web Services CLI example in
- * Enabling Amazon S3 server access logging in the
- * Amazon S3 User Guide.
+ *
You can specify the person (grantee) to whom you're assigning access rights (by using request
+ * elements) in the following ways. For examples of how to specify these grantee values in JSON
+ * format, see the Amazon Web Services CLI example in Enabling Amazon S3 server
+ * access logging in the Amazon S3 User Guide.
To enable logging, you use LoggingEnabled and its children request
- * elements. To disable logging, you use an empty BucketLoggingStatus request
- * element:
+ *
To enable logging, you use LoggingEnabled and its children request elements. To disable
+ * logging, you use an empty BucketLoggingStatus request element:
*
- *
+ *
*
*
For more information about server access logging, see Server Access Logging in the
- * Amazon S3 User Guide.
- *
For more information about creating a bucket, see CreateBucket. For more
- * information about returning the logging status of a bucket, see GetBucketLogging.
+ * Amazon S3 User Guide.
+ *
For more information about creating a bucket, see CreateBucket. For more information about
+ * returning the logging status of a bucket, see GetBucketLogging.
*
The following operations are related to PutBucketLogging:
This operation is not supported for directory buckets.
*
- *
Sets a metrics configuration (specified by the metrics configuration ID) for the bucket.
- * You can have up to 1,000 metrics configurations per bucket. If you're updating an existing
- * metrics configuration, note that this is a full replacement of the existing metrics
- * configuration. If you don't include the elements you want to keep, they are erased.
+ *
Sets a metrics configuration (specified by the metrics configuration ID) for the bucket. You can
+ * have up to 1,000 metrics configurations per bucket. If you're updating an existing metrics
+ * configuration, note that this is a full replacement of the existing metrics configuration. If you don't
+ * include the elements you want to keep, they are erased.
This operation is not supported for directory buckets.
*
*
Enables notifications of specified events for a bucket. For more information about event
- * notifications, see Configuring Event
- * Notifications.
- *
Using this API, you can replace an existing notification configuration. The
- * configuration is an XML file that defines the event types that you want Amazon S3 to publish and
- * the destination where you want Amazon S3 to publish an event notification when it detects an
- * event of the specified type.
Using this API, you can replace an existing notification configuration. The configuration is an XML
+ * file that defines the event types that you want Amazon S3 to publish and the destination where you want Amazon S3
+ * to publish an event notification when it detects an event of the specified type.
*
By default, your bucket has no event notifications configured. That is, the notification
- * configuration will be an empty NotificationConfiguration.
+ * configuration will be an empty NotificationConfiguration.
*
*
*
*
*
*
- *
This action replaces the existing notification configuration with the configuration you
- * include in the request body.
- *
After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification
- * Service (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and
- * that the bucket owner has permission to publish to it by sending a test notification. In
- * the case of Lambda destinations, Amazon S3 verifies that the Lambda function permissions
- * grant Amazon S3 permission to invoke the function from the Amazon S3 bucket. For more information,
- * see Configuring Notifications for Amazon S3 Events.
- *
You can disable notifications by adding the empty NotificationConfiguration
- * element.
- *
For more information about the number of event notification configurations that you can
- * create per bucket, see Amazon S3 service quotas in Amazon Web Services
- * General Reference.
- *
By default, only the bucket owner can configure notifications on a bucket. However,
- * bucket owners can use a bucket policy to grant permission to other users to set this
- * configuration with the required s3:PutBucketNotification permission.
+ *
This action replaces the existing notification configuration with the configuration you include in
+ * the request body.
+ *
After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification Service
+ * (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and that the bucket owner
+ * has permission to publish to it by sending a test notification. In the case of Lambda destinations,
+ * Amazon S3 verifies that the Lambda function permissions grant Amazon S3 permission to invoke the function from the
+ * Amazon S3 bucket. For more information, see Configuring Notifications for Amazon S3
+ * Events.
+ *
You can disable notifications by adding the empty NotificationConfiguration element.
+ *
For more information about the number of event notification configurations that you can create per
+ * bucket, see Amazon S3 service
+ * quotas in Amazon Web Services General Reference.
+ *
By default, only the bucket owner can configure notifications on a bucket. However, bucket owners
+ * can use a bucket policy to grant permission to other users to set this configuration with the required
+ * s3:PutBucketNotification permission.
*
- *
The PUT notification is an atomic operation. For example, suppose your notification
- * configuration includes SNS topic, SQS queue, and Lambda function configurations. When
- * you send a PUT request with this configuration, Amazon S3 sends test messages to your SNS
- * topic. If the message fails, the entire PUT action will fail, and Amazon S3 will not add the
- * configuration to your bucket.
+ *
The PUT notification is an atomic operation. For example, suppose your notification configuration
+ * includes SNS topic, SQS queue, and Lambda function configurations. When you send a PUT request with
+ * this configuration, Amazon S3 sends test messages to your SNS topic. If the message fails, the entire PUT
+ * action will fail, and Amazon S3 will not add the configuration to your bucket.
*
- *
If the configuration in the request body includes only one
- * TopicConfiguration specifying only the
- * s3:ReducedRedundancyLostObject event type, the response will also include
- * the x-amz-sns-test-message-id header containing the message ID of the test
- * notification sent to the topic.
- *
The following action is related to
- * PutBucketNotificationConfiguration:
+ *
If the configuration in the request body includes only one TopicConfiguration
+ * specifying only the s3:ReducedRedundancyLostObject event type, the response will also
+ * include the x-amz-sns-test-message-id header containing the message ID of the test
+ * notification sent to the topic.
+ *
The following action is related to PutBucketNotificationConfiguration:
This operation is not supported for directory buckets.
*
- *
Creates or modifies OwnershipControls for an Amazon S3 bucket. To use this
- * operation, you must have the s3:PutBucketOwnershipControls permission. For
- * more information about Amazon S3 permissions, see Specifying permissions in a
- * policy.
Creates or modifies OwnershipControls for an Amazon S3 bucket. To use this operation, you
+ * must have the s3:PutBucketOwnershipControls permission. For more information about Amazon S3
+ * permissions, see Specifying permissions in a policy.
If you are using an identity other than the root user of the Amazon Web Services account that
- * owns the bucket, the calling identity must both have the
- * PutBucketPolicy permissions on the specified bucket and belong to
- * the bucket owner's account in order to use this operation.
- *
If you don't have PutBucketPolicy permissions, Amazon S3 returns a
- * 403 Access Denied error. If you have the correct permissions, but
- * you're not using an identity that belongs to the bucket owner's account, Amazon S3
- * returns a 405 Method Not Allowed error.
+ *
If you are using an identity other than the root user of the Amazon Web Services account that owns the
+ * bucket, the calling identity must both have the PutBucketPolicy permissions on the
+ * specified bucket and belong to the bucket owner's account in order to use this operation.
+ *
If you don't have PutBucketPolicy permissions, Amazon S3 returns a 403 Access
+ * Denied error. If you have the correct permissions, but you're not using an identity that
+ * belongs to the bucket owner's account, Amazon S3 returns a 405 Method Not Allowed
+ * error.
*
- *
To ensure that bucket owners don't inadvertently lock themselves out of
- * their own buckets, the root principal in a bucket owner's Amazon Web Services account can
- * perform the GetBucketPolicy, PutBucketPolicy, and
- * DeleteBucketPolicy API actions, even if their bucket policy
- * explicitly denies the root principal's access. Bucket owner root principals can
- * only be blocked from performing these API actions by VPC endpoint policies and
- * Amazon Web Services Organizations policies.
+ *
To ensure that bucket owners don't inadvertently lock themselves out of their own buckets,
+ * the root principal in a bucket owner's Amazon Web Services account can perform the
+ * GetBucketPolicy, PutBucketPolicy, and
+ * DeleteBucketPolicy API actions, even if their bucket policy explicitly denies the
+ * root principal's access. Bucket owner root principals can only be blocked from performing these
+ * API actions by VPC endpoint policies and Amazon Web Services Organizations policies.
*
*
*
*
* General purpose bucket permissions - The
- * s3:PutBucketPolicy permission is required in a policy. For
- * more information about general purpose buckets bucket policies, see Using Bucket Policies and User Policies in the
- * Amazon S3 User Guide.
+ * s3:PutBucketPolicy permission is required in a policy. For more information
+ * about general purpose buckets bucket policies, see Using Bucket Policies and User
+ * Policies in the Amazon S3 User Guide.
*
*
*
- * Directory bucket permissions -
- * To grant access to this API operation, you must have the
- * s3express:PutBucketPolicy permission in
- * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
+ * Directory bucket permissions - To grant access to
+ * this API operation, you must have the s3express:PutBucketPolicy permission in
+ * an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ * For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
*
*
*
*
Example bucket policies
*
*
- * General purpose buckets example bucket policies
- * - See Bucket policy
- * examples in the Amazon S3 User Guide.
+ * General purpose buckets example bucket policies - See Bucket policy
+ * examples in the Amazon S3 User Guide.
*
This operation is not supported for directory buckets.
*
- *
Creates a replication configuration or replaces an existing one. For more information,
- * see Replication in the Amazon S3 User Guide.
- *
Specify the replication configuration in the request body. In the replication
- * configuration, you provide the name of the destination bucket or buckets where you want
- * Amazon S3 to replicate objects, the IAM role that Amazon S3 can assume to replicate objects on your
- * behalf, and other relevant information. You can invoke this request for a specific Amazon Web Services
- * Region by using the
+ *
Specify the replication configuration in the request body. In the replication configuration, you
+ * provide the name of the destination bucket or buckets where you want Amazon S3 to replicate objects, the
+ * IAM role that Amazon S3 can assume to replicate objects on your behalf, and other relevant information. You
+ * can invoke this request for a specific Amazon Web Services Region by using the
* aws:RequestedRegion
* condition key.
- *
A replication configuration must include at least one rule, and can contain a maximum of
- * 1,000. Each rule identifies a subset of objects to replicate by filtering the objects in
- * the source bucket. To choose additional subsets of objects to replicate, add a rule for
- * each subset.
- *
To specify a subset of the objects in the source bucket to apply a replication rule to,
- * add the Filter element as a child of the Rule element. You can filter objects based on an
- * object key prefix, one or more object tags, or both. When you add the Filter element in the
- * configuration, you must also add the following elements:
- * DeleteMarkerReplication, Status, and
- * Priority.
+ *
A replication configuration must include at least one rule, and can contain a maximum of 1,000. Each
+ * rule identifies a subset of objects to replicate by filtering the objects in the source bucket. To
+ * choose additional subsets of objects to replicate, add a rule for each subset.
+ *
To specify a subset of the objects in the source bucket to apply a replication rule to, add the
+ * Filter element as a child of the Rule element. You can filter objects based on an object key prefix, one
+ * or more object tags, or both. When you add the Filter element in the configuration, you must also add
+ * the following elements: DeleteMarkerReplication, Status, and
+ * Priority.
*
- *
If you are using an earlier version of the replication configuration, Amazon S3 handles
- * replication of delete markers differently. For more information, see Backward Compatibility.
+ *
If you are using an earlier version of the replication configuration, Amazon S3 handles replication of
+ * delete markers differently. For more information, see Backward Compatibility.
*
*
For information about enabling versioning on a bucket, see Using Versioning.
*
*
Handling Replication of Encrypted Objects
*
- *
By default, Amazon S3 doesn't replicate objects that are stored at rest using
- * server-side encryption with KMS keys. To replicate Amazon Web Services KMS-encrypted objects,
- * add the following: SourceSelectionCriteria,
- * SseKmsEncryptedObjects, Status,
- * EncryptionConfiguration, and ReplicaKmsKeyID. For
- * information about replication configuration, see Replicating
- * Objects Created with SSE Using KMS keys.
+ *
By default, Amazon S3 doesn't replicate objects that are stored at rest using server-side
+ * encryption with KMS keys. To replicate Amazon Web Services KMS-encrypted objects, add the following:
+ * SourceSelectionCriteria, SseKmsEncryptedObjects, Status,
+ * EncryptionConfiguration, and ReplicaKmsKeyID. For information about
+ * replication configuration, see Replicating Objects Created
+ * with SSE Using KMS keys.
To create a PutBucketReplication request, you must have
- * s3:PutReplicationConfiguration permissions for the bucket.
+ * s3:PutReplicationConfiguration permissions for the bucket.
*
- *
This operation is not supported for directory buckets.
*
- *
Sets the request payment configuration for a bucket. By default, the bucket owner pays
- * for downloads from the bucket. This configuration parameter enables the bucket owner (only)
- * to specify that the person requesting the download will be charged for the download. For
- * more information, see Requester Pays
- * Buckets.
+ *
Sets the request payment configuration for a bucket. By default, the bucket owner pays for downloads
+ * from the bucket. This configuration parameter enables the bucket owner (only) to specify that the person
+ * requesting the download will be charged for the download. For more information, see Requester Pays
+ * Buckets.
*
The following operations are related to PutBucketRequestPayment:
This operation is not supported for directory buckets.
*
*
Sets the tags for a bucket.
- *
Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this,
- * sign up to get your Amazon Web Services account bill with tag key values included. Then, to see the cost
- * of combined resources, organize your billing information according to resources with the
- * same tag key values. For example, you can tag several resources with a specific application
- * name, and then organize your billing information to see the total cost of that application
- * across several services. For more information, see Cost Allocation and
- * Tagging and Using Cost Allocation in Amazon S3
- * Bucket Tags.
+ *
Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this, sign up to get
+ * your Amazon Web Services account bill with tag key values included. Then, to see the cost of combined resources,
+ * organize your billing information according to resources with the same tag key values. For example, you
+ * can tag several resources with a specific application name, and then organize your billing information
+ * to see the total cost of that application across several services. For more information, see Cost Allocation and
+ * Tagging and Using Cost Allocation in Amazon S3 Bucket Tags.
*
- *
When this operation sets the tags for a bucket, it will overwrite any current tags
- * the bucket already has. You cannot use this operation to add tags to an existing list of
- * tags.
+ *
When this operation sets the tags for a bucket, it will overwrite any current tags the bucket
+ * already has. You cannot use this operation to add tags to an existing list of tags.
+ * InvalidTag - The tag provided was not a valid tag. This error can occur if
+ * the tag did not pass input validation. For more information, see Using Cost Allocation in Amazon S3 Bucket
+ * Tags.
*
*
*
- * MalformedXML - The XML provided does not match the
- * schema.
+ * MalformedXML - The XML provided does not match the schema.
*
*
*
- * OperationAborted - A conflicting conditional action is
- * currently in progress against this resource. Please try again.
+ * OperationAborted - A conflicting conditional action is currently in progress
+ * against this resource. Please try again.
*
*
*
- * InternalError - The service was unable to apply the provided
- * tag to the bucket.
+ * InternalError - The service was unable to apply the provided tag to the
+ * bucket.
*
*
*
The following operations are related to PutBucketTagging:
This operation is not supported for directory buckets.
*
*
- *
When you enable versioning on a bucket for the first time, it might take a short
- * amount of time for the change to be fully propagated. While this change is propagating,
- * you might encounter intermittent HTTP 404 NoSuchKey errors for requests to
- * objects created or updated after enabling versioning. We recommend that you wait for 15
- * minutes after enabling versioning before issuing write operations (PUT or
- * DELETE) on objects in the bucket.
+ *
When you enable versioning on a bucket for the first time, it might take a short amount of time
+ * for the change to be fully propagated. While this change is propagating, you might encounter
+ * intermittent HTTP 404 NoSuchKey errors for requests to objects created or updated after
+ * enabling versioning. We recommend that you wait for 15 minutes after enabling versioning before
+ * issuing write operations (PUT or DELETE) on objects in the bucket.
*
*
Sets the versioning state of an existing bucket.
*
You can set the versioning state with one of the following values:
*
- * Enabled—Enables versioning for the objects in the
- * bucket. All objects added to the bucket receive a unique version ID.
+ * Enabled—Enables versioning for the objects in the bucket. All
+ * objects added to the bucket receive a unique version ID.
*
- * Suspended—Disables versioning for the objects in the
- * bucket. All objects added to the bucket receive the version ID null.
- *
If the versioning state has never been set on a bucket, it has no versioning state; a
- * GetBucketVersioning request does not return a versioning state value.
- *
In order to enable MFA Delete, you must be the bucket owner. If you are the bucket owner
- * and want to enable MFA Delete in the bucket versioning configuration, you must include the
- * x-amz-mfa request header and the Status and the
- * MfaDelete request elements in a request to set the versioning state of the
- * bucket.
+ * Suspended—Disables versioning for the objects in the bucket. All
+ * objects added to the bucket receive the version ID null.
+ *
If the versioning state has never been set on a bucket, it has no versioning state; a GetBucketVersioning request does not return a versioning state value.
+ *
In order to enable MFA Delete, you must be the bucket owner. If you are the bucket owner and want to
+ * enable MFA Delete in the bucket versioning configuration, you must include the x-amz-mfa
+ * request header and the Status and the MfaDelete request elements in a
+ * request to set the versioning state of the bucket.
*
- *
If you have an object expiration lifecycle configuration in your non-versioned bucket
- * and you want to maintain the same permanent delete behavior when you enable versioning,
- * you must add a noncurrent expiration policy. The noncurrent expiration lifecycle
- * configuration will manage the deletes of the noncurrent object versions in the
- * version-enabled bucket. (A version-enabled bucket maintains one current and zero or more
- * noncurrent object versions.) For more information, see Lifecycle and Versioning.
+ *
If you have an object expiration lifecycle configuration in your non-versioned bucket and you want
+ * to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent
+ * expiration policy. The noncurrent expiration lifecycle configuration will manage the deletes of the
+ * noncurrent object versions in the version-enabled bucket. (A version-enabled bucket maintains one
+ * current and zero or more noncurrent object versions.) For more information, see Lifecycle and
+ * Versioning.
*
*
The following operations are related to PutBucketVersioning:
This operation is not supported for directory buckets.
*
- *
Sets the configuration of the website that is specified in the website
- * subresource. To configure a bucket as a website, you can add this subresource on the bucket
- * with website configuration information such as the file name of the index document and any
- * redirect rules. For more information, see Hosting Websites on Amazon S3.
- *
This PUT action requires the S3:PutBucketWebsite permission. By default,
- * only the bucket owner can configure the website attached to a bucket; however, bucket
- * owners can allow other users to set the website configuration by writing a bucket policy
- * that grants them the S3:PutBucketWebsite permission.
- *
To redirect all website requests sent to the bucket's website endpoint, you add a
- * website configuration with the following elements. Because all requests are sent to another
- * website, you don't need to provide index document name for the bucket.
+ *
Sets the configuration of the website that is specified in the website subresource. To
+ * configure a bucket as a website, you can add this subresource on the bucket with website configuration
+ * information such as the file name of the index document and any redirect rules. For more information,
+ * see Hosting Websites on
+ * Amazon S3.
+ *
This PUT action requires the S3:PutBucketWebsite permission. By default, only the
+ * bucket owner can configure the website attached to a bucket; however, bucket owners can allow other
+ * users to set the website configuration by writing a bucket policy that grants them the
+ * S3:PutBucketWebsite permission.
+ *
To redirect all website requests sent to the bucket's website endpoint, you add a website
+ * configuration with the following elements. Because all requests are sent to another website, you don't
+ * need to provide index document name for the bucket.
If you want granular control over redirects, you can use the following elements to add
- * routing rules that describe conditions for redirecting requests and information about the
- * redirect destination. In this case, the website configuration must provide an index
- * document for the bucket, because some requests might not be redirected.
+ *
If you want granular control over redirects, you can use the following elements to add routing rules
+ * that describe conditions for redirecting requests and information about the redirect destination. In
+ * this case, the website configuration must provide an index document for the bucket, because some
+ * requests might not be redirected.
Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more
- * than 50 routing rules, you can use object redirect. For more information, see Configuring an
- * Object Redirect in the Amazon S3 User Guide.
+ *
Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more than 50
+ * routing rules, you can use object redirect. For more information, see Configuring an Object Redirect in the
+ * Amazon S3 User Guide.
*
The maximum request length is limited to 128 KB.
* @example
* Use a bare-bones client and the command you need to make an API call.
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectAclCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectAclCommand.d.ts
index 7a4a296d..a386ecde 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectAclCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectAclCommand.d.ts
@@ -30,23 +30,22 @@ declare const PutObjectAclCommand_base: {
*
*
This operation is not supported for directory buckets.
*
- *
Uses the acl subresource to set the access control list (ACL) permissions
- * for a new or existing object in an S3 bucket. You must have the WRITE_ACP
- * permission to set the ACL of an object. For more information, see What
- * permissions can I grant? in the Amazon S3 User Guide.
+ *
Uses the acl subresource to set the access control list (ACL) permissions for a new or
+ * existing object in an S3 bucket. You must have the WRITE_ACP permission to set the ACL of
+ * an object. For more information, see What permissions can I grant? in the
+ * Amazon S3 User Guide.
*
This functionality is not supported for Amazon S3 on Outposts.
- *
Depending on your application needs, you can choose to set the ACL on an object using
- * either the request body or the headers. For example, if you have an existing application
- * that updates a bucket ACL using the request body, you can continue to use that approach.
- * For more information, see Access Control List (ACL) Overview
- * in the Amazon S3 User Guide.
+ *
Depending on your application needs, you can choose to set the ACL on an object using either the
+ * request body or the headers. For example, if you have an existing application that updates a bucket ACL
+ * using the request body, you can continue to use that approach. For more information, see Access Control List (ACL)
+ * Overview in the Amazon S3 User Guide.
*
- *
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs
- * are disabled and no longer affect permissions. You must use policies to grant access to
- * your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return
- * the AccessControlListNotSupported error code. Requests to read ACLs are
- * still supported. For more information, see Controlling object
- * ownership in the Amazon S3 User Guide.
+ *
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled
+ * and no longer affect permissions. You must use policies to grant access to your bucket and the objects
+ * in it. Requests to set ACLs or update ACLs fail and return the
+ * AccessControlListNotSupported error code. Requests to read ACLs are still supported.
+ * For more information, see Controlling object ownership in
+ * the Amazon S3 User Guide.
You can set access permissions using one of the following methods:
*
*
- *
Specify a canned ACL with the x-amz-acl request header. Amazon S3
- * supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has
- * a predefined set of grantees and permissions. Specify the canned ACL name as
- * the value of x-amz-acl. If you use this header, you cannot use
- * other access control-specific headers in your request. For more information,
- * see Canned
- * ACL.
+ *
Specify a canned ACL with the x-amz-acl request header. Amazon S3 supports a set
+ * of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and
+ * permissions. Specify the canned ACL name as the value of x-amz-acl. If you use
+ * this header, you cannot use other access control-specific headers in your request. For more
+ * information, see Canned ACL.
*
*
- *
Specify access permissions explicitly with the
- * x-amz-grant-read, x-amz-grant-read-acp,
- * x-amz-grant-write-acp, and
- * x-amz-grant-full-control headers. When using these headers,
- * you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3
- * groups) who will receive the permission. If you use these ACL-specific
- * headers, you cannot use x-amz-acl header to set a canned ACL.
- * These parameters map to the set of permissions that Amazon S3 supports in an ACL.
- * For more information, see Access Control List (ACL)
- * Overview.
- *
You specify each grantee as a type=value pair, where the type is one of
- * the following:
+ *
Specify access permissions explicitly with the x-amz-grant-read,
+ * x-amz-grant-read-acp, x-amz-grant-write-acp, and
+ * x-amz-grant-full-control headers. When using these headers, you specify
+ * explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who will receive the
+ * permission. If you use these ACL-specific headers, you cannot use x-amz-acl
+ * header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports
+ * in an ACL. For more information, see Access Control List (ACL)
+ * Overview.
+ *
You specify each grantee as a type=value pair, where the type is one of the
+ * following:
*
*
*
- * id – if the value specified is the canonical user ID
- * of an Amazon Web Services account
+ * id – if the value specified is the canonical user ID of an
+ * Amazon Web Services account
*
*
*
- * uri – if you are granting permissions to a predefined
- * group
+ * uri – if you are granting permissions to a predefined group
*
*
*
- * emailAddress – if the value specified is the email
- * address of an Amazon Web Services account
+ * emailAddress – if the value specified is the email address of an
+ * Amazon Web Services account
*
*
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
For example, the following x-amz-grant-read header grants
- * list objects permission to the two Amazon Web Services accounts identified by their email
- * addresses.
+ *
For example, the following x-amz-grant-read header grants list objects
+ * permission to the two Amazon Web Services accounts identified by their email addresses.
You can use either a canned ACL or specify access permissions explicitly. You
- * cannot do both.
+ *
You can use either a canned ACL or specify access permissions explicitly. You cannot do
+ * both.
*
*
Grantee Values
*
- *
You can specify the person (grantee) to whom you're assigning access rights
- * (using request elements) in the following ways. For examples of how to specify these
- * grantee values in JSON format, see the Amazon Web Services CLI example in
- * Enabling Amazon S3 server access logging in the
- * Amazon S3 User Guide.
+ *
You can specify the person (grantee) to whom you're assigning access rights (using request
+ * elements) in the following ways. For examples of how to specify these grantee values in JSON
+ * format, see the Amazon Web Services CLI example in Enabling Amazon S3 server
+ * access logging in the Amazon S3 User Guide.
The ACL of an object is set at the object version level. By default, PUT sets
- * the ACL of the current version of an object. To set the ACL of a different
- * version, use the versionId subresource.
+ *
The ACL of an object is set at the object version level. By default, PUT sets the ACL of the
+ * current version of an object. To set the ACL of a different version, use the
+ * versionId subresource.
*
*
*
The following operations are related to PutObjectAcl:
Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added
- * the entire object to the bucket. You cannot use PutObject to only
- * update a single piece of metadata for an existing object. You must put the entire
- * object with updated metadata if you want to update some values.
+ *
Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire
+ * object to the bucket. You cannot use PutObject to only update a single piece of
+ * metadata for an existing object. You must put the entire object with updated metadata if you want
+ * to update some values.
*
*
- *
If your bucket uses the bucket owner enforced setting for Object Ownership,
- * ACLs are disabled and no longer affect permissions. All objects written to the
- * bucket by any account will be owned by the bucket owner.
+ *
If your bucket uses the bucket owner enforced setting for Object Ownership, ACLs are disabled
+ * and no longer affect permissions. All objects written to the bucket by any account will be owned
+ * by the bucket owner.
*
*
*
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
Amazon S3 is a distributed system. If it receives multiple write requests for the same object
- * simultaneously, it overwrites all but the last object written. However, Amazon S3 provides
- * features that can modify this behavior:
+ * simultaneously, it overwrites all but the last object written. However, Amazon S3 provides features that can
+ * modify this behavior:
*
*
*
- * S3 Object Lock - To prevent objects from
- * being deleted or overwritten, you can use Amazon S3 Object
- * Lock in the Amazon S3 User Guide.
+ * S3 Object Lock - To prevent objects from being deleted
+ * or overwritten, you can use Amazon S3 Object Lock in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
*
*
*
*
- * If-None-Match - Uploads the object only if the object key name does not already exist in the specified bucket. Otherwise, Amazon S3 returns a 412 Precondition Failed error. If a conflicting operation occurs during the upload, S3 returns a 409 ConditionalRequestConflict response. On a 409 failure, retry the upload.
+ * If-None-Match - Uploads the object only if the object
+ * key name does not already exist in the specified bucket. Otherwise, Amazon S3 returns a 412
+ * Precondition Failed error. If a conflicting operation occurs during the upload, S3 returns
+ * a 409 ConditionalRequestConflict response. On a 409 failure, retry the upload.
*
This functionality is not supported for S3 on Outposts.
*
*
*
*
- * S3 Versioning - When you enable versioning
- * for a bucket, if Amazon S3 receives multiple write requests for the same object
- * simultaneously, it stores all versions of the objects. For each write request that is
- * made to the same object, Amazon S3 automatically generates a unique version ID of that
- * object being stored in Amazon S3. You can retrieve, replace, or delete any version of the
- * object. For more information about versioning, see Adding
- * Objects to Versioning-Enabled Buckets in the Amazon S3 User
- * Guide. For information about returning the versioning state of a
- * bucket, see GetBucketVersioning.
+ * S3 Versioning - When you enable versioning for a bucket,
+ * if Amazon S3 receives multiple write requests for the same object simultaneously, it stores all versions
+ * of the objects. For each write request that is made to the same object, Amazon S3 automatically generates
+ * a unique version ID of that object being stored in Amazon S3. You can retrieve, replace, or delete any
+ * version of the object. For more information about versioning, see Adding Objects to
+ * Versioning-Enabled Buckets in the Amazon S3 User Guide. For information
+ * about returning the versioning state of a bucket, see GetBucketVersioning.
*
*
This functionality is not supported for directory buckets.
- * General purpose bucket permissions - The
- * following permissions are required in your policies when your
- * PutObject request includes specific headers.
+ * General purpose bucket permissions - The following
+ * permissions are required in your policies when your PutObject request includes
+ * specific headers.
*
*
*
*
* s3:PutObject
- * -
- * To successfully complete the PutObject request, you must
- * always have the s3:PutObject permission on a bucket to
- * add an object to it.
+ * - To successfully
+ * complete the PutObject request, you must always have the
+ * s3:PutObject permission on a bucket to add an object to it.
*
*
*
*
* s3:PutObjectAcl
- * - To successfully change the objects ACL of your
- * PutObject request, you must have the
- * s3:PutObjectAcl.
+ * - To successfully change the objects ACL of your PutObject
+ * request, you must have the s3:PutObjectAcl.
*
*
*
*
* s3:PutObjectTagging
- * - To successfully set the tag-set with your
- * PutObject request, you must have the
- * s3:PutObjectTagging.
+ * - To successfully set the tag-set with your PutObject
+ * request, you must have the s3:PutObjectTagging.
*
If the object is encrypted with SSE-KMS, you must also have the
- * kms:GenerateDataKey and kms:Decrypt permissions
- * in IAM identity-based policies and KMS key policies for the KMS
- * key.
+ * kms:GenerateDataKey and kms:Decrypt permissions in IAM
+ * identity-based policies and KMS key policies for the KMS key.
*
- * General purpose bucket - To ensure that
- * data is not corrupted traversing the network, use the
- * Content-MD5 header. When you use this header, Amazon S3 checks
- * the object against the provided MD5 value and, if they do not match, Amazon S3
- * returns an error. Alternatively, when the object's ETag is its MD5 digest,
- * you can calculate the MD5 while putting the object to Amazon S3 and compare the
- * returned ETag to the calculated MD5 value.
+ * General purpose bucket - To ensure that data is not
+ * corrupted traversing the network, use the Content-MD5 header. When you use this
+ * header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, Amazon S3
+ * returns an error. Alternatively, when the object's ETag is its MD5 digest, you can calculate
+ * the MD5 while putting the object to Amazon S3 and compare the returned ETag to the calculated MD5
+ * value.
*
*
*
* Directory bucket -
- * This functionality is not supported for directory buckets.
+ * This functionality is not supported for directory buckets.
*
- * The existing object was created with a different encryption type.
- * Subsequent write requests must include the appropriate encryption
- * parameters in the request or while creating the session.
- *
+ *
The existing object was created with a different encryption type. Subsequent write requests must
+ * include the appropriate encryption parameters in the request or while creating the session.
- * You have attempted to add more parts than the maximum of 10000
- * that are allowed for this object. You can use the CopyObject operation
- * to copy this object to another and then add more data to the newly copied object.
- *
+ *
You have attempted to add more parts than the maximum of 10000 that are allowed for this object.
+ * You can use the CopyObject operation to copy this object to another and then add more data to the newly
+ * copied object.
*
* @throws {@link S3ServiceException}
*
Base exception class for all service exceptions from S3 service.
This operation is not supported for directory buckets.
*
- *
Applies a legal hold configuration to the specified object. For more information, see
- * Locking
- * Objects.
+ *
Applies a legal hold configuration to the specified object. For more information, see Locking Objects.
*
This functionality is not supported for Amazon S3 on Outposts.
* @example
* Use a bare-bones client and the command you need to make an API call.
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectLockConfigurationCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectLockConfigurationCommand.d.ts
index 9b311711..0c9d5e73 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectLockConfigurationCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectLockConfigurationCommand.d.ts
@@ -30,24 +30,23 @@ declare const PutObjectLockConfigurationCommand_base: {
*
*
This operation is not supported for directory buckets.
*
- *
Places an Object Lock configuration on the specified bucket. The rule specified in the
- * Object Lock configuration will be applied by default to every new object placed in the
- * specified bucket. For more information, see Locking Objects.
+ *
Places an Object Lock configuration on the specified bucket. The rule specified in the Object Lock
+ * configuration will be applied by default to every new object placed in the specified bucket. For more
+ * information, see Locking
+ * Objects.
*
*
*
- *
The DefaultRetention settings require both a mode and a
- * period.
+ *
The DefaultRetention settings require both a mode and a period.
*
*
- *
The DefaultRetention period can be either Days or
- * Years but you must select one. You cannot specify
- * Days and Years at the same time.
+ *
The DefaultRetention period can be either Days or Years
+ * but you must select one. You cannot specify Days and Years at the same
+ * time.
*
*
- *
You can enable Object Lock for new or existing buckets. For more information,
- * see Configuring Object
- * Lock.
+ *
You can enable Object Lock for new or existing buckets. For more information, see Configuring
+ * Object Lock.
This operation is not supported for directory buckets.
*
- *
Places an Object Retention configuration on an object. For more information, see Locking Objects.
- * Users or accounts require the s3:PutObjectRetention permission in order to
- * place an Object Retention configuration on objects. Bypassing a Governance Retention
- * configuration requires the s3:BypassGovernanceRetention permission.
+ *
Places an Object Retention configuration on an object. For more information, see Locking Objects. Users or
+ * accounts require the s3:PutObjectRetention permission in order to place an Object Retention
+ * configuration on objects. Bypassing a Governance Retention configuration requires the
+ * s3:BypassGovernanceRetention permission.
*
This functionality is not supported for Amazon S3 on Outposts.
* @example
* Use a bare-bones client and the command you need to make an API call.
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectTaggingCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectTaggingCommand.d.ts
index 0a799a8a..dea34a60 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectTaggingCommand.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/PutObjectTaggingCommand.d.ts
@@ -30,44 +30,38 @@ declare const PutObjectTaggingCommand_base: {
*
*
This operation is not supported for directory buckets.
*
- *
Sets the supplied tag-set to an object that already exists in a bucket. A tag is a
- * key-value pair. For more information, see Object Tagging.
- *
You can associate tags with an object by sending a PUT request against the tagging
- * subresource that is associated with the object. You can retrieve tags by sending a GET
- * request. For more information, see GetObjectTagging.
+ *
Sets the supplied tag-set to an object that already exists in a bucket. A tag is a key-value pair.
+ * For more information, see Object Tagging.
+ *
You can associate tags with an object by sending a PUT request against the tagging subresource that
+ * is associated with the object. You can retrieve tags by sending a GET request. For more information, see
+ * GetObjectTagging.
*
For tagging-related restrictions related to characters and encodings, see Tag
- * Restrictions. Note that Amazon S3 limits the maximum number of tags to 10 tags per
- * object.
- *
To use this operation, you must have permission to perform the
- * s3:PutObjectTagging action. By default, the bucket owner has this
- * permission and can grant this permission to others.
- *
To put tags of any other version, use the versionId query parameter. You
- * also need permission for the s3:PutObjectVersionTagging action.
+ * Restrictions. Note that Amazon S3 limits the maximum number of tags to 10 tags per object.
+ *
To use this operation, you must have permission to perform the s3:PutObjectTagging
+ * action. By default, the bucket owner has this permission and can grant this permission to others.
+ *
To put tags of any other version, use the versionId query parameter. You also need
+ * permission for the s3:PutObjectVersionTagging action.
*
- * PutObjectTagging has the following special errors. For more Amazon S3 errors
- * see, Error
- * Responses.
+ * PutObjectTagging has the following special errors. For more Amazon S3 errors see, Error Responses.
*
*
*
- * InvalidTag - The tag provided was not a valid tag. This error
- * can occur if the tag did not pass input validation. For more information, see Object
- * Tagging.
+ * InvalidTag - The tag provided was not a valid tag. This error can occur if
+ * the tag did not pass input validation. For more information, see Object Tagging.
*
*
*
- * MalformedXML - The XML provided does not match the
- * schema.
+ * MalformedXML - The XML provided does not match the schema.
*
*
*
- * OperationAborted - A conflicting conditional action is
- * currently in progress against this resource. Please try again.
+ * OperationAborted - A conflicting conditional action is currently in progress
+ * against this resource. Please try again.
*
*
*
- * InternalError - The service was unable to apply the provided
- * tag to the object.
+ * InternalError - The service was unable to apply the provided tag to the
+ * object.
*
*
*
The following operations are related to PutObjectTagging:
This operation is not supported for directory buckets.
*
- *
Creates or modifies the PublicAccessBlock configuration for an Amazon S3 bucket.
- * To use this operation, you must have the s3:PutBucketPublicAccessBlock
- * permission. For more information about Amazon S3 permissions, see Specifying Permissions in a
- * Policy.
+ *
Creates or modifies the PublicAccessBlock configuration for an Amazon S3 bucket. To use this
+ * operation, you must have the s3:PutBucketPublicAccessBlock permission. For more information
+ * about Amazon S3 permissions, see Specifying Permissions in a
+ * Policy.
*
- *
When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or
- * an object, it checks the PublicAccessBlock configuration for both the
- * bucket (or the bucket that contains the object) and the bucket owner's account. If the
- * PublicAccessBlock configurations are different between the bucket and
- * the account, Amazon S3 uses the most restrictive combination of the bucket-level and
- * account-level settings.
+ *
When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or an object, it
+ * checks the PublicAccessBlock configuration for both the bucket (or the bucket that
+ * contains the object) and the bucket owner's account. If the PublicAccessBlock
+ * configurations are different between the bucket and the account, Amazon S3 uses the most restrictive
+ * combination of the bucket-level and account-level settings.
*
*
For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of "Public".
*
The following operations are related to PutPublicAccessBlock:
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.
+ *
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.
+ * 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.
+ *
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-Match conditional header with the value ‘*’ in
- * the RenameObject request. Amazon S3 then returns a 412 Precondition
- * Failed error if the object with the specified name already exists.
- * For more information, see RFC 7232.
+ * 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-Match conditional header with the
+ * value ‘*’ in the RenameObject request. Amazon S3 then returns a 412
+ * Precondition Failed error if the object with the specified name already exists. For more
+ * information, see RFC 7232.
*
*
*
*
Permissions
*
- *
To grant access to the RenameObject operation on a directory
- * bucket, we recommend that you use the CreateSession operation for
- * session-based authorization. Specifically, you grant the
- * s3express:CreateSession permission to the directory bucket in a
- * bucket policy or an IAM identity-based policy. Then, you make the
- * CreateSession API 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 another
- * CreateSession API 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 the
- * s3express:SessionMode condition key to control who can create a
- * ReadWrite or ReadOnly session. A
- * ReadWrite session is required for executing all the Zonal endpoint
- * API operations, including RenameObject. For more information about
- * authorization, see
+ *
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.
+ *
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.
+ *
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.
Objects that you archive to the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage class, and S3 Intelligent-Tiering Archive or
- * S3 Intelligent-Tiering Deep Archive tiers, are not accessible in real time. For objects in the
- * S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive
- * storage classes, you must first initiate a restore request, and then wait until a
- * temporary copy of the object is available. If you want a permanent copy of the
- * object, create a copy of it in the Amazon S3 Standard storage class in your S3 bucket.
- * To access an archived object, you must restore the object for the duration (number
- * of days) that you specify. For objects in the Archive Access or Deep Archive
- * Access tiers of S3 Intelligent-Tiering, you must first initiate a restore request,
- * and then wait until the object is moved into the Frequent Access tier.
- *
To restore a specific object version, you can provide a version ID. If you
- * don't provide a version ID, Amazon S3 restores the current version.
- *
When restoring an archived object, you can specify one of the following data
- * access tier options in the Tier element of the request body:
+ *
Objects that you archive to the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive
+ * storage class, and S3 Intelligent-Tiering Archive or S3 Intelligent-Tiering Deep Archive tiers, are not accessible in
+ * real time. For objects in the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive
+ * storage classes, you must first initiate a restore request, and then wait until a temporary copy
+ * of the object is available. If you want a permanent copy of the object, create a copy of it in the
+ * Amazon S3 Standard storage class in your S3 bucket. To access an archived object, you must restore the
+ * object for the duration (number of days) that you specify. For objects in the Archive Access or
+ * Deep Archive Access tiers of S3 Intelligent-Tiering, you must first initiate a restore request, and
+ * then wait until the object is moved into the Frequent Access tier.
+ *
To restore a specific object version, you can provide a version ID. If you don't provide a
+ * version ID, Amazon S3 restores the current version.
+ *
When restoring an archived object, you can specify one of the following data access tier
+ * options in the Tier element of the request body:
*
*
*
- * Expedited - Expedited retrievals allow you to quickly access
- * your data stored in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier when occasional urgent requests
- * for restoring archives are required. For all but the largest archived
- * objects (250 MB+), data accessed using Expedited retrievals is typically
- * made available within 1–5 minutes. Provisioned capacity ensures that
- * retrieval capacity for Expedited retrievals is available when you need it.
- * Expedited retrievals and provisioned capacity are not available for objects
- * stored in the S3 Glacier Deep Archive storage class or
- * S3 Intelligent-Tiering Deep Archive tier.
+ * Expedited - Expedited retrievals allow you to quickly access your data stored
+ * in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier when occasional
+ * urgent requests for restoring archives are required. For all but the largest archived objects
+ * (250 MB+), data accessed using Expedited retrievals is typically made available within 1–5
+ * minutes. Provisioned capacity ensures that retrieval capacity for Expedited retrievals is
+ * available when you need it. Expedited retrievals and provisioned capacity are not available
+ * for objects stored in the S3 Glacier Deep Archive storage class or
+ * S3 Intelligent-Tiering Deep Archive tier.
*
*
*
- * Standard - Standard retrievals allow you to access any of
- * your archived objects within several hours. This is the default option for
- * retrieval requests that do not specify the retrieval option. Standard
- * retrievals typically finish within 3–5 hours for objects stored in the
- * S3 Glacier Flexible Retrieval storage class or
- * S3 Intelligent-Tiering Archive tier. They typically finish within 12 hours for
- * objects stored in the S3 Glacier Deep Archive storage class or
- * S3 Intelligent-Tiering Deep Archive tier. Standard retrievals are free for objects stored
- * in S3 Intelligent-Tiering.
+ * Standard - Standard retrievals allow you to access any of your archived
+ * objects within several hours. This is the default option for retrieval requests that do not
+ * specify the retrieval option. Standard retrievals typically finish within 3–5 hours for
+ * objects stored in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier.
+ * They typically finish within 12 hours for objects stored in the
+ * S3 Glacier Deep Archive storage class or S3 Intelligent-Tiering Deep Archive tier. Standard
+ * retrievals are free for objects stored in S3 Intelligent-Tiering.
*
*
*
- * Bulk - Bulk retrievals free for objects stored in the
- * S3 Glacier Flexible Retrieval and S3 Intelligent-Tiering storage classes,
- * enabling you to retrieve large amounts, even petabytes, of data at no cost.
- * Bulk retrievals typically finish within 5–12 hours for objects stored in the
- * S3 Glacier Flexible Retrieval storage class or
- * S3 Intelligent-Tiering Archive tier. Bulk retrievals are also the lowest-cost
- * retrieval option when restoring objects from
- * S3 Glacier Deep Archive. They typically finish within 48 hours for
- * objects stored in the S3 Glacier Deep Archive storage class or
- * S3 Intelligent-Tiering Deep Archive tier.
+ * Bulk - Bulk retrievals free for objects stored in the S3 Glacier Flexible
+ * Retrieval and S3 Intelligent-Tiering storage classes, enabling you to retrieve large amounts,
+ * even petabytes, of data at no cost. Bulk retrievals typically finish within 5–12 hours for
+ * objects stored in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier.
+ * Bulk retrievals are also the lowest-cost retrieval option when restoring objects from
+ * S3 Glacier Deep Archive. They typically finish within 48 hours for objects stored in
+ * the S3 Glacier Deep Archive storage class or S3 Intelligent-Tiering Deep Archive tier.
*
*
- *
For more information about archive retrieval options and provisioned capacity
- * for Expedited data access, see Restoring Archived
- * Objects in the Amazon S3 User Guide.
- *
You can use Amazon S3 restore speed upgrade to change the restore speed to a faster
- * speed while it is in progress. For more information, see Upgrading the speed of an in-progress restore in the
- * Amazon S3 User Guide.
- *
To get the status of object restoration, you can send a HEAD
- * request. Operations return the x-amz-restore header, which provides
- * information about the restoration status, in the response. You can use Amazon S3 event
- * notifications to notify you when a restore is initiated or completed. For more
- * information, see Configuring Amazon S3 Event
- * Notifications in the Amazon S3 User Guide.
- *
After restoring an archived object, you can update the restoration period by
- * reissuing the request with a new period. Amazon S3 updates the restoration period
- * relative to the current time and charges only for the request-there are no
- * data transfer charges. You cannot update the restoration period when Amazon S3 is
- * actively processing your current restore request for the object.
- *
If your bucket has a lifecycle configuration with a rule that includes an
- * expiration action, the object expiration overrides the life span that you specify
- * in a restore request. For example, if you restore an object copy for 10 days, but
- * the object is scheduled to expire in 3 days, Amazon S3 deletes the object in 3 days.
- * For more information about lifecycle configuration, see PutBucketLifecycleConfiguration and Object Lifecycle
- * Management in Amazon S3 User Guide.
+ *
For more information about archive retrieval options and provisioned capacity for
+ * Expedited data access, see Restoring Archived Objects in the
+ * Amazon S3 User Guide.
+ *
You can use Amazon S3 restore speed upgrade to change the restore speed to a faster speed while it
+ * is in progress. For more information, see
+ * Upgrading the speed of an in-progress restore in the
+ * Amazon S3 User Guide.
+ *
To get the status of object restoration, you can send a HEAD request. Operations
+ * return the x-amz-restore header, which provides information about the restoration
+ * status, in the response. You can use Amazon S3 event notifications to notify you when a restore is
+ * initiated or completed. For more information, see Configuring Amazon S3 Event Notifications in
+ * the Amazon S3 User Guide.
+ *
After restoring an archived object, you can update the restoration period by reissuing the
+ * request with a new period. Amazon S3 updates the restoration period relative to the current time and
+ * charges only for the request-there are no data transfer charges. You cannot update the
+ * restoration period when Amazon S3 is actively processing your current restore request for the
+ * object.
+ *
If your bucket has a lifecycle configuration with a rule that includes an expiration action,
+ * the object expiration overrides the life span that you specify in a restore request. For example,
+ * if you restore an object copy for 10 days, but the object is scheduled to expire in 3 days, Amazon S3
+ * deletes the object in 3 days. For more information about lifecycle configuration, see PutBucketLifecycleConfiguration and Object Lifecycle Management in
+ * Amazon S3 User Guide.
*
*
Responses
*
- *
A successful action returns either the 200 OK or 202
- * Accepted status code.
+ *
A successful action returns either the 200 OK or 202 Accepted status
+ * code.
*
*
- *
If the object is not previously restored, then Amazon S3 returns 202
- * Accepted in the response.
+ *
If the object is not previously restored, then Amazon S3 returns 202 Accepted in
+ * the response.
*
*
- *
If the object is previously restored, Amazon S3 returns 200 OK in
- * the response.
+ *
If the object is previously restored, Amazon S3 returns 200 OK in the response.
+ *
- * Cause: expedited retrievals are currently not available.
- * Try again later. (Returned if there is insufficient capacity to
- * process the Expedited request. This error applies only to Expedited
- * retrievals and not to S3 Standard or Bulk retrievals.)
+ * Cause: expedited retrievals are currently not available. Try again later.
+ * (Returned if there is insufficient capacity to process the Expedited request. This error
+ * applies only to Expedited retrievals and not to S3 Standard or Bulk
+ * retrievals.)
*
This operation is not supported for directory buckets.
*
- *
This action filters the contents of an Amazon S3 object based on a simple structured query
- * language (SQL) statement. In the request, along with the SQL expression, you must also
- * specify a data serialization format (JSON, CSV, or Apache Parquet) of the object. Amazon S3 uses
- * this format to parse object data into records, and returns only records that match the
- * specified SQL expression. You must also specify the data serialization format for the
- * response.
+ *
This action filters the contents of an Amazon S3 object based on a simple structured query language (SQL)
+ * statement. In the request, along with the SQL expression, you must also specify a data serialization
+ * format (JSON, CSV, or Apache Parquet) of the object. Amazon S3 uses this format to parse object data into
+ * records, and returns only records that match the specified SQL expression. You must also specify the
+ * data serialization format for the response.
*
This functionality is not supported for Amazon S3 on Outposts.
You must have the s3:GetObject permission for this operation. Amazon S3
- * Select does not support anonymous access. For more information about permissions,
- * see Specifying Permissions in
- * a Policy in the Amazon S3 User Guide.
+ *
You must have the s3:GetObject permission for this operation. Amazon S3 Select does
+ * not support anonymous access. For more information about permissions, see Specifying Permissions
+ * in a Policy in the Amazon S3 User Guide.
*
*
Object Data Formats
*
- *
You can use Amazon S3 Select to query objects that have the following format
- * properties:
+ *
You can use Amazon S3 Select to query objects that have the following format properties:
*
*
*
- * CSV, JSON, and Parquet - Objects must be in CSV,
- * JSON, or Parquet format.
+ * CSV, JSON, and Parquet - Objects must be in CSV, JSON, or Parquet
+ * format.
*
*
*
- * UTF-8 - UTF-8 is the only encoding type Amazon S3 Select
- * supports.
+ * UTF-8 - UTF-8 is the only encoding type Amazon S3 Select supports.
*
*
*
- * GZIP or BZIP2 - CSV and JSON files can be compressed
- * using GZIP or BZIP2. GZIP and BZIP2 are the only compression formats that
- * Amazon S3 Select supports for CSV and JSON files. Amazon S3 Select supports columnar
- * compression for Parquet using GZIP or Snappy. Amazon S3 Select does not support
- * whole-object compression for Parquet objects.
+ * GZIP or BZIP2 - CSV and JSON files can be compressed using GZIP or
+ * BZIP2. GZIP and BZIP2 are the only compression formats that Amazon S3 Select supports for CSV and
+ * JSON files. Amazon S3 Select supports columnar compression for Parquet using GZIP or Snappy. Amazon S3
+ * Select does not support whole-object compression for Parquet objects.
*
*
*
- * Server-side encryption - Amazon S3 Select supports
- * querying objects that are protected with server-side encryption.
- *
For objects that are encrypted with customer-provided encryption keys
- * (SSE-C), you must use HTTPS, and you must use the headers that are
- * documented in the GetObject. For more
- * information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys)
- * in the Amazon S3 User Guide.
- *
For objects that are encrypted with Amazon S3 managed keys (SSE-S3) and
- * Amazon Web Services KMS keys (SSE-KMS), server-side encryption is handled transparently,
- * so you don't need to specify anything. For more information about
- * server-side encryption, including SSE-S3 and SSE-KMS, see Protecting Data Using Server-Side Encryption in the
- * Amazon S3 User Guide.
+ * Server-side encryption - Amazon S3 Select supports querying objects that
+ * are protected with server-side encryption.
+ *
For objects that are encrypted with customer-provided encryption keys (SSE-C), you must
+ * use HTTPS, and you must use the headers that are documented in the GetObject. For more information about
+ * SSE-C, see Server-Side Encryption
+ * (Using Customer-Provided Encryption Keys) in the
+ * Amazon S3 User Guide.
+ *
For objects that are encrypted with Amazon S3 managed keys (SSE-S3) and Amazon Web Services KMS keys
+ * (SSE-KMS), server-side encryption is handled transparently, so you don't need to specify
+ * anything. For more information about server-side encryption, including SSE-S3 and SSE-KMS, see
+ * Protecting
+ * Data Using Server-Side Encryption in the
+ * Amazon S3 User Guide.
*
*
*
*
Working with the Response Body
*
- *
Given the response size is unknown, Amazon S3 Select streams the response as a
- * series of messages and includes a Transfer-Encoding header with
- * chunked as its value in the response. For more information, see
- * Appendix:
- * SelectObjectContent
- * Response.
+ *
Given the response size is unknown, Amazon S3 Select streams the response as a series of messages
+ * and includes a Transfer-Encoding header with chunked as its value in the
+ * response. For more information, see Appendix: SelectObjectContent
+ * Response.
*
*
GetObject Support
*
*
The SelectObjectContent action does not support the following
- * GetObject functionality. For more information, see GetObject.
+ * GetObject functionality. For more information, see GetObject.
*
*
*
- * Range: Although you can specify a scan range for an Amazon S3 Select
- * request (see SelectObjectContentRequest - ScanRange in the request
- * parameters), you cannot specify the range of bytes of an object to return.
- *
+ * Range: Although you can specify a scan range for an Amazon S3 Select request (see
+ * SelectObjectContentRequest - ScanRange in the request parameters), you
+ * cannot specify the range of bytes of an object to return.
*
*
- *
The GLACIER, DEEP_ARCHIVE, and
- * REDUCED_REDUNDANCY storage classes, or the
- * ARCHIVE_ACCESS and DEEP_ARCHIVE_ACCESS access
- * tiers of the INTELLIGENT_TIERING storage class: You cannot
- * query objects in the GLACIER, DEEP_ARCHIVE, or
- * REDUCED_REDUNDANCY storage classes, nor objects in the
- * ARCHIVE_ACCESS or DEEP_ARCHIVE_ACCESS access
- * tiers of the INTELLIGENT_TIERING storage class. For more
- * information about storage classes, see Using Amazon S3
- * storage classes in the
- * Amazon S3 User Guide.
+ *
The GLACIER, DEEP_ARCHIVE, and REDUCED_REDUNDANCY
+ * storage classes, or the ARCHIVE_ACCESS and DEEP_ARCHIVE_ACCESS
+ * access tiers of the INTELLIGENT_TIERING storage class: You cannot query objects
+ * in the GLACIER, DEEP_ARCHIVE, or REDUCED_REDUNDANCY
+ * storage classes, nor objects in the ARCHIVE_ACCESS or
+ * DEEP_ARCHIVE_ACCESS access tiers of the INTELLIGENT_TIERING
+ * storage class. For more information about storage classes, see Using Amazon S3 storage classes
+ * in the Amazon S3 User Guide.
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/UpdateBucketMetadataInventoryTableConfigurationCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/UpdateBucketMetadataInventoryTableConfigurationCommand.d.ts
new file mode 100644
index 00000000..987f85ce
--- /dev/null
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/UpdateBucketMetadataInventoryTableConfigurationCommand.d.ts
@@ -0,0 +1,161 @@
+import { Command as $Command } from "@smithy/smithy-client";
+import { MetadataBearer as __MetadataBearer } from "@smithy/types";
+import { UpdateBucketMetadataInventoryTableConfigurationRequest } from "../models/models_1";
+import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
+/**
+ * @public
+ */
+export type { __MetadataBearer };
+export { $Command };
+/**
+ * @public
+ *
+ * The input for {@link UpdateBucketMetadataInventoryTableConfigurationCommand}.
+ */
+export interface UpdateBucketMetadataInventoryTableConfigurationCommandInput extends UpdateBucketMetadataInventoryTableConfigurationRequest {
+}
+/**
+ * @public
+ *
+ * The output of {@link UpdateBucketMetadataInventoryTableConfigurationCommand}.
+ */
+export interface UpdateBucketMetadataInventoryTableConfigurationCommandOutput extends __MetadataBearer {
+}
+declare const UpdateBucketMetadataInventoryTableConfigurationCommand_base: {
+ new (input: UpdateBucketMetadataInventoryTableConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl;
+ new (input: UpdateBucketMetadataInventoryTableConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl;
+ getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+};
+/**
+ *
Enables or disables a live inventory table for an S3 Metadata configuration on a general
+ * purpose bucket. For more information, see
+ * Accelerating
+ * data discovery with S3 Metadata in the Amazon S3 User Guide.
If you want to encrypt your inventory table with server-side encryption with Key Management Service
+ * (KMS) keys (SSE-KMS), you need additional permissions in your KMS key policy. For more
+ * information, see
+ * Setting up permissions for configuring metadata tables in the
+ * Amazon S3 User Guide.
Base exception class for all service exceptions from S3 service.
+ *
+ *
+ * @public
+ */
+export declare class UpdateBucketMetadataInventoryTableConfigurationCommand extends UpdateBucketMetadataInventoryTableConfigurationCommand_base {
+ /** @internal type navigation helper, not in runtime. */
+ protected static __types: {
+ api: {
+ input: UpdateBucketMetadataInventoryTableConfigurationRequest;
+ output: {};
+ };
+ sdk: {
+ input: UpdateBucketMetadataInventoryTableConfigurationCommandInput;
+ output: UpdateBucketMetadataInventoryTableConfigurationCommandOutput;
+ };
+ };
+}
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/UpdateBucketMetadataJournalTableConfigurationCommand.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/UpdateBucketMetadataJournalTableConfigurationCommand.d.ts
new file mode 100644
index 00000000..4519e42e
--- /dev/null
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/UpdateBucketMetadataJournalTableConfigurationCommand.d.ts
@@ -0,0 +1,113 @@
+import { Command as $Command } from "@smithy/smithy-client";
+import { MetadataBearer as __MetadataBearer } from "@smithy/types";
+import { UpdateBucketMetadataJournalTableConfigurationRequest } from "../models/models_1";
+import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
+/**
+ * @public
+ */
+export type { __MetadataBearer };
+export { $Command };
+/**
+ * @public
+ *
+ * The input for {@link UpdateBucketMetadataJournalTableConfigurationCommand}.
+ */
+export interface UpdateBucketMetadataJournalTableConfigurationCommandInput extends UpdateBucketMetadataJournalTableConfigurationRequest {
+}
+/**
+ * @public
+ *
+ * The output of {@link UpdateBucketMetadataJournalTableConfigurationCommand}.
+ */
+export interface UpdateBucketMetadataJournalTableConfigurationCommandOutput extends __MetadataBearer {
+}
+declare const UpdateBucketMetadataJournalTableConfigurationCommand_base: {
+ new (input: UpdateBucketMetadataJournalTableConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl;
+ new (input: UpdateBucketMetadataJournalTableConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl;
+ getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+};
+/**
+ *
Enables or disables journal table record expiration for an S3 Metadata configuration on a general
+ * purpose bucket. For more information, see
+ * Accelerating
+ * data discovery with S3 Metadata in the Amazon S3 User Guide.
In this operation, you provide new data as a part of an object in your request.
- * However, you have an option to specify your existing Amazon S3 object as a data source for
- * the part you are uploading. To upload a part from an existing object, you use the UploadPartCopy operation.
+ *
In this operation, you provide new data as a part of an object in your request. However, you have
+ * an option to specify your existing Amazon S3 object as a data source for the part you are uploading. To
+ * upload a part from an existing object, you use the UploadPartCopy operation.
*
- *
You must initiate a multipart upload (see CreateMultipartUpload)
- * before you can upload any part. In response to your initiate request, Amazon S3 returns an
- * upload ID, a unique identifier that you must include in your upload part request.
- *
Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely
- * identifies a part and also defines its position within the object being created. If you
- * upload a new part using the same part number that was used with a previous part, the
- * previously uploaded part is overwritten.
- *
For information about maximum and minimum part sizes and other multipart upload
- * specifications, see Multipart upload limits in the Amazon S3 User Guide.
+ *
You must initiate a multipart upload (see CreateMultipartUpload) before you can
+ * upload any part. In response to your initiate request, Amazon S3 returns an upload ID, a unique identifier
+ * that you must include in your upload part request.
+ *
Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part
+ * and also defines its position within the object being created. If you upload a new part using the same
+ * part number that was used with a previous part, the previously uploaded part is overwritten.
+ *
For information about maximum and minimum part sizes and other multipart upload specifications, see
+ * Multipart upload
+ * limits in the Amazon S3 User Guide.
*
- *
After you initiate multipart upload and upload one or more parts, you must either
- * complete or abort multipart upload in order to stop getting charged for storage of the
- * uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up
- * the parts storage and stops charging you for the parts storage.
+ *
After you initiate multipart upload and upload one or more parts, you must either complete or
+ * abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after
+ * you either complete or abort multipart upload, Amazon S3 frees up the parts storage and stops charging you
+ * for the parts storage.
*
*
For more information on multipart uploads, go to Multipart Upload Overview in the
- * Amazon S3 User Guide .
+ * Amazon S3 User Guide .
*
*
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
- * General purpose bucket permissions - To
- * perform a multipart upload with encryption using an Key Management Service key, the
- * requester must have permission to the kms:Decrypt and
- * kms:GenerateDataKey actions on the key. The requester must
- * also have permissions for the kms:GenerateDataKey action for
- * the CreateMultipartUpload API. Then, the requester needs
- * permissions for the kms:Decrypt action on the
- * UploadPart and UploadPartCopy APIs.
+ * General purpose bucket permissions - To perform a
+ * multipart upload with encryption using an Key Management Service key, the requester must have permission to
+ * the kms:Decrypt and kms:GenerateDataKey actions on the key. The
+ * requester must also have permissions for the kms:GenerateDataKey action for the
+ * CreateMultipartUpload API. Then, the requester needs permissions for the
+ * kms:Decrypt action on the UploadPart and
+ * UploadPartCopy APIs.
+ *
If the object is encrypted with SSE-KMS, you must also have the
- * kms:GenerateDataKey and kms:Decrypt permissions
- * in IAM identity-based policies and KMS key policies for the KMS
- * key.
+ * kms:GenerateDataKey and kms:Decrypt permissions in IAM
+ * identity-based policies and KMS key policies for the KMS key.
*
*
*
*
Data integrity
*
*
- * General purpose bucket - To ensure that data
- * is not corrupted traversing the network, specify the Content-MD5
- * header in the upload part request. Amazon S3 checks the part data against the provided
- * MD5 value. If they do not match, Amazon S3 returns an error. If the upload request is
- * signed with Signature Version 4, then Amazon Web Services S3 uses the
- * x-amz-content-sha256 header as a checksum instead of
- * Content-MD5. For more information see Authenticating Requests: Using the Authorization Header (Amazon Web Services Signature
- * Version 4).
+ * General purpose bucket - To ensure that data is not corrupted
+ * traversing the network, specify the Content-MD5 header in the upload part request.
+ * Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an
+ * error. If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the
+ * x-amz-content-sha256 header as a checksum instead of Content-MD5. For
+ * more information see Authenticating Requests:
+ * Using the Authorization Header (Amazon Web Services Signature Version 4).
*
*
* Directory buckets - MD5 is not supported by directory buckets. You can use checksum algorithms to check object integrity.
- * General purpose bucket - Server-side
- * encryption is for data encryption at rest. Amazon S3 encrypts your data as it
- * writes it to disks in its data centers and decrypts it when you access it.
- * You have mutually exclusive options to protect data using server-side
- * encryption in Amazon S3, depending on how you choose to manage the encryption
- * keys. Specifically, the encryption key options are Amazon S3 managed keys
- * (SSE-S3), Amazon Web Services KMS keys (SSE-KMS), and Customer-Provided Keys (SSE-C).
- * Amazon S3 encrypts data with server-side encryption using Amazon S3 managed keys
- * (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt data at rest
- * using server-side encryption with other key options. The option you use
- * depends on whether you want to use KMS keys (SSE-KMS) or provide your own
- * encryption key (SSE-C).
- *
Server-side encryption is supported by the S3 Multipart Upload
- * operations. Unless you are using a customer-provided encryption key (SSE-C),
- * you don't need to specify the encryption parameters in each UploadPart
- * request. Instead, you only need to specify the server-side encryption
- * parameters in the initial Initiate Multipart request. For more information,
- * see CreateMultipartUpload.
- *
If you request server-side encryption using a customer-provided
- * encryption key (SSE-C) in your initiate multipart upload request, you must
- * provide identical encryption information in each part upload using the
- * following request headers.
+ * General purpose bucket - Server-side encryption is for
+ * data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers
+ * and decrypts it when you access it. You have mutually exclusive options to protect data using
+ * server-side encryption in Amazon S3, depending on how you choose to manage the encryption keys.
+ * Specifically, the encryption key options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys
+ * (SSE-KMS), and Customer-Provided Keys (SSE-C). Amazon S3 encrypts data with server-side encryption
+ * using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt data at
+ * rest using server-side encryption with other key options. The option you use depends on
+ * whether you want to use KMS keys (SSE-KMS) or provide your own encryption key
+ * (SSE-C).
+ *
Server-side encryption is supported by the S3 Multipart Upload operations. Unless you are
+ * using a customer-provided encryption key (SSE-C), you don't need to specify the encryption
+ * parameters in each UploadPart request. Instead, you only need to specify the server-side
+ * encryption parameters in the initial Initiate Multipart request. For more information, see
+ * CreateMultipartUpload.
+ *
If you request server-side encryption using a customer-provided encryption key (SSE-C) in
+ * your initiate multipart upload request, you must provide identical encryption information in
+ * each part upload using the following request headers.
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms).
+ * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms).
*
Description: The specified multipart upload does not exist. The
- * upload ID might be invalid, or the multipart upload might have been
- * aborted or completed.
+ *
Description: The specified multipart upload does not exist. The upload ID might be
+ * invalid, or the multipart upload might have been aborted or completed.
Uploads a part by copying data from an existing object as data source. To specify the
- * data source, you add the request header x-amz-copy-source in your request. To
- * specify a byte range, you add the request header x-amz-copy-source-range in
- * your request.
- *
For information about maximum and minimum part sizes and other multipart upload
- * specifications, see Multipart upload limits in the Amazon S3 User Guide.
+ *
Uploads a part by copying data from an existing object as data source. To specify the data source,
+ * you add the request header x-amz-copy-source in your request. To specify a byte range, you
+ * add the request header x-amz-copy-source-range in your request.
+ *
For information about maximum and minimum part sizes and other multipart upload specifications, see
+ * Multipart upload
+ * limits in the Amazon S3 User Guide.
*
- *
Instead of copying data from an existing object as part data, you might use the
- * UploadPart action to upload new data as a part of an object in your
- * request.
+ *
Instead of copying data from an existing object as part data, you might use the UploadPart action to
+ * upload new data as a part of an object in your request.
*
- *
You must initiate a multipart upload before you can upload any part. In response to your
- * initiate request, Amazon S3 returns the upload ID, a unique identifier that you must include in
- * your upload part request.
- *
For conceptual information about multipart uploads, see Uploading Objects Using Multipart
- * Upload in the Amazon S3 User Guide. For information about
- * copying objects using a single atomic action vs. a multipart upload, see Operations on
- * Objects in the Amazon S3 User Guide.
+ *
You must initiate a multipart upload before you can upload any part. In response to your initiate
+ * request, Amazon S3 returns the upload ID, a unique identifier that you must include in your upload part
+ * request.
+ *
For conceptual information about multipart uploads, see Uploading Objects Using Multipart Upload in
+ * the Amazon S3 User Guide. For information about copying objects using a single atomic
+ * action vs. a multipart upload, see Operations on Objects in the
+ * Amazon S3 User Guide.
*
*
- * Directory buckets -
- * For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
+ * Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://amzn-s3-demo-bucket.s3express-zone-id.region-code.amazonaws.com/key-name
* . Path-style requests are not supported. For more information about endpoints in Availability Zones, see Regional and Zonal endpoints for directory buckets in Availability Zones in the
* Amazon S3 User Guide. For more information about endpoints in Local Zones, see Concepts for directory buckets in Local Zones in the
* Amazon S3 User Guide.
All UploadPartCopy requests must be authenticated and signed by
- * using IAM credentials (access key ID and secret access key for the IAM
- * identities). All headers with the x-amz- prefix, including
- * x-amz-copy-source, must be signed. For more information, see
- * REST Authentication.
+ *
All UploadPartCopy requests must be authenticated and signed by using IAM
+ * credentials (access key ID and secret access key for the IAM identities). All headers with the
+ * x-amz- prefix, including x-amz-copy-source, must be signed. For more
+ * information, see REST Authentication.
*
- * Directory buckets - You must use IAM
- * credentials to authenticate and authorize your access to the
- * UploadPartCopy API operation, instead of using the temporary
- * security credentials through the CreateSession API operation.
- *
Amazon Web Services CLI or SDKs handles authentication and authorization on your
- * behalf.
+ * Directory buckets - You must use IAM credentials to
+ * authenticate and authorize your access to the UploadPartCopy API operation, instead
+ * of using the temporary security credentials through the CreateSession API
+ * operation.
+ *
Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.
*
*
Permissions
*
- *
You must have READ access to the source object and
- * WRITE access to the destination bucket.
+ *
You must have READ access to the source object and WRITE access to
+ * the destination bucket.
*
*
*
- * General purpose bucket permissions - You
- * must have the permissions in a policy based on the bucket types of your
- * source bucket and destination bucket in an UploadPartCopy
- * operation.
+ * General purpose bucket permissions - You must have the
+ * permissions in a policy based on the bucket types of your source bucket and destination bucket
+ * in an UploadPartCopy operation.
*
*
- *
If the source object is in a general purpose bucket, you must have the
- *
+ *
If the source object is in a general purpose bucket, you must have the
* s3:GetObject
- *
- * permission to read the source object that is being copied.
+ * permission to read the source object that is
+ * being copied.
*
*
- *
If the destination bucket is a general purpose bucket, you must have the
- *
+ *
If the destination bucket is a general purpose bucket, you must have the
* s3:PutObject
- *
- * permission to write the object copy to the destination bucket.
+ * permission to write the object copy to
+ * the destination bucket.
*
*
- *
To perform a multipart upload with encryption using an Key Management Service
- * key, the requester must have permission to the
- * kms:Decrypt and kms:GenerateDataKey
- * actions on the key. The requester must also have permissions for the
- * kms:GenerateDataKey action for the
- * CreateMultipartUpload API. Then, the requester needs
- * permissions for the kms:Decrypt action on the
- * UploadPart and UploadPartCopy APIs. These
- * permissions are required because Amazon S3 must decrypt and read data from
- * the encrypted file parts before it completes the multipart upload. For
- * more information about KMS permissions, see Protecting
- * data using server-side encryption with KMS in the
- * Amazon S3 User Guide. For information about the
- * permissions required to use the multipart upload API, see Multipart upload
- * and permissions and Multipart upload API and permissions in the
- * Amazon S3 User Guide.
+ *
To perform a multipart upload with encryption using an Key Management Service key, the requester
+ * must have permission to the kms:Decrypt and kms:GenerateDataKey
+ * actions on the key. The requester must also have permissions for the
+ * kms:GenerateDataKey action for the CreateMultipartUpload API.
+ * Then, the requester needs permissions for the kms:Decrypt action on the
+ * UploadPart and UploadPartCopy APIs. These permissions are
+ * required because Amazon S3 must decrypt and read data from the encrypted file parts before it
+ * completes the multipart upload. For more information about KMS permissions, see Protecting
+ * data using server-side encryption with KMS in the
+ * Amazon S3 User Guide. For information about the permissions required to
+ * use the multipart upload API, see Multipart upload and
+ * permissions and Multipart upload API
+ * and permissions in the Amazon S3 User Guide.
*
*
*
*
*
- * Directory bucket permissions -
- * You must have permissions in a bucket policy or an IAM identity-based policy based on the
- * source and destination bucket types in an UploadPartCopy
- * operation.
+ * Directory bucket permissions - You must have
+ * permissions in a bucket policy or an IAM identity-based policy based on the source and destination bucket types
+ * in an UploadPartCopy operation.
*
*
- *
If the source object that you want to copy is in a
- * directory bucket, you must have the
+ *
If the source object that you want to copy is in a directory bucket, you must have
+ * the
* s3express:CreateSession
* permission in
- * the Action element of a policy to read the object. By
- * default, the session is in the ReadWrite mode. If you
- * want to restrict the access, you can explicitly set the
- * s3express:SessionMode condition key to
- * ReadOnly on the copy source bucket.
+ * the Action element of a policy to read the object. By default, the session is
+ * in the ReadWrite mode. If you want to restrict the access, you can explicitly
+ * set the s3express:SessionMode condition key to ReadOnly on the
+ * copy source bucket.
*
*
- *
If the copy destination is a directory bucket, you must have the
- *
+ *
If the copy destination is a directory bucket, you must have the
* s3express:CreateSession
* permission in the
- * Action element of a policy to write the object to the
- * destination. The s3express:SessionMode condition key
- * cannot be set to ReadOnly on the copy destination.
- *
+ * Action element of a policy to write the object to the destination. The
+ * s3express:SessionMode condition key cannot be set to ReadOnly
+ * on the copy destination.
*
*
*
If the object is encrypted with SSE-KMS, you must also have the
- * kms:GenerateDataKey and kms:Decrypt permissions
- * in IAM identity-based policies and KMS key policies for the KMS
- * key.
* General purpose buckets -
- * For information about using
- * server-side encryption with customer-provided encryption keys with the
- * UploadPartCopy operation, see CopyObject and
- * UploadPart.
+ * For information about using server-side encryption with
+ * customer-provided encryption keys with the UploadPartCopy operation, see CopyObject and
+ * UploadPart.
*
*
*
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). For more
+ * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). For more
* information, see Protecting data with server-side encryption in the Amazon S3 User Guide.
*
- *
For directory buckets, when you perform a
- * CreateMultipartUpload operation and an
- * UploadPartCopy operation, the request headers you provide
- * in the CreateMultipartUpload request must match the default
- * encryption configuration of the destination bucket.
+ *
For directory buckets, when you perform a CreateMultipartUpload operation
+ * and an UploadPartCopy operation, the request headers you provide in the
+ * CreateMultipartUpload request must match the default encryption configuration
+ * of the destination bucket.
*
*
S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
* to directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through UploadPartCopy. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
Description: The specified multipart upload does not exist. The
- * upload ID might be invalid, or the multipart upload might have been
- * aborted or completed.
+ *
Description: The specified multipart upload does not exist. The upload ID might be
+ * invalid, or the multipart upload might have been aborted or completed.
This operation is not supported for directory buckets.
*
- *
Passes transformed objects to a GetObject operation when using Object Lambda access points. For
- * information about Object Lambda access points, see Transforming objects with
- * Object Lambda access points in the Amazon S3 User Guide.
+ *
Passes transformed objects to a GetObject operation when using Object Lambda access points. For information
+ * about Object Lambda access points, see Transforming objects with Object Lambda access points in the Amazon S3 User Guide.
*
This operation supports metadata that can be returned by GetObject, in addition to
- * RequestRoute, RequestToken, StatusCode,
- * ErrorCode, and ErrorMessage. The GetObject
- * response metadata is supported so that the WriteGetObjectResponse caller,
- * typically an Lambda function, can provide the same metadata when it internally invokes
- * GetObject. When WriteGetObjectResponse is called by a
- * customer-owned Lambda function, the metadata returned to the end user
- * GetObject call might differ from what Amazon S3 would normally return.
- *
You can include any number of metadata headers. When including a metadata header, it
- * should be prefaced with x-amz-meta. For example,
- * x-amz-meta-my-custom-header: MyCustomValue. The primary use case for this
- * is to forward GetObject metadata.
- *
Amazon Web Services provides some prebuilt Lambda functions that you can use with S3 Object Lambda to
- * detect and redact personally identifiable information (PII) and decompress S3 objects.
- * These Lambda functions are available in the Amazon Web Services Serverless Application Repository, and
- * can be selected through the Amazon Web Services Management Console when you create your Object Lambda access point.
- *
Example 1: PII Access Control - This Lambda function uses Amazon Comprehend, a
- * natural language processing (NLP) service using machine learning to find insights and
- * relationships in text. It automatically detects personally identifiable information (PII)
- * such as names, addresses, dates, credit card numbers, and social security numbers from
- * documents in your Amazon S3 bucket.
- *
Example 2: PII Redaction - This Lambda function uses Amazon Comprehend, a natural
- * language processing (NLP) service using machine learning to find insights and relationships
- * in text. It automatically redacts personally identifiable information (PII) such as names,
- * addresses, dates, credit card numbers, and social security numbers from documents in your
- * Amazon S3 bucket.
- *
Example 3: Decompression - The Lambda function S3ObjectLambdaDecompression, is
- * equipped to decompress objects stored in S3 in one of six compressed file formats including
- * bzip2, gzip, snappy, zlib, zstandard and ZIP.
+ * RequestRoute, RequestToken, StatusCode, ErrorCode,
+ * and ErrorMessage. The GetObject response metadata is supported so that the
+ * WriteGetObjectResponse caller, typically an Lambda function, can provide the same
+ * metadata when it internally invokes GetObject. When WriteGetObjectResponse is
+ * called by a customer-owned Lambda function, the metadata returned to the end user GetObject
+ * call might differ from what Amazon S3 would normally return.
+ *
You can include any number of metadata headers. When including a metadata header, it should be
+ * prefaced with x-amz-meta. For example, x-amz-meta-my-custom-header:
+ * MyCustomValue. The primary use case for this is to forward GetObject
+ * metadata.
+ *
Amazon Web Services provides some prebuilt Lambda functions that you can use with S3 Object Lambda to detect and
+ * redact personally identifiable information (PII) and decompress S3 objects. These Lambda functions are
+ * available in the Amazon Web Services Serverless Application Repository, and can be selected through the Amazon Web Services
+ * Management Console when you create your Object Lambda access point.
+ *
Example 1: PII Access Control - This Lambda function uses Amazon Comprehend, a natural
+ * language processing (NLP) service using machine learning to find insights and relationships in text. It
+ * automatically detects personally identifiable information (PII) such as names, addresses, dates, credit
+ * card numbers, and social security numbers from documents in your Amazon S3 bucket.
+ *
Example 2: PII Redaction - This Lambda function uses Amazon Comprehend, a natural language
+ * processing (NLP) service using machine learning to find insights and relationships in text. It
+ * automatically redacts personally identifiable information (PII) such as names, addresses, dates, credit
+ * card numbers, and social security numbers from documents in your Amazon S3 bucket.
+ *
Example 3: Decompression - The Lambda function S3ObjectLambdaDecompression, is equipped to
+ * decompress objects stored in S3 in one of six compressed file formats including bzip2, gzip, snappy,
+ * zlib, zstandard and ZIP.
* @example
* Use a bare-bones client and the command you need to make an API call.
* ```javascript
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/index.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/index.d.ts
index 2b6bafb7..6eba8258 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/index.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/commands/index.d.ts
@@ -2,6 +2,7 @@ export * from "./AbortMultipartUploadCommand";
export * from "./CompleteMultipartUploadCommand";
export * from "./CopyObjectCommand";
export * from "./CreateBucketCommand";
+export * from "./CreateBucketMetadataConfigurationCommand";
export * from "./CreateBucketMetadataTableConfigurationCommand";
export * from "./CreateMultipartUploadCommand";
export * from "./CreateSessionCommand";
@@ -12,6 +13,7 @@ export * from "./DeleteBucketEncryptionCommand";
export * from "./DeleteBucketIntelligentTieringConfigurationCommand";
export * from "./DeleteBucketInventoryConfigurationCommand";
export * from "./DeleteBucketLifecycleCommand";
+export * from "./DeleteBucketMetadataConfigurationCommand";
export * from "./DeleteBucketMetadataTableConfigurationCommand";
export * from "./DeleteBucketMetricsConfigurationCommand";
export * from "./DeleteBucketOwnershipControlsCommand";
@@ -33,6 +35,7 @@ export * from "./GetBucketInventoryConfigurationCommand";
export * from "./GetBucketLifecycleConfigurationCommand";
export * from "./GetBucketLocationCommand";
export * from "./GetBucketLoggingCommand";
+export * from "./GetBucketMetadataConfigurationCommand";
export * from "./GetBucketMetadataTableConfigurationCommand";
export * from "./GetBucketMetricsConfigurationCommand";
export * from "./GetBucketNotificationConfigurationCommand";
@@ -94,6 +97,8 @@ export * from "./PutPublicAccessBlockCommand";
export * from "./RenameObjectCommand";
export * from "./RestoreObjectCommand";
export * from "./SelectObjectContentCommand";
+export * from "./UpdateBucketMetadataInventoryTableConfigurationCommand";
+export * from "./UpdateBucketMetadataJournalTableConfigurationCommand";
export * from "./UploadPartCommand";
export * from "./UploadPartCopyCommand";
export * from "./WriteGetObjectResponseCommand";
diff --git a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/models/models_0.d.ts b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/models/models_0.d.ts
index d530e3fb..a8f7679b 100644
--- a/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/models/models_0.d.ts
+++ b/SerpentRace_Backend/node_modules/@aws-sdk/client-s3/dist-types/models/models_0.d.ts
@@ -2,16 +2,15 @@ import { ExceptionOptionType as __ExceptionOptionType } from "@smithy/smithy-cli
import { StreamingBlobTypes } from "@smithy/types";
import { S3ServiceException as __BaseException } from "./S3ServiceException";
/**
- *
The bucket name to which the upload was taking place.
*
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -91,12 +90,11 @@ export interface AbortMultipartUploadRequest {
*/
UploadId: string | undefined;
/**
- *
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
If present, this header aborts an in progress multipart upload only if it was initiated on the provided timestamp.
- * If the initiated timestamp of the multipart upload does not match the provided value, the operation returns a 412 Precondition Failed error.
- * If the initiated timestamp matches or if the multipart upload doesn’t exist, the operation returns a 204 Success (No Content) response.
- *
+ *
If present, this header aborts an in progress multipart upload only if it was initiated on the
+ * provided timestamp. If the initiated timestamp of the multipart upload does not match the provided
+ * value, the operation returns a 412 Precondition Failed error. If the initiated timestamp
+ * matches or if the multipart upload doesn’t exist, the operation returns a 204 Success (No
+ * Content) response.
*
*
This functionality is only supported for directory buckets.
Configures the transfer acceleration state for an Amazon S3 bucket. For more information, see
- * Amazon S3
- * Transfer Acceleration in the Amazon S3 User Guide.
+ *
Configures the transfer acceleration state for an Amazon S3 bucket. For more information, see Amazon S3 Transfer
+ * Acceleration in the Amazon S3 User Guide.
If the object expiration is configured, this will contain the expiration date
- * (expiry-date) and rule ID (rule-id). The value of
- * rule-id is URL-encoded.
+ * (expiry-date) and rule ID (rule-id). The value of rule-id is
+ * URL-encoded.
*
*
This functionality is not supported for directory buckets.
Entity tag that identifies the newly created object's data. Objects with different
- * object data will have different entity tags. The entity tag is an opaque string. The entity
- * tag may or may not be an MD5 digest of the object data. If the entity tag is not an MD5
- * digest of the object data, it will contain one or more nonhexadecimal characters and/or
- * will consist of less than 32 or more than 32 hexadecimal digits. For more information about
- * how the entity tag is calculated, see Checking object
- * integrity in the Amazon S3 User Guide.
+ *
Entity tag that identifies the newly created object's data. Objects with different object data will
+ * have different entity tags. The entity tag is an opaque string. The entity tag may or may not be an MD5
+ * digest of the object data. If the entity tag is not an MD5 digest of the object data, it will contain
+ * one or more nonhexadecimal characters and/or will consist of less than 32 or more than 32 hexadecimal
+ * digits. For more information about how the entity tag is calculated, see Checking object integrity in
+ * the Amazon S3 User Guide.
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, 64-bit
- * CRC64NVME checksum of the object. The CRC64NVME checksum is
- * always a full object checksum. For more information, see Checking object integrity
- * in the Amazon S3 User Guide.
+ *
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, 64-bit CRC64NVME
+ * checksum of the object. The CRC64NVME checksum is always a full object checksum. For more
+ * information, see Checking object integrity in the Amazon S3
+ * User Guide.
The checksum type, which determines how part-level checksums are combined to create an
- * object-level checksum for multipart objects. You can use this header as a data integrity
- * check to verify that the checksum type that is received is the same checksum type that was
- * specified during the CreateMultipartUpload request. For more information, see
- * Checking object integrity
- * in the Amazon S3 User Guide.
+ *
The checksum type, which determines how part-level checksums are combined to create an object-level
+ * checksum for multipart objects. You can use this header as a data integrity check to verify that the
+ * checksum type that is received is the same checksum type that was specified during the
+ * CreateMultipartUpload request. For more information, see Checking object integrity in the Amazon S3
+ * User Guide.
The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present
- * if the multipart upload request was created with the CRC32 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present if the
+ * multipart upload request was created with the CRC32 checksum algorithm. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present
- * if the multipart upload request was created with the CRC32C checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present if the
+ * multipart upload request was created with the CRC32C checksum algorithm. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present
- * if the multipart upload request was created with the CRC64NVME checksum algorithm to the uploaded object). For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present if
+ * the multipart upload request was created with the CRC64NVME checksum algorithm to the
+ * uploaded object). For more information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present
- * if the multipart upload request was created with the SHA1 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present if the
+ * multipart upload request was created with the SHA1 checksum algorithm. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present
- * if the multipart upload request was created with the SHA256 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present if
+ * the multipart upload request was created with the SHA256 checksum algorithm. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
Part number that identifies the part. This is a positive integer between 1 and
- * 10,000.
+ *
Part number that identifies the part. This is a positive integer between 1 and 10,000.
*
*
*
*
* General purpose buckets - In
- * CompleteMultipartUpload, when a additional checksum (including
- * x-amz-checksum-crc32, x-amz-checksum-crc32c,
- * x-amz-checksum-sha1, or x-amz-checksum-sha256) is
- * applied to each part, the PartNumber must start at 1 and the part
- * numbers must be consecutive. Otherwise, Amazon S3 generates an HTTP 400 Bad
- * Request status code and an InvalidPartOrder error
- * code.
+ * CompleteMultipartUpload, when a additional checksum (including
+ * x-amz-checksum-crc32, x-amz-checksum-crc32c,
+ * x-amz-checksum-sha1, or x-amz-checksum-sha256) is applied to each
+ * part, the PartNumber must start at 1 and the part numbers must be consecutive.
+ * Otherwise, Amazon S3 generates an HTTP 400 Bad Request status code and an
+ * InvalidPartOrder error code.
*
*
*
* Directory buckets - In
- * CompleteMultipartUpload, the PartNumber must start at
- * 1 and the part numbers must be consecutive.
+ * CompleteMultipartUpload, the PartNumber must start at 1 and the part
+ * numbers must be consecutive.
*
Name of the bucket to which the multipart upload was initiated.
*
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -655,11 +659,11 @@ export interface CompleteMultipartUploadRequest {
*/
ChecksumCRC32C?: string | undefined;
/**
- *
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, 64-bit
- * CRC64NVME checksum of the object. The CRC64NVME checksum is
- * always a full object checksum. For more information, see Checking object integrity
- * in the Amazon S3 User Guide.
+ *
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, 64-bit CRC64NVME
+ * checksum of the object. The CRC64NVME checksum is always a full object checksum. For more
+ * information, see Checking object integrity in the Amazon S3
+ * User Guide.
This header specifies the checksum type of the object, which determines how part-level
- * checksums are combined to create an object-level checksum for multipart objects. You can
- * use this header as a data integrity check to verify that the checksum type that is received
- * is the same checksum that was specified. If the checksum type doesn’t match the checksum
- * type that was specified for the object during the CreateMultipartUpload
- * request, it’ll result in a BadDigest error. For more information, see Checking
- * object integrity in the Amazon S3 User Guide.
+ *
This header specifies the checksum type of the object, which determines how part-level checksums are
+ * combined to create an object-level checksum for multipart objects. You can use this header as a data
+ * integrity check to verify that the checksum type that is received is the same checksum that was
+ * specified. If the checksum type doesn’t match the checksum type that was specified for the object during
+ * the CreateMultipartUpload request, it’ll result in a BadDigest error. For more
+ * information, see Checking object integrity in the Amazon S3 User Guide.
The expected total object size of the multipart upload request. If there’s a mismatch
- * between the specified object size value and the actual object size value, it results in an
- * HTTP 400 InvalidRequest error.
+ *
The expected total object size of the multipart upload request. If there’s a mismatch between the
+ * specified object size value and the actual object size value, it results in an HTTP 400
+ * InvalidRequest error.
* @public
*/
MpuObjectSize?: number | undefined;
/**
- *
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Uploads the object only if the ETag (entity tag) value provided during the WRITE
- * operation matches the ETag of the object in S3. If the ETag values do not match, the
- * operation returns a 412 Precondition Failed error.
+ *
Uploads the object only if the ETag (entity tag) value provided during the WRITE operation matches
+ * the ETag of the object in S3. If the ETag values do not match, the operation returns a 412
+ * Precondition Failed error.
*
If a conflicting operation occurs during the upload S3 returns a 409
- * ConditionalRequestConflict response. On a 409 failure you should fetch the object's ETag, re-initiate the
- * multipart upload with CreateMultipartUpload, and re-upload each part.
+ * ConditionalRequestConflict response. On a 409 failure you should fetch the object's ETag,
+ * re-initiate the multipart upload with CreateMultipartUpload, and re-upload each
+ * part.
*
Expects the ETag value as a string.
- *
For more information about conditional requests, see RFC 7232, or Conditional requests in the Amazon S3 User Guide.
+ *
For more information about conditional requests, see RFC 7232, or Conditional requests in the
+ * Amazon S3 User Guide.
Uploads the object only if the object key name does not already exist in the bucket
- * specified. Otherwise, Amazon S3 returns a 412 Precondition Failed error.
+ *
Uploads the object only if the object key name does not already exist in the bucket specified.
+ * Otherwise, Amazon S3 returns a 412 Precondition Failed error.
*
If a conflicting operation occurs during the upload S3 returns a 409
- * ConditionalRequestConflict response. On a 409 failure you should re-initiate the
- * multipart upload with CreateMultipartUpload and re-upload each part.
+ * ConditionalRequestConflict response. On a 409 failure you should re-initiate the multipart
+ * upload with CreateMultipartUpload and re-upload each part.
*
Expects the '*' (asterisk) character.
- *
For more information about conditional requests, see RFC 7232, or Conditional requests in the Amazon S3 User Guide.
+ *
For more information about conditional requests, see RFC 7232, or Conditional requests in the
+ * Amazon S3 User Guide.
The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is
- * required only when the object was created using a checksum algorithm or if your bucket
- * policy requires the use of SSE-C. For more information, see Protecting data using SSE-C keys in the Amazon S3 User
- * Guide.
+ *
The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is required
+ * only when the object was created using a checksum algorithm or if your bucket policy requires the use of
+ * SSE-C. For more information, see Protecting data using SSE-C keys in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
The checksum type that is used to calculate the object’s
- * checksum value. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The checksum type that is used to calculate the object’s checksum value. For more information, see
+ * Checking
+ * object integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the object. This checksum is present
- * if the object being copied was uploaded with the CRC64NVME checksum algorithm, or if the object was uploaded without a
- * checksum (and Amazon S3 added the default checksum, CRC64NVME, to the uploaded object). For more information, see Checking object integrity in the Amazon S3 User Guide.
+ * if the object being copied was uploaded with the CRC64NVME checksum algorithm, or if the
+ * object was uploaded without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to
+ * the uploaded object). For more information, see Checking object integrity in
+ * the Amazon S3 User Guide.
* @public
*/
ChecksumCRC64NVME?: string | undefined;
@@ -842,7 +849,8 @@ export interface CopyObjectOutput {
/**
*
If the object expiration is configured, the response includes this header.
*
- *
Object expiration information is not returned in directory buckets and this header returns the value "NotImplemented" in all responses for directory buckets.
+ *
Object expiration information is not returned in directory buckets and this header returns the
+ * value "NotImplemented" in all responses for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to confirm the encryption algorithm that's used.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to confirm the encryption algorithm that's used.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to provide the round-trip message integrity verification
- * of the customer-provided encryption key.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to provide the round-trip message integrity verification of the customer-provided
+ * encryption key.
*
*
This functionality is not supported for directory buckets.
If present, indicates the Amazon Web Services KMS Encryption Context to use for object encryption. The
- * value of this header is a Base64 encoded UTF-8 string holding JSON with the encryption
- * context key-value pairs.
+ *
If present, indicates the Amazon Web Services KMS Encryption Context to use for object encryption. The value of
+ * this header is a Base64 encoded UTF-8 string holding JSON with the encryption context key-value
+ * pairs.
The canned access control list (ACL) to apply to the object.
- *
When you copy an object, the ACL metadata is not preserved and is set to
- * private by default. Only the owner has full access control. To override the
- * default ACL setting, specify a new ACL when you generate a copy request. For more
- * information, see Using ACLs.
- *
If the destination bucket that you're copying objects to uses the bucket owner enforced
- * setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions.
- * Buckets that use this setting only accept PUT requests that don't specify an
- * ACL or PUT requests that specify bucket owner full control ACLs, such as the
- * bucket-owner-full-control canned ACL or an equivalent form of this ACL
- * expressed in the XML format. For more information, see Controlling ownership of
- * objects and disabling ACLs in the Amazon S3 User Guide.
+ *
When you copy an object, the ACL metadata is not preserved and is set to private by
+ * default. Only the owner has full access control. To override the default ACL setting, specify a new ACL
+ * when you generate a copy request. For more information, see Using ACLs.
+ *
If the destination bucket that you're copying objects to uses the bucket owner enforced setting for
+ * S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that use this setting
+ * only accept PUT requests that don't specify an ACL or PUT requests that
+ * specify bucket owner full control ACLs, such as the bucket-owner-full-control canned ACL or
+ * an equivalent form of this ACL expressed in the XML format. For more information, see Controlling ownership
+ * of objects and disabling ACLs in the Amazon S3 User Guide.
*
*
*
- *
If your destination bucket uses the bucket owner enforced setting for Object
- * Ownership, all objects written to the bucket by any account will be owned by the
- * bucket owner.
+ *
If your destination bucket uses the bucket owner enforced setting for Object Ownership, all
+ * objects written to the bucket by any account will be owned by the bucket owner.
*
*
*
This functionality is not supported for directory buckets.
@@ -1065,8 +1072,10 @@ export interface CopyObjectRequest {
* restrictions, see Directory bucket naming
* rules in the Amazon S3 User Guide.
*
- *
Copying objects across different Amazon Web Services Regions isn't supported when the source or destination bucket is in Amazon Web Services Local Zones. The source and destination buckets must have the same parent Amazon Web Services Region. Otherwise,
- * you get an HTTP 400 Bad Request error with the error code InvalidRequest.
+ *
Copying objects across different Amazon Web Services Regions isn't supported when the source or destination
+ * bucket is in Amazon Web Services Local Zones. The source and destination buckets must have the same parent Amazon Web Services Region.
+ * Otherwise, you get an HTTP 400 Bad Request error with the error code
+ * InvalidRequest.
*
*
* Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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.
Object Lambda access points are not supported by directory buckets.
*
*
- * S3 on Outposts - When you use this action with S3 on Outposts, you must use the Outpost bucket access point ARN or the access point alias for the destination bucket.
- *
- * You can only copy objects within the same Outpost bucket. It's not supported to copy objects across different Amazon Web Services Outposts, between buckets on the same Outposts, or between Outposts buckets and any other bucket types.
- * For more information about S3 on Outposts, see What is S3 on Outposts? in the S3 on Outposts guide.
- * When you use this action with S3 on Outposts through the REST API, you must direct requests to the S3 on Outposts hostname, in the format
- *
- * AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com. The hostname isn't required when you use the Amazon Web Services CLI or SDKs.
- *
+ * S3 on Outposts - When you use this action with S3 on Outposts,
+ * you must use the Outpost bucket access point ARN or the access point alias for the destination bucket.
+ * You can only copy objects within the same Outpost bucket. It's not supported to copy objects across
+ * different Amazon Web Services Outposts, between buckets on the same Outposts, or between Outposts buckets and any
+ * other bucket types. For more information about S3 on Outposts, see What is S3 on Outposts? in the
+ * S3 on Outposts guide. When you use this action with S3 on Outposts through the REST
+ * API, you must direct requests to the S3 on Outposts hostname, in the format
+ *
+ * AccessPointName-AccountId.outpostID.s3-outposts.Region.amazonaws.com.
+ * The hostname isn't required when you use the Amazon Web Services CLI or SDKs.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
Indicates the algorithm that you want Amazon S3 to use to create the checksum for the object. For more information, see
* Checking object integrity in
* the Amazon S3 User Guide.
- *
When you copy an object, if the source object has a checksum, that checksum value will
- * be copied to the new object by default. If the CopyObject request does not
- * include this x-amz-checksum-algorithm header, the checksum algorithm will be
- * copied from the source object to the destination object (if it's present on the source
- * object). You can optionally specify a different checksum algorithm to use with the
- * x-amz-checksum-algorithm header. Unrecognized or unsupported values will
- * respond with the HTTP status code 400 Bad Request.
+ *
When you copy an object, if the source object has a checksum, that checksum value will be copied to
+ * the new object by default. If the CopyObject request does not include this
+ * x-amz-checksum-algorithm header, the checksum algorithm will be copied from the source
+ * object to the destination object (if it's present on the source object). You can optionally specify a
+ * different checksum algorithm to use with the x-amz-checksum-algorithm header. Unrecognized
+ * or unsupported values will respond with the HTTP status code 400 Bad Request.
*
*
For directory buckets, when you use Amazon Web Services SDKs, CRC32 is the default checksum algorithm that's used for performance.
Specifies presentational information for the object. Indicates whether an object should
- * be displayed in a web browser or downloaded as a file. It allows specifying the desired
- * filename for the downloaded file.
+ *
Specifies presentational information for the object. Indicates whether an object should be displayed
+ * in a web browser or downloaded as a file. It allows specifying the desired filename for the downloaded
+ * file.
Specifies what content encodings have been applied to the object and thus what decoding
- * mechanisms must be applied to obtain the media-type referenced by the Content-Type header
- * field.
+ *
Specifies what content encodings have been applied to the object and thus what decoding mechanisms
+ * must be applied to obtain the media-type referenced by the Content-Type header field.
*
*
For directory buckets, only the aws-chunked value is supported in this header field.
Specifies the source object for the copy operation. The source object can be up to 5 GB.
- * If the source object is an object that was uploaded by using a multipart upload, the object
- * copy will be a single part object after the source object is copied to the destination
- * bucket.
- *
You specify the value of the copy source in one of two formats, depending on whether you
- * want to access the source object through an access point:
+ *
Specifies the source object for the copy operation. The source object can be up to 5 GB. If the
+ * source object is an object that was uploaded by using a multipart upload, the object copy will be a
+ * single part object after the source object is copied to the destination bucket.
+ *
You specify the value of the copy source in one of two formats, depending on whether you want to
+ * access the source object through an access point:
*
*
- *
For objects not accessed through an access point, specify the name of the source bucket
- * and the key of the source object, separated by a slash (/). For example, to copy the
- * object reports/january.pdf from the general purpose bucket
- * awsexamplebucket, use
- * awsexamplebucket/reports/january.pdf. The value must be URL-encoded.
- * To copy the object reports/january.pdf from the directory bucket
- * awsexamplebucket--use1-az5--x-s3, use
- * awsexamplebucket--use1-az5--x-s3/reports/january.pdf. The value must
- * be URL-encoded.
+ *
For objects not accessed through an access point, specify the name of the source bucket and the key of
+ * the source object, separated by a slash (/). For example, to copy the object
+ * reports/january.pdf from the general purpose bucket awsexamplebucket, use
+ * awsexamplebucket/reports/january.pdf. The value must be URL-encoded. To copy the
+ * object reports/january.pdf from the directory bucket
+ * awsexamplebucket--use1-az5--x-s3, use
+ * awsexamplebucket--use1-az5--x-s3/reports/january.pdf. The value must be
+ * URL-encoded.
*
*
*
For objects accessed through access points, specify the Amazon Resource Name (ARN) of the object as accessed through the access point, in the format arn:aws:s3:::accesspoint//object/. For example, to copy the object reports/january.pdf through access point my-access-point owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3:us-west-2:123456789012:accesspoint/my-access-point/object/reports/january.pdf. The value must be URL encoded.
Alternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format arn:aws:s3-outposts:::outpost//object/. For example, to copy the object reports/january.pdf through outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf. The value must be URL-encoded.
*
*
- *
If your source bucket versioning is enabled, the x-amz-copy-source header
- * by default identifies the current version of an object to copy. If the current version is a
- * delete marker, Amazon S3 behaves as if the object was deleted. To copy a different version, use
- * the versionId query parameter. Specifically, append
- * ?versionId= to the value (for example,
- * awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893).
- * If you don't specify a version ID, Amazon S3 copies the latest version of the source
- * object.
- *
If you enable versioning on the destination bucket, Amazon S3 generates a unique version ID
- * for the copied object. This version ID is different from the version ID of the source
- * object. Amazon S3 returns the version ID of the copied object in the
- * x-amz-version-id response header in the response.
- *
If you do not enable versioning or suspend it on the destination bucket, the version ID
- * that Amazon S3 generates in the x-amz-version-id response header is always
- * null.
+ *
If your source bucket versioning is enabled, the x-amz-copy-source header by default
+ * identifies the current version of an object to copy. If the current version is a delete marker, Amazon S3
+ * behaves as if the object was deleted. To copy a different version, use the versionId query
+ * parameter. Specifically, append ?versionId= to the value (for example,
+ * awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893). If
+ * you don't specify a version ID, Amazon S3 copies the latest version of the source object.
+ *
If you enable versioning on the destination bucket, Amazon S3 generates a unique version ID for the
+ * copied object. This version ID is different from the version ID of the source object. Amazon S3 returns the
+ * version ID of the copied object in the x-amz-version-id response header in the
+ * response.
+ *
If you do not enable versioning or suspend it on the destination bucket, the version ID that Amazon S3
+ * generates in the x-amz-version-id response header is always null.
*
*
- * Directory buckets -
- * S3 Versioning isn't enabled and supported for directory buckets.
Copies the object if its entity tag (ETag) matches the specified tag.
*
If both the x-amz-copy-source-if-match and
- * x-amz-copy-source-if-unmodified-since headers are present in the request
- * and evaluate as follows, Amazon S3 returns 200 OK and copies the data:
+ * x-amz-copy-source-if-unmodified-since headers are present in the request and evaluate as
+ * follows, Amazon S3 returns 200 OK and copies the data:
*
Copies the object if it has been modified since the specified time.
*
If both the x-amz-copy-source-if-none-match and
- * x-amz-copy-source-if-modified-since headers are present in the request and
- * evaluate as follows, Amazon S3 returns the 412 Precondition Failed response
- * code:
+ * x-amz-copy-source-if-modified-since headers are present in the request and evaluate as
+ * follows, Amazon S3 returns the 412 Precondition Failed response code:
*
Copies the object if its entity tag (ETag) is different than the specified ETag.
*
If both the x-amz-copy-source-if-none-match and
- * x-amz-copy-source-if-modified-since headers are present in the request and
- * evaluate as follows, Amazon S3 returns the 412 Precondition Failed response
- * code:
+ * x-amz-copy-source-if-modified-since headers are present in the request and evaluate as
+ * follows, Amazon S3 returns the 412 Precondition Failed response code:
*
Copies the object if it hasn't been modified since the specified time.
*
If both the x-amz-copy-source-if-match and
- * x-amz-copy-source-if-unmodified-since headers are present in the request
- * and evaluate as follows, Amazon S3 returns 200 OK and copies the data:
+ * x-amz-copy-source-if-unmodified-since headers are present in the request and evaluate as
+ * follows, Amazon S3 returns 200 OK and copies the data:
*
Specifies whether the metadata is copied from the source object or replaced with
- * metadata that's provided in the request. When copying an object, you can preserve all
- * metadata (the default) or specify new metadata. If this header isn’t specified,
- * COPY is the default behavior.
+ *
Specifies whether the metadata is copied from the source object or replaced with metadata that's
+ * provided in the request. When copying an object, you can preserve all metadata (the default) or specify
+ * new metadata. If this header isn’t specified, COPY is the default behavior.
*
- * General purpose bucket - For general purpose buckets, when you
- * grant permissions, you can use the s3:x-amz-metadata-directive condition key
- * to enforce certain metadata behavior when objects are uploaded. For more information, see
- * Amazon S3
- * condition key examples in the Amazon S3 User Guide.
+ * General purpose bucket - For general purpose buckets, when you grant
+ * permissions, you can use the s3:x-amz-metadata-directive condition key to enforce certain
+ * metadata behavior when objects are uploaded. For more information, see Amazon S3 condition key examples in the
+ * Amazon S3 User Guide.
*
*
- * x-amz-website-redirect-location is unique to each object and is not
- * copied when using the x-amz-metadata-directive header. To copy the value,
- * you must specify x-amz-website-redirect-location in the request
- * header.
+ * x-amz-website-redirect-location is unique to each object and is not copied when using
+ * the x-amz-metadata-directive header. To copy the value, you must specify
+ * x-amz-website-redirect-location in the request header.
*
* @public
*/
MetadataDirective?: MetadataDirective | undefined;
/**
- *
Specifies whether the object tag-set is copied from the source object or replaced with
- * the tag-set that's provided in the request.
+ *
Specifies whether the object tag-set is copied from the source object or replaced with the tag-set
+ * that's provided in the request.
The server-side encryption algorithm used when storing this object in Amazon S3. Unrecognized
- * or unsupported values won’t write a destination object and will receive a 400 Bad
- * Request response.
- *
Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket. When
- * copying an object, if you don't specify encryption information in your copy request, the
- * encryption setting of the target object is set to the default encryption configuration of
- * the destination bucket. By default, all buckets have a base level of encryption
- * configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3). If the
- * destination bucket has a different default encryption configuration, Amazon S3 uses the
- * corresponding encryption key to encrypt the target object copy.
- *
With server-side encryption, Amazon S3 encrypts your data as it writes your data to disks in
- * its data centers and decrypts the data when you access it. For more information about
- * server-side encryption, see Using Server-Side Encryption
- * in the Amazon S3 User Guide.
+ *
The server-side encryption algorithm used when storing this object in Amazon S3. Unrecognized or
+ * unsupported values won’t write a destination object and will receive a 400 Bad Request
+ * response.
+ *
Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket. When copying an object,
+ * if you don't specify encryption information in your copy request, the encryption setting of the target
+ * object is set to the default encryption configuration of the destination bucket. By default, all buckets
+ * have a base level of encryption configuration that uses server-side encryption with Amazon S3 managed keys
+ * (SSE-S3). If the destination bucket has a different default encryption configuration, Amazon S3 uses the
+ * corresponding encryption key to encrypt the target object copy.
+ *
With server-side encryption, Amazon S3 encrypts your data as it writes your data to disks in its data
+ * centers and decrypts the data when you access it. For more information about server-side encryption, see
+ * Using Server-Side
+ * Encryption in the Amazon S3 User Guide.
*
* General purpose buckets
*
*
*
- *
For general purpose buckets, there are the following supported options for server-side
- * encryption: server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer
- * server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), and server-side encryption
- * with customer-provided encryption keys (SSE-C). Amazon S3 uses the corresponding
- * KMS key, or a customer-provided key to encrypt the target object copy.
+ *
For general purpose buckets, there are the following supported options for server-side encryption:
+ * server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer server-side encryption with
+ * Amazon Web Services KMS keys (DSSE-KMS), and server-side encryption with customer-provided encryption keys
+ * (SSE-C). Amazon S3 uses the corresponding KMS key, or a customer-provided key to encrypt the target
+ * object copy.
*
*
- *
When you perform a CopyObject operation, if you want to use a
- * different type of encryption setting for the target object, you can specify
- * appropriate encryption-related headers to encrypt the target object with an Amazon S3
- * managed key, a KMS key, or a customer-provided key. If the encryption setting in
- * your request is different from the default encryption configuration of the
- * destination bucket, the encryption setting in your request takes precedence.
+ *
When you perform a CopyObject operation, if you want to use a different type of
+ * encryption setting for the target object, you can specify appropriate encryption-related headers to
+ * encrypt the target object with an Amazon S3 managed key, a KMS key, or a customer-provided key. If the
+ * encryption setting in your request is different from the default encryption configuration of the
+ * destination bucket, the encryption setting in your request takes precedence.
To encrypt new object copies to a directory bucket with SSE-KMS, we recommend you
- * specify SSE-KMS as the directory bucket's default encryption configuration with
- * a KMS key (specifically, a customer managed key).
- * The Amazon Web Services managed key (aws/s3) isn't supported. Your SSE-KMS
- * configuration can only support 1 customer managed key per
- * directory bucket for the lifetime of the bucket. After you specify a customer managed key for
- * SSE-KMS, you can't override the customer managed key for the bucket's SSE-KMS
- * configuration. Then, when you perform a CopyObject operation and want to
- * specify server-side encryption settings for new object copies with SSE-KMS in the
- * encryption-related request headers, you must ensure the encryption key is the same
- * customer managed key that you specified for the directory bucket's default encryption
- * configuration.
- *
+ *
To encrypt new object copies to a directory bucket with SSE-KMS, we recommend you specify
+ * SSE-KMS as the directory bucket's default encryption configuration with a KMS key
+ * (specifically, a customer managed key). The Amazon Web Services managed key (aws/s3) isn't supported. Your SSE-KMS configuration can
+ * only support 1 customer managed key per
+ * directory bucket for the lifetime of the bucket. After you specify a customer managed key for SSE-KMS, you
+ * can't override the customer managed key for the bucket's SSE-KMS configuration. Then, when you
+ * perform a CopyObject operation and want to specify server-side encryption settings for
+ * new object copies with SSE-KMS in the encryption-related request headers, you must ensure the
+ * encryption key is the same customer managed key that you specified for the directory bucket's default
+ * encryption configuration.
+ *
*
*
*
- * S3 access points for Amazon FSx - When accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side encryption option is aws:fsx. All Amazon FSx file systems have encryption configured by default and are encrypted at rest. Data is automatically encrypted before being written to the file system, and automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
+ * S3 access points for Amazon FSx - When accessing data stored in
+ * Amazon FSx file systems using S3 access points, the only valid server side encryption option is
+ * aws:fsx. All Amazon FSx file systems have encryption configured by default and are
+ * encrypted at rest. Data is automatically encrypted before being written to the file system, and
+ * automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
*
If the x-amz-storage-class header is not used, the copied object will be
- * stored in the STANDARD Storage Class by default. The STANDARD
- * storage class provides high durability and high availability. Depending on performance
- * needs, you can specify a different Storage Class.
+ *
If the x-amz-storage-class header is not used, the copied object will be stored in the
+ * STANDARD Storage Class by default. The STANDARD storage class provides high
+ * durability and high availability. Depending on performance needs, you can specify a different Storage
+ * Class.
*
*
*
*
* Directory buckets -
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
* Unsupported storage class values won't write a destination object and will respond with the HTTP status code 400 Bad Request.
*
*
*
- * Amazon S3 on Outposts - S3 on Outposts only
- * uses the OUTPOSTS Storage Class.
+ * Amazon S3 on Outposts - S3 on Outposts only uses the
+ * OUTPOSTS Storage Class.
*
*
*
- *
You can use the CopyObject action to change the storage class of an object
- * that is already stored in Amazon S3 by using the x-amz-storage-class header. For
- * more information, see Storage Classes in the
- * Amazon S3 User Guide.
- *
Before using an object as a source object for the copy operation, you must restore a
- * copy of it if it meets any of the following conditions:
+ *
You can use the CopyObject action to change the storage class of an object that is
+ * already stored in Amazon S3 by using the x-amz-storage-class header. For more information, see
+ * Storage Classes
+ * in the Amazon S3 User Guide.
+ *
Before using an object as a source object for the copy operation, you must restore a copy of it if
+ * it meets any of the following conditions:
*
*
*
The storage class of the source object is GLACIER or
- * DEEP_ARCHIVE.
+ * DEEP_ARCHIVE.
*
*
- *
The storage class of the source object is INTELLIGENT_TIERING and
- * it's S3 Intelligent-Tiering access tier is Archive Access or
- * Deep Archive Access.
+ *
The storage class of the source object is INTELLIGENT_TIERING and it's S3
+ * Intelligent-Tiering access tier is Archive Access or Deep Archive
+ * Access.
If the destination bucket is configured as a website, redirects requests for this object
- * copy to another object in the same bucket or to an external URL. Amazon S3 stores the value of
- * this header in the object metadata. This value is unique to each object and is not copied
- * when using the x-amz-metadata-directive header. Instead, you may opt to
- * provide this header in combination with the x-amz-metadata-directive
- * header.
+ *
If the destination bucket is configured as a website, redirects requests for this object copy to
+ * another object in the same bucket or to an external URL. Amazon S3 stores the value of this header in the
+ * object metadata. This value is unique to each object and is not copied when using the
+ * x-amz-metadata-directive header. Instead, you may opt to provide this header in
+ * combination with the x-amz-metadata-directive header.
*
*
This functionality is not supported for directory buckets.
Specifies the algorithm to use when encrypting the object (for example,
- * AES256).
- *
When you perform a CopyObject operation, if you want to use a different
- * type of encryption setting for the target object, you can specify appropriate
- * encryption-related headers to encrypt the target object with an Amazon S3 managed key, a
- * KMS key, or a customer-provided key. If the encryption setting in your request is
- * different from the default encryption configuration of the destination bucket, the
- * encryption setting in your request takes precedence.
+ *
Specifies the algorithm to use when encrypting the object (for example, AES256).
+ *
When you perform a CopyObject operation, if you want to use a different type of
+ * encryption setting for the target object, you can specify appropriate encryption-related headers to
+ * encrypt the target object with an Amazon S3 managed key, a KMS key, or a customer-provided key. If the
+ * encryption setting in your request is different from the default encryption configuration of the
+ * destination bucket, the encryption setting in your request takes precedence.
*
*
This functionality is not supported when the destination bucket is a directory bucket.
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.
+ *
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 functionality is not supported when the destination bucket is a directory bucket.
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 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.
*
*
This functionality is not supported when the destination bucket is a directory bucket.
Specifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption.
- * All GET and PUT requests for an object protected by KMS will fail if they're not made via
- * SSL or using SigV4. For information about configuring any of the officially supported Amazon Web Services
- * SDKs and Amazon Web Services CLI, see Specifying the
- * Signature Version in Request Authentication in the
- * Amazon S3 User Guide.
+ *
Specifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption. All GET and
+ * PUT requests for an object protected by KMS will fail if they're not made via SSL or using SigV4. For
+ * information about configuring any of the officially supported Amazon Web Services SDKs and Amazon Web Services CLI, see Specifying
+ * the Signature Version in Request Authentication in the
+ * Amazon S3 User Guide.
*
* Directory buckets -
- * To encrypt data using SSE-KMS, it's recommended to specify the
+ * To encrypt data using SSE-KMS, it's recommended to specify the
* x-amz-server-side-encryption header to aws:kms. Then, the x-amz-server-side-encryption-aws-kms-key-id header implicitly uses
* the bucket's default KMS customer managed key ID. If you want to explicitly set the
* x-amz-server-side-encryption-aws-kms-key-id header, it must match the bucket's default customer managed key (using key ID or ARN, not alias). Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime.
@@ -1584,33 +1573,33 @@ export interface CopyObjectRequest {
*/
SSEKMSKeyId?: string | undefined;
/**
- *
Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use
- * for the destination object encryption. The value of this header is a base64-encoded UTF-8 string holding JSON with the encryption context key-value pairs.
+ *
Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use for the
+ * destination object encryption. The value of this header is a base64-encoded UTF-8 string holding JSON
+ * with the encryption context key-value pairs.
*
- * General purpose buckets - This value must be explicitly
- * added to specify encryption context for CopyObject requests if you want an
- * additional encryption context for your destination object. The additional encryption
- * context of the source object won't be copied to the destination object. For more
- * information, see Encryption
- * context in the Amazon S3 User Guide.
+ * General purpose buckets - This value must be explicitly added to
+ * specify encryption context for CopyObject requests if you want an additional encryption
+ * context for your destination object. The additional encryption context of the source object won't be
+ * copied to the destination object. For more information, see Encryption context
+ * in the Amazon S3 User Guide.
*
* Directory buckets - You can optionally provide an explicit encryption context value. The value must match the default encryption context - the bucket Amazon Resource Name (ARN). An additional encryption context value is not supported.
Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with
- * server-side encryption using Key Management Service (KMS) keys (SSE-KMS). If a target object uses
- * SSE-KMS, you can enable an S3 Bucket Key for the object.
- *
Setting this header to true causes Amazon S3 to use an S3 Bucket Key for object
- * encryption with SSE-KMS. Specifying this header with a COPY action doesn’t affect
- * bucket-level settings for S3 Bucket Key.
Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with server-side encryption
+ * using Key Management Service (KMS) keys (SSE-KMS). If a target object uses SSE-KMS, you can enable an S3 Bucket Key
+ * for the object.
+ *
Setting this header to true causes Amazon S3 to use an S3 Bucket Key for object encryption
+ * with SSE-KMS. Specifying this header with a COPY action doesn’t affect bucket-level settings for S3
+ * Bucket Key.
* Directory buckets -
- * S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
+ * S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
* to directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
Specifies the algorithm to use when decrypting the source object (for example,
- * AES256).
- *
If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
- * necessary encryption information in your request so that Amazon S3 can decrypt the object for
- * copying.
+ * AES256).
+ *
If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the necessary
+ * encryption information in your request so that Amazon S3 can decrypt the object for copying.
*
*
This functionality is not supported when the source object is in a directory bucket.
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 the same one that was used when
- * the source object was created.
- *
If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
- * necessary encryption information in your request so that Amazon S3 can decrypt the object for
- * copying.
+ *
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 the same one that was used when the source object was
+ * created.
+ *
If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the necessary
+ * encryption information in your request so that Amazon S3 can decrypt the object for copying.
*
*
This functionality is not supported when the source object is in a directory bucket.
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.
- *
If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
- * necessary encryption information in your request so that Amazon S3 can decrypt the object for
- * copying.
+ *
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.
+ *
If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the necessary
+ * encryption information in your request so that Amazon S3 can decrypt the object for copying.
*
*
This functionality is not supported when the source object is in a directory bucket.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
The tag-set for the object copy in the destination bucket. This value must be used in
- * conjunction with the x-amz-tagging-directive if you choose
- * REPLACE for the x-amz-tagging-directive. If you choose
- * COPY for the x-amz-tagging-directive, you don't need to set
- * the x-amz-tagging header, because the tag-set will be copied from the source
- * object directly. The tag-set must be encoded as URL Query parameters.
+ *
The tag-set for the object copy in the destination bucket. This value must be used in conjunction
+ * with the x-amz-tagging-directive if you choose REPLACE for the
+ * x-amz-tagging-directive. If you choose COPY for the
+ * x-amz-tagging-directive, you don't need to set the x-amz-tagging header,
+ * because the tag-set will be copied from the source object directly. The tag-set must be encoded as URL
+ * Query parameters.
The bucket you tried to create already exists, and you own it. Amazon S3 returns this error
- * in all Amazon Web Services Regions except in the North Virginia Region. For legacy compatibility, if you
- * re-create an existing bucket that you already own in the North Virginia Region, Amazon S3
- * returns 200 OK and resets the bucket access control lists (ACLs).
+ *
The bucket you tried to create already exists, and you own it. Amazon S3 returns this error in all Amazon Web Services
+ * Regions except in the North Virginia Region. For legacy compatibility, if you re-create an existing
+ * bucket that you already own in the North Virginia Region, Amazon S3 returns 200 OK and resets the bucket
+ * access control lists (ACLs).
Specifies the information about the bucket that will be created. For more information
- * about directory buckets, see Directory buckets in the Amazon S3 User Guide.
+ *
Specifies the information about the bucket that will be created. For more information about
+ * directory buckets, see Directory buckets in the
+ * Amazon S3 User Guide.
*
*
This functionality is only supported by directory buckets.
Specifies the location where the bucket will be created.
- *
For directory buckets, the location type is Availability Zone or Local Zone. For more information about directory buckets, see
- * Working with directory buckets in the Amazon S3 User Guide.
+ *
For directory buckets, the location type is Availability Zone or Local Zone. For more information about
+ * directory buckets, see Working with
+ * directory buckets in the Amazon S3 User Guide.
*
*
This functionality is only supported by directory buckets.
The name of the location where the bucket will be created.
- *
For directory buckets, the name of the location is the Zone ID of the Availability Zone (AZ) or Local Zone (LZ) where the bucket will be created. An example AZ ID value is usw2-az1.
+ *
For directory buckets, the name of the location is the Zone ID of the Availability Zone (AZ) or Local Zone (LZ) where
+ * the bucket will be created. An example AZ ID value is usw2-az1.
Specifies the Region where the bucket will be created. You might choose a Region to
- * optimize latency, minimize costs, or address regulatory requirements. For example, if you
- * reside in Europe, you will probably find it advantageous to create buckets in the Europe
- * (Ireland) Region.
- *
If you don't specify a Region, the bucket is created in the US East (N. Virginia) Region
- * (us-east-1) by default. Configurations using the value EU will create a bucket in eu-west-1.
- *
For a list of the valid values for all of the Amazon Web Services Regions, see Regions and
- * Endpoints.
+ *
Specifies the Region where the bucket will be created. You might choose a Region to optimize
+ * latency, minimize costs, or address regulatory requirements. For example, if you reside in Europe, you
+ * will probably find it advantageous to create buckets in the Europe (Ireland) Region.
+ *
If you don't specify a Region, the bucket is created in the US East (N. Virginia) Region (us-east-1)
+ * by default. Configurations using the value EU will create a bucket in
+ * eu-west-1.
+ *
For a list of the valid values for all of the Amazon Web Services Regions, see Regions and Endpoints.
*
*
This functionality is not supported for directory buckets.
Specifies the location where the bucket will be created.
*
- * Directory buckets - The location type is Availability Zone or Local Zone.
- * To use the Local Zone location type, your account must be enabled for Local Zones. Otherwise, you get an HTTP 403 Forbidden error with the
- * error code AccessDenied. To learn more, see Enable accounts for Local Zones in the Amazon S3 User Guide.
- *
+ * Directory buckets - The location type is Availability Zone or Local Zone. To
+ * use the Local Zone location type, your account must be enabled
+ * for Local Zones. Otherwise, you get an HTTP 403 Forbidden error with the error code
+ * AccessDenied. To learn more,
+ * see Enable
+ * accounts for Local Zones in the Amazon S3 User Guide.
*
*
This functionality is only supported by directory buckets.
An array of tags that you can apply to the bucket that you're creating. Tags are key-value pairs of metadata used to categorize and organize your buckets, track costs, and control access.
+ *
An array of tags that you can apply to the bucket that you're creating. Tags are key-value pairs of
+ * metadata used to categorize and organize your buckets, track costs, and control access.
The container element for object ownership for a bucket's ownership controls.
*
- * BucketOwnerPreferred - Objects uploaded to the bucket change ownership to
- * the bucket owner if the objects are uploaded with the
- * bucket-owner-full-control canned ACL.
+ * BucketOwnerPreferred - Objects uploaded to the bucket change ownership to the bucket
+ * owner if the objects are uploaded with the bucket-owner-full-control canned ACL.
*
- * ObjectWriter - The uploading account will own the object if the object is
- * uploaded with the bucket-owner-full-control canned ACL.
+ * ObjectWriter - The uploading account will own the object if the object is uploaded with
+ * the bucket-owner-full-control canned ACL.
*
- * BucketOwnerEnforced - Access control lists (ACLs) are disabled and no
- * longer affect permissions. The bucket owner automatically owns and has full control over
- * every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL
- * or specify bucket owner full control ACLs (such as the predefined
- * bucket-owner-full-control canned ACL or a custom ACL in XML format that
- * grants the same permissions).
- *
By default, ObjectOwnership is set to BucketOwnerEnforced and
- * ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where
- * you must control access for each object individually. For more information about S3 Object
- * Ownership, see Controlling ownership of
- * objects and disabling ACLs for your bucket in the
- * Amazon S3 User Guide.
+ * BucketOwnerEnforced - Access control lists (ACLs) are disabled and no longer affect
+ * permissions. The bucket owner automatically owns and has full control over every object in the bucket.
+ * The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner full control ACLs
+ * (such as the predefined bucket-owner-full-control canned ACL or a custom ACL in XML format
+ * that grants the same permissions).
+ *
By default, ObjectOwnership is set to BucketOwnerEnforced and ACLs are
+ * disabled. We recommend keeping ACLs disabled, except in uncommon use cases where you must control access
+ * for each object individually. For more information about S3 Object Ownership, see Controlling
+ * ownership of objects and disabling ACLs for your bucket in the
+ * Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.
- * The destination information for the metadata table configuration. The destination table bucket
- * must be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata
- * table name must be unique within the aws_s3_metadata namespace in the destination
- * table bucket.
- *
+ * The encryption settings for an S3 Metadata journal table or inventory table configuration.
+ *
+ * @public
+ */
+export interface MetadataTableEncryptionConfiguration {
+ /**
+ *
+ * The encryption type specified for a metadata table. To specify server-side encryption with
+ * Key Management Service (KMS) keys (SSE-KMS), use the aws:kms value. To specify server-side
+ * encryption with Amazon S3 managed keys (SSE-S3), use the AES256 value.
+ *
+ * If server-side encryption with Key Management Service (KMS) keys (SSE-KMS) is specified, you must also
+ * specify the KMS key Amazon Resource Name (ARN). You must specify a customer-managed KMS key
+ * that's located in the same Region as the general purpose bucket that corresponds to the metadata
+ * table configuration.
+ *
+ * If you enable journal table record expiration, you can set the number of days to retain your
+ * journal table records. Journal table records must be retained for a minimum of 7 days. To set
+ * this value, specify any whole number from 7 to 2147483647. For example,
+ * to retain your journal table records for one year, set this value to 365.
+ *
+ * The general purpose bucket that you want to create the metadata configuration for.
+ *
+ *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The destination information for a V1 S3 Metadata configuration. The destination table bucket must
+ * be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name
+ * must be unique within the aws_s3_metadata namespace in the destination table bucket.
+ *
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
- * The Amazon Resource Name (ARN) for the table bucket that's specified as the
- * destination in the metadata table configuration. The destination table bucket
- * must be in the same Region and Amazon Web Services account as the general purpose bucket.
- *
+ *
The Amazon Resource Name (ARN) for the table bucket that's specified as the destination in the
+ * metadata table configuration. The destination table bucket must be in the same Region and Amazon Web Services account
+ * as the general purpose bucket.
- * The name for the metadata table in your metadata table configuration. The specified metadata
- * table name must be unique within the aws_s3_metadata namespace in the destination
- * table bucket.
- *
+ *
The name for the metadata table in your metadata table configuration. The specified metadata table
+ * name must be unique within the aws_s3_metadata namespace in the destination table bucket.
+ *
- * The metadata table configuration for a general purpose bucket.
- *
+ *
The V1 S3 Metadata configuration for a general purpose bucket.
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
- * The destination information for the metadata table configuration. The destination table bucket
- * must be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata
- * table name must be unique within the aws_s3_metadata namespace in the destination
- * table bucket.
- *
+ *
The destination information for the metadata table configuration. The destination table bucket must
+ * be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name
+ * must be unique within the aws_s3_metadata namespace in the destination table bucket.
+ *
- * The general purpose bucket that you want to create the metadata table configuration in.
- *
+ *
The general purpose bucket that you want to create the metadata table configuration for.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
* @public
*/
Bucket: string | undefined;
/**
- *
- * The Content-MD5 header for the metadata table configuration.
- *
+ *
The Content-MD5 header for the metadata table configuration.
If the bucket has a lifecycle rule configured with an action to abort incomplete
- * multipart uploads and the prefix in the lifecycle rule matches the object name in the
- * request, the response includes this header. The header indicates when the initiated
- * multipart upload becomes eligible for an abort operation. For more information, see
- * Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration in
- * the Amazon S3 User Guide.
- *
The response also includes the x-amz-abort-rule-id header that provides the
- * ID of the lifecycle configuration rule that defines the abort action.
+ *
If the bucket has a lifecycle rule configured with an action to abort incomplete multipart uploads
+ * and the prefix in the lifecycle rule matches the object name in the request, the response includes this
+ * header. The header indicates when the initiated multipart upload becomes eligible for an abort
+ * operation. For more information, see Aborting
+ * Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration in the
+ * Amazon S3 User Guide.
+ *
The response also includes the x-amz-abort-rule-id header that provides the ID of the
+ * lifecycle configuration rule that defines the abort action.
*
*
This functionality is not supported for directory buckets.
This header is returned along with the x-amz-abort-date header. It
- * identifies the applicable lifecycle configuration rule that defines the action to abort
- * incomplete multipart uploads.
+ *
This header is returned along with the x-amz-abort-date header. It identifies the
+ * applicable lifecycle configuration rule that defines the action to abort incomplete multipart
+ * uploads.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to confirm the encryption algorithm that's used.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to confirm the encryption algorithm that's used.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to provide the round-trip message integrity verification
- * of the customer-provided encryption key.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to provide the round-trip message integrity verification of the customer-provided
+ * encryption key.
*
*
This functionality is not supported for directory buckets.
The canned ACL to apply to the object. Amazon S3 supports a set of predefined ACLs, known as
- * canned ACLs. Each canned ACL has a predefined set of grantees and
- * permissions. For more information, see Canned ACL in the
- * Amazon S3 User Guide.
- *
By default, all objects are private. Only the owner has full access control. When
- * uploading an object, you can grant access permissions to individual Amazon Web Services accounts or to
- * predefined groups defined by Amazon S3. These permissions are then added to the access control
- * list (ACL) on the new object. For more information, see Using ACLs. One way to grant
- * the permissions using the request headers is to specify a canned ACL with the
- * x-amz-acl request header.
+ * canned ACLs. Each canned ACL has a predefined set of grantees and permissions.
+ * For more information, see Canned ACL in the
+ * Amazon S3 User Guide.
+ *
By default, all objects are private. Only the owner has full access control. When uploading an
+ * object, you can grant access permissions to individual Amazon Web Services accounts or to predefined groups defined by
+ * Amazon S3. These permissions are then added to the access control list (ACL) on the new object. For more
+ * information, see Using
+ * ACLs. One way to grant the permissions using the request headers is to specify a canned ACL
+ * with the x-amz-acl request header.
The name of the bucket where the multipart upload is initiated and where the object is
- * uploaded.
+ * uploaded.
*
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -2395,9 +2572,8 @@ export interface CreateMultipartUploadRequest {
*/
ContentDisposition?: string | undefined;
/**
- *
Specifies what content encodings have been applied to the object and thus what decoding
- * mechanisms must be applied to obtain the media-type referenced by the Content-Type header
- * field.
+ *
Specifies what content encodings have been applied to the object and thus what decoding mechanisms
+ * must be applied to obtain the media-type referenced by the Content-Type header field.
*
*
For directory buckets, only the aws-chunked value is supported in this header field.
Specify access permissions explicitly to give the grantee READ, READ_ACP, and WRITE_ACP
- * permissions on the object.
- *
By default, all objects are private. Only the owner has full access control. When
- * uploading an object, you can use this header to explicitly grant access permissions to
- * specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3
- * supports in an ACL. For more information, see Access Control List (ACL) Overview
- * in the Amazon S3 User Guide.
- *
You specify each grantee as a type=value pair, where the type is one of the
- * following:
+ *
Specify access permissions explicitly to give the grantee READ, READ_ACP, and WRITE_ACP permissions
+ * on the object.
+ *
By default, all objects are private. Only the owner has full access control. When uploading an
+ * object, you can use this header to explicitly grant access permissions to specific Amazon Web Services accounts or
+ * groups. This header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see
+ * Access Control List (ACL)
+ * Overview in the Amazon S3 User Guide.
+ *
You specify each grantee as a type=value pair, where the type is one of the following:
*
*
*
- * id – if the value specified is the canonical user ID of an
- * Amazon Web Services account
+ * id – if the value specified is the canonical user ID of an Amazon Web Services account
Specify access permissions explicitly to allow grantee to read the object data and its
- * metadata.
- *
By default, all objects are private. Only the owner has full access control. When
- * uploading an object, you can use this header to explicitly grant access permissions to
- * specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3
- * supports in an ACL. For more information, see Access Control List (ACL) Overview
- * in the Amazon S3 User Guide.
- *
You specify each grantee as a type=value pair, where the type is one of the
- * following:
+ * metadata.
+ *
By default, all objects are private. Only the owner has full access control. When uploading an
+ * object, you can use this header to explicitly grant access permissions to specific Amazon Web Services accounts or
+ * groups. This header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see
+ * Access Control List (ACL)
+ * Overview in the Amazon S3 User Guide.
+ *
You specify each grantee as a type=value pair, where the type is one of the following:
*
*
*
- * id – if the value specified is the canonical user ID of an
- * Amazon Web Services account
+ * id – if the value specified is the canonical user ID of an Amazon Web Services account
*
Specify access permissions explicitly to allows grantee to read the object ACL.
- *
By default, all objects are private. Only the owner has full access control. When
- * uploading an object, you can use this header to explicitly grant access permissions to
- * specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3
- * supports in an ACL. For more information, see Access Control List (ACL) Overview
- * in the Amazon S3 User Guide.
- *
You specify each grantee as a type=value pair, where the type is one of the
- * following:
+ *
By default, all objects are private. Only the owner has full access control. When uploading an
+ * object, you can use this header to explicitly grant access permissions to specific Amazon Web Services accounts or
+ * groups. This header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see
+ * Access Control List (ACL)
+ * Overview in the Amazon S3 User Guide.
+ *
You specify each grantee as a type=value pair, where the type is one of the following:
*
*
*
- * id – if the value specified is the canonical user ID of an
- * Amazon Web Services account
+ * id – if the value specified is the canonical user ID of an Amazon Web Services account
*
Specify access permissions explicitly to allows grantee to allow grantee to write the
- * ACL for the applicable object.
- *
By default, all objects are private. Only the owner has full access control. When
- * uploading an object, you can use this header to explicitly grant access permissions to
- * specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3
- * supports in an ACL. For more information, see Access Control List (ACL) Overview
- * in the Amazon S3 User Guide.
- *
You specify each grantee as a type=value pair, where the type is one of the
- * following:
+ *
Specify access permissions explicitly to allows grantee to allow grantee to write the ACL for the
+ * applicable object.
+ *
By default, all objects are private. Only the owner has full access control. When uploading an
+ * object, you can use this header to explicitly grant access permissions to specific Amazon Web Services accounts or
+ * groups. This header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see
+ * Access Control List (ACL)
+ * Overview in the Amazon S3 User Guide.
+ *
You specify each grantee as a type=value pair, where the type is one of the following:
*
*
*
- * id – if the value specified is the canonical user ID of an
- * Amazon Web Services account
+ * id – if the value specified is the canonical user ID of an Amazon Web Services account
*
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+ * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
* CreateSession requests or PUT object requests. Then, new objects
* are automatically encrypted with the desired encryption settings. For more
* information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
- * S3 access points for Amazon FSx - When accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side encryption option is aws:fsx. All Amazon FSx file systems have encryption configured by default and are encrypted at rest. Data is automatically encrypted before being written to the file system, and automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
+ * S3 access points for Amazon FSx - When accessing data stored in
+ * Amazon FSx file systems using S3 access points, the only valid server side encryption option is
+ * aws:fsx. All Amazon FSx file systems have encryption configured by default and are
+ * encrypted at rest. Data is automatically encrypted before being written to the file system, and
+ * automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
*
By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The
- * STANDARD storage class provides high durability and high availability. Depending on
- * performance needs, you can specify a different Storage Class. For more information, see
- * Storage
- * Classes in the Amazon S3 User Guide.
+ *
By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The STANDARD
+ * storage class provides high durability and high availability. Depending on performance needs, you can
+ * specify a different Storage Class. For more information, see Storage Classes in the
+ * Amazon S3 User Guide.
*
*
*
- *
Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ *
Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in
+ * Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in
+ * Dedicated Local Zones.
*
*
*
Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.
If the bucket is configured as a website, redirects requests for this object to another
- * object in the same bucket or to an external URL. Amazon S3 stores the value of this header in
- * the object metadata.
+ *
If the bucket is configured as a website, redirects requests for this object to another object in
+ * the same bucket or to an external URL. Amazon S3 stores the value of this header in the object
+ * metadata.
*
*
This functionality is not supported for directory buckets.
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.
+ *
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 functionality is not supported for directory buckets.
Specifies the 128-bit MD5 digest of the customer-provided 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 128-bit MD5 digest of the customer-provided 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.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
The established temporary security credentials of the session.
*
*
- * Directory buckets - These session
- * credentials are only supported for the authentication and authorization of Zonal endpoint API operations
- * on directory buckets.
+ * Directory buckets - These session credentials are only
+ * supported for the authentication and authorization of Zonal endpoint API operations on directory buckets.
*
* @public
*/
export interface SessionCredentials {
/**
- *
A unique identifier that's associated with a secret access key. The access key ID and
- * the secret access key are used together to sign programmatic Amazon Web Services requests
- * cryptographically.
+ *
A unique identifier that's associated with a secret access key. The access key ID and the secret
+ * access key are used together to sign programmatic Amazon Web Services requests cryptographically.
A key that's used with the access key ID to cryptographically sign programmatic Amazon Web Services
- * requests. Signing a request identifies the sender and prevents the request from being
- * altered.
+ *
A key that's used with the access key ID to cryptographically sign programmatic Amazon Web Services requests.
+ * Signing a request identifies the sender and prevents the request from being altered.
Temporary security credentials expire after a specified interval. After temporary
- * credentials expire, any calls that you make with those credentials will fail. So you must
- * generate a new set of temporary credentials. Temporary credentials cannot be extended or
- * refreshed beyond the original specified interval.
+ *
Temporary security credentials expire after a specified interval. After temporary credentials
+ * expire, any calls that you make with those credentials will fail. So you must generate a new set of
+ * temporary credentials. Temporary credentials cannot be extended or refreshed beyond the original
+ * specified interval.
Specifies the mode of the session that will be created, either ReadWrite or
- * ReadOnly. By default, a ReadWrite session is created. A
- * ReadWrite session is capable of executing all the Zonal endpoint API operations on a
- * directory bucket. A ReadOnly session is constrained to execute the following
- * Zonal endpoint API operations: GetObject, HeadObject, ListObjectsV2,
- * GetObjectAttributes, ListParts, and
- * ListMultipartUploads.
+ * ReadOnly. By default, a ReadWrite session is created. A
+ * ReadWrite session is capable of executing all the Zonal endpoint API operations on a directory bucket. A
+ * ReadOnly session is constrained to execute the following Zonal endpoint API operations:
+ * GetObject, HeadObject, ListObjectsV2,
+ * GetObjectAttributes, ListParts, and
+ * ListMultipartUploads.
* @public
*/
SessionMode?: SessionMode | undefined;
@@ -3039,7 +3209,11 @@ export interface CreateSessionRequest {
* For more
* information, see Protecting data with server-side encryption in the Amazon S3 User Guide.
*
- * S3 access points for Amazon FSx - When accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side encryption option is aws:fsx. All Amazon FSx file systems have encryption configured by default and are encrypted at rest. Data is automatically encrypted before being written to the file system, and automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
+ * S3 access points for Amazon FSx - When accessing data stored in Amazon FSx
+ * file systems using S3 access points, the only valid server side encryption option is aws:fsx. All
+ * Amazon FSx file systems have encryption configured by default and are encrypted at rest. Data is
+ * automatically encrypted before being written to the file system, and automatically decrypted as it is
+ * read. These processes are handled transparently by Amazon FSx.
* @public
*/
ServerSideEncryption?: ServerSideEncryption | undefined;
@@ -3158,8 +3332,7 @@ export interface DeleteBucketCorsRequest {
*/
export interface DeleteBucketEncryptionRequest {
/**
- *
The name of the bucket containing the server-side encryption configuration to
- * delete.
+ *
The name of the bucket containing the server-side encryption configuration to delete.
*
* Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name
* . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format
@@ -3239,31 +3412,49 @@ export interface DeleteBucketLifecycleRequest {
/**
*
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
+ * The general purpose bucket that you want to remove the metadata configuration from.
+ *
+ *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
- * The general purpose bucket that you want to remove the metadata table configuration from.
- *
+ *
The general purpose bucket that you want to remove the metadata table configuration from.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
* @public
*/
Bucket: string | undefined;
/**
- *
- * The expected bucket owner of the general purpose bucket that you want to remove the
- * metadata table configuration from.
- *
+ *
The expected bucket owner of the general purpose bucket that you want to remove the metadata table
+ * configuration from.
The ID used to identify the metrics configuration. The ID has a 64 character limit and
- * can only contain letters, numbers, periods, dashes, and underscores.
+ *
The ID used to identify the metrics configuration. The ID has a 64 character limit and can only
+ * contain letters, numbers, periods, dashes, and underscores.
Indicates whether the specified object version that was permanently deleted was (true)
- * or was not (false) a delete marker before deletion. In a simple DELETE, this header
- * indicates whether (true) or not (false) the current version of the object is a delete
- * marker. To learn more about delete markers, see Working with delete markers.
+ *
Indicates whether the specified object version that was permanently deleted was (true) or was not
+ * (false) a delete marker before deletion. In a simple DELETE, this header indicates whether (true) or not
+ * (false) the current version of the object is a delete marker. To learn more about delete markers, see
+ * Working with delete
+ * markers.
*
*
This functionality is not supported for directory buckets.
The bucket name of the bucket containing the object.
*
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -3454,9 +3645,9 @@ export interface DeleteObjectRequest {
*/
Key: string | undefined;
/**
- *
The concatenation of the authentication device's serial number, a space, and the value
- * that is displayed on your authentication device. Required to permanently delete a versioned
- * object if versioning is configured with MFA delete enabled.
+ *
The concatenation of the authentication device's serial number, a space, and the value that is
+ * displayed on your authentication device. Required to permanently delete a versioned object if versioning
+ * is configured with MFA delete enabled.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Indicates whether S3 Object Lock should bypass Governance-mode restrictions to process
- * this operation. To use this header, you must have the
- * s3:BypassGovernanceRetention permission.
+ *
Indicates whether S3 Object Lock should bypass Governance-mode restrictions to process this
+ * operation. To use this header, you must have the s3:BypassGovernanceRetention
+ * permission.
*
*
This functionality is not supported for directory buckets.
The If-Match header field makes the request method conditional on ETags. If the ETag value does not match, the operation returns
- * a 412 Precondition Failed error. If the ETag matches or if the object doesn't exist, the operation will return a 204 Success (No
- * Content) response.
+ *
The If-Match header field makes the request method conditional on ETags. If the ETag
+ * value does not match, the operation returns a 412 Precondition Failed error. If the ETag
+ * matches or if the object doesn't exist, the operation will return a 204 Success (No Content)
+ * response.
*
For more information about conditional requests, see RFC 7232.
*
*
This functionality is only supported for directory buckets.
If present, the object is deleted only if its modification times matches the provided
- * Timestamp. If the Timestamp values do not match, the operation
- * returns a 412 Precondition Failed error. If the Timestamp matches
- * or if the object doesn’t exist, the operation returns a 204 Success (No
- * Content) response.
+ * Timestamp. If the Timestamp values do not match, the operation returns a
+ * 412 Precondition Failed error. If the Timestamp matches or if the object
+ * doesn’t exist, the operation returns a 204 Success (No Content) response.
*
*
This functionality is only supported for directory buckets.
If present, the object is deleted only if its size matches the provided size in bytes. If the Size value does not match, the operation returns a 412 Precondition Failed error. If the Size matches or if the object doesn’t exist,
- * the operation returns a 204 Success (No Content) response.
+ *
If present, the object is deleted only if its size matches the provided size in bytes. If the
+ * Size value does not match, the operation returns a 412 Precondition Failed
+ * error. If the Size matches or if the object doesn’t exist, the operation returns a
+ * 204 Success (No Content) response.
*
*
This functionality is only supported for directory buckets.
*
*
- *
You can use the If-Match, x-amz-if-match-last-modified-time and x-amz-if-match-size
- * conditional headers in conjunction with each-other or individually.
+ *
You can use the If-Match, x-amz-if-match-last-modified-time and
+ * x-amz-if-match-size conditional headers in conjunction with each-other or
+ * individually.
Indicates whether the specified object version that was permanently deleted was (true)
- * or was not (false) a delete marker before deletion. In a simple DELETE, this header
- * indicates whether (true) or not (false) the current version of the object is a delete
- * marker. To learn more about delete markers, see Working with delete markers.
+ *
Indicates whether the specified object version that was permanently deleted was (true) or was not
+ * (false) a delete marker before deletion. In a simple DELETE, this header indicates whether (true) or not
+ * (false) the current version of the object is a delete marker. To learn more about delete markers, see
+ * Working with delete
+ * markers.
*
*
This functionality is not supported for directory buckets.
The version ID of the delete marker created as a result of the DELETE operation. If you
- * delete a specific object version, the value returned by this header is the version ID of
- * the object version deleted.
+ *
The version ID of the delete marker created as a result of the DELETE operation. If you delete a
+ * specific object version, the value returned by this header is the version ID of the object version
+ * deleted.
*
*
This functionality is not supported for directory buckets.
The error code is a string that uniquely identifies an error condition. It is meant to
- * be read and understood by programs that detect and handle errors by type. The following is
- * a list of Amazon S3 error codes. For more information, see Error responses.
+ *
The error code is a string that uniquely identifies an error condition. It is meant to be read and
+ * understood by programs that detect and handle errors by type. The following is a list of Amazon S3 error
+ * codes. For more information, see Error responses.
*
*
*
@@ -3627,9 +3821,8 @@ export interface _Error {
*
*
*
- * Description: There is a problem with your Amazon Web Services account
- * that prevents the action from completing successfully. Contact Amazon Web Services Support
- * for further assistance.
+ * Description: There is a problem with your Amazon Web Services account that prevents
+ * the action from completing successfully. Contact Amazon Web Services Support for further assistance.
*
*
*
@@ -3649,8 +3842,8 @@ export interface _Error {
*
*
*
- * Description: All access to this Amazon S3 resource has been
- * disabled. Contact Amazon Web Services Support for further assistance.
+ * Description: All access to this Amazon S3 resource has been disabled.
+ * Contact Amazon Web Services Support for further assistance.
*
*
*
@@ -3670,8 +3863,8 @@ export interface _Error {
*
*
*
- * Description: The email address you provided is
- * associated with more than one account.
+ * Description: The email address you provided is associated with more
+ * than one account.
*
*
*
@@ -3691,8 +3884,7 @@ export interface _Error {
*
*
*
- * Description: The authorization header you provided is
- * invalid.
+ * Description: The authorization header you provided is invalid.
*
*
*
@@ -3712,8 +3904,8 @@ export interface _Error {
*
*
*
- * Description: The Content-MD5 you specified did not
- * match what we received.
+ * Description: The Content-MD5 you specified did not match what we
+ * received.
*
*
*
@@ -3733,9 +3925,9 @@ export interface _Error {
*
*
*
- * Description: The requested bucket name is not
- * available. The bucket namespace is shared by all users of the system. Please
- * select a different name and try again.
+ * Description: The requested bucket name is not available. The bucket
+ * namespace is shared by all users of the system. Please select a different name and try
+ * again.
*
- * Description: The bucket you tried to create already
- * exists, and you own it. Amazon S3 returns this error in all Amazon Web Services Regions except in
- * the North Virginia Region. For legacy compatibility, if you re-create an
- * existing bucket that you already own in the North Virginia Region, Amazon S3 returns
- * 200 OK and resets the bucket access control lists (ACLs).
+ * Description: The bucket you tried to create already exists, and you own
+ * it. Amazon S3 returns this error in all Amazon Web Services Regions except in the North Virginia Region. For legacy
+ * compatibility, if you re-create an existing bucket that you already own in the North Virginia
+ * Region, Amazon S3 returns 200 OK and resets the bucket access control lists (ACLs).
*
*
*
- * Code: 409 Conflict (in all Regions except the North
- * Virginia Region)
+ * Code: 409 Conflict (in all Regions except the North Virginia Region)
+ *
*
*
*
@@ -3780,8 +3971,7 @@ export interface _Error {
*
*
*
- * Description: The bucket you tried to delete is not
- * empty.
+ * Description: The bucket you tried to delete is not empty.
*
*
*
@@ -3801,8 +3991,7 @@ export interface _Error {
*
*
*
- * Description: This request does not support
- * credentials.
+ * Description: This request does not support credentials.
*
*
*
@@ -3822,9 +4011,8 @@ export interface _Error {
*
*
*
- * Description: Cross-location logging not allowed.
- * Buckets in one geographic location cannot log information to a bucket in
- * another location.
+ * Description: Cross-location logging not allowed. Buckets in one
+ * geographic location cannot log information to a bucket in another location.
*
*
*
@@ -3844,8 +4032,8 @@ export interface _Error {
*
*
*
- * Description: Your proposed upload is smaller than the
- * minimum allowed object size.
+ * Description: Your proposed upload is smaller than the minimum allowed
+ * object size.
*
*
*
@@ -3865,8 +4053,8 @@ export interface _Error {
*
*
*
- * Description: Your proposed upload exceeds the maximum
- * allowed object size.
+ * Description: Your proposed upload exceeds the maximum allowed object
+ * size.
*
*
*
@@ -3906,8 +4094,8 @@ export interface _Error {
*
*
*
- * Description: Indicates that the versioning
- * configuration specified in the request is invalid.
+ * Description: Indicates that the versioning configuration specified in
+ * the request is invalid.
*
*
*
@@ -3927,8 +4115,8 @@ export interface _Error {
*
*
*
- * Description: You did not provide the number of bytes
- * specified by the Content-Length HTTP header
+ * Description: You did not provide the number of bytes specified by the
+ * Content-Length HTTP header
*
*
*
@@ -3948,8 +4136,7 @@ export interface _Error {
*
*
*
- * Description: POST requires exactly one file upload per
- * request.
+ * Description: POST requires exactly one file upload per request.
*
*
*
@@ -3969,8 +4156,7 @@ export interface _Error {
*
*
*
- * Description: Inline data exceeds the maximum allowed
- * size.
+ * Description: Inline data exceeds the maximum allowed size.
*
*
*
@@ -3990,8 +4176,7 @@ export interface _Error {
*
*
*
- * Description: We encountered an internal error. Please
- * try again.
+ * Description: We encountered an internal error. Please try again.
*
*
*
@@ -4011,8 +4196,8 @@ export interface _Error {
*
*
*
- * Description: The Amazon Web Services access key ID you provided does
- * not exist in our records.
+ * Description: The Amazon Web Services access key ID you provided does not exist in our
+ * records.
*
*
*
@@ -4032,8 +4217,7 @@ export interface _Error {
*
*
*
- * Description: You must specify the Anonymous
- * role.
+ * Description: You must specify the Anonymous role.
*
*
*
@@ -4093,8 +4277,8 @@ export interface _Error {
*
*
*
- * Description: The request is not valid with the current
- * state of the bucket.
+ * Description: The request is not valid with the current state of the
+ * bucket.
*
*
*
@@ -4114,8 +4298,7 @@ export interface _Error {
*
*
*
- * Description: The Content-MD5 you specified is not
- * valid.
+ * Description: The Content-MD5 you specified is not valid.
*
*
*
@@ -4135,8 +4318,8 @@ export interface _Error {
*
*
*
- * Description: The encryption request you specified is
- * not valid. The valid value is AES256.
+ * Description: The encryption request you specified is not valid. The
+ * valid value is AES256.
*
- * Description: The action is not valid for the current
- * state of the object.
+ * Description: The action is not valid for the current state of the
+ * object.
*
*
*
@@ -4199,9 +4382,9 @@ export interface _Error {
*
*
*
- * Description: One or more of the specified parts could
- * not be found. The part might not have been uploaded, or the specified entity
- * tag might not have matched the part's entity tag.
+ * Description: One or more of the specified parts could not be found. The
+ * part might not have been uploaded, or the specified entity tag might not have matched the part's
+ * entity tag.
*
*
*
@@ -4221,8 +4404,8 @@ export interface _Error {
*
*
*
- * Description: The list of parts was not in ascending
- * order. Parts list must be specified in order by part number.
+ * Description: The list of parts was not in ascending order. Parts list
+ * must be specified in order by part number.
*
*
*
@@ -4242,8 +4425,8 @@ export interface _Error {
*
*
*
- * Description: All access to this object has been
- * disabled. Please contact Amazon Web Services Support for further assistance.
+ * Description: All access to this object has been disabled. Please
+ * contact Amazon Web Services Support for further assistance.
*
*
*
@@ -4263,8 +4446,8 @@ export interface _Error {
*
*
*
- * Description: The content of the form does not meet the
- * conditions specified in the policy document.
+ * Description: The content of the form does not meet the conditions
+ * specified in the policy document.
*
- * Description: The requested range cannot be
- * satisfied.
+ * Description: The requested range cannot be satisfied.
*
*
*
- * HTTP Status Code: 416 Requested Range Not
- * Satisfiable
+ * HTTP Status Code: 416 Requested Range Not Satisfiable
*
*
*
@@ -4306,8 +4487,7 @@ export interface _Error {
*
*
*
- * Description: Please use
- * AWS4-HMAC-SHA256.
+ * Description: Please use AWS4-HMAC-SHA256.
*
*
*
@@ -4328,7 +4508,7 @@ export interface _Error {
*
*
* Description: SOAP requests must be made over an HTTPS
- * connection.
+ * connection.
*
*
*
@@ -4348,8 +4528,8 @@ export interface _Error {
*
*
*
- * Description: Amazon S3 Transfer Acceleration is not
- * supported for buckets with non-DNS compliant names.
+ * Description: Amazon S3 Transfer Acceleration is not supported for buckets
+ * with non-DNS compliant names.
*
*
*
@@ -4369,8 +4549,8 @@ export interface _Error {
*
*
*
- * Description: Amazon S3 Transfer Acceleration is not
- * supported for buckets with periods (.) in their names.
+ * Description: Amazon S3 Transfer Acceleration is not supported for buckets
+ * with periods (.) in their names.
*
*
*
@@ -4390,8 +4570,8 @@ export interface _Error {
*
*
*
- * Description: Amazon S3 Transfer Accelerate endpoint only
- * supports virtual style requests.
+ * Description: Amazon S3 Transfer Accelerate endpoint only supports virtual
+ * style requests.
*
*
*
@@ -4411,8 +4591,8 @@ export interface _Error {
*
*
*
- * Description: Amazon S3 Transfer Accelerate is not configured
- * on this bucket.
+ * Description: Amazon S3 Transfer Accelerate is not configured on this
+ * bucket.
*
*
*
@@ -4432,8 +4612,8 @@ export interface _Error {
*
*
*
- * Description: Amazon S3 Transfer Accelerate is disabled on
- * this bucket.
+ * Description: Amazon S3 Transfer Accelerate is disabled on this
+ * bucket.
*
*
*
@@ -4453,8 +4633,8 @@ export interface _Error {
*
*
*
- * Description: Amazon S3 Transfer Acceleration is not
- * supported on this bucket. Contact Amazon Web Services Support for more information.
+ * Description: Amazon S3 Transfer Acceleration is not supported on this
+ * bucket. Contact Amazon Web Services Support for more information.
*
*
*
@@ -4474,8 +4654,8 @@ export interface _Error {
*
*
*
- * Description: Amazon S3 Transfer Acceleration cannot be
- * enabled on this bucket. Contact Amazon Web Services Support for more information.
+ * Description: Amazon S3 Transfer Acceleration cannot be enabled on this
+ * bucket. Contact Amazon Web Services Support for more information.
*
*
*
@@ -4495,8 +4675,7 @@ export interface _Error {
*
*
*
- * Description: The provided security credentials are not
- * valid.
+ * Description: The provided security credentials are not valid.
*
*
*
@@ -4536,8 +4715,7 @@ export interface _Error {
*
*
*
- * Description: The storage class you specified is not
- * valid.
+ * Description: The storage class you specified is not valid.
*
*
*
@@ -4557,9 +4735,8 @@ export interface _Error {
*
*
*
- * Description: The target bucket for logging does not
- * exist, is not owned by you, or does not have the appropriate grants for the
- * log-delivery group.
+ * Description: The target bucket for logging does not exist, is not owned
+ * by you, or does not have the appropriate grants for the log-delivery group.
*
*
*
@@ -4579,8 +4756,8 @@ export interface _Error {
*
*
*
- * Description: The provided token is malformed or
- * otherwise invalid.
+ * Description: The provided token is malformed or otherwise
+ * invalid.
*
*
*
@@ -4640,8 +4817,8 @@ export interface _Error {
*
*
*
- * Description: The XML you provided was not well-formed
- * or did not validate against our published schema.
+ * Description: The XML you provided was not well-formed or did not
+ * validate against our published schema.
*
*
*
@@ -4661,8 +4838,8 @@ export interface _Error {
*
*
*
- * Description: The body of your POST request is not
- * well-formed multipart/form-data.
+ * Description: The body of your POST request is not well-formed
+ * multipart/form-data.
*
- * Description: This happens when the user sends malformed
- * XML (XML that doesn't conform to the published XSD) for the configuration. The
- * error message is, "The XML you provided was not well-formed or did not validate
- * against our published schema."
+ * Description: This happens when the user sends malformed XML (XML that
+ * doesn't conform to the published XSD) for the configuration. The error message is, "The XML you
+ * provided was not well-formed or did not validate against our published schema."
*
*
*
@@ -4725,8 +4901,8 @@ export interface _Error {
*
*
*
- * Description: Your POST request fields preceding the
- * upload file were too large.
+ * Description: Your POST request fields preceding the upload file were
+ * too large.
*
*
*
@@ -4746,8 +4922,8 @@ export interface _Error {
*
*
*
- * Description: Your metadata headers exceed the maximum
- * allowed metadata size.
+ * Description: Your metadata headers exceed the maximum allowed metadata
+ * size.
*
*
*
@@ -4767,8 +4943,8 @@ export interface _Error {
*
*
*
- * Description: The specified method is not allowed
- * against this resource.
+ * Description: The specified method is not allowed against this
+ * resource.
*
*
*
@@ -4788,8 +4964,8 @@ export interface _Error {
*
*
*
- * Description: A SOAP attachment was expected, but none
- * were found.
+ * Description: A SOAP attachment was expected, but none were
+ * found.
*
*
*
@@ -4809,8 +4985,7 @@ export interface _Error {
*
*
*
- * Description: You must provide the Content-Length HTTP
- * header.
+ * Description: You must provide the Content-Length HTTP header.
*
*
*
@@ -4830,9 +5005,8 @@ export interface _Error {
*
*
*
- * Description: This happens when the user sends an empty
- * XML document as a request. The error message is, "Request body is empty."
- *
+ * Description: This happens when the user sends an empty XML document as
+ * a request. The error message is, "Request body is empty."
*
*
*
@@ -4852,8 +5026,7 @@ export interface _Error {
*
*
*
- * Description: The SOAP 1.1 request is missing a security
- * element.
+ * Description: The SOAP 1.1 request is missing a security element.
*
*
*
@@ -4873,8 +5046,7 @@ export interface _Error {
*
*
*
- * Description: Your request is missing a required
- * header.
+ * Description: Your request is missing a required header.
*
*
*
@@ -4894,8 +5066,8 @@ export interface _Error {
*
*
*
- * Description: There is no such thing as a logging status
- * subresource for a key.
+ * Description: There is no such thing as a logging status subresource for
+ * a key.
*
*
*
@@ -4915,8 +5087,7 @@ export interface _Error {
*
*
*
- * Description: The specified bucket does not
- * exist.
+ * Description: The specified bucket does not exist.
*
*
*
@@ -4936,8 +5107,7 @@ export interface _Error {
*
*
*
- * Description: The specified bucket does not have a
- * bucket policy.
+ * Description: The specified bucket does not have a bucket policy.
*
*
*
@@ -4977,8 +5147,7 @@ export interface _Error {
*
*
*
- * Description: The lifecycle configuration does not
- * exist.
+ * Description: The lifecycle configuration does not exist.
*
*
*
@@ -4998,9 +5167,8 @@ export interface _Error {
*
*
*
- * Description: The specified multipart upload does not
- * exist. The upload ID might be invalid, or the multipart upload might have been
- * aborted or completed.
+ * Description: The specified multipart upload does not exist. The upload
+ * ID might be invalid, or the multipart upload might have been aborted or completed.
*
*
*
@@ -5020,8 +5188,8 @@ export interface _Error {
*
*
*
- * Description: Indicates that the version ID specified in
- * the request does not match an existing version.
+ * Description: Indicates that the version ID specified in the request
+ * does not match an existing version.
*
*
*
@@ -5041,8 +5209,8 @@ export interface _Error {
*
*
*
- * Description: A header you provided implies
- * functionality that is not implemented.
+ * Description: A header you provided implies functionality that is not
+ * implemented.
*
*
*
@@ -5062,9 +5230,8 @@ export interface _Error {
*
*
*
- * Description: Your account is not signed up for the Amazon S3
- * service. You must sign up before you can use Amazon S3. You can sign up at the
- * following URL: Amazon S3
+ * Description: Your account is not signed up for the Amazon S3 service. You
+ * must sign up before you can use Amazon S3. You can sign up at the following URL: Amazon S3
*
*
*
@@ -5085,8 +5252,8 @@ export interface _Error {
*
*
*
- * Description: A conflicting conditional action is
- * currently in progress against this resource. Try again.
+ * Description: A conflicting conditional action is currently in progress
+ * against this resource. Try again.
*
*
*
@@ -5106,9 +5273,8 @@ export interface _Error {
*
*
*
- * Description: The bucket you are attempting to access
- * must be addressed using the specified endpoint. Send all future requests to
- * this endpoint.
+ * Description: The bucket you are attempting to access must be addressed
+ * using the specified endpoint. Send all future requests to this endpoint.
*
*
*
@@ -5128,8 +5294,8 @@ export interface _Error {
*
*
*
- * Description: At least one of the preconditions you
- * specified did not hold.
+ * Description: At least one of the preconditions you specified did not
+ * hold.
*
*
*
@@ -5169,8 +5335,7 @@ export interface _Error {
*
*
*
- * Description: Object restore is already in
- * progress.
+ * Description: Object restore is already in progress.
*
*
*
@@ -5191,7 +5356,7 @@ export interface _Error {
*
*
* Description: Bucket POST must be of the enclosure-type
- * multipart/form-data.
+ * multipart/form-data.
*
*
*
@@ -5211,8 +5376,8 @@ export interface _Error {
*
*
*
- * Description: Your socket connection to the server was
- * not read from or written to within the timeout period.
+ * Description: Your socket connection to the server was not read from or
+ * written to within the timeout period.
*
*
*
@@ -5232,8 +5397,8 @@ export interface _Error {
*
*
*
- * Description: The difference between the request time
- * and the server's time is too large.
+ * Description: The difference between the request time and the server's
+ * time is too large.
*
*
*
@@ -5253,8 +5418,8 @@ export interface _Error {
*
*
*
- * Description: Requesting the torrent file of a bucket is
- * not permitted.
+ * Description: Requesting the torrent file of a bucket is not
+ * permitted.
*
- * Description: The request signature we calculated does
- * not match the signature you provided. Check your Amazon Web Services secret access key and
- * signing method. For more information, see REST
- * Authentication and SOAP
- * Authentication for details.
+ * Description: The request signature we calculated does not match the
+ * signature you provided. Check your Amazon Web Services secret access key and signing method. For more
+ * information, see REST Authentication and SOAP Authentication for
+ * details.
*
*
*
@@ -5298,8 +5462,7 @@ export interface _Error {
*
*
*
- * Description: Service is unable to handle
- * request.
+ * Description: Service is unable to handle request.
*
*
*
@@ -5339,8 +5502,8 @@ export interface _Error {
*
*
*
- * Description: You are being redirected to the bucket
- * while DNS updates.
+ * Description: You are being redirected to the bucket while DNS
+ * updates.
*
*
*
@@ -5360,8 +5523,7 @@ export interface _Error {
*
*
*
- * Description: The provided token must be
- * refreshed.
+ * Description: The provided token must be refreshed.
*
*
*
@@ -5381,8 +5543,8 @@ export interface _Error {
*
*
*
- * Description: You have attempted to create more buckets
- * than allowed.
+ * Description: You have attempted to create more buckets than
+ * allowed.
*
*
*
@@ -5402,8 +5564,7 @@ export interface _Error {
*
*
*
- * Description: This request does not support
- * content.
+ * Description: This request does not support content.
*
*
*
@@ -5423,8 +5584,8 @@ export interface _Error {
*
*
*
- * Description: The email address you provided does not
- * match any account on record.
+ * Description: The email address you provided does not match any account
+ * on record.
*
*
*
@@ -5444,8 +5605,8 @@ export interface _Error {
*
*
*
- * Description: The bucket POST must contain the specified
- * field name. If it is specified, check the order of the fields.
+ * Description: The bucket POST must contain the specified field name. If
+ * it is specified, check the order of the fields.
*
The error message contains a generic description of the error condition in English. It
- * is intended for a human audience. Simple programs display the message directly to the end
- * user if they encounter an error condition they don't know how or don't care to handle.
- * Sophisticated programs with more exhaustive error handling and proper internationalization
- * are more likely to ignore the error message.
+ *
The error message contains a generic description of the error condition in English. It is intended
+ * for a human audience. Simple programs display the message directly to the end user if they encounter an
+ * error condition they don't know how or don't care to handle. Sophisticated programs with more exhaustive
+ * error handling and proper internationalization are more likely to ignore the error message.
An entity tag (ETag) is an identifier assigned by a web server to a specific version of a resource found at a URL.
- * This header field makes the request method conditional on ETags.
+ *
An entity tag (ETag) is an identifier assigned by a web server to a specific version of a resource
+ * found at a URL. This header field makes the request method conditional on ETags.
*
- *
Entity tags (ETags) for S3 Express One Zone are random alphanumeric strings unique to the object.
+ *
Entity tags (ETags) for S3 Express One Zone are random alphanumeric strings unique to the object.
+ *
*
* @public
*/
ETag?: string | undefined;
/**
- *
If present, the objects are deleted only if its modification times matches the provided Timestamp.
- *
+ *
If present, the objects are deleted only if its modification times matches the provided
+ * Timestamp.
*
*
This functionality is only supported for directory buckets.
- * Directory buckets - For directory buckets,
- * an object that's composed entirely of whitespace characters is not supported by the
- * DeleteObjects API operation. The request will receive a 400 Bad
- * Request error and none of the objects in the request will be deleted.
+ * Directory buckets - For directory buckets, an object
+ * that's composed entirely of whitespace characters is not supported by the DeleteObjects
+ * API operation. The request will receive a 400 Bad Request error and none of the objects
+ * in the request will be deleted.
*
* @public
*/
Objects: ObjectIdentifier[] | undefined;
/**
- *
Element to enable quiet mode for the request. When you add this element, you must set
- * its value to true.
+ *
Element to enable quiet mode for the request. When you add this element, you must set its value to
+ * true.
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -5606,16 +5767,15 @@ export interface DeleteObjectsRequest {
*/
Delete: Delete | undefined;
/**
- *
The concatenation of the authentication device's serial number, a space, and the value
- * that is displayed on your authentication device. Required to permanently delete a versioned
- * object if versioning is configured with MFA delete enabled.
- *
When performing the DeleteObjects operation on an MFA delete enabled
- * bucket, which attempts to delete the specified versioned objects, you must include an MFA
- * token. If you don't provide an MFA token, the entire request will fail, even if there are
- * non-versioned objects that you are trying to delete. If you provide an invalid token,
- * whether there are versioned object keys in the request or not, the entire Multi-Object
- * Delete request will fail. For information about MFA Delete, see MFA
- * Delete in the Amazon S3 User Guide.
+ *
The concatenation of the authentication device's serial number, a space, and the value that is
+ * displayed on your authentication device. Required to permanently delete a versioned object if versioning
+ * is configured with MFA delete enabled.
+ *
When performing the DeleteObjects operation on an MFA delete enabled bucket, which
+ * attempts to delete the specified versioned objects, you must include an MFA token. If you don't provide
+ * an MFA token, the entire request will fail, even if there are non-versioned objects that you are trying
+ * to delete. If you provide an invalid token, whether there are versioned object keys in the request or
+ * not, the entire Multi-Object Delete request will fail. For information about MFA Delete, see MFA
+ * Delete in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Specifies whether you want to delete this object even if it has a Governance-type Object
- * Lock in place. To use this header, you must have the
- * s3:BypassGovernanceRetention permission.
+ *
Specifies whether you want to delete this object even if it has a Governance-type Object Lock in
+ * place. To use this header, you must have the s3:BypassGovernanceRetention
+ * permission.
*
*
This functionality is not supported for directory buckets.
*
@@ -5691,8 +5850,8 @@ export interface DeleteObjectsRequest {
* the Amazon S3 User Guide.
*
If the individual checksum value you provide through x-amz-checksum-algorithm
* doesn't match the checksum algorithm you set through x-amz-sdk-checksum-algorithm, Amazon S3 fails the request with a BadDigest error.
- *
If you provide an individual checksum, Amazon S3 ignores any provided
- * ChecksumAlgorithm parameter.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
The Amazon S3 bucket whose PublicAccessBlock configuration you want to delete.
- *
+ *
The Amazon S3 bucket whose PublicAccessBlock configuration you want to delete.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter.
- * The operator must have at least two predicates in any combination, and an object must match
- * all of the predicates for the filter to apply.
+ *
A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The
+ * operator must have at least two predicates in any combination, and an object must match all of the
+ * predicates for the filter to apply.
The filter used to describe a set of objects for analyses. A filter must have exactly
- * one prefix, one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided,
- * all objects will be considered in any analysis.
+ *
The filter used to describe a set of objects for analyses. A filter must have exactly one prefix,
+ * one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided, all objects will be
+ * considered in any analysis.
Specifies data related to access patterns to be collected and made available to analyze
- * the tradeoffs between different storage classes for an Amazon S3 bucket.
+ *
Specifies data related to access patterns to be collected and made available to analyze the
+ * tradeoffs between different storage classes for an Amazon S3 bucket.
The filter used to describe a set of objects for analyses. A filter must have exactly
- * one prefix, one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided,
- * all objects will be considered in any analysis.
+ *
The filter used to describe a set of objects for analyses. A filter must have exactly one prefix,
+ * one tag, or one conjunction (AnalyticsAndOperator). If no filter is provided, all objects will be
+ * considered in any analysis.
Headers that are specified in the Access-Control-Request-Headers header.
- * These headers are allowed in a preflight OPTIONS request. In response to any preflight
- * OPTIONS request, Amazon S3 returns any requested headers that are allowed.
+ *
Headers that are specified in the Access-Control-Request-Headers header. These headers
+ * are allowed in a preflight OPTIONS request. In response to any preflight OPTIONS request, Amazon S3 returns
+ * any requested headers that are allowed.
One or more headers in the response that you want customers to be able to access from
- * their applications (for example, from a JavaScript XMLHttpRequest
- * object).
+ *
One or more headers in the response that you want customers to be able to access from their
+ * applications (for example, from a JavaScript XMLHttpRequest object).
Describes the default server-side encryption to apply to new objects in the bucket. If a
- * PUT Object request doesn't specify any server-side encryption, this default encryption will
- * be applied. For more information, see PutBucketEncryption.
+ *
Describes the default server-side encryption to apply to new objects in the bucket. If a PUT Object
+ * request doesn't specify any server-side encryption, this default encryption will be applied. For more
+ * information, see PutBucketEncryption.
*
*
*
*
- * General purpose buckets - If you don't specify
- * a customer managed key at configuration, Amazon S3 automatically creates an Amazon Web Services KMS key
- * (aws/s3) in your Amazon Web Services account the first time that you add an
- * object encrypted with SSE-KMS to a bucket. By default, Amazon S3 uses this KMS key
- * for SSE-KMS.
+ * General purpose buckets - If you don't specify a customer managed key
+ * at configuration, Amazon S3 automatically creates an Amazon Web Services KMS key (aws/s3) in your Amazon Web Services
+ * account the first time that you add an object encrypted with SSE-KMS to a bucket. By default, Amazon S3
+ * uses this KMS key for SSE-KMS.
*
*
*
* Directory buckets -
- * Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime.
+ * Your SSE-KMS configuration can only support 1 customer managed key per directory bucket's lifetime.
* The Amazon Web Services managed key (aws/s3) isn't supported.
*
*
*
*
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS.
+ * For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS.
*
If you are using encryption with cross-account or Amazon Web Services service operations, you must use
- * a fully qualified KMS key ARN. For more information, see Using encryption for cross-account operations.
+ *
If you are using encryption with cross-account or Amazon Web Services service operations, you must use a fully
+ * qualified KMS key ARN. For more information, see Using
+ * encryption for cross-account operations.
*
*
*
*
- * General purpose buckets - If you're specifying
- * a customer managed KMS key, we recommend using a fully qualified KMS key ARN.
- * If you use a KMS key alias instead, then KMS resolves the key within the
- * requester’s account. This behavior can result in data that's encrypted with a
- * KMS key that belongs to the requester, and not the bucket owner. Also, if you
- * use a key ID, you can run into a LogDestination undeliverable error when creating
- * a VPC flow log.
+ * General purpose buckets - If you're specifying a customer
+ * managed KMS key, we recommend using a fully qualified KMS key ARN. If you use a KMS key
+ * alias instead, then KMS resolves the key within the requester’s account. This behavior can
+ * result in data that's encrypted with a KMS key that belongs to the requester, and not the bucket
+ * owner. Also, if you use a key ID, you can run into a LogDestination undeliverable error when
+ * creating a VPC flow log.
*
*
*
* Directory buckets -
- * When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.
+ * When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.
*
*
*
*
- *
Amazon S3 only supports symmetric encryption KMS keys. For more information, see Asymmetric keys in Amazon Web Services KMS in the Amazon Web Services Key Management Service
- * Developer Guide.
+ *
Amazon S3 only supports symmetric encryption KMS keys. For more information, see Asymmetric keys in
+ * Amazon Web Services KMS in the Amazon Web Services Key Management Service Developer Guide.
- * General purpose buckets - If you're specifying
- * a customer managed KMS key, we recommend using a fully qualified KMS key ARN.
- * If you use a KMS key alias instead, then KMS resolves the key within the
- * requester’s account. This behavior can result in data that's encrypted with a
- * KMS key that belongs to the requester, and not the bucket owner.
+ * General purpose buckets - If you're specifying a customer
+ * managed KMS key, we recommend using a fully qualified KMS key ARN. If you use a KMS key
+ * alias instead, then KMS resolves the key within the requester’s account. This behavior can
+ * result in data that's encrypted with a KMS key that belongs to the requester, and not the bucket
+ * owner.
*
*
*
* Directory buckets -
- * When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.
+ * When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.
*
Specifies the default server-side encryption to apply to new objects in the bucket. If a
- * PUT Object request doesn't specify any server-side encryption, this default encryption will
- * be applied.
+ *
Specifies the default server-side encryption to apply to new objects in the bucket. If a PUT Object
+ * request doesn't specify any server-side encryption, this default encryption will be applied.
Specifies whether Amazon S3 should use an S3 Bucket Key with server-side encryption using KMS
- * (SSE-KMS) for new objects in the bucket. Existing objects are not affected. Setting the
- * BucketKeyEnabled element to true causes Amazon S3 to use an S3
- * Bucket Key.
+ *
Specifies whether Amazon S3 should use an S3 Bucket Key with server-side encryption using KMS (SSE-KMS)
+ * for new objects in the bucket. Existing objects are not affected. Setting the
+ * BucketKeyEnabled element to true causes Amazon S3 to use an S3 Bucket Key.
*
*
*
*
- * General purpose buckets - By default, S3
- * Bucket Key is not enabled. For more information, see Amazon S3 Bucket Keys in the
- * Amazon S3 User Guide.
+ * General purpose buckets - By default, S3 Bucket Key is not
+ * enabled. For more information, see Amazon S3 Bucket Keys in the
+ * Amazon S3 User Guide.
*
*
*
* Directory buckets -
- * S3 Bucket Keys are always enabled for GET and PUT operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
+ * S3 Bucket Keys are always enabled for GET and PUT operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
* to directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject, UploadPartCopy, the Copy operation in Batch Operations, or
* the import jobs. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.
The name of the bucket from which the server-side encryption configuration is
- * retrieved.
+ *
The name of the bucket from which the server-side encryption configuration is retrieved.
*
* Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name
* . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format
@@ -6359,33 +6505,31 @@ export interface GetBucketEncryptionRequest {
ExpectedBucketOwner?: string | undefined;
}
/**
- *
A container for specifying S3 Intelligent-Tiering filters. The filters determine the
- * subset of objects to which the rule applies.
+ *
A container for specifying S3 Intelligent-Tiering filters. The filters determine the subset of
+ * objects to which the rule applies.
Specifies whether the inventory is enabled or disabled. If set to True, an
- * inventory list is generated. If set to False, no inventory list is
- * generated.
+ *
Specifies whether the inventory is enabled or disabled. If set to True, an inventory
+ * list is generated. If set to False, no inventory list is generated.
Object versions to include in the inventory list. If set to All, the list
- * includes all the object versions, which adds the version-related fields
- * VersionId, IsLatest, and DeleteMarker to the
- * list. If set to Current, the list does not contain these version-related
- * fields.
+ *
Object versions to include in the inventory list. If set to All, the list includes all
+ * the object versions, which adds the version-related fields VersionId,
+ * IsLatest, and DeleteMarker to the list. If set to Current, the
+ * list does not contain these version-related fields.
Indicates at what date the object is to be moved or deleted. The date value must conform
- * to the ISO 8601 format. The time is always midnight UTC.
+ *
Indicates at what date the object is to be moved or deleted. The date value must conform to the ISO
+ * 8601 format. The time is always midnight UTC.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
*
* @public
*/
Date?: Date | undefined;
/**
- *
Indicates the lifetime, in days, of the objects that are subject to the rule. The value
- * must be a non-zero positive integer.
+ *
Indicates the lifetime, in days, of the objects that are subject to the rule. The value must be a
+ * non-zero positive integer.
* @public
*/
Days?: number | undefined;
/**
- *
Indicates whether Amazon S3 will remove a delete marker with no noncurrent versions. If set
- * to true, the delete marker will be expired; if set to false the policy takes no action.
- * This cannot be specified with Days or Date in a Lifecycle Expiration Policy.
+ *
Indicates whether Amazon S3 will remove a delete marker with no noncurrent versions. If set to true, the
+ * delete marker will be expired; if set to false the policy takes no action. This cannot be specified with
+ * Days or Date in a Lifecycle Expiration Policy.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
This is used in a Lifecycle Rule Filter to apply a logical AND to two or more
- * predicates. The Lifecycle Rule will apply to any object matching all of the predicates
- * configured inside the And operator.
+ *
This is used in a Lifecycle Rule Filter to apply a logical AND to two or more predicates. The
+ * Lifecycle Rule will apply to any object matching all of the predicates configured inside the And
+ * operator.
The Filter is used to identify objects that a Lifecycle Rule applies to. A
- * Filter can have exactly one of Prefix, Tag,
- * ObjectSizeGreaterThan, ObjectSizeLessThan, or And
- * specified. If the Filter element is left empty, the Lifecycle Rule applies to
- * all objects in the bucket.
+ * Filter can have exactly one of Prefix, Tag,
+ * ObjectSizeGreaterThan, ObjectSizeLessThan, or And specified. If
+ * the Filter element is left empty, the Lifecycle Rule applies to all objects in the
+ * bucket.
This is used in a Lifecycle Rule Filter to apply a logical AND to two or more
- * predicates. The Lifecycle Rule will apply to any object matching all of the predicates
- * configured inside the And operator.
+ *
This is used in a Lifecycle Rule Filter to apply a logical AND to two or more predicates. The
+ * Lifecycle Rule will apply to any object matching all of the predicates configured inside the And
+ * operator.
Specifies when noncurrent object versions expire. Upon expiration, Amazon S3 permanently
- * deletes the noncurrent object versions. You set this lifecycle configuration action on a
- * bucket that has versioning enabled (or suspended) to request that Amazon S3 delete noncurrent
- * object versions at a specific period in the object's lifetime.
+ *
Specifies when noncurrent object versions expire. Upon expiration, Amazon S3 permanently deletes the
+ * noncurrent object versions. You set this lifecycle configuration action on a bucket that has versioning
+ * enabled (or suspended) to request that Amazon S3 delete noncurrent object versions at a specific period in
+ * the object's lifetime.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
Specifies the number of days an object is noncurrent before Amazon S3 can perform the
- * associated action. The value must be a non-zero positive integer. For information about the
- * noncurrent days calculations, see How
- * Amazon S3 Calculates When an Object Became Noncurrent in the
- * Amazon S3 User Guide.
+ *
Specifies the number of days an object is noncurrent before Amazon S3 can perform the associated action.
+ * The value must be a non-zero positive integer. For information about the noncurrent days calculations,
+ * see How Amazon S3 Calculates
+ * When an Object Became Noncurrent in the Amazon S3 User Guide.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
Specifies how many noncurrent versions Amazon S3 will retain. You can specify up to 100
- * noncurrent versions to retain. Amazon S3 will permanently delete any additional noncurrent
- * versions beyond the specified number to retain. For more information about noncurrent
- * versions, see Lifecycle configuration
- * elements in the Amazon S3 User Guide.
+ *
Specifies how many noncurrent versions Amazon S3 will retain. You can specify up to 100 noncurrent
+ * versions to retain. Amazon S3 will permanently delete any additional noncurrent versions beyond the specified
+ * number to retain. For more information about noncurrent versions, see Lifecycle configuration elements in
+ * the Amazon S3 User Guide.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
Container for the transition rule that describes when noncurrent objects transition to
- * the STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING,
- * GLACIER_IR, GLACIER, or DEEP_ARCHIVE storage
- * class. If your bucket is versioning-enabled (or versioning is suspended), you can set this
- * action to request that Amazon S3 transition noncurrent object versions to the
- * STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING,
- * GLACIER_IR, GLACIER, or DEEP_ARCHIVE storage
- * class at a specific period in the object's lifetime.
+ *
Container for the transition rule that describes when noncurrent objects transition to the
+ * STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING,
+ * GLACIER_IR, GLACIER, or DEEP_ARCHIVE storage class. If your
+ * bucket is versioning-enabled (or versioning is suspended), you can set this action to request that Amazon S3
+ * transition noncurrent object versions to the STANDARD_IA, ONEZONE_IA,
+ * INTELLIGENT_TIERING, GLACIER_IR, GLACIER, or
+ * DEEP_ARCHIVE storage class at a specific period in the object's lifetime.
Specifies the number of days an object is noncurrent before Amazon S3 can perform the
- * associated action. For information about the noncurrent days calculations, see How
- * Amazon S3 Calculates How Long an Object Has Been Noncurrent in the
- * Amazon S3 User Guide.
Specifies how many noncurrent versions Amazon S3 will retain in the same storage class before
- * transitioning objects. You can specify up to 100 noncurrent versions to retain. Amazon S3 will
- * transition any additional noncurrent versions beyond the specified number to retain. For
- * more information about noncurrent versions, see Lifecycle configuration
- * elements in the Amazon S3 User Guide.
+ * transitioning objects. You can specify up to 100 noncurrent versions to retain. Amazon S3 will transition any
+ * additional noncurrent versions beyond the specified number to retain. For more information about
+ * noncurrent versions, see Lifecycle configuration elements in
+ * the Amazon S3 User Guide.
* @public
*/
NewerNoncurrentVersions?: number | undefined;
@@ -6981,29 +7114,27 @@ export declare const ExpirationStatus: {
*/
export type ExpirationStatus = (typeof ExpirationStatus)[keyof typeof ExpirationStatus];
/**
- *
Specifies when an object transitions to a specified storage class. For more information
- * about Amazon S3 lifecycle configuration rules, see Transitioning
- * Objects Using Amazon S3 Lifecycle in the Amazon S3 User Guide.
+ *
Specifies when an object transitions to a specified storage class. For more information about Amazon S3
+ * lifecycle configuration rules, see Transitioning Objects Using
+ * Amazon S3 Lifecycle in the Amazon S3 User Guide.
Indicates when objects are transitioned to the specified storage class. The date value
- * must be in ISO 8601 format. The time is always midnight UTC.
+ *
Indicates when objects are transitioned to the specified storage class. The date value must be in
+ * ISO 8601 format. The time is always midnight UTC.
* @public
*/
Date?: Date | undefined;
/**
- *
Indicates the number of days after creation when objects are transitioned to the
- * specified storage class. If the specified storage class is INTELLIGENT_TIERING,
- * GLACIER_IR, GLACIER, or DEEP_ARCHIVE, valid values are
- * 0 or positive integers. If the specified storage class is STANDARD_IA
- * or ONEZONE_IA, valid values are positive integers greater than 30. Be
- * aware that some storage classes have a minimum storage duration and that you're charged for
- * transitioning objects before their minimum storage duration. For more information, see
- *
- * Constraints and considerations for transitions in the
- * Amazon S3 User Guide.
+ *
Indicates the number of days after creation when objects are transitioned to the specified storage
+ * class. If the specified storage class is INTELLIGENT_TIERING, GLACIER_IR,
+ * GLACIER, or DEEP_ARCHIVE, valid values are 0 or positive
+ * integers. If the specified storage class is STANDARD_IA or ONEZONE_IA, valid
+ * values are positive integers greater than 30. Be aware that some storage classes have a
+ * minimum storage duration and that you're charged for transitioning objects before their minimum storage
+ * duration. For more information, see Constraints and considerations for transitions in the Amazon S3 User
+ * Guide.
+ * Filter must have exactly one of Prefix, Tag,
+ * ObjectSizeGreaterThan, ObjectSizeLessThan, or And specified.
+ * Filter is required if the LifecycleRule does not contain a
+ * Prefix element.
Specifies the transition rule for the lifecycle rule that describes when noncurrent
- * objects transition to a specific storage class. If your bucket is versioning-enabled (or
- * versioning is suspended), you can set this action to request that Amazon S3 transition
- * noncurrent object versions to a specific storage class at a set period in the object's
- * lifetime.
+ *
Specifies the transition rule for the lifecycle rule that describes when noncurrent objects
+ * transition to a specific storage class. If your bucket is versioning-enabled (or versioning is
+ * suspended), you can set this action to request that Amazon S3 transition noncurrent object versions to a
+ * specific storage class at a set period in the object's lifetime.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
Specifies when noncurrent object versions expire. Upon expiration, Amazon S3 permanently
- * deletes the noncurrent object versions. You set this lifecycle configuration action on a
- * bucket that has versioning enabled (or suspended) to request that Amazon S3 delete noncurrent
- * object versions at a specific period in the object's lifetime.
+ *
Specifies when noncurrent object versions expire. Upon expiration, Amazon S3 permanently deletes the
+ * noncurrent object versions. You set this lifecycle configuration action on a bucket that has versioning
+ * enabled (or suspended) to request that Amazon S3 delete noncurrent object versions at a specific period in
+ * the object's lifetime.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
Indicates which default minimum object size behavior is applied to the lifecycle
- * configuration.
+ * configuration.
*
- *
This parameter applies to general purpose buckets only. It isn't supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It isn't supported for directory bucket
+ * lifecycle configurations.
*
*
*
*
- * all_storage_classes_128K - Objects smaller than 128 KB will not transition to any storage class by default.
+ * all_storage_classes_128K - Objects smaller than 128 KB will not transition to
+ * any storage class by default.
*
*
*
- * varies_by_storage_class - Objects smaller than 128 KB will
- * transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By
- * default, all other storage classes will prevent transitions smaller than 128 KB.
- *
+ * varies_by_storage_class - Objects smaller than 128 KB will transition to Glacier
+ * Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes
+ * will prevent transitions smaller than 128 KB.
*
*
- *
To customize the minimum object size for any transition you can add a filter that
- * specifies a custom ObjectSizeGreaterThan or ObjectSizeLessThan in
- * the body of your transition rule. Custom filters always take precedence over the default
- * transition behavior.
+ *
To customize the minimum object size for any transition you can add a filter that specifies a custom
+ * ObjectSizeGreaterThan or ObjectSizeLessThan in the body of your transition
+ * rule. Custom filters always take precedence over the default transition behavior.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
Specifies the Region where the bucket resides. For a list of all the Amazon S3 supported
- * location constraints by Region, see Regions and Endpoints.
- *
Buckets in Region us-east-1 have a LocationConstraint of
- * null. Buckets with a LocationConstraint of EU reside in eu-west-1.
+ *
Specifies the Region where the bucket resides. For a list of all the Amazon S3 supported location
+ * constraints by Region, see Regions and Endpoints.
+ *
Buckets in Region us-east-1 have a LocationConstraint of null. Buckets
+ * with a LocationConstraint of EU reside in eu-west-1.
Buckets that use the bucket owner enforced setting for Object Ownership don't support
- * target grants. For more information, see Permissions server access log delivery in the
- * Amazon S3 User Guide.
+ *
Buckets that use the bucket owner enforced setting for Object Ownership don't support target grants.
+ * For more information, see Permissions server access log delivery in the Amazon S3 User Guide.
* @public
*/
export interface TargetGrant {
@@ -7260,27 +7390,24 @@ export type PartitionDateSource = (typeof PartitionDateSource)[keyof typeof Part
*
Specifies the partition date source for the partitioned prefix.
- * PartitionDateSource can be EventTime or
- * DeliveryTime.
- *
For DeliveryTime, the time in the log file names corresponds to the
- * delivery time for the log files.
- *
For EventTime, The logs delivered are for a specific day only. The year,
- * month, and day correspond to the day on which the event occurred, and the hour, minutes and
- * seconds are set to 00 in the key.
+ *
Specifies the partition date source for the partitioned prefix. PartitionDateSource can
+ * be EventTime or DeliveryTime.
+ *
For DeliveryTime, the time in the log file names corresponds to the delivery time for
+ * the log files.
+ *
For EventTime, The logs delivered are for a specific day only. The year, month, and
+ * day correspond to the day on which the event occurred, and the hour, minutes and seconds are set to 00
+ * in the key.
Describes where logs are stored and the prefix that Amazon S3 assigns to all log object keys
- * for a bucket. For more information, see PUT Bucket logging in the
- * Amazon S3 API Reference.
+ *
Describes where logs are stored and the prefix that Amazon S3 assigns to all log object keys for a
+ * bucket. For more information, see PUT Bucket logging in the
+ * Amazon S3 API Reference.
Specifies the bucket where you want Amazon S3 to store server access logs. You can have your
- * logs delivered to any bucket that you own, including the same bucket that is being logged.
- * You can also configure multiple buckets to deliver their logs to the same target bucket. In
- * this case, you should choose a different TargetPrefix for each source bucket
- * so that the delivered log files can be distinguished by key.
+ *
Specifies the bucket where you want Amazon S3 to store server access logs. You can have your logs
+ * delivered to any bucket that you own, including the same bucket that is being logged. You can also
+ * configure multiple buckets to deliver their logs to the same target bucket. In this case, you should
+ * choose a different TargetPrefix for each source bucket so that the delivered log files can
+ * be distinguished by key.
Buckets that use the bucket owner enforced setting for Object Ownership don't support
- * target grants. For more information, see Permissions for server access log delivery in the
- * Amazon S3 User Guide.
+ *
Buckets that use the bucket owner enforced setting for Object Ownership don't support target grants.
+ * For more information, see Permissions for server access log delivery in the
+ * Amazon S3 User Guide.
A prefix for all log object keys. If you store log files from multiple Amazon S3 buckets in a
- * single bucket, you can use a prefix to distinguish which log files came from which
- * bucket.
+ *
A prefix for all log object keys. If you store log files from multiple Amazon S3 buckets in a single
+ * bucket, you can use a prefix to distinguish which log files came from which bucket.
Describes where logs are stored and the prefix that Amazon S3 assigns to all log object keys
- * for a bucket. For more information, see PUT Bucket logging in the
- * Amazon S3 API Reference.
+ *
Describes where logs are stored and the prefix that Amazon S3 assigns to all log object keys for a
+ * bucket. For more information, see PUT Bucket logging in the
+ * Amazon S3 API Reference.
- * If the CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was
- * unable to create the table, this structure contains the error code and error message.
- *
+ * The destination information for the S3 Metadata configuration.
+ *
+ * @public
+ */
+export interface DestinationResult {
+ /**
+ *
+ * The type of the table bucket where the metadata configuration is stored. The aws
+ * value indicates an Amazon Web Services managed table bucket, and the customer value indicates a
+ * customer-managed table bucket. V2 metadata configurations are stored in Amazon Web Services managed table
+ * buckets, and V1 metadata configurations are stored in customer-managed table buckets.
+ *
If an S3 Metadata V1 CreateBucketMetadataTableConfiguration or V2
+ * CreateBucketMetadataConfiguration request succeeds, but S3 Metadata was
+ * unable to create the table, this structure contains the error code and error message.
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
- * If the CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was
- * unable to create the table, this structure contains the error code. The possible error codes and
- * error messages are as follows:
- *
+ *
If the V1 CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was
+ * unable to create the table, this structure contains the error code. The possible error codes and error
+ * messages are as follows:
*
*
*
- * AccessDeniedCreatingResources - You don't have sufficient permissions to
- * create the required resources. Make sure that you have s3tables:CreateNamespace,
- * s3tables:CreateTable, s3tables:GetTable and
- * s3tables:PutTablePolicy permissions, and then try again. To create a new metadata
- * table, you must delete the metadata configuration for this bucket, and then create a new
- * metadata configuration.
- *
+ * AccessDeniedCreatingResources - You don't have sufficient permissions to create the
+ * required resources. Make sure that you have s3tables:CreateNamespace,
+ * s3tables:CreateTable, s3tables:GetTable and
+ * s3tables:PutTablePolicy permissions, and then try again. To create a new metadata
+ * table, you must delete the metadata configuration for this bucket, and then create a new metadata
+ * configuration.
*
*
*
* AccessDeniedWritingToTable - Unable to write to the metadata table because of
- * missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new
- * metadata table. To create a new metadata table, you must delete the metadata configuration for
- * this bucket, and then create a new metadata configuration.
+ * missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata
+ * table. To create a new metadata table, you must delete the metadata configuration for this bucket,
+ * and then create a new metadata configuration.
*
*
*
- * DestinationTableNotFound - The destination table doesn't exist. To create a
- * new metadata table, you must delete the metadata configuration for this bucket, and then
- * create a new metadata configuration.
+ * DestinationTableNotFound - The destination table doesn't exist. To create a new
+ * metadata table, you must delete the metadata configuration for this bucket, and then create a new
+ * metadata configuration.
*
*
*
* ServerInternalError - An internal error has occurred. To create a new metadata
- * table, you must delete the metadata configuration for this bucket, and then create a new
- * metadata configuration.
+ * table, you must delete the metadata configuration for this bucket, and then create a new metadata
+ * configuration.
*
*
*
* TableAlreadyExists - The table that you specified already exists in the table
- * bucket's namespace. Specify a different table name. To create a new metadata table, you must
- * delete the metadata configuration for this bucket, and then create a new metadata
- * configuration.
+ * bucket's namespace. Specify a different table name. To create a new metadata table, you must delete
+ * the metadata configuration for this bucket, and then create a new metadata configuration.
*
*
*
- * TableBucketNotFound - The table bucket that you specified doesn't exist in
- * this Amazon Web Services Region and account. Create or choose a different table bucket. To create a new
- * metadata table, you must delete the metadata configuration for this bucket, and then create
- * a new metadata configuration.
+ * TableBucketNotFound - The table bucket that you specified doesn't exist in this
+ * Amazon Web Services Region and account. Create or choose a different table bucket. To create a new metadata table,
+ * you must delete the metadata configuration for this bucket, and then create a new metadata
+ * configuration.
+ *
+ *
+ *
If the V2 CreateBucketMetadataConfiguration request succeeds, but S3 Metadata was
+ * unable to create the table, this structure contains the error code. The possible error codes and error
+ * messages are as follows:
+ *
+ *
+ *
+ * AccessDeniedCreatingResources - You don't have sufficient permissions to create
+ * the required resources. Make sure that you have s3tables:CreateTableBucket,
+ * s3tables:CreateNamespace, s3tables:CreateTable,
+ * s3tables:GetTable, s3tables:PutTablePolicy,
+ * kms:DescribeKey, and s3tables:PutTableEncryption permissions.
+ * Additionally, ensure that the KMS key used to encrypt the table still exists, is active and
+ * has a resource policy granting access to the S3 service principals
+ * 'maintenance.s3tables.amazonaws.com' and 'metadata.s3.amazonaws.com'.
+ * To create a new metadata table, you must delete the metadata configuration for this bucket, and
+ * then create a new metadata configuration.
+ *
+ *
+ *
+ * AccessDeniedWritingToTable - Unable to write to the metadata table because of
+ * missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata
+ * table. To create a new metadata table, you must delete the metadata configuration for this bucket,
+ * and then create a new metadata configuration.
+ *
+ *
+ *
+ * DestinationTableNotFound - The destination table doesn't exist. To create a new
+ * metadata table, you must delete the metadata configuration for this bucket, and then create a new
+ * metadata configuration.
+ *
+ *
+ *
+ * ServerInternalError - An internal error has occurred. To create a new metadata
+ * table, you must delete the metadata configuration for this bucket, and then create a new metadata
+ * configuration.
+ *
+ *
+ *
+ * JournalTableAlreadyExists - A journal table already exists in the Amazon Web Services managed table bucket's
+ * namespace. Delete the journal table, and then try again. To create a new metadata table, you must delete
+ * the metadata configuration for this bucket, and then create a new metadata configuration.
+ *
+ *
+ *
+ * InventoryTableAlreadyExists - An inventory table already exists in the Amazon Web Services managed table
+ * bucket's namespace. Delete the inventory table, and then try again. To create a new metadata table, you must delete
+ * the metadata configuration for this bucket, and then create a new metadata configuration.
+ *
+ *
+ *
+ * JournalTableNotAvailable - The journal table that the inventory table relies on
+ * has a FAILED status. An inventory table requires a journal table with an
+ * ACTIVE status. To create a new journal or inventory table, you must delete the metadata
+ * configuration for this bucket, along with any journal or inventory tables, and then create a new
+ * metadata configuration.
+ *
+ *
+ *
+ * NoSuchBucket - The specified general purpose bucket does not exist.
- * If the CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was
- * unable to create the table, this structure contains the error message. The possible error codes and
- * error messages are as follows:
- *
+ *
If the V1 CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was
+ * unable to create the table, this structure contains the error message. The possible error codes and
+ * error messages are as follows:
*
*
*
- * AccessDeniedCreatingResources - You don't have sufficient permissions to
- * create the required resources. Make sure that you have s3tables:CreateNamespace,
- * s3tables:CreateTable, s3tables:GetTable and
- * s3tables:PutTablePolicy permissions, and then try again. To create a new metadata
- * table, you must delete the metadata configuration for this bucket, and then create a new
- * metadata configuration.
- *
+ * AccessDeniedCreatingResources - You don't have sufficient permissions to create the
+ * required resources. Make sure that you have s3tables:CreateNamespace,
+ * s3tables:CreateTable, s3tables:GetTable and
+ * s3tables:PutTablePolicy permissions, and then try again. To create a new metadata
+ * table, you must delete the metadata configuration for this bucket, and then create a new metadata
+ * configuration.
*
*
*
* AccessDeniedWritingToTable - Unable to write to the metadata table because of
- * missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new
- * metadata table. To create a new metadata table, you must delete the metadata configuration for
- * this bucket, and then create a new metadata configuration.
+ * missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata
+ * table. To create a new metadata table, you must delete the metadata configuration for this bucket,
+ * and then create a new metadata configuration.
*
*
*
- * DestinationTableNotFound - The destination table doesn't exist. To create a
- * new metadata table, you must delete the metadata configuration for this bucket, and then
- * create a new metadata configuration.
+ * DestinationTableNotFound - The destination table doesn't exist. To create a new
+ * metadata table, you must delete the metadata configuration for this bucket, and then create a new
+ * metadata configuration.
*
*
*
* ServerInternalError - An internal error has occurred. To create a new metadata
- * table, you must delete the metadata configuration for this bucket, and then create a new
- * metadata configuration.
+ * table, you must delete the metadata configuration for this bucket, and then create a new metadata
+ * configuration.
*
*
*
* TableAlreadyExists - The table that you specified already exists in the table
- * bucket's namespace. Specify a different table name. To create a new metadata table, you must
- * delete the metadata configuration for this bucket, and then create a new metadata
- * configuration.
+ * bucket's namespace. Specify a different table name. To create a new metadata table, you must delete
+ * the metadata configuration for this bucket, and then create a new metadata configuration.
*
*
*
- * TableBucketNotFound - The table bucket that you specified doesn't exist in
- * this Amazon Web Services Region and account. Create or choose a different table bucket. To create a new
- * metadata table, you must delete the metadata configuration for this bucket, and then create
- * a new metadata configuration.
+ * TableBucketNotFound - The table bucket that you specified doesn't exist in this
+ * Amazon Web Services Region and account. Create or choose a different table bucket. To create a new metadata table,
+ * you must delete the metadata configuration for this bucket, and then create a new metadata
+ * configuration.
+ *
+ *
+ *
If the V2 CreateBucketMetadataConfiguration request succeeds, but S3 Metadata was
+ * unable to create the table, this structure contains the error code. The possible error codes and error
+ * messages are as follows:
+ *
+ *
+ *
+ * AccessDeniedCreatingResources - You don't have sufficient permissions to create
+ * the required resources. Make sure that you have s3tables:CreateTableBucket,
+ * s3tables:CreateNamespace, s3tables:CreateTable,
+ * s3tables:GetTable, s3tables:PutTablePolicy,
+ * kms:DescribeKey, and s3tables:PutTableEncryption permissions.
+ * Additionally, ensure that the KMS key used to encrypt the table still exists, is active and
+ * has a resource policy granting access to the S3 service principals
+ * 'maintenance.s3tables.amazonaws.com' and 'metadata.s3.amazonaws.com'.
+ * To create a new metadata table, you must delete the metadata configuration for this bucket, and
+ * then create a new metadata configuration.
+ *
+ *
+ *
+ * AccessDeniedWritingToTable - Unable to write to the metadata table because of
+ * missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata
+ * table. To create a new metadata table, you must delete the metadata configuration for this bucket,
+ * and then create a new metadata configuration.
+ *
+ *
+ *
+ * DestinationTableNotFound - The destination table doesn't exist. To create a new
+ * metadata table, you must delete the metadata configuration for this bucket, and then create a new
+ * metadata configuration.
+ *
+ *
+ *
+ * ServerInternalError - An internal error has occurred. To create a new metadata
+ * table, you must delete the metadata configuration for this bucket, and then create a new metadata
+ * configuration.
+ *
+ *
+ *
+ * JournalTableAlreadyExists - A journal table already exists in the Amazon Web Services managed table bucket's
+ * namespace. Delete the journal table, and then try again. To create a new metadata table, you must delete
+ * the metadata configuration for this bucket, and then create a new metadata configuration.
+ *
+ *
+ *
+ * InventoryTableAlreadyExists - An inventory table already exists in the Amazon Web Services managed table
+ * bucket's namespace. Delete the inventory table, and then try again. To create a new metadata table, you must delete
+ * the metadata configuration for this bucket, and then create a new metadata configuration.
+ *
+ *
+ *
+ * JournalTableNotAvailable - The journal table that the inventory table relies on
+ * has a FAILED status. An inventory table requires a journal table with an
+ * ACTIVE status. To create a new journal or inventory table, you must delete the metadata
+ * configuration for this bucket, along with any journal or inventory tables, and then create a new
+ * metadata configuration.
+ *
+ *
+ *
+ * NoSuchBucket - The specified general purpose bucket does not exist.
- * The destination information for the metadata table configuration. The destination table bucket
- * must be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata
- * table name must be unique within the aws_s3_metadata namespace in the destination
- * table bucket.
- *
+ * The inventory table configuration for an S3 Metadata configuration.
+ *
* @public
*/
-export interface S3TablesDestinationResult {
+export interface InventoryTableConfigurationResult {
/**
*
- * The Amazon Resource Name (ARN) for the table bucket that's specified as the
- * destination in the metadata table configuration. The destination table bucket
- * must be in the same Region and Amazon Web Services account as the general purpose bucket.
- *
+ * The configuration state of the inventory table, indicating whether the inventory table is enabled
+ * or disabled.
+ *
* @public
*/
- TableBucketArn: string | undefined;
+ ConfigurationState: InventoryConfigurationState | undefined;
+ /**
+ *
The status of the inventory table. The status values are:
+ *
+ *
+ *
+ * CREATING - The inventory table is in the process of being created in the specified
+ * Amazon Web Services managed table bucket.
+ *
+ *
+ *
+ * BACKFILLING - The inventory table is in the process of being backfilled. When
+ * you enable the inventory table for your metadata configuration, the table goes through a
+ * process known as backfilling, during which Amazon S3 scans your general purpose bucket to retrieve
+ * the initial metadata for all objects in the bucket. Depending on the number of objects in your
+ * bucket, this process can take several hours. When the backfilling process is finished, the
+ * status of your inventory table changes from BACKFILLING to ACTIVE.
+ * After backfilling is completed, updates to your objects are reflected in the inventory table
+ * within one hour.
+ *
+ *
+ *
+ * ACTIVE - The inventory table has been created successfully, and records are being
+ * delivered to the table.
+ *
+ *
+ *
+ * FAILED - Amazon S3 is unable to create the inventory table, or Amazon S3 is unable to deliver
+ * records.
If an S3 Metadata V1 CreateBucketMetadataTableConfiguration or V2
+ * CreateBucketMetadataConfiguration request succeeds, but S3 Metadata was
+ * unable to create the table, this structure contains the error code and error message.
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
- * The name for the metadata table in your metadata table configuration. The specified metadata
- * table name must be unique within the aws_s3_metadata namespace in the destination
- * table bucket.
- *
+ * The name of the inventory table.
+ *
+ * @public
+ */
+ TableName?: string | undefined;
+ /**
+ *
+ * The Amazon Resource Name (ARN) for the inventory table.
+ *
If an S3 Metadata V1 CreateBucketMetadataTableConfiguration or V2
+ * CreateBucketMetadataConfiguration request succeeds, but S3 Metadata was
+ * unable to create the table, this structure contains the error code and error message.
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
- * The Amazon Resource Name (ARN) for the metadata table in the metadata table configuration. The
- * specified metadata table name must be unique within the aws_s3_metadata namespace
- * in the destination table bucket.
- *
+ * The Amazon Resource Name (ARN) for the journal table.
+ *
+ * @public
+ */
+ TableArn?: string | undefined;
+ /**
+ *
+ * The journal table record expiration settings for the journal table.
+ *
+ * The general purpose bucket that corresponds to the metadata configuration that you want to
+ * retrieve.
+ *
+ *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The destination information for a V1 S3 Metadata configuration. The destination table bucket must
+ * be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name
+ * must be unique within the aws_s3_metadata namespace in the destination table bucket.
+ *
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
The Amazon Resource Name (ARN) for the table bucket that's specified as the destination in the
+ * metadata table configuration. The destination table bucket must be in the same Region and Amazon Web Services account
+ * as the general purpose bucket.
The name for the metadata table in your metadata table configuration. The specified metadata table
+ * name must be unique within the aws_s3_metadata namespace in the destination table bucket.
+ *
The Amazon Resource Name (ARN) for the metadata table in the metadata table configuration. The
+ * specified metadata table name must be unique within the aws_s3_metadata namespace in the
+ * destination table bucket.
- * The metadata table configuration for a general purpose bucket. The destination table bucket
- * must be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata
- * table name must be unique within the aws_s3_metadata namespace in the destination
- * table bucket.
- *
+ *
The V1 S3 Metadata configuration for a general purpose bucket. The destination table bucket must be
+ * in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name
+ * must be unique within the aws_s3_metadata namespace in the destination table bucket.
+ *
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
- * The destination information for the metadata table configuration. The destination table bucket
- * must be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata
- * table name must be unique within the aws_s3_metadata namespace in the destination
- * table bucket.
- *
+ *
The destination information for the metadata table configuration. The destination table bucket must
+ * be in the same Region and Amazon Web Services account as the general purpose bucket. The specified metadata table name
+ * must be unique within the aws_s3_metadata namespace in the destination table bucket.
+ *
- * The metadata table configuration for a general purpose bucket.
- *
+ *
The V1 S3 Metadata configuration for a general purpose bucket.
+ *
+ *
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ * and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
+ * a live inventory table.
- * The status of the metadata table. The status values are:
- *
+ *
The status of the metadata table. The status values are:
*
*
*
- * CREATING - The metadata table is in the process of being created in the
- * specified table bucket.
+ * CREATING - The metadata table is in the process of being created in the specified
+ * table bucket.
*
*
*
- * ACTIVE - The metadata table has been created successfully and records
- * are being delivered to the table.
- *
+ * ACTIVE - The metadata table has been created successfully, and records are being
+ * delivered to the table.
*
*
*
* FAILED - Amazon S3 is unable to create the metadata table, or Amazon S3 is unable to deliver
- * records. See ErrorDetails for details.
+ * records. See ErrorDetails for details.
*
*
* @public
*/
Status: string | undefined;
/**
- *
- * If the CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was
- * unable to create the table, this structure contains the error code and error message.
- *
+ *
If the CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was
+ * unable to create the table, this structure contains the error code and error message.
- * The general purpose bucket that contains the metadata table configuration that you want to retrieve.
- *
+ *
The general purpose bucket that corresponds to the metadata table configuration that you want to
+ * retrieve.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
* @public
*/
Bucket: string | undefined;
/**
- *
- * The expected owner of the general purpose bucket that you want to retrieve the metadata table configuration from.
- *
+ *
The expected owner of the general purpose bucket that you want to retrieve the metadata table
+ * configuration for.
A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter.
- * The operator must have at least two predicates, and an object must match all of the
- * predicates in order for the filter to apply.
+ *
A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The
+ * operator must have at least two predicates, and an object must match all of the predicates in order for
+ * the filter to apply.
Specifies a metrics configuration filter. The metrics configuration only includes
- * objects that meet the filter's criteria. A filter must be a prefix, an object tag, an
- * access point ARN, or a conjunction (MetricsAndOperator). For more information, see PutBucketMetricsConfiguration.
+ *
Specifies a metrics configuration filter. The metrics configuration only includes objects that meet
+ * the filter's criteria. A filter must be a prefix, an object tag, an access point ARN, or a conjunction
+ * (MetricsAndOperator). For more information, see PutBucketMetricsConfiguration.
A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter.
- * The operator must have at least two predicates, and an object must match all of the
- * predicates in order for the filter to apply.
+ *
A conjunction (logical AND) of predicates, which is used in evaluating a metrics filter. The
+ * operator must have at least two predicates, and an object must match all of the predicates in order for
+ * the filter to apply.
Specifies a metrics configuration for the CloudWatch request metrics (specified by the
- * metrics configuration ID) from an Amazon S3 bucket. If you're updating an existing metrics
- * configuration, note that this is a full replacement of the existing metrics configuration.
- * If you don't include the elements you want to keep, they are erased. For more information,
- * see PutBucketMetricsConfiguration.
+ *
Specifies a metrics configuration for the CloudWatch request metrics (specified by the metrics
+ * configuration ID) from an Amazon S3 bucket. If you're updating an existing metrics configuration, note that
+ * this is a full replacement of the existing metrics configuration. If you don't include the elements you
+ * want to keep, they are erased. For more information, see PutBucketMetricsConfiguration.
The ID used to identify the metrics configuration. The ID has a 64 character limit and
- * can only contain letters, numbers, periods, dashes, and underscores.
+ *
The ID used to identify the metrics configuration. The ID has a 64 character limit and can only
+ * contain letters, numbers, periods, dashes, and underscores.
* @public
*/
Id: string | undefined;
/**
- *
Specifies a metrics configuration filter. The metrics configuration will only include
- * objects that meet the filter's criteria. A filter must be a prefix, an object tag, an
- * access point ARN, or a conjunction (MetricsAndOperator).
+ *
Specifies a metrics configuration filter. The metrics configuration will only include objects that
+ * meet the filter's criteria. A filter must be a prefix, an object tag, an access point ARN, or a
+ * conjunction (MetricsAndOperator).
The ID used to identify the metrics configuration. The ID has a 64 character limit and
- * can only contain letters, numbers, periods, dashes, and underscores.
+ *
The ID used to identify the metrics configuration. The ID has a 64 character limit and can only
+ * contain letters, numbers, periods, dashes, and underscores.
Specifies the Amazon S3 object key name to filter on. An object key name is the name assigned
- * to an object in your Amazon S3 bucket. You specify whether to filter on the suffix or prefix of
- * the object key name. A prefix is a specific string of characters at the beginning of an
- * object key name, which you can use to organize objects. For example, you can start the key
- * names of related objects with a prefix, such as 2023- or
- * engineering/. Then, you can use FilterRule to find objects in
- * a bucket with key names that have the same prefix. A suffix is similar to a prefix, but it
- * is at the end of the object key name instead of at the beginning.
+ *
Specifies the Amazon S3 object key name to filter on. An object key name is the name assigned to an
+ * object in your Amazon S3 bucket. You specify whether to filter on the suffix or prefix of the object key
+ * name. A prefix is a specific string of characters at the beginning of an object key name, which you can
+ * use to organize objects. For example, you can start the key names of related objects with a prefix, such
+ * as 2023- or engineering/. Then, you can use FilterRule to find
+ * objects in a bucket with key names that have the same prefix. A suffix is similar to a prefix, but it is
+ * at the end of the object key name instead of at the beginning.
The object key name prefix or suffix identifying one or more objects to which the
- * filtering rule applies. The maximum length is 1,024 characters. Overlapping prefixes and
- * suffixes are not supported. For more information, see Configuring Event Notifications
- * in the Amazon S3 User Guide.
+ *
The object key name prefix or suffix identifying one or more objects to which the filtering rule
+ * applies. The maximum length is 1,024 characters. Overlapping prefixes and suffixes are not supported.
+ * For more information, see Configuring Event Notifications in the Amazon S3 User Guide.
The Amazon S3 bucket event for which to invoke the Lambda function. For more information,
- * see Supported
- * Event Types in the Amazon S3 User Guide.
+ *
The Amazon S3 bucket event for which to invoke the Lambda function. For more information, see Supported Event Types in
+ * the Amazon S3 User Guide.
A container for specifying the configuration for publication of messages to an Amazon
- * Simple Notification Service (Amazon SNS) topic when Amazon S3 detects specified events.
+ *
A container for specifying the configuration for publication of messages to an Amazon Simple
+ * Notification Service (Amazon SNS) topic when Amazon S3 detects specified events.
The container element for object ownership for a bucket's ownership controls.
*
- * BucketOwnerPreferred - Objects uploaded to the bucket change ownership to
- * the bucket owner if the objects are uploaded with the
- * bucket-owner-full-control canned ACL.
+ * BucketOwnerPreferred - Objects uploaded to the bucket change ownership to the bucket
+ * owner if the objects are uploaded with the bucket-owner-full-control canned ACL.
*
- * ObjectWriter - The uploading account will own the object if the object is
- * uploaded with the bucket-owner-full-control canned ACL.
+ * ObjectWriter - The uploading account will own the object if the object is uploaded with
+ * the bucket-owner-full-control canned ACL.
*
- * BucketOwnerEnforced - Access control lists (ACLs) are disabled and no
- * longer affect permissions. The bucket owner automatically owns and has full control over
- * every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL
- * or specify bucket owner full control ACLs (such as the predefined
- * bucket-owner-full-control canned ACL or a custom ACL in XML format that
- * grants the same permissions).
- *
By default, ObjectOwnership is set to BucketOwnerEnforced and
- * ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where
- * you must control access for each object individually. For more information about S3 Object
- * Ownership, see Controlling ownership of
- * objects and disabling ACLs for your bucket in the
- * Amazon S3 User Guide.
+ * BucketOwnerEnforced - Access control lists (ACLs) are disabled and no longer affect
+ * permissions. The bucket owner automatically owns and has full control over every object in the bucket.
+ * The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner full control ACLs
+ * (such as the predefined bucket-owner-full-control canned ACL or a custom ACL in XML format
+ * that grants the same permissions).
+ *
By default, ObjectOwnership is set to BucketOwnerEnforced and ACLs are
+ * disabled. We recommend keeping ACLs disabled, except in uncommon use cases where you must control access
+ * for each object individually. For more information about S3 Object Ownership, see Controlling
+ * ownership of objects and disabling ACLs for your bucket in the
+ * Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.
The name of the Amazon S3 bucket whose OwnershipControls you want to retrieve.
- *
+ *
The name of the Amazon S3 bucket whose OwnershipControls you want to retrieve.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
Specifies whether Amazon S3 replicates delete markers. If you specify a Filter
- * in your replication configuration, you must also include a
- * DeleteMarkerReplication element. If your Filter includes a
- * Tag element, the DeleteMarkerReplication
- * Status must be set to Disabled, because Amazon S3 does not support replicating
- * delete markers for tag-based rules. For an example configuration, see Basic Rule Configuration.
Specifies whether Amazon S3 replicates delete markers. If you specify a Filter in your
+ * replication configuration, you must also include a DeleteMarkerReplication element. If your
+ * Filter includes a Tag element, the DeleteMarkerReplication
+ * Status must be set to Disabled, because Amazon S3 does not support replicating delete markers
+ * for tag-based rules. For an example configuration, see Basic Rule
+ * Configuration.
If you are using an earlier version of the replication configuration, Amazon S3 handles
- * replication of delete markers differently. For more information, see Backward Compatibility.
+ *
If you are using an earlier version of the replication configuration, Amazon S3 handles replication of
+ * delete markers differently. For more information, see Backward Compatibility.
Specifies encryption-related information for an Amazon S3 bucket that is a destination for
- * replicated objects.
+ *
Specifies encryption-related information for an Amazon S3 bucket that is a destination for replicated
+ * objects.
*
- *
If you're specifying a customer managed KMS key, we recommend using a fully
- * qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the
- * key within the requester’s account. This behavior can result in data that's encrypted
- * with a KMS key that belongs to the requester, and not the bucket owner.
+ *
If you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key
+ * ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester’s account.
+ * This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and
+ * not the bucket owner.
Specifies the ID (Key ARN or Alias ARN) of the customer managed Amazon Web Services KMS key stored in
- * Amazon Web Services Key Management Service (KMS) for the destination bucket. Amazon S3 uses this key to
- * encrypt replica objects. Amazon S3 only supports symmetric encryption KMS keys. For more
- * information, see Asymmetric keys in Amazon Web Services
- * KMS in the Amazon Web Services Key Management Service Developer
- * Guide.
+ *
Specifies the ID (Key ARN or Alias ARN) of the customer managed Amazon Web Services KMS key stored in Amazon Web Services Key
+ * Management Service (KMS) for the destination bucket. Amazon S3 uses this key to encrypt replica objects. Amazon S3
+ * only supports symmetric encryption KMS keys. For more information, see Asymmetric keys in Amazon Web Services KMS in the
+ * Amazon Web Services Key Management Service Developer Guide.
A container specifying S3 Replication Time Control (S3 RTC) related information, including whether S3 RTC is
- * enabled and the time when all objects and operations on objects must be replicated. Must be
- * specified together with a Metrics block.
+ *
A container specifying S3 Replication Time Control (S3 RTC) related information, including whether S3 RTC is enabled and
+ * the time when all objects and operations on objects must be replicated. Must be specified together with
+ * a Metrics block.
The Amazon Resource Name (ARN) of the bucket where you want Amazon S3 to store the
- * results.
+ *
The Amazon Resource Name (ARN) of the bucket where you want Amazon S3 to store the results.
* @public
*/
Bucket: string | undefined;
/**
- *
Destination bucket owner account ID. In a cross-account scenario, if you direct Amazon S3 to
- * change replica ownership to the Amazon Web Services account that owns the destination bucket by
- * specifying the AccessControlTranslation property, this is the account ID of
- * the destination bucket owner. For more information, see Replication Additional
- * Configuration: Changing the Replica Owner in the
- * Amazon S3 User Guide.
+ *
Destination bucket owner account ID. In a cross-account scenario, if you direct Amazon S3 to change
+ * replica ownership to the Amazon Web Services account that owns the destination bucket by specifying the
+ * AccessControlTranslation property, this is the account ID of the destination bucket
+ * owner. For more information, see Replication Additional Configuration: Changing
+ * the Replica Owner in the Amazon S3 User Guide.
The storage class to use when replicating objects, such as S3 Standard or reduced
- * redundancy. By default, Amazon S3 uses the storage class of the source object to create the
- * object replica.
- *
For valid values, see the StorageClass element of the PUT Bucket
- * replication action in the Amazon S3 API Reference.
+ *
The storage class to use when replicating objects, such as S3 Standard or reduced redundancy. By
+ * default, Amazon S3 uses the storage class of the source object to create the object replica.
+ *
For valid values, see the StorageClass element of the PUT Bucket replication action in the
+ * Amazon S3 API Reference.
*
* FSX_OPENZFS is not an accepted value when replicating objects.
Specify this only in a cross-account scenario (where source and destination bucket
- * owners are not the same), and you want to change replica ownership to the Amazon Web Services account
- * that owns the destination bucket. If this is not specified in the replication
- * configuration, the replicas are owned by same Amazon Web Services account that owns the source
- * object.
+ *
Specify this only in a cross-account scenario (where source and destination bucket owners are not
+ * the same), and you want to change replica ownership to the Amazon Web Services account that owns the destination
+ * bucket. If this is not specified in the replication configuration, the replicas are owned by same
+ * Amazon Web Services account that owns the source object.
A container specifying S3 Replication Time Control (S3 RTC), including whether S3 RTC is enabled and the time
- * when all objects and operations on objects must be replicated. Must be specified together
- * with a Metrics block.
+ *
A container specifying S3 Replication Time Control (S3 RTC), including whether S3 RTC is enabled and the time when all
+ * objects and operations on objects must be replicated. Must be specified together with a
+ * Metrics block.
A container for specifying rule filters. The filters determine the subset of objects to
- * which the rule applies. This element is required only if you specify more than one filter.
+ *
A container for specifying rule filters. The filters determine the subset of objects to which the
+ * rule applies. This element is required only if you specify more than one filter.
*
For example:
*
*
- *
If you specify both a Prefix and a Tag filter, wrap
- * these filters in an And tag.
+ *
If you specify both a Prefix and a Tag filter, wrap these filters in
+ * an And tag.
*
*
- *
If you specify a filter based on multiple tags, wrap the Tag elements
- * in an And tag.
+ *
If you specify a filter based on multiple tags, wrap the Tag elements in an
+ * And tag.
A filter that identifies the subset of objects to which the replication rule applies. A
- * Filter must specify exactly one Prefix, Tag, or
- * an And child element.
+ * Filter must specify exactly one Prefix, Tag, or an
+ * And child element.
* @public
*/
export interface ReplicationRuleFilter {
/**
- *
An object key name prefix that identifies the subset of objects to which the rule
- * applies.
+ *
An object key name prefix that identifies the subset of objects to which the rule applies.
The priority indicates which rule has precedence whenever two or more replication rules conflict.
+ * Amazon S3 will attempt to replicate objects according to all replication rules. However, if there are two or
+ * more rules with the same destination bucket, then objects will be replicated according to the rule with
+ * the highest priority. The higher the number, the higher the priority.
+ *
For more information, see Replication in the Amazon S3 User Guide.
* @public
*/
Priority?: number | undefined;
/**
- *
An object key name prefix that identifies the object or objects to which the rule
- * applies. The maximum prefix length is 1,024 characters. To include all objects in a bucket,
- * specify an empty string.
+ *
An object key name prefix that identifies the object or objects to which the rule applies. The
+ * maximum prefix length is 1,024 characters. To include all objects in a bucket, specify an empty string.
+ *
A container that describes additional filters for identifying the source objects that
- * you want to replicate. You can choose to enable or disable the replication of these
- * objects. Currently, Amazon S3 supports only the filter that you can specify for objects created
- * with server-side encryption using a customer managed key stored in Amazon Web Services Key Management Service
- * (SSE-KMS).
+ *
A container that describes additional filters for identifying the source objects that you want to
+ * replicate. You can choose to enable or disable the replication of these objects. Currently, Amazon S3
+ * supports only the filter that you can specify for objects created with server-side encryption using a
+ * customer managed key stored in Amazon Web Services Key Management Service (SSE-KMS).
Specifies whether Amazon S3 replicates delete markers. If you specify a Filter
- * in your replication configuration, you must also include a
- * DeleteMarkerReplication element. If your Filter includes a
- * Tag element, the DeleteMarkerReplication
- * Status must be set to Disabled, because Amazon S3 does not support replicating
- * delete markers for tag-based rules. For an example configuration, see Basic Rule Configuration.
Specifies whether Amazon S3 replicates delete markers. If you specify a Filter in your
+ * replication configuration, you must also include a DeleteMarkerReplication element. If your
+ * Filter includes a Tag element, the DeleteMarkerReplication
+ * Status must be set to Disabled, because Amazon S3 does not support replicating delete markers
+ * for tag-based rules. For an example configuration, see Basic Rule
+ * Configuration.
If you are using an earlier version of the replication configuration, Amazon S3 handles
- * replication of delete markers differently. For more information, see Backward Compatibility.
+ *
If you are using an earlier version of the replication configuration, Amazon S3 handles replication of
+ * delete markers differently. For more information, see Backward Compatibility.
The Amazon Resource Name (ARN) of the Identity and Access Management (IAM) role that Amazon S3 assumes when
- * replicating objects. For more information, see How to Set Up Replication
- * in the Amazon S3 User Guide.
+ *
The Amazon Resource Name (ARN) of the Identity and Access Management (IAM) role that Amazon S3 assumes when replicating
+ * objects. For more information, see How to Set Up Replication in the
+ * Amazon S3 User Guide.
* @public
*/
Role: string | undefined;
/**
- *
A container for one or more replication rules. A replication configuration must have at
- * least one rule and can contain a maximum of 1,000 rules.
+ *
A container for one or more replication rules. A replication configuration must have at least one
+ * rule and can contain a maximum of 1,000 rules.
Specifies whether MFA delete is enabled in the bucket versioning configuration. This
- * element is only returned if the bucket has been configured with MFA delete. If the bucket
- * has never been so configured, this element is not returned.
+ *
Specifies whether MFA delete is enabled in the bucket versioning configuration. This element is only
+ * returned if the bucket has been configured with MFA delete. If the bucket has never been so configured,
+ * this element is not returned.
A suffix that is appended to a request that is for a directory on the website endpoint.
- * (For example, if the suffix is index.html and you make a request to
- * samplebucket/images/, the data that is returned will be for the object with
- * the key name images/index.html.) The suffix must not be empty and must not
- * include a slash character.
+ *
A suffix that is appended to a request that is for a directory on the website endpoint. (For
+ * example, if the suffix is index.html and you make a request to
+ * samplebucket/images/, the data that is returned will be for the object with the key name
+ * images/index.html.) The suffix must not be empty and must not include a slash
+ * character.
The object key prefix to use in the redirect request. For example, to redirect requests
- * for all pages with prefix docs/ (objects in the docs/ folder) to
- * documents/, you can set a condition block with KeyPrefixEquals
- * set to docs/ and in the Redirect set ReplaceKeyPrefixWith to
- * /documents. Not required if one of the siblings is present. Can be present
- * only if ReplaceKeyWith is not provided.
+ *
The object key prefix to use in the redirect request. For example, to redirect requests for all
+ * pages with prefix docs/ (objects in the docs/ folder) to
+ * documents/, you can set a condition block with KeyPrefixEquals set to
+ * docs/ and in the Redirect set ReplaceKeyPrefixWith to
+ * /documents. Not required if one of the siblings is present. Can be present only if
+ * ReplaceKeyWith is not provided.
Specifies the redirect behavior and when a redirect is applied. For more information about routing
+ * rules, see Configuring
+ * advanced conditional redirects in the Amazon S3 User Guide.
A container for describing a condition that must be met for the specified redirect to
- * apply. For example, 1. If request is for pages in the /docs folder, redirect
- * to the /documents folder. 2. If request results in HTTP error 4xx, redirect
- * request to another host where you might process the error.
+ *
A container for describing a condition that must be met for the specified redirect to apply. For
+ * example, 1. If request is for pages in the /docs folder, redirect to the
+ * /documents folder. 2. If request results in HTTP error 4xx, redirect request to another
+ * host where you might process the error.
Container for redirect information. You can redirect requests to another host, to
- * another page, or with another protocol. In the event of an error, you can specify a
- * different error code to return.
+ *
Container for redirect information. You can redirect requests to another host, to another page, or
+ * with another protocol. In the event of an error, you can specify a different error code to
+ * return.
Indicates whether the object retrieved was (true) or was not (false) a Delete Marker. If
- * false, this response header does not appear in the response.
+ *
Indicates whether the object retrieved was (true) or was not (false) a Delete Marker. If false, this
+ * response header does not appear in the response.
*
*
*
- *
If the current version of the object is a delete marker, Amazon S3 behaves as if the
- * object was deleted and includes x-amz-delete-marker: true in the
- * response.
+ *
If the current version of the object is a delete marker, Amazon S3 behaves as if the object was
+ * deleted and includes x-amz-delete-marker: true in the response.
*
*
- *
If the specified version in the request is a delete marker, the response
- * returns a 405 Method Not Allowed error and the Last-Modified:
- * timestamp response header.
+ *
If the specified version in the request is a delete marker, the response returns a 405
+ * Method Not Allowed error and the Last-Modified: timestamp response
+ * header.
If the object expiration is configured (see
* PutBucketLifecycleConfiguration
- * ), the response includes this
- * header. It includes the expiry-date and rule-id key-value pairs
- * providing object expiration information. The value of the rule-id is
- * URL-encoded.
+ * ), the response includes this header. It
+ * includes the expiry-date and rule-id key-value pairs providing object
+ * expiration information. The value of the rule-id is URL-encoded.
*
- *
Object expiration information is not returned in directory buckets and this header returns the value "NotImplemented" in all responses for directory buckets.
+ *
Object expiration information is not returned in directory buckets and this header returns the
+ * value "NotImplemented" in all responses for directory buckets.
Provides information about object restoration action and expiration time of the restored
- * object copy.
+ *
Provides information about object restoration action and expiration time of the restored object
+ * copy.
*
- *
This functionality is not supported for directory buckets.
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ *
This functionality is not supported for directory buckets. Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
* General purpose buckets - When you specify a
- * versionId of the object in your request, if the specified version in the
- * request is a delete marker, the response returns a 405 Method Not Allowed
- * error and the Last-Modified: timestamp response header.
+ * versionId of the object in your request, if the specified version in the request is a
+ * delete marker, the response returns a 405 Method Not Allowed error and the
+ * Last-Modified: timestamp response header.
The checksum type, which determines how part-level checksums are combined to create an
- * object-level checksum for multipart objects. You can use this header response to verify
- * that the checksum type that is received is the same checksum type that was specified in the
- * CreateMultipartUpload request. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The checksum type, which determines how part-level checksums are combined to create an object-level
+ * checksum for multipart objects. You can use this header response to verify that the checksum type that
+ * is received is the same checksum type that was specified in the CreateMultipartUpload
+ * request. For more information, see Checking object integrity in
+ * the Amazon S3 User Guide.
This is set to the number of metadata entries not returned in the headers that are
- * prefixed with x-amz-meta-. This can happen if you create metadata using an API
- * like SOAP that supports more flexible metadata than the REST API. For example, using SOAP,
- * you can create metadata whose values are not legal HTTP headers.
+ *
This is set to the number of metadata entries not returned in the headers that are prefixed with
+ * x-amz-meta-. This can happen if you create metadata using an API like SOAP that supports
+ * more flexible metadata than the REST API. For example, using SOAP, you can create metadata whose values
+ * are not legal HTTP headers.
*
*
This functionality is not supported for directory buckets.
Indicates what content encodings have been applied to the object and thus what decoding
- * mechanisms must be applied to obtain the media-type referenced by the Content-Type header
- * field.
+ *
Indicates what content encodings have been applied to the object and thus what decoding mechanisms
+ * must be applied to obtain the media-type referenced by the Content-Type header field.
If the bucket is configured as a website, redirects requests for this object to another
- * object in the same bucket or to an external URL. Amazon S3 stores the value of this header in
- * the object metadata.
+ *
If the bucket is configured as a website, redirects requests for this object to another object in
+ * the same bucket or to an external URL. Amazon S3 stores the value of this header in the object
+ * metadata.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to confirm the encryption algorithm that's used.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to confirm the encryption algorithm that's used.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to provide the round-trip message integrity verification
- * of the customer-provided encryption key.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to provide the round-trip message integrity verification of the customer-provided
+ * encryption key.
*
*
This functionality is not supported for directory buckets.
Provides storage class information of the object. Amazon S3 returns this header for all
- * objects except for S3 Standard storage class objects.
+ *
Provides storage class information of the object. Amazon S3 returns this header for all objects except
+ * for S3 Standard storage class objects.
*
*
* Directory buckets -
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
The count of parts this object has. This value is only returned if you specify
- * partNumber in your request and the object was uploaded as a multipart
- * upload.
+ * partNumber in your request and the object was uploaded as a multipart upload.
* @public
*/
PartsCount?: number | undefined;
/**
- *
The number of tags, if any, on the object, when you have the relevant permission to read
- * object tags.
- *
You can use GetObjectTagging to retrieve
- * the tag set associated with an object.
+ *
The number of tags, if any, on the object, when you have the relevant permission to read object
+ * tags.
+ *
You can use GetObjectTagging to retrieve the tag set associated with an object.
*
*
This functionality is not supported for directory buckets.
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -9448,46 +9902,45 @@ export interface GetObjectRequest {
*/
Bucket: string | undefined;
/**
- *
Return the object only if its entity tag (ETag) is the same as the one specified in this
- * header; otherwise, return a 412 Precondition Failed error.
- *
If both of the If-Match and If-Unmodified-Since headers are
- * present in the request as follows: If-Match condition evaluates to
- * true, and; If-Unmodified-Since condition evaluates to
- * false; then, S3 returns 200 OK and the data requested.
+ *
Return the object only if its entity tag (ETag) is the same as the one specified in this header;
+ * otherwise, return a 412 Precondition Failed error.
+ *
If both of the If-Match and If-Unmodified-Since headers are present in the
+ * request as follows: If-Match condition evaluates to true, and;
+ * If-Unmodified-Since condition evaluates to false; then, S3 returns 200
+ * OK and the data requested.
*
For more information about conditional requests, see RFC 7232.
Return the object only if it has been modified since the specified time; otherwise,
- * return a 304 Not Modified error.
- *
If both of the If-None-Match and If-Modified-Since headers are
- * present in the request as follows: If-None-Match condition evaluates to
- * false, and; If-Modified-Since condition evaluates to
- * true; then, S3 returns 304 Not Modified status code.
+ *
Return the object only if it has been modified since the specified time; otherwise, return a
+ * 304 Not Modified error.
+ *
If both of the If-None-Match and If-Modified-Since headers are present in
+ * the request as follows: If-None-Match condition evaluates to false, and;
+ * If-Modified-Since condition evaluates to true; then, S3 returns 304
+ * Not Modified status code.
*
For more information about conditional requests, see RFC 7232.
* @public
*/
IfModifiedSince?: Date | undefined;
/**
- *
Return the object only if its entity tag (ETag) is different from the one specified in
- * this header; otherwise, return a 304 Not Modified error.
- *
If both of the If-None-Match and If-Modified-Since headers are
- * present in the request as follows: If-None-Match condition evaluates to
- * false, and; If-Modified-Since condition evaluates to
- * true; then, S3 returns 304 Not Modified HTTP status
- * code.
+ *
Return the object only if its entity tag (ETag) is different from the one specified in this header;
+ * otherwise, return a 304 Not Modified error.
+ *
If both of the If-None-Match and If-Modified-Since headers are present in
+ * the request as follows: If-None-Match condition evaluates to false, and;
+ * If-Modified-Since condition evaluates to true; then, S3 returns 304
+ * Not Modified HTTP status code.
*
For more information about conditional requests, see RFC 7232.
Return the object only if it has not been modified since the specified time; otherwise,
- * return a 412 Precondition Failed error.
- *
If both of the If-Match and If-Unmodified-Since headers are
- * present in the request as follows: If-Match condition evaluates to
- * true, and; If-Unmodified-Since condition evaluates to
- * false; then, S3 returns 200 OK and the data requested.
+ *
Return the object only if it has not been modified since the specified time; otherwise, return a
+ * 412 Precondition Failed error.
+ *
If both of the If-Match and If-Unmodified-Since headers are present in the
+ * request as follows: If-Match condition evaluates to true, and;
+ * If-Unmodified-Since condition evaluates to false; then, S3 returns 200
+ * OK and the data requested.
*
For more information about conditional requests, see RFC 7232.
Version ID used to reference a specific version of the object.
- *
By default, the GetObject operation returns the current version of an
- * object. To return a different version, use the versionId subresource.
+ *
By default, the GetObject operation returns the current version of an object. To return
+ * a different version, use the versionId subresource.
*
*
*
- *
If you include a versionId in your request header, you must have
- * the s3:GetObjectVersion permission to access a specific version of an
- * object. The s3:GetObject permission is not required in this
- * scenario.
+ *
If you include a versionId in your request header, you must have the
+ * s3:GetObjectVersion permission to access a specific version of an object. The
+ * s3:GetObject permission is not required in this scenario.
*
*
- *
If you request the current version of an object without a specific
- * versionId in the request header, only the
- * s3:GetObject permission is required. The
- * s3:GetObjectVersion permission is not required in this
- * scenario.
+ *
If you request the current version of an object without a specific versionId in
+ * the request header, only the s3:GetObject permission is required. The
+ * s3:GetObjectVersion permission is not required in this scenario.
*
*
*
- * Directory buckets -
- * S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null to the
- * versionId query parameter in the request.
+ * Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets.
+ * You can only specify null to the versionId query parameter in the
+ * request.
Specifies the algorithm to use when decrypting the object (for example,
- * AES256).
- *
If you encrypt an object by using server-side encryption with customer-provided
- * encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,
- * you must use the following headers:
+ *
Specifies the algorithm to use when decrypting the object (for example, AES256).
+ *
If you encrypt an object by using server-side encryption with customer-provided encryption keys
+ * (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following
+ * headers:
Specifies the customer-provided encryption key that you originally provided for Amazon S3 to
- * encrypt the data before storing it. This value is used to decrypt the object when
- * recovering it and must match the one used when storing the data. The key must be
- * appropriate for use with the algorithm specified in the
- * x-amz-server-side-encryption-customer-algorithm header.
- *
If you encrypt an object by using server-side encryption with customer-provided
- * encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,
- * you must use the following headers:
+ *
Specifies the customer-provided encryption key that you originally provided for Amazon S3 to encrypt the
+ * data before storing it. This value is used to decrypt the object when recovering it and must match the
+ * one used when storing the data. The key must be appropriate for use with the algorithm specified in the
+ * x-amz-server-side-encryption-customer-algorithm header.
+ *
If you encrypt an object by using server-side encryption with customer-provided encryption keys
+ * (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following
+ * headers:
Specifies the 128-bit MD5 digest of the customer-provided 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.
- *
If you encrypt an object by using server-side encryption with customer-provided
- * encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,
- * you must use the following headers:
+ *
Specifies the 128-bit MD5 digest of the customer-provided 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.
+ *
If you encrypt an object by using server-side encryption with customer-provided encryption keys
+ * (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following
+ * headers:
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Part number of the object being read. This is a positive integer between 1 and 10,000.
- * Effectively performs a 'ranged' GET request for the part specified. Useful for downloading
- * just a part of an object.
+ *
Part number of the object being read. This is a positive integer between 1 and 10,000. Effectively
+ * performs a 'ranged' GET request for the part specified. Useful for downloading just a part of an
+ * object.
Object is archived and inaccessible until restored.
- *
If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage
- * class, the S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access
- * tier, or the S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you
- * must first restore a copy using RestoreObject. Otherwise, this
- * operation returns an InvalidObjectState error. For information about restoring
- * archived objects, see Restoring Archived Objects in
- * the Amazon S3 User Guide.
+ *
If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class, the
+ * S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the
+ * S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a copy
+ * using RestoreObject. Otherwise, this operation returns an InvalidObjectState error. For
+ * information about restoring archived objects, see Restoring Archived Objects in the
+ * Amazon S3 User Guide.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
The Base64 encoded, 64-bit CRC64NVME checksum of the object. This checksum is present
- * if the object was uploaded with the CRC64NVME checksum algorithm, or if the object was uploaded without a
- * checksum (and Amazon S3 added the default checksum, CRC64NVME, to the uploaded object). For more information, see Checking object integrity in the Amazon S3 User Guide.
+ * if the object was uploaded with the CRC64NVME checksum algorithm, or if the object was
+ * uploaded without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to the
+ * uploaded object). For more information, see Checking object integrity in
+ * the Amazon S3 User Guide.
* @public
*/
ChecksumCRC64NVME?: string | undefined;
@@ -9846,8 +10290,9 @@ export interface Checksum {
*/
ChecksumSHA256?: string | undefined;
/**
- *
The checksum type that is used to calculate the object’s
- * checksum value. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The checksum type that is used to calculate the object’s checksum value. For more information, see
+ * Checking
+ * object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present
- * if the multipart upload request was created with the CRC32 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present if the
+ * multipart upload request was created with the CRC32 checksum algorithm. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present
- * if the multipart upload request was created with the CRC32C checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present if the
+ * multipart upload request was created with the CRC32C checksum algorithm. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present
- * if the multipart upload request was created with the CRC64NVME checksum algorithm, or if the object was uploaded without a
- * checksum (and Amazon S3 added the default checksum, CRC64NVME, to the uploaded object). For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present if
+ * the multipart upload request was created with the CRC64NVME checksum algorithm, or if the
+ * object was uploaded without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to
+ * the uploaded object). For more information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present
- * if the multipart upload request was created with the SHA1 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present if the
+ * multipart upload request was created with the SHA1 checksum algorithm. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present
- * if the multipart upload request was created with the SHA256 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present if
+ * the multipart upload request was created with the SHA256 checksum algorithm. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
When a list is truncated, this element specifies the last part in the list, as well as
- * the value to use for the PartNumberMarker request parameter in a subsequent
- * request.
+ *
When a list is truncated, this element specifies the last part in the list, as well as the value to
+ * use for the PartNumberMarker request parameter in a subsequent request.
Indicates whether the returned list of parts is truncated. A value of true
- * indicates that the list was truncated. A list can be truncated if the number of parts
- * exceeds the limit returned in the MaxParts element.
+ *
Indicates whether the returned list of parts is truncated. A value of true indicates
+ * that the list was truncated. A list can be truncated if the number of parts exceeds the limit returned
+ * in the MaxParts element.
A container for elements related to a particular part. A response can contain zero or
- * more Parts elements.
+ *
A container for elements related to a particular part. A response can contain zero or more
+ * Parts elements.
*
*
*
*
* General purpose buckets - For
- * GetObjectAttributes, if an additional checksum (including
- * x-amz-checksum-crc32, x-amz-checksum-crc32c,
- * x-amz-checksum-sha1, or x-amz-checksum-sha256) isn't
- * applied to the object specified in the request, the response doesn't return
- * the Part element.
+ * GetObjectAttributes, if an additional checksum (including
+ * x-amz-checksum-crc32, x-amz-checksum-crc32c,
+ * x-amz-checksum-sha1, or x-amz-checksum-sha256) isn't applied to the
+ * object specified in the request, the response doesn't return the Part element.
*
*
*
* Directory buckets - For
- * GetObjectAttributes, regardless of whether an additional checksum is
- * applied to the object specified in the request, the response returns
- * the Part element.
+ * GetObjectAttributes, regardless of whether an additional checksum is applied to the
+ * object specified in the request, the response returns the Part element.
*
Specifies whether the object retrieved was (true) or was not
- * (false) a delete marker. If false, this response header does
- * not appear in the response. To learn more about delete markers, see Working with delete markers.
+ *
Specifies whether the object retrieved was (true) or was not (false) a
+ * delete marker. If false, this response header does not appear in the response. To learn
+ * more about delete markers, see Working with delete markers.
*
*
This functionality is not supported for directory buckets.
* Directory buckets -
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
*
* @public
*/
@@ -10053,8 +10505,7 @@ export interface GetObjectAttributesRequest {
/**
*
The name of the bucket that contains the object.
*
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -10083,19 +10534,21 @@ export interface GetObjectAttributesRequest {
*
The version ID used to reference a specific version of the object.
*
*
S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null to the
- * versionId query parameter in the request.
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.
+ *
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 functionality is not supported for directory buckets.
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 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.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
The default Object Lock retention mode and period that you want to apply to new objects
- * placed in the specified bucket. Bucket settings require both a mode and a period. The
- * period can be either Days or Years but you must select one. You
- * cannot specify Days and Years at the same time.
+ *
The default Object Lock retention mode and period that you want to apply to new objects placed in
+ * the specified bucket. Bucket settings require both a mode and a period. The period can be either
+ * Days or Years but you must select one. You cannot specify Days
+ * and Years at the same time.
Indicates whether this bucket has an Object Lock configuration enabled. Enable
- * ObjectLockEnabled when you apply ObjectLockConfiguration to a
- * bucket.
+ * ObjectLockEnabled when you apply ObjectLockConfiguration to a bucket.
+ *
* @public
*/
ObjectLockEnabled?: ObjectLockEnabled | undefined;
/**
- *
Specifies the Object Lock rule for the specified object. Enable the this rule when you
- * apply ObjectLockConfiguration to a bucket. Bucket settings require both a mode
- * and a period. The period can be either Days or Years but you must
- * select one. You cannot specify Days and Years at the same
- * time.
+ *
Specifies the Object Lock rule for the specified object. Enable the this rule when you apply
+ * ObjectLockConfiguration to a bucket. Bucket settings require both a mode and a period.
+ * The period can be either Days or Years but you must select one. You cannot
+ * specify Days and Years at the same time.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can
- * enable the configuration options in any combination. For more information about when Amazon S3
- * considers a bucket or object public, see The Meaning of "Public" in the Amazon S3 User Guide.
+ *
The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the
+ * configuration options in any combination. For more information about when Amazon S3 considers a bucket or
+ * object public, see The Meaning of "Public" in the Amazon S3 User Guide.
Specifies whether Amazon S3 should block public access control lists (ACLs) for this bucket
- * and objects in this bucket. Setting this element to TRUE causes the following
- * behavior:
+ *
Specifies whether Amazon S3 should block public access control lists (ACLs) for this bucket and objects
+ * in this bucket. Setting this element to TRUE causes the following behavior:
*
*
- *
PUT Bucket ACL and PUT Object ACL calls fail if the specified ACL is
- * public.
+ *
PUT Bucket ACL and PUT Object ACL calls fail if the specified ACL is public.
*
*
*
PUT Object calls fail if the request includes a public ACL.
Specifies whether Amazon S3 should ignore public ACLs for this bucket and objects in this
- * bucket. Setting this element to TRUE causes Amazon S3 to ignore all public ACLs on
- * this bucket and objects in this bucket.
- *
Enabling this setting doesn't affect the persistence of any existing ACLs and doesn't
- * prevent new public ACLs from being set.
+ *
Specifies whether Amazon S3 should ignore public ACLs for this bucket and objects in this bucket. Setting
+ * this element to TRUE causes Amazon S3 to ignore all public ACLs on this bucket and objects in
+ * this bucket.
+ *
Enabling this setting doesn't affect the persistence of any existing ACLs and doesn't prevent new
+ * public ACLs from being set.
Specifies whether Amazon S3 should block public bucket policies for this bucket. Setting this
- * element to TRUE causes Amazon S3 to reject calls to PUT Bucket policy if the
- * specified bucket policy allows public access.
+ *
Specifies whether Amazon S3 should block public bucket policies for this bucket. Setting this element to
+ * TRUE causes Amazon S3 to reject calls to PUT Bucket policy if the specified bucket policy
+ * allows public access.
*
Enabling this setting doesn't affect existing bucket policies.
Specifies whether Amazon S3 should restrict public bucket policies for this bucket. Setting
- * this element to TRUE restricts access to this bucket to only Amazon Web Services service principals and authorized users within this account if the bucket has
- * a public policy.
- *
Enabling this setting doesn't affect previously stored bucket policies, except that
- * public and cross-account access within any public bucket policy, including non-public
- * delegation to specific accounts, is blocked.
+ *
Specifies whether Amazon S3 should restrict public bucket policies for this bucket. Setting this element
+ * to TRUE restricts access to this bucket to only Amazon Web Services service principals and
+ * authorized users within this account if the bucket has a public policy.
+ *
Enabling this setting doesn't affect previously stored bucket policies, except that public and
+ * cross-account access within any public bucket policy, including non-public delegation to specific
+ * accounts, is blocked.
The name of the Amazon S3 bucket whose PublicAccessBlock configuration you want
- * to retrieve.
+ *
The name of the Amazon S3 bucket whose PublicAccessBlock configuration you want to retrieve.
+ *
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The name of the location where the bucket will be created.
- *
For directory buckets, the Zone ID of the Availability Zone or the Local Zone where the bucket is created. An example Zone ID value for an Availability Zone is usw2-az1.
+ *
For directory buckets, the Zone ID of the Availability Zone or the Local Zone where the bucket is created. An example
+ * Zone ID value for an Availability Zone is usw2-az1.
*
*
This functionality is only supported by directory buckets.
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -10720,8 +11165,8 @@ export type ArchiveStatus = (typeof ArchiveStatus)[keyof typeof ArchiveStatus];
*/
export interface HeadObjectOutput {
/**
- *
Specifies whether the object retrieved was (true) or was not (false) a Delete Marker. If
- * false, this response header does not appear in the response.
+ *
Specifies whether the object retrieved was (true) or was not (false) a Delete Marker. If false, this
+ * response header does not appear in the response.
*
*
This functionality is not supported for directory buckets.
If the object expiration is configured (see
* PutBucketLifecycleConfiguration
- * ), the response includes this
- * header. It includes the expiry-date and rule-id key-value pairs
- * providing object expiration information. The value of the rule-id is
- * URL-encoded.
+ * ), the response includes this header. It
+ * includes the expiry-date and rule-id key-value pairs providing object
+ * expiration information. The value of the rule-id is URL-encoded.
*
- *
Object expiration information is not returned in directory buckets and this header returns the value "NotImplemented" in all responses for directory buckets.
+ *
Object expiration information is not returned in directory buckets and this header returns the
+ * value "NotImplemented" in all responses for directory buckets.
If the object is an archived object (an object whose storage class is GLACIER), the
- * response includes this header if either the archive restoration is in progress (see RestoreObject or an archive copy is already restored.
- *
If an archive copy is already restored, the header value indicates when Amazon S3 is
- * scheduled to delete the object copy. For example:
+ *
If the object is an archived object (an object whose storage class is GLACIER), the response
+ * includes this header if either the archive restoration is in progress (see RestoreObject or an archive copy is already
+ * restored.
+ *
If an archive copy is already restored, the header value indicates when Amazon S3 is scheduled to delete
+ * the object copy. For example:
This functionality is not supported for directory buckets.
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ *
This functionality is not supported for directory buckets. Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
The checksum type, which determines how part-level checksums are combined to create an
- * object-level checksum for multipart objects. You can use this header response to verify
- * that the checksum type that is received is the same checksum type that was specified in
- * CreateMultipartUpload request. For more
- * information, see Checking object integrity
- * in the Amazon S3 User Guide.
+ *
The checksum type, which determines how part-level checksums are combined to create an object-level
+ * checksum for multipart objects. You can use this header response to verify that the checksum type that
+ * is received is the same checksum type that was specified in CreateMultipartUpload request.
+ * For more information, see Checking object integrity in the Amazon S3
+ * User Guide.
An entity tag (ETag) is an opaque identifier assigned by a web server to a specific
- * version of a resource found at a URL.
+ *
An entity tag (ETag) is an opaque identifier assigned by a web server to a specific version of a
+ * resource found at a URL.
* @public
*/
ETag?: string | undefined;
/**
- *
This is set to the number of metadata entries not returned in x-amz-meta
- * headers. This can happen if you create metadata using an API like SOAP that supports more
- * flexible metadata than the REST API. For example, using SOAP, you can create metadata whose
- * values are not legal HTTP headers.
+ *
This is set to the number of metadata entries not returned in x-amz-meta headers. This
+ * can happen if you create metadata using an API like SOAP that supports more flexible metadata than the
+ * REST API. For example, using SOAP, you can create metadata whose values are not legal HTTP
+ * headers.
*
*
This functionality is not supported for directory buckets.
Indicates what content encodings have been applied to the object and thus what decoding
- * mechanisms must be applied to obtain the media-type referenced by the Content-Type header
- * field.
+ *
Indicates what content encodings have been applied to the object and thus what decoding mechanisms
+ * must be applied to obtain the media-type referenced by the Content-Type header field.
If the bucket is configured as a website, redirects requests for this object to another
- * object in the same bucket or to an external URL. Amazon S3 stores the value of this header in
- * the object metadata.
+ *
If the bucket is configured as a website, redirects requests for this object to another object in
+ * the same bucket or to an external URL. Amazon S3 stores the value of this header in the object
+ * metadata.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to confirm the encryption algorithm that's used.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to confirm the encryption algorithm that's used.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to provide the round-trip message integrity verification
- * of the customer-provided encryption key.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to provide the round-trip message integrity verification of the customer-provided
+ * encryption key.
*
*
This functionality is not supported for directory buckets.
* Directory buckets -
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
*
* @public
*/
StorageClass?: StorageClass | undefined;
/**
- *
Amazon S3 can return this header if your request involves a bucket that is either a source or
- * a destination in a replication rule.
- *
In replication, you have a source bucket on which you configure replication and
- * destination bucket or buckets where Amazon S3 stores object replicas. When you request an object
- * (GetObject) or object metadata (HeadObject) from these
- * buckets, Amazon S3 will return the x-amz-replication-status header in the response
- * as follows:
+ *
Amazon S3 can return this header if your request involves a bucket that is either a source or a
+ * destination in a replication rule.
+ *
In replication, you have a source bucket on which you configure replication and destination bucket
+ * or buckets where Amazon S3 stores object replicas. When you request an object (GetObject) or
+ * object metadata (HeadObject) from these buckets, Amazon S3 will return the
+ * x-amz-replication-status header in the response as follows:
*
*
*
- * If requesting an object from the source bucket,
- * Amazon S3 will return the x-amz-replication-status header if the object in
- * your request is eligible for replication.
- *
For example, suppose that in your replication configuration, you specify object
- * prefix TaxDocs requesting Amazon S3 to replicate objects with key prefix
- * TaxDocs. Any objects you upload with this key name prefix, for
- * example TaxDocs/document1.pdf, are eligible for replication. For any
- * object request with this key name prefix, Amazon S3 will return the
- * x-amz-replication-status header with value PENDING, COMPLETED or
- * FAILED indicating object replication status.
+ * If requesting an object from the source bucket, Amazon S3 will
+ * return the x-amz-replication-status header if the object in your request is eligible
+ * for replication.
+ *
For example, suppose that in your replication configuration, you specify object prefix
+ * TaxDocs requesting Amazon S3 to replicate objects with key prefix TaxDocs.
+ * Any objects you upload with this key name prefix, for example TaxDocs/document1.pdf,
+ * are eligible for replication. For any object request with this key name prefix, Amazon S3 will return the
+ * x-amz-replication-status header with value PENDING, COMPLETED or FAILED indicating
+ * object replication status.
*
*
*
- * If requesting an object from a destination
- * bucket, Amazon S3 will return the x-amz-replication-status header
- * with value REPLICA if the object in your request is a replica that Amazon S3 created and
- * there is no replica modification replication in progress.
+ * If requesting an object from a destination bucket, Amazon S3 will
+ * return the x-amz-replication-status header with value REPLICA if the object in your
+ * request is a replica that Amazon S3 created and there is no replica modification replication in
+ * progress.
*
*
*
- * When replicating objects to multiple destination
- * buckets, the x-amz-replication-status header acts
- * differently. The header of the source object will only return a value of COMPLETED
- * when replication is successful to all destinations. The header will remain at value
- * PENDING until replication has completed for all destinations. If one or more
- * destinations fails replication the header will return FAILED.
+ * When replicating objects to multiple destination buckets, the
+ * x-amz-replication-status header acts differently. The header of the source object
+ * will only return a value of COMPLETED when replication is successful to all destinations. The header
+ * will remain at value PENDING until replication has completed for all destinations. If one or more
+ * destinations fails replication the header will return FAILED.
*
The count of parts this object has. This value is only returned if you specify
- * partNumber in your request and the object was uploaded as a multipart
- * upload.
+ * partNumber in your request and the object was uploaded as a multipart upload.
* @public
*/
PartsCount?: number | undefined;
/**
- *
The number of tags, if any, on the object, when you have the relevant permission to read
- * object tags.
- *
You can use GetObjectTagging to retrieve
- * the tag set associated with an object.
+ *
The number of tags, if any, on the object, when you have the relevant permission to read object
+ * tags.
+ *
You can use GetObjectTagging to retrieve the tag set associated with an object.
*
*
This functionality is not supported for directory buckets.
The Object Lock mode, if any, that's in effect for this object. This header is only
- * returned if the requester has the s3:GetObjectRetention permission. For more
- * information about S3 Object Lock, see Object Lock.
+ *
The Object Lock mode, if any, that's in effect for this object. This header is only returned if the
+ * requester has the s3:GetObjectRetention permission. For more information about S3 Object
+ * Lock, see Object Lock.
*
*
This functionality is not supported for directory buckets.
The date and time when the Object Lock retention period expires. This header is only
- * returned if the requester has the s3:GetObjectRetention permission.
+ *
The date and time when the Object Lock retention period expires. This header is only returned if the
+ * requester has the s3:GetObjectRetention permission.
*
*
This functionality is not supported for directory buckets.
Specifies whether a legal hold is in effect for this object. This header is only
- * returned if the requester has the s3:GetObjectLegalHold permission. This
- * header is not returned if the specified version of this object has never had a legal hold
- * applied. For more information about S3 Object Lock, see Object Lock.
+ *
Specifies whether a legal hold is in effect for this object. This header is only returned if the
+ * requester has the s3:GetObjectLegalHold permission. This header is not returned if the
+ * specified version of this object has never had a legal hold applied. For more information about S3
+ * Object Lock, see Object
+ * Lock.
*
*
This functionality is not supported for directory buckets.
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -11099,10 +11539,10 @@ export interface HeadObjectRequest {
*/
Bucket: string | undefined;
/**
- *
Return the object only if its entity tag (ETag) is the same as the one specified;
- * otherwise, return a 412 (precondition failed) error.
- *
If both of the If-Match and If-Unmodified-Since headers are
- * present in the request as follows:
+ *
Return the object only if its entity tag (ETag) is the same as the one specified; otherwise, return
+ * a 412 (precondition failed) error.
+ *
If both of the If-Match and If-Unmodified-Since headers are present in the
+ * request as follows:
HeadObject returns only the metadata for an object. If the Range is satisfiable, only
- * the ContentLength is affected in the response. If the Range is not
- * satisfiable, S3 returns a 416 - Requested Range Not Satisfiable error.
+ *
HeadObject returns only the metadata for an object. If the Range is satisfiable, only the
+ * ContentLength is affected in the response. If the Range is not satisfiable, S3 returns a
+ * 416 - Requested Range Not Satisfiable error.
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.
+ *
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 functionality is not supported for directory buckets.
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 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.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Part number of the object being read. This is a positive integer between 1 and 10,000.
- * Effectively performs a 'ranged' HEAD request for the part specified. Useful querying about
- * the size of the part and the number of parts in this object.
+ *
Part number of the object being read. This is a positive integer between 1 and 10,000. Effectively
+ * performs a 'ranged' HEAD request for the part specified. Useful querying about the size of the part and
+ * the number of parts in this object.
To retrieve the checksum, this parameter must be enabled.
*
* General purpose buckets -
- * If you enable checksum mode and the object is uploaded with a
- * checksum
- * and encrypted with an Key Management Service (KMS) key, you must have permission to use the
- * kms:Decrypt action to retrieve the checksum.
+ * If you enable checksum mode and the object is uploaded with a checksum and encrypted with
+ * an Key Management Service (KMS) key, you must have permission to use the kms:Decrypt action to
+ * retrieve the checksum.
*
- * Directory buckets - If you enable
- * ChecksumMode and the object is encrypted with Amazon Web Services Key Management Service
- * (Amazon Web Services KMS), you must also have the kms:GenerateDataKey and
- * kms:Decrypt permissions in IAM identity-based policies and KMS key
- * policies for the KMS key to retrieve the checksum of the object.
+ * Directory buckets - If you enable ChecksumMode
+ * and the object is encrypted with Amazon Web Services Key Management Service (Amazon Web Services KMS), you must also have the
+ * kms:GenerateDataKey and kms:Decrypt permissions in IAM identity-based
+ * policies and KMS key policies for the KMS key to retrieve the checksum of the object.
* @public
*/
ChecksumMode?: ChecksumMode | undefined;
@@ -11305,24 +11741,23 @@ export interface HeadObjectRequest {
*/
export interface ListBucketAnalyticsConfigurationsOutput {
/**
- *
Indicates whether the returned list of analytics configurations is complete. A value of
- * true indicates that the list is not complete and the NextContinuationToken will be provided
- * for a subsequent request.
+ *
Indicates whether the returned list of analytics configurations is complete. A value of true
+ * indicates that the list is not complete and the NextContinuationToken will be provided for a subsequent
+ * request.
- * NextContinuationToken is sent when isTruncated is true, which
- * indicates that there are more analytics configurations to list. The next request must
- * include this NextContinuationToken. The token is obfuscated and is not a
- * usable value.
+ * NextContinuationToken is sent when isTruncated is true, which indicates
+ * that there are more analytics configurations to list. The next request must include this
+ * NextContinuationToken. The token is obfuscated and is not a usable value.
* @public
*/
NextContinuationToken?: string | undefined;
@@ -11344,8 +11779,8 @@ export interface ListBucketAnalyticsConfigurationsRequest {
*/
Bucket: string | undefined;
/**
- *
The ContinuationToken that represents a placeholder from where this request
- * should begin.
+ *
The ContinuationToken that represents a placeholder from where this request should
+ * begin.
Indicates whether the returned list of analytics configurations is complete. A value of
- * true indicates that the list is not complete and the
- * NextContinuationToken will be provided for a subsequent request.
+ * true indicates that the list is not complete and the NextContinuationToken
+ * will be provided for a subsequent request.
* @public
*/
IsTruncated?: boolean | undefined;
/**
- *
The ContinuationToken that represents a placeholder from where this request
- * should begin.
+ *
The ContinuationToken that represents a placeholder from where this request should
+ * begin.
The marker used to continue this inventory configuration listing. Use the
- * NextContinuationToken from this response to continue the listing in a
- * subsequent request. The continuation token is an opaque value that Amazon S3 understands.
+ * NextContinuationToken from this response to continue the listing in a subsequent request.
+ * The continuation token is an opaque value that Amazon S3 understands.
* @public
*/
NextContinuationToken?: string | undefined;
@@ -11397,8 +11832,8 @@ export interface ListBucketIntelligentTieringConfigurationsRequest {
*/
Bucket: string | undefined;
/**
- *
The ContinuationToken that represents a placeholder from where this request
- * should begin.
+ *
The ContinuationToken that represents a placeholder from where this request should
+ * begin.
Tells whether the returned list of inventory configurations is complete. A value of true
- * indicates that the list is not complete and the NextContinuationToken is provided for a
- * subsequent request.
+ *
Tells whether the returned list of inventory configurations is complete. A value of true indicates
+ * that the list is not complete and the NextContinuationToken is provided for a subsequent request.
The marker used to continue this inventory configuration listing. Use the
- * NextContinuationToken from this response to continue the listing in a
- * subsequent request. The continuation token is an opaque value that Amazon S3 understands.
+ * NextContinuationToken from this response to continue the listing in a subsequent request.
+ * The continuation token is an opaque value that Amazon S3 understands.
* @public
*/
NextContinuationToken?: string | undefined;
@@ -11450,10 +11884,9 @@ export interface ListBucketInventoryConfigurationsRequest {
*/
Bucket: string | undefined;
/**
- *
The marker used to continue an inventory configuration listing that has been truncated.
- * Use the NextContinuationToken from a previously truncated list response to
- * continue the listing. The continuation token is an opaque value that Amazon S3
- * understands.
+ *
The marker used to continue an inventory configuration listing that has been truncated. Use the
+ * NextContinuationToken from a previously truncated list response to continue the listing.
+ * The continuation token is an opaque value that Amazon S3 understands.
Indicates whether the returned list of metrics configurations is complete. A value of
- * true indicates that the list is not complete and the NextContinuationToken will be provided
- * for a subsequent request.
+ *
Indicates whether the returned list of metrics configurations is complete. A value of true indicates
+ * that the list is not complete and the NextContinuationToken will be provided for a subsequent
+ * request.
The marker used to continue a metrics configuration listing that has been truncated. Use
- * the NextContinuationToken from a previously truncated list response to
- * continue the listing. The continuation token is an opaque value that Amazon S3
- * understands.
+ *
The marker used to continue a metrics configuration listing that has been truncated. Use the
+ * NextContinuationToken from a previously truncated list response to continue the listing.
+ * The continuation token is an opaque value that Amazon S3 understands.
The marker that is used to continue a metrics configuration listing that has been
- * truncated. Use the NextContinuationToken from a previously truncated list
- * response to continue the listing. The continuation token is an opaque value that Amazon S3
- * understands.
+ *
The marker that is used to continue a metrics configuration listing that has been truncated. Use the
+ * NextContinuationToken from a previously truncated list response to continue the listing.
+ * The continuation token is an opaque value that Amazon S3 understands.
Date the bucket was created. This date can change when making changes to your bucket,
- * such as editing its bucket policy.
+ *
Date the bucket was created. This date can change when making changes to your bucket, such as
+ * editing its bucket policy.
* @public
*/
CreationDate?: Date | undefined;
/**
*
- * BucketRegion indicates the Amazon Web Services region where the bucket is located. If the
- * request contains at least one valid parameter, it is included in the response.
+ * BucketRegion indicates the Amazon Web Services region where the bucket is located. If the request
+ * contains at least one valid parameter, it is included in the response.
* @public
*/
BucketRegion?: string | undefined;
/**
- *
The Amazon Resource Name (ARN) of the S3 bucket. ARNs uniquely identify Amazon Web Services resources across all of Amazon Web Services.
+ *
The Amazon Resource Name (ARN) of the S3 bucket. ARNs uniquely identify Amazon Web Services resources across all
+ * of Amazon Web Services.
- * ContinuationToken is included in the response when there are more buckets
- * that can be listed with pagination. The next ListBuckets request to Amazon S3 can
- * be continued with this ContinuationToken. ContinuationToken is
- * obfuscated and is not a real bucket.
+ * ContinuationToken is included in the response when there are more buckets that can be
+ * listed with pagination. The next ListBuckets request to Amazon S3 can be continued with this
+ * ContinuationToken. ContinuationToken is obfuscated and is not a real
+ * bucket.
* @public
*/
ContinuationToken?: string | undefined;
@@ -11586,43 +12019,41 @@ export interface ListBucketsOutput {
*/
export interface ListBucketsRequest {
/**
- *
Maximum number of buckets to be returned in response. When the number is more than the
- * count of buckets that are owned by an Amazon Web Services account, return all the buckets in
- * response.
+ *
Maximum number of buckets to be returned in response. When the number is more than the count of
+ * buckets that are owned by an Amazon Web Services account, return all the buckets in response.
* @public
*/
MaxBuckets?: number | undefined;
/**
*
- * ContinuationToken indicates to Amazon S3 that the list is being continued on
- * this bucket with a token. ContinuationToken is obfuscated and is not a real
- * key. You can use this ContinuationToken for pagination of the list results.
+ * ContinuationToken indicates to Amazon S3 that the list is being continued on this bucket
+ * with a token. ContinuationToken is obfuscated and is not a real key. You can use this
+ * ContinuationToken for pagination of the list results.
*
Length Constraints: Minimum length of 0. Maximum length of 1024.
*
Required: No.
*
- *
If you specify the bucket-region, prefix, or continuation-token
- * query parameters without using max-buckets to set the maximum number of buckets returned in the response,
- * Amazon S3 applies a default page size of 10,000 and provides a continuation token if there are more buckets.
+ *
If you specify the bucket-region, prefix, or
+ * continuation-token query parameters without using max-buckets to set the
+ * maximum number of buckets returned in the response, Amazon S3 applies a default page size of 10,000 and
+ * provides a continuation token if there are more buckets.
Limits the response to bucket names that begin with the specified bucket name
- * prefix.
+ *
Limits the response to bucket names that begin with the specified bucket name prefix.
* @public
*/
Prefix?: string | undefined;
/**
- *
Limits the response to buckets that are located in the specified Amazon Web Services Region. The Amazon Web Services
- * Region must be expressed according to the Amazon Web Services Region code, such as us-west-2
- * for the US West (Oregon) Region. For a list of the valid values for all of the Amazon Web Services
- * Regions, see Regions and Endpoints.
+ *
Limits the response to buckets that are located in the specified Amazon Web Services Region. The Amazon Web Services Region must
+ * be expressed according to the Amazon Web Services Region code, such as us-west-2 for the US West (Oregon)
+ * Region. For a list of the valid values for all of the Amazon Web Services Regions, see Regions and Endpoints.
*
- *
Requests made to a Regional endpoint that is different from the
- * bucket-region parameter are not supported. For example, if you want to
- * limit the response to your buckets in Region us-west-2, the request must be
- * made to an endpoint in Region us-west-2.
+ *
Requests made to a Regional endpoint that is different from the bucket-region
+ * parameter are not supported. For example, if you want to limit the response to your buckets in Region
+ * us-west-2, the request must be made to an endpoint in Region
+ * us-west-2.
If ContinuationToken was sent with the request, it is included in the
- * response. You can use the returned ContinuationToken for pagination of the
- * list response.
+ *
If ContinuationToken was sent with the request, it is included in the response. You can
+ * use the returned ContinuationToken for pagination of the list response.
- * ContinuationToken indicates to Amazon S3 that the list is being continued on
- * buckets in this account with a token. ContinuationToken is obfuscated and is
- * not a real bucket name. You can use this ContinuationToken for the pagination
- * of the list results.
+ * ContinuationToken indicates to Amazon S3 that the list is being continued on buckets in this
+ * account with a token. ContinuationToken is obfuscated and is not a real bucket name. You
+ * can use this ContinuationToken for the pagination of the list results.
* @public
*/
ContinuationToken?: string | undefined;
/**
- *
Maximum number of buckets to be returned in response. When the number is more than the
- * count of buckets that are owned by an Amazon Web Services account, return all the buckets in
- * response.
+ *
Maximum number of buckets to be returned in response. When the number is more than the count of
+ * buckets that are owned by an Amazon Web Services account, return all the buckets in response.
Container for all (if there are any) keys between Prefix and the next occurrence of the
- * string specified by a delimiter. CommonPrefixes lists keys that act like subdirectories in
- * the directory specified by Prefix. For example, if the prefix is notes/ and the delimiter
- * is a slash (/) as in notes/summer/july, the common prefix is notes/summer/.
+ *
Container for all (if there are any) keys between Prefix and the next occurrence of the string
+ * specified by a delimiter. CommonPrefixes lists keys that act like subdirectories in the directory
+ * specified by Prefix. For example, if the prefix is notes/ and the delimiter is a slash (/) as in
+ * notes/summer/july, the common prefix is notes/summer/.
If the principal is an Amazon Web Services account, it provides the Canonical User ID. If the
- * principal is an IAM User, it provides a user ARN value.
+ *
If the principal is an Amazon Web Services account, it provides the Canonical User ID. If the principal is an
+ * IAM User, it provides a user ARN value.
*
*
- * Directory buckets - If the principal is an
- * Amazon Web Services account, it provides the Amazon Web Services account ID. If the principal is an IAM User, it
- * provides a user ARN value.
+ * Directory buckets - If the principal is an Amazon Web Services account,
+ * it provides the Amazon Web Services account ID. If the principal is an IAM User, it provides a user ARN
+ * value.
*
* @public
*/
@@ -11742,7 +12170,7 @@ export interface MultipartUpload {
*
*
* Directory buckets -
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
*
* @public
*/
@@ -11751,8 +12179,8 @@ export interface MultipartUpload {
*
Specifies the owner of the object that is part of the multipart upload.
*
*
- * Directory buckets - The bucket owner is
- * returned as the object owner for all the objects.
+ * Directory buckets - The bucket owner is returned as the
+ * object owner for all the objects.
*
* @public
*/
@@ -11768,8 +12196,9 @@ export interface MultipartUpload {
*/
ChecksumAlgorithm?: ChecksumAlgorithm | undefined;
/**
- *
The checksum type that is used to calculate the object’s
- * checksum value. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
The checksum type that is used to calculate the object’s checksum value. For more information, see
+ * Checking
+ * object integrity in the Amazon S3 User Guide.
Together with key-marker, specifies the multipart upload after which listing should
- * begin. If key-marker is not specified, the upload-id-marker parameter is ignored.
- * Otherwise, any multipart uploads for a key equal to the key-marker might be included in the
- * list only if they have an upload ID lexicographically greater than the specified
- * upload-id-marker.
+ *
Together with key-marker, specifies the multipart upload after which listing should begin. If
+ * key-marker is not specified, the upload-id-marker parameter is ignored. Otherwise, any multipart uploads
+ * for a key equal to the key-marker might be included in the list only if they have an upload ID
+ * lexicographically greater than the specified upload-id-marker.
*
*
This functionality is not supported for directory buckets.
When a prefix is provided in the request, this field contains the specified prefix. The
- * result contains only keys starting with the specified prefix.
+ *
When a prefix is provided in the request, this field contains the specified prefix. The result
+ * contains only keys starting with the specified prefix.
*
*
* Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
Maximum number of multipart uploads that could have been included in the
- * response.
+ *
Maximum number of multipart uploads that could have been included in the response.
* @public
*/
MaxUploads?: number | undefined;
/**
- *
Indicates whether the returned list of multipart uploads is truncated. A value of true
- * indicates that the list was truncated. The list can be truncated if the number of multipart
- * uploads exceeds the limit allowed or specified by max uploads.
+ *
Indicates whether the returned list of multipart uploads is truncated. A value of true indicates
+ * that the list was truncated. The list can be truncated if the number of multipart uploads exceeds the
+ * limit allowed or specified by max uploads.
If you specify a delimiter in the request, then the result returns each distinct key
- * prefix containing the delimiter in a CommonPrefixes element. The distinct key
- * prefixes are returned in the Prefix child element.
+ *
If you specify a delimiter in the request, then the result returns each distinct key prefix
+ * containing the delimiter in a CommonPrefixes element. The distinct key prefixes are
+ * returned in the Prefix child element.
*
*
* Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
Encoding type used by Amazon S3 to encode object keys in the response.
- *
If you specify the encoding-type request parameter, Amazon S3 includes this
- * element in the response, and returns encoded key name values in the following response
- * elements:
+ *
If you specify the encoding-type request parameter, Amazon S3 includes this element in the
+ * response, and returns encoded key name values in the following response elements:
The name of the bucket to which the multipart upload was initiated.
*
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -11917,14 +12343,14 @@ export interface ListMultipartUploadsRequest {
Bucket: string | undefined;
/**
*
Character you use to group keys.
- *
All keys that contain the same string between the prefix, if specified, and the first
- * occurrence of the delimiter after the prefix are grouped under a single result element,
- * CommonPrefixes. If you don't specify the prefix parameter, then the
- * substring starts at the beginning of the key. The keys that are grouped under
- * CommonPrefixes result element are not returned elsewhere in the
- * response.
+ *
All keys that contain the same string between the prefix, if specified, and the first occurrence of
+ * the delimiter after the prefix are grouped under a single result element, CommonPrefixes.
+ * If you don't specify the prefix parameter, then the substring starts at the beginning of the key. The
+ * keys that are grouped under CommonPrefixes result element are not returned elsewhere in the
+ * response.
*
- * CommonPrefixes is filtered out from results if it is not lexicographically greater than the key-marker.
+ * CommonPrefixes is filtered out from results if it is not lexicographically greater than
+ * the key-marker.
*
*
* Directory buckets - For directory buckets, / is the only supported delimiter.
Encoding type used by Amazon S3 to encode the object keys in the response.
- * Responses are encoded only in UTF-8. An object key can contain any Unicode character.
- * However, the XML 1.0 parser can't parse certain characters, such as characters with an
- * ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this
- * parameter to request that Amazon S3 encode the keys in the response. For more information about
- * characters to avoid in object key names, see Object key naming
- * guidelines.
+ *
Encoding type used by Amazon S3 to encode the object keys in the response. Responses are
+ * encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser
+ * can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that
+ * aren't supported in XML 1.0, you can add this parameter to request that Amazon S3 encode the keys in the
+ * response. For more information about characters to avoid in object key names, see Object key
+ * naming guidelines.
*
- *
When using the URL encoding type, non-ASCII characters that are used in an object's
- * key name will be percent-encoded according to UTF-8 code values. For example, the object
- * test_file(3).png will appear as
- * test_file%283%29.png.
+ *
When using the URL encoding type, non-ASCII characters that are used in an object's key name will
+ * be percent-encoded according to UTF-8 code values. For example, the object
+ * test_file(3).png will appear as test_file%283%29.png.
- * General purpose buckets - For
- * general purpose buckets, key-marker is an object key. Together with
- * upload-id-marker, this parameter specifies the multipart upload
- * after which listing should begin.
- *
If upload-id-marker is not specified, only the keys
- * lexicographically greater than the specified key-marker will be
- * included in the list.
- *
If upload-id-marker is specified, any multipart uploads for a key
- * equal to the key-marker might also be included, provided those
- * multipart uploads have upload IDs lexicographically greater than the specified
- * upload-id-marker.
+ * General purpose buckets - For general purpose buckets,
+ * key-marker is an object key. Together with upload-id-marker, this
+ * parameter specifies the multipart upload after which listing should begin.
+ *
If upload-id-marker is not specified, only the keys lexicographically greater
+ * than the specified key-marker will be included in the list.
+ *
If upload-id-marker is specified, any multipart uploads for a key equal to the
+ * key-marker might also be included, provided those multipart uploads have upload IDs
+ * lexicographically greater than the specified upload-id-marker.
*
*
*
- * Directory buckets - For
- * directory buckets, key-marker is obfuscated and isn't a real object
- * key. The upload-id-marker parameter isn't supported by
- * directory buckets. To list the additional multipart uploads, you only need to set
- * the value of key-marker to the NextKeyMarker value from
- * the previous response.
- *
In the ListMultipartUploads response, the multipart uploads aren't
- * sorted lexicographically based on the object keys.
+ * Directory buckets - For directory buckets,
+ * key-marker is obfuscated and isn't a real object key. The
+ * upload-id-marker parameter isn't supported by directory buckets. To list the
+ * additional multipart uploads, you only need to set the value of key-marker to the
+ * NextKeyMarker value from the previous response.
+ *
In the ListMultipartUploads response, the multipart uploads aren't sorted
+ * lexicographically based on the object keys.
*
- *
Sets the maximum number of multipart uploads, from 1 to 1,000, to return in the response
- * body. 1,000 is the maximum number of uploads that can be returned in a response.
+ *
Sets the maximum number of multipart uploads, from 1 to 1,000, to return in the response body. 1,000
+ * is the maximum number of uploads that can be returned in a response.
* @public
*/
MaxUploads?: number | undefined;
/**
- *
Lists in-progress uploads only for those keys that begin with the specified prefix. You
- * can use prefixes to separate a bucket into different grouping of keys. (You can think of
- * using prefix to make groups in the same way that you'd use a folder in a file
- * system.)
+ *
Lists in-progress uploads only for those keys that begin with the specified prefix. You can use
+ * prefixes to separate a bucket into different grouping of keys. (You can think of using
+ * prefix to make groups in the same way that you'd use a folder in a file system.)
*
*
* Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
Together with key-marker, specifies the multipart upload after which listing should
- * begin. If key-marker is not specified, the upload-id-marker parameter is ignored.
- * Otherwise, any multipart uploads for a key equal to the key-marker might be included in the
- * list only if they have an upload ID lexicographically greater than the specified
- * upload-id-marker.
+ *
Together with key-marker, specifies the multipart upload after which listing should begin. If
+ * key-marker is not specified, the upload-id-marker parameter is ignored. Otherwise, any multipart uploads
+ * for a key equal to the key-marker might be included in the list only if they have an upload ID
+ * lexicographically greater than the specified upload-id-marker.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Specifies the restoration status of an object. Objects in certain storage classes must
- * be restored before they can be retrieved. For more information about these storage classes
- * and how to work with archived objects, see Working with archived
- * objects in the Amazon S3 User Guide.
+ *
Specifies the restoration status of an object. Objects in certain storage classes must be restored
+ * before they can be retrieved. For more information about these storage classes and how to work with
+ * archived objects, see
+ * Working with archived objects in the Amazon S3 User Guide.
*
- *
This functionality is not supported for directory buckets.
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ *
This functionality is not supported for directory buckets. Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
Specifies whether the object is currently being restored. If the object restoration is
- * in progress, the header returns the value TRUE. For example:
+ *
Specifies whether the object is currently being restored. If the object restoration is in progress,
+ * the header returns the value TRUE. For example:
The entity tag is a hash of the object. The ETag reflects changes only to the contents
- * of an object, not its metadata. The ETag may or may not be an MD5 digest of the object
- * data. Whether or not it is depends on how the object was created and how it is encrypted as
- * described below:
- *
- *
- *
Objects created by the PUT Object, POST Object, or Copy operation, or through the
- * Amazon Web Services Management Console, and are encrypted by SSE-S3 or plaintext, have ETags that
- * are an MD5 digest of their object data.
- *
- *
- *
Objects created by the PUT Object, POST Object, or Copy operation, or through the
- * Amazon Web Services Management Console, and are encrypted by SSE-C or SSE-KMS, have ETags that are
- * not an MD5 digest of their object data.
- *
- *
- *
If an object is created by either the Multipart Upload or Part Copy operation, the
- * ETag is not an MD5 digest, regardless of the method of encryption. If an object is
- * larger than 16 MB, the Amazon Web Services Management Console will upload or copy that object as a
- * Multipart Upload, and therefore the ETag will not be an MD5 digest.
- *
- *
- *
- *
- * Directory buckets - MD5 is not supported by directory buckets.
The checksum type that is used to calculate the object’s
- * checksum value. For more information, see Checking object integrity in the Amazon S3 User Guide.
- * Directory buckets -
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
Specifies the restoration status of an object. Objects in certain storage classes must
- * be restored before they can be retrieved. For more information about these storage classes
- * and how to work with archived objects, see Working with archived
- * objects in the Amazon S3 User Guide.
- *
- *
This functionality is not supported for directory buckets.
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
When the response is truncated (the IsTruncated element value in the
- * response is true), you can use the key name in this field as the
- * marker parameter in the subsequent request to get the next set of objects.
- * Amazon S3 lists objects in alphabetical order.
- *
- *
This element is returned only if you have the delimiter request
- * parameter specified. If the response does not include the NextMarker
- * element and it is truncated, you can use the value of the last Key element
- * in the response as the marker parameter in the subsequent request to get
- * the next set of object keys.
Causes keys that contain the same string between the prefix and the first occurrence of
- * the delimiter to be rolled up into a single result element in the
- * CommonPrefixes collection. These rolled-up keys are not returned elsewhere
- * in the response. Each rolled-up result counts as only one return against the
- * MaxKeys value.
All of the keys (up to 1,000) rolled up in a common prefix count as a single return when
- * calculating the number of returns.
- *
A response can contain CommonPrefixes only if you specify a
- * delimiter.
- *
- * CommonPrefixes contains all (if there are any) keys between
- * Prefix and the next occurrence of the string specified by the
- * delimiter.
- *
- * CommonPrefixes lists keys that act like subdirectories in the directory
- * specified by Prefix.
- *
For example, if the prefix is notes/ and the delimiter is a slash
- * (/), as in notes/summer/july, the common prefix is
- * notes/summer/. All of the keys that roll up into a common prefix count as a
- * single return when calculating the number of returns.
Encoding type used by Amazon S3 to encode the object keys in the response.
- * Responses are encoded only in UTF-8. An object key can contain any Unicode character.
- * However, the XML 1.0 parser can't parse certain characters, such as characters with an
- * ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this
- * parameter to request that Amazon S3 encode the keys in the response. For more information about
- * characters to avoid in object key names, see Object key naming
- * guidelines.
- *
- *
When using the URL encoding type, non-ASCII characters that are used in an object's
- * key name will be percent-encoded according to UTF-8 code values. For example, the object
- * test_file(3).png will appear as
- * test_file%283%29.png.
- * Directory buckets -
- * When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
- * bucket-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.
- *
- * Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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.
- *
- *
Object Lambda access points are not supported by directory buckets.
- *
- *
- * S3 on Outposts - When you use this action with 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 you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
- *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
- * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
Encoding type used by Amazon S3 to encode the object keys in the response.
- * Responses are encoded only in UTF-8. An object key can contain any Unicode character.
- * However, the XML 1.0 parser can't parse certain characters, such as characters with an
- * ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this
- * parameter to request that Amazon S3 encode the keys in the response. For more information about
- * characters to avoid in object key names, see Object key naming
- * guidelines.
- *
- *
When using the URL encoding type, non-ASCII characters that are used in an object's
- * key name will be percent-encoded according to UTF-8 code values. For example, the object
- * test_file(3).png will appear as
- * test_file%283%29.png.
Sets the maximum number of keys returned in the response. By default, the action returns
- * up to 1,000 key names. The response might contain fewer keys but will never contain more.
- *
Confirms that the requester knows that she or he will be charged for the list objects
- * request. Bucket owners need not specify this parameter in their requests.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Set to false if all of the results were returned. Set to true
- * if more keys are available to return. If the number of results exceeds that specified by
- * MaxKeys, all of the results might not be returned.
Causes keys that contain the same string between the prefix and the first
- * occurrence of the delimiter to be rolled up into a single result element in the
- * CommonPrefixes collection. These rolled-up keys are not returned elsewhere
- * in the response. Each rolled-up result counts as only one return against the
- * MaxKeys value.
- *
- *
- * Directory buckets - For directory buckets, / is the only supported delimiter.
Sets the maximum number of keys returned in the response. By default, the action returns
- * up to 1,000 key names. The response might contain fewer keys but will never contain
- * more.
All of the keys (up to 1,000) that share the same prefix are grouped together. When
- * counting the total numbers of returns by this API operation, this group of keys is
- * considered as one item.
- *
A response can contain CommonPrefixes only if you specify a
- * delimiter.
- *
- * CommonPrefixes contains all (if there are any) keys between
- * Prefix and the next occurrence of the string specified by a
- * delimiter.
- *
- * CommonPrefixes lists keys that act like subdirectories in the directory
- * specified by Prefix.
- *
For example, if the prefix is notes/ and the delimiter is a slash
- * (/) as in notes/summer/july, the common prefix is
- * notes/summer/. All of the keys that roll up into a common prefix count as a
- * single return when calculating the number of returns.
- *
- *
- *
- *
- * Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
- *
- *
- *
- * Directory buckets - When you query
- * ListObjectsV2 with a delimiter during in-progress multipart
- * uploads, the CommonPrefixes response parameter contains the prefixes
- * that are associated with the in-progress multipart uploads. For more information
- * about multipart uploads, see Multipart Upload Overview in
- * the Amazon S3 User Guide.
Encoding type used by Amazon S3 to encode object key names in the XML response.
- *
If you specify the encoding-type request parameter, Amazon S3 includes this
- * element in the response, and returns encoded key name values in the following response
- * elements:
- * KeyCount is the number of keys returned with this request.
- * KeyCount will always be less than or equal to the MaxKeys
- * field. For example, if you ask for 50 keys, your result will include 50 keys or
- * fewer.
If ContinuationToken was sent with the request, it is included in the
- * response. You can use the returned ContinuationToken for pagination of the
- * list response.
- * NextContinuationToken is sent when isTruncated is true, which
- * means there are more keys in the bucket that can be listed. The next list requests to Amazon S3
- * can be continued with this NextContinuationToken.
- * NextContinuationToken is obfuscated and is not a real key
- * Directory buckets -
- * When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
- * bucket-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.
- *
- * Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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.
- *
- *
Object Lambda access points are not supported by directory buckets.
- *
- *
- * S3 on Outposts - When you use this action with 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 you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
- *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
- * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
A delimiter is a character that you use to group keys.
- *
- * CommonPrefixes is filtered out from results if it is not lexicographically greater than the StartAfter value.
- *
- *
- *
- *
- * Directory buckets - For directory buckets, / is the only supported delimiter.
- *
- *
- *
- * Directory buckets - When you query
- * ListObjectsV2 with a delimiter during in-progress multipart
- * uploads, the CommonPrefixes response parameter contains the prefixes
- * that are associated with the in-progress multipart uploads. For more information
- * about multipart uploads, see Multipart Upload Overview in
- * the Amazon S3 User Guide.
Encoding type used by Amazon S3 to encode the object keys in the response.
- * Responses are encoded only in UTF-8. An object key can contain any Unicode character.
- * However, the XML 1.0 parser can't parse certain characters, such as characters with an
- * ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this
- * parameter to request that Amazon S3 encode the keys in the response. For more information about
- * characters to avoid in object key names, see Object key naming
- * guidelines.
- *
- *
When using the URL encoding type, non-ASCII characters that are used in an object's
- * key name will be percent-encoded according to UTF-8 code values. For example, the object
- * test_file(3).png will appear as
- * test_file%283%29.png.
Sets the maximum number of keys returned in the response. By default, the action returns
- * up to 1,000 key names. The response might contain fewer keys but will never contain
- * more.
- * ContinuationToken indicates to Amazon S3 that the list is being continued on
- * this bucket with a token. ContinuationToken is obfuscated and is not a real
- * key. You can use this ContinuationToken for pagination of the list results.
- *
The owner field is not present in ListObjectsV2 by default. If you want to
- * return the owner field with each key in the result, then set the FetchOwner
- * field to true.
- *
- *
- * Directory buckets - For directory buckets,
- * the bucket owner is returned as the object owner for all objects.
StartAfter is where you want Amazon S3 to start listing from. Amazon S3 starts listing after this
- * specified key. StartAfter can be any key in the bucket.
- *
- *
This functionality is not supported for directory buckets.
Confirms that the requester knows that she or he will be charged for the list objects
- * request in V2 style. Bucket owners need not specify this parameter in their
- * requests.
- *
- *
This functionality is not supported for directory buckets.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The checksum type that is used to calculate the object’s
- * checksum value. For more information, see Checking object integrity in the Amazon S3 User Guide.
Specifies the restoration status of an object. Objects in certain storage classes must
- * be restored before they can be retrieved. For more information about these storage classes
- * and how to work with archived objects, see Working with archived
- * objects in the Amazon S3 User Guide.
A flag that indicates whether Amazon S3 returned all of the results that satisfied the search
- * criteria. If your results were truncated, you can make a follow-up paginated request by
- * using the NextKeyMarker and NextVersionIdMarker response
- * parameters as a starting place in another request to return the rest of the results.
When the number of responses exceeds the value of MaxKeys,
- * NextKeyMarker specifies the first key not returned that satisfies the
- * search criteria. Use this value for the key-marker request parameter in a subsequent
- * request.
When the number of responses exceeds the value of MaxKeys,
- * NextVersionIdMarker specifies the first object version not returned that
- * satisfies the search criteria. Use this value for the version-id-marker
- * request parameter in a subsequent request.
The delimiter grouping the included keys. A delimiter is a character that you specify to
- * group keys. All keys that contain the same string between the prefix and the first
- * occurrence of the delimiter are grouped under a single result element in
- * CommonPrefixes. These groups are counted as one result against the
- * max-keys limitation. These keys are not returned elsewhere in the
- * response.
Encoding type used by Amazon S3 to encode object key names in the XML response.
- *
If you specify the encoding-type request parameter, Amazon S3 includes this
- * element in the response, and returns encoded key name values in the following response
- * elements:
- *
- * KeyMarker, NextKeyMarker, Prefix, Key, and Delimiter.
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
- * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
A delimiter is a character that you specify to group keys. All keys that contain the
- * same string between the prefix and the first occurrence of the delimiter are
- * grouped under a single result element in CommonPrefixes. These groups are
- * counted as one result against the max-keys limitation. These keys are not
- * returned elsewhere in the response.
- *
- * CommonPrefixes is filtered out from results if it is not lexicographically greater than the key-marker.
Encoding type used by Amazon S3 to encode the object keys in the response.
- * Responses are encoded only in UTF-8. An object key can contain any Unicode character.
- * However, the XML 1.0 parser can't parse certain characters, such as characters with an
- * ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this
- * parameter to request that Amazon S3 encode the keys in the response. For more information about
- * characters to avoid in object key names, see Object key naming
- * guidelines.
- *
- *
When using the URL encoding type, non-ASCII characters that are used in an object's
- * key name will be percent-encoded according to UTF-8 code values. For example, the object
- * test_file(3).png will appear as
- * test_file%283%29.png.
Sets the maximum number of keys returned in the response. By default, the action returns
- * up to 1,000 key names. The response might contain fewer keys but will never contain more.
- * If additional keys satisfy the search criteria, but were not returned because
- * max-keys was exceeded, the response contains
- * true. To return the additional keys,
- * see key-marker and version-id-marker.
Use this parameter to select only those keys that begin with the specified prefix. You
- * can use prefixes to separate a bucket into different groupings of keys. (You can think of
- * using prefix to make groups in the same way that you'd use a folder in a file
- * system.) You can use prefix with delimiter to roll up numerous
- * objects into a single result under CommonPrefixes.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
- *
- *
This functionality is not supported for directory buckets.
The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present
- * if the object was uploaded with the CRC32 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present
- * if the object was uploaded with the CRC32C checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present
- * if the multipart upload request was created with the CRC64NVME checksum algorithm, or if the object was uploaded without a
- * checksum (and Amazon S3 added the default checksum, CRC64NVME, to the uploaded object). For more information, see Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present
- * if the object was uploaded with the SHA1 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present
- * if the object was uploaded with the SHA256 checksum algorithm. For more information, see Checking object integrity in the Amazon S3 User Guide.
If the bucket has a lifecycle rule configured with an action to abort incomplete
- * multipart uploads and the prefix in the lifecycle rule matches the object name in the
- * request, then the response includes this header indicating when the initiated multipart
- * upload will become eligible for abort operation. For more information, see Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle
- * Configuration.
- *
The response will also include the x-amz-abort-rule-id header that will
- * provide the ID of the lifecycle configuration rule that defines this action.
- *
- *
This functionality is not supported for directory buckets.
This header is returned along with the x-amz-abort-date header. It
- * identifies applicable lifecycle configuration rule that defines the action to abort
- * incomplete multipart uploads.
- *
- *
This functionality is not supported for directory buckets.
When a list is truncated, this element specifies the last part in the list, as well as
- * the value to use for the part-number-marker request parameter in a subsequent
- * request.
Indicates whether the returned list of parts is truncated. A true value indicates that
- * the list was truncated. A list can be truncated if the number of parts exceeds the limit
- * returned in the MaxParts element.
Container element that identifies who initiated the multipart upload. If the initiator
- * is an Amazon Web Services account, this element provides the same information as the Owner
- * element. If the initiator is an IAM User, this element provides the user ARN and display
- * name.
Container element that identifies the object owner, after the object is created. If
- * multipart upload is initiated by an IAM user, this element provides the parent account ID
- * and display name.
- *
- *
- * Directory buckets - The bucket owner is
- * returned as the object owner for all the parts.
The class of storage used to store the uploaded object.
- *
- *
- * Directory buckets -
- * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
The checksum type, which determines how part-level checksums are combined to create an
- * object-level checksum for multipart objects. You can use this header response to verify
- * that the checksum type that is received is the same checksum type that was specified in
- * CreateMultipartUpload request. For more
- * information, see Checking object integrity
- * in the Amazon S3 User Guide.
The name of the bucket to which the parts are being uploaded.
- *
- * Directory buckets -
- * When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
- * bucket-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.
- *
- * Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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.
- *
- *
Object Lambda access points are not supported by directory buckets.
- *
- *
- * S3 on Outposts - When you use this action with 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 you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
- *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
- * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
- *
- *
This functionality is not supported for directory buckets.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is needed only when the object was created
- * using a checksum algorithm. For more information,
- * see Protecting data using SSE-C keys in the
- * Amazon S3 User Guide.
- *
- *
This functionality is not supported for directory buckets.
The server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum algorithm.
- * For more information, see
- * Protecting data using SSE-C keys in the
- * Amazon S3 User Guide.
- *
- *
This functionality is not supported for directory buckets.
The MD5 server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum
- * algorithm. For more information,
- * see Protecting data using SSE-C keys in the
- * Amazon S3 User Guide.
- *
- *
This functionality is not supported for directory buckets.
The name of the bucket for which the accelerate configuration is set.
- *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
- * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any
- * additional functionality if you don't use the SDK. When you send 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.
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
- * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a message
- * integrity check to verify that the request body was not corrupted in transit. For more
- * information, go to RFC
- * 1864.
- *
- *
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any
- * additional functionality if you don't use the SDK. When you send 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.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The name of the bucket to which an analytics configuration is stored.
- *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
- * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more
- * information, see Enabling
- * Cross-Origin Resource Sharing in the
- * Amazon S3 User Guide.
The entity tag is a hash of the object. The ETag reflects changes only to the contents of an object,
+ * not its metadata. The ETag may or may not be an MD5 digest of the object data. Whether or not it is
+ * depends on how the object was created and how it is encrypted as described below:
+ *
+ *
+ *
Objects created by the PUT Object, POST Object, or Copy operation, or through the Amazon Web Services
+ * Management Console, and are encrypted by SSE-S3 or plaintext, have ETags that are an MD5 digest of
+ * their object data.
+ *
+ *
+ *
Objects created by the PUT Object, POST Object, or Copy operation, or through the Amazon Web Services
+ * Management Console, and are encrypted by SSE-C or SSE-KMS, have ETags that are not an MD5 digest of
+ * their object data.
+ *
+ *
+ *
If an object is created by either the Multipart Upload or Part Copy operation, the ETag is not
+ * an MD5 digest, regardless of the method of encryption. If an object is larger than 16 MB, the Amazon Web Services
+ * Management Console will upload or copy that object as a Multipart Upload, and therefore the ETag
+ * will not be an MD5 digest.
+ *
+ *
+ *
+ *
+ * Directory buckets - MD5 is not supported by directory buckets.
The checksum type that is used to calculate the object’s checksum value. For more information, see
+ * Checking
+ * object integrity in the Amazon S3 User Guide.
+ * Directory buckets -
+ * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
Specifies the restoration status of an object. Objects in certain storage classes must be restored
+ * before they can be retrieved. For more information about these storage classes and how to work with
+ * archived objects, see
+ * Working with archived objects in the Amazon S3 User Guide.
+ *
+ *
This functionality is not supported for directory buckets. Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
When the response is truncated (the IsTruncated element value in the response is
+ * true), you can use the key name in this field as the marker parameter in the
+ * subsequent request to get the next set of objects. Amazon S3 lists objects in alphabetical order.
+ *
+ *
This element is returned only if you have the delimiter request parameter specified.
+ * If the response does not include the NextMarker element and it is truncated, you can use
+ * the value of the last Key element in the response as the marker parameter in
+ * the subsequent request to get the next set of object keys.
Causes keys that contain the same string between the prefix and the first occurrence of the
+ * delimiter to be rolled up into a single result element in the CommonPrefixes collection.
+ * These rolled-up keys are not returned elsewhere in the response. Each rolled-up result counts as only
+ * one return against the MaxKeys value.
All of the keys (up to 1,000) rolled up in a common prefix count as a single return when calculating
+ * the number of returns.
+ *
A response can contain CommonPrefixes only if you specify a delimiter.
+ *
+ * CommonPrefixes contains all (if there are any) keys between Prefix and the
+ * next occurrence of the string specified by the delimiter.
+ *
+ * CommonPrefixes lists keys that act like subdirectories in the directory specified by
+ * Prefix.
+ *
For example, if the prefix is notes/ and the delimiter is a slash (/), as
+ * in notes/summer/july, the common prefix is notes/summer/. All of the keys that
+ * roll up into a common prefix count as a single return when calculating the number of returns.
Encoding type used by Amazon S3 to encode the object keys in the response. Responses are
+ * encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser
+ * can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that
+ * aren't supported in XML 1.0, you can add this parameter to request that Amazon S3 encode the keys in the
+ * response. For more information about characters to avoid in object key names, see Object key
+ * naming guidelines.
+ *
+ *
When using the URL encoding type, non-ASCII characters that are used in an object's key name will
+ * be percent-encoded according to UTF-8 code values. For example, the object
+ * test_file(3).png will appear as test_file%283%29.png.
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
+ * bucket-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.
+ *
+ * Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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.
+ *
+ *
Object Lambda access points are not supported by directory buckets.
+ *
+ *
+ * S3 on Outposts - When you use this action with 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 you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
+ *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
Encoding type used by Amazon S3 to encode the object keys in the response. Responses are
+ * encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser
+ * can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that
+ * aren't supported in XML 1.0, you can add this parameter to request that Amazon S3 encode the keys in the
+ * response. For more information about characters to avoid in object key names, see Object key
+ * naming guidelines.
+ *
+ *
When using the URL encoding type, non-ASCII characters that are used in an object's key name will
+ * be percent-encoded according to UTF-8 code values. For example, the object
+ * test_file(3).png will appear as test_file%283%29.png.
Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000
+ * key names. The response might contain fewer keys but will never contain more.
Confirms that the requester knows that she or he will be charged for the list objects request.
+ * Bucket owners need not specify this parameter in their requests.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Set to false if all of the results were returned. Set to true if more keys
+ * are available to return. If the number of results exceeds that specified by MaxKeys, all of
+ * the results might not be returned.
Causes keys that contain the same string between the prefix and the first occurrence of
+ * the delimiter to be rolled up into a single result element in the CommonPrefixes
+ * collection. These rolled-up keys are not returned elsewhere in the response. Each rolled-up result
+ * counts as only one return against the MaxKeys value.
+ *
+ *
+ * Directory buckets - For directory buckets, / is the only supported delimiter.
Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000
+ * key names. The response might contain fewer keys but will never contain more.
All of the keys (up to 1,000) that share the same prefix are grouped together. When counting the
+ * total numbers of returns by this API operation, this group of keys is considered as one item.
+ *
A response can contain CommonPrefixes only if you specify a delimiter.
+ *
+ * CommonPrefixes contains all (if there are any) keys between Prefix and the
+ * next occurrence of the string specified by a delimiter.
+ *
+ * CommonPrefixes lists keys that act like subdirectories in the directory specified by
+ * Prefix.
+ *
For example, if the prefix is notes/ and the delimiter is a slash (/) as
+ * in notes/summer/july, the common prefix is notes/summer/. All of the keys that
+ * roll up into a common prefix count as a single return when calculating the number of returns.
+ *
+ *
+ *
+ *
+ * Directory buckets - For directory buckets, only prefixes that end in a delimiter (/) are supported.
+ *
+ *
+ *
+ * Directory buckets - When you query
+ * ListObjectsV2 with a delimiter during in-progress multipart uploads, the
+ * CommonPrefixes response parameter contains the prefixes that are associated with
+ * the in-progress multipart uploads. For more information about multipart uploads, see Multipart Upload
+ * Overview in the Amazon S3 User Guide.
Encoding type used by Amazon S3 to encode object key names in the XML response.
+ *
If you specify the encoding-type request parameter, Amazon S3 includes this element in the
+ * response, and returns encoded key name values in the following response elements:
+ * KeyCount is the number of keys returned with this request. KeyCount will
+ * always be less than or equal to the MaxKeys field. For example, if you ask for 50 keys,
+ * your result will include 50 keys or fewer.
If ContinuationToken was sent with the request, it is included in the response. You
+ * can use the returned ContinuationToken for pagination of the list response.
+ * NextContinuationToken is sent when isTruncated is true, which means there
+ * are more keys in the bucket that can be listed. The next list requests to Amazon S3 can be continued with
+ * this NextContinuationToken. NextContinuationToken is obfuscated and is not a
+ * real key
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
+ * bucket-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.
+ *
+ * Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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.
+ *
+ *
Object Lambda access points are not supported by directory buckets.
+ *
+ *
+ * S3 on Outposts - When you use this action with 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 you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
+ *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
A delimiter is a character that you use to group keys.
+ *
+ * CommonPrefixes is filtered out from results if it is not lexicographically greater than
+ * the StartAfter value.
+ *
+ *
+ *
+ *
+ * Directory buckets - For directory buckets, / is the only supported delimiter.
+ *
+ *
+ *
+ * Directory buckets - When you query
+ * ListObjectsV2 with a delimiter during in-progress multipart uploads, the
+ * CommonPrefixes response parameter contains the prefixes that are associated with
+ * the in-progress multipart uploads. For more information about multipart uploads, see Multipart Upload
+ * Overview in the Amazon S3 User Guide.
Encoding type used by Amazon S3 to encode the object keys in the response. Responses are
+ * encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser
+ * can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that
+ * aren't supported in XML 1.0, you can add this parameter to request that Amazon S3 encode the keys in the
+ * response. For more information about characters to avoid in object key names, see Object key
+ * naming guidelines.
+ *
+ *
When using the URL encoding type, non-ASCII characters that are used in an object's key name will
+ * be percent-encoded according to UTF-8 code values. For example, the object
+ * test_file(3).png will appear as test_file%283%29.png.
Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000
+ * key names. The response might contain fewer keys but will never contain more.
+ * ContinuationToken indicates to Amazon S3 that the list is being continued on this bucket
+ * with a token. ContinuationToken is obfuscated and is not a real key. You can use this
+ * ContinuationToken for pagination of the list results.
The owner field is not present in ListObjectsV2 by default. If you want to return the
+ * owner field with each key in the result, then set the FetchOwner field to
+ * true.
+ *
+ *
+ * Directory buckets - For directory buckets, the bucket
+ * owner is returned as the object owner for all objects.
StartAfter is where you want Amazon S3 to start listing from. Amazon S3 starts listing after this specified
+ * key. StartAfter can be any key in the bucket.
+ *
+ *
This functionality is not supported for directory buckets.
Confirms that the requester knows that she or he will be charged for the list objects request in V2
+ * style. Bucket owners need not specify this parameter in their requests.
+ *
+ *
This functionality is not supported for directory buckets.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The checksum type that is used to calculate the object’s checksum value. For more information, see
+ * Checking
+ * object integrity in the Amazon S3 User Guide.
Specifies the restoration status of an object. Objects in certain storage classes must be restored
+ * before they can be retrieved. For more information about these storage classes and how to work with
+ * archived objects, see
+ * Working with archived objects in the Amazon S3 User Guide.
A flag that indicates whether Amazon S3 returned all of the results that satisfied the search criteria.
+ * If your results were truncated, you can make a follow-up paginated request by using the
+ * NextKeyMarker and NextVersionIdMarker response parameters as a starting
+ * place in another request to return the rest of the results.
When the number of responses exceeds the value of MaxKeys, NextKeyMarker
+ * specifies the first key not returned that satisfies the search criteria. Use this value for the
+ * key-marker request parameter in a subsequent request.
When the number of responses exceeds the value of MaxKeys,
+ * NextVersionIdMarker specifies the first object version not returned that satisfies the
+ * search criteria. Use this value for the version-id-marker request parameter in a subsequent
+ * request.
The delimiter grouping the included keys. A delimiter is a character that you specify to group keys.
+ * All keys that contain the same string between the prefix and the first occurrence of the delimiter are
+ * grouped under a single result element in CommonPrefixes. These groups are counted as one
+ * result against the max-keys limitation. These keys are not returned elsewhere in the
+ * response.
Encoding type used by Amazon S3 to encode object key names in the XML response.
+ *
If you specify the encoding-type request parameter, Amazon S3 includes this element in the
+ * response, and returns encoded key name values in the following response elements:
+ *
+ * KeyMarker, NextKeyMarker, Prefix, Key, and Delimiter.
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
A delimiter is a character that you specify to group keys. All keys that contain the same string
+ * between the prefix and the first occurrence of the delimiter are grouped under a single
+ * result element in CommonPrefixes. These groups are counted as one result against the
+ * max-keys limitation. These keys are not returned elsewhere in the response.
+ *
+ * CommonPrefixes is filtered out from results if it is not lexicographically greater than
+ * the key-marker.
Encoding type used by Amazon S3 to encode the object keys in the response. Responses are
+ * encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser
+ * can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that
+ * aren't supported in XML 1.0, you can add this parameter to request that Amazon S3 encode the keys in the
+ * response. For more information about characters to avoid in object key names, see Object key
+ * naming guidelines.
+ *
+ *
When using the URL encoding type, non-ASCII characters that are used in an object's key name will
+ * be percent-encoded according to UTF-8 code values. For example, the object
+ * test_file(3).png will appear as test_file%283%29.png.
Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000
+ * key names. The response might contain fewer keys but will never contain more. If additional keys satisfy
+ * the search criteria, but were not returned because max-keys was exceeded, the response
+ * contains true. To return the additional keys, see
+ * key-marker and version-id-marker.
Use this parameter to select only those keys that begin with the specified prefix. You can use
+ * prefixes to separate a bucket into different groupings of keys. (You can think of using
+ * prefix to make groups in the same way that you'd use a folder in a file system.) You can
+ * use prefix with delimiter to roll up numerous objects into a single result
+ * under CommonPrefixes.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
+ *
+ *
This functionality is not supported for directory buckets.
The Base64 encoded, 32-bit CRC32 checksum of the part. This checksum is present if the
+ * object was uploaded with the CRC32 checksum algorithm. For more information, see Checking object
+ * integrity in the Amazon S3 User Guide.
The Base64 encoded, 32-bit CRC32C checksum of the part. This checksum is present if the
+ * object was uploaded with the CRC32C checksum algorithm. For more information, see Checking object
+ * integrity in the Amazon S3 User Guide.
The Base64 encoded, 64-bit CRC64NVME checksum of the part. This checksum is present if
+ * the multipart upload request was created with the CRC64NVME checksum algorithm, or if the
+ * object was uploaded without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to
+ * the uploaded object). For more information, see Checking object integrity in
+ * the Amazon S3 User Guide.
The Base64 encoded, 160-bit SHA1 checksum of the part. This checksum is present if the
+ * object was uploaded with the SHA1 checksum algorithm. For more information, see Checking object
+ * integrity in the Amazon S3 User Guide.
The Base64 encoded, 256-bit SHA256 checksum of the part. This checksum is present if
+ * the object was uploaded with the SHA256 checksum algorithm. For more information, see
+ * Checking
+ * object integrity in the Amazon S3 User Guide.
If the bucket has a lifecycle rule configured with an action to abort incomplete multipart uploads
+ * and the prefix in the lifecycle rule matches the object name in the request, then the response includes
+ * this header indicating when the initiated multipart upload will become eligible for abort operation. For
+ * more information, see Aborting
+ * Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration.
+ *
The response will also include the x-amz-abort-rule-id header that will provide the ID
+ * of the lifecycle configuration rule that defines this action.
+ *
+ *
This functionality is not supported for directory buckets.
This header is returned along with the x-amz-abort-date header. It identifies
+ * applicable lifecycle configuration rule that defines the action to abort incomplete multipart
+ * uploads.
+ *
+ *
This functionality is not supported for directory buckets.
When a list is truncated, this element specifies the last part in the list, as well as the value to
+ * use for the part-number-marker request parameter in a subsequent request.
Indicates whether the returned list of parts is truncated. A true value indicates that the list was
+ * truncated. A list can be truncated if the number of parts exceeds the limit returned in the MaxParts
+ * element.
Container element that identifies who initiated the multipart upload. If the initiator is an
+ * Amazon Web Services account, this element provides the same information as the Owner element. If the
+ * initiator is an IAM User, this element provides the user ARN and display name.
Container element that identifies the object owner, after the object is created. If multipart upload
+ * is initiated by an IAM user, this element provides the parent account ID and display name.
+ *
+ *
+ * Directory buckets - The bucket owner is returned as the
+ * object owner for all the parts.
The class of storage used to store the uploaded object.
+ *
+ *
+ * Directory buckets -
+ * Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
The checksum type, which determines how part-level checksums are combined to create an object-level
+ * checksum for multipart objects. You can use this header response to verify that the checksum type that
+ * is received is the same checksum type that was specified in CreateMultipartUpload request.
+ * For more information, see Checking object integrity in the Amazon S3
+ * User Guide.
The name of the bucket to which the parts are being uploaded.
+ *
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
+ * bucket-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.
+ *
+ * Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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.
+ *
+ *
Object Lambda access points are not supported by directory buckets.
+ *
+ *
+ * S3 on Outposts - When you use this action with 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 you use this action with S3 on Outposts, the destination bucket must be the Outposts access point ARN or the access point alias. For more information about S3 on Outposts, see What is S3 on Outposts? in the Amazon S3 User Guide.
+ *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
+ *
+ *
This functionality is not supported for directory buckets.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is needed only when the object was created
+ * using a checksum algorithm. For more information,
+ * see Protecting data using SSE-C keys in the
+ * Amazon S3 User Guide.
+ *
+ *
This functionality is not supported for directory buckets.
The server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum algorithm.
+ * For more information, see
+ * Protecting data using SSE-C keys in the
+ * Amazon S3 User Guide.
+ *
+ *
This functionality is not supported for directory buckets.
The MD5 server-side encryption (SSE) customer managed key. This parameter is needed only when the object was created using a checksum
+ * algorithm. For more information,
+ * see Protecting data using SSE-C keys in the
+ * Amazon S3 User Guide.
+ *
+ *
This functionality is not supported for directory buckets.
The name of the bucket for which the accelerate configuration is set.
+ *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any
+ * additional functionality if you don't use the SDK. When you send 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.
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a
+ * message integrity check to verify that the request body was not corrupted in transit. For more
+ * information, go to RFC 1864.
+ *
+ *
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
Indicates the algorithm used to create the checksum for the request when you use the SDK. This header will not provide any
+ * additional functionality if you don't use the SDK. When you send 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.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
The name of the bucket to which an analytics configuration is stored.
+ *
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
+ * For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information,
+ * see Enabling Cross-Origin Resource
+ * Sharing in the Amazon S3 User Guide.
Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more
- * information, see Enabling
- * Cross-Origin Resource Sharing in the
- * Amazon S3 User Guide.
+ *
Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information,
+ * see Enabling Cross-Origin Resource
+ * Sharing in the Amazon S3 User Guide.
The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a message
- * integrity check to verify that the request body was not corrupted in transit. For more
- * information, go to RFC
- * 1864.
+ *
The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a
+ * message integrity check to verify that the request body was not corrupted in transit. For more
+ * information, go to RFC 1864.
*
*
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
* @public
@@ -52,8 +1342,8 @@ export interface PutBucketCorsRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
Specifies default encryption for a bucket using server-side encryption with different
- * key options.
+ *
Specifies default encryption for a bucket using server-side encryption with different key
+ * options.
*
* Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format https://s3express-control.region-code.amazonaws.com/bucket-name
* . Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the format
@@ -83,7 +1373,7 @@ export interface PutBucketEncryptionRequest {
Bucket: string | undefined;
/**
*
The Base64 encoded 128-bit MD5 digest of the server-side encryption
- * configuration.
+ * configuration.
*
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
*
*
This functionality is not supported for directory buckets.
@@ -97,8 +1387,8 @@ export interface PutBucketEncryptionRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
*
*
For directory buckets, when you use Amazon Web Services SDKs, CRC32 is the default checksum algorithm that's used for performance.
Indicates which default minimum object size behavior is applied to the lifecycle
- * configuration.
+ * configuration.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
*
*
*
*
- * all_storage_classes_128K - Objects smaller than 128 KB will not
- * transition to any storage class by default.
+ * all_storage_classes_128K - Objects smaller than 128 KB will not transition to
+ * any storage class by default.
*
*
*
- * varies_by_storage_class - Objects smaller than 128 KB will
- * transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By
- * default, all other storage classes will prevent transitions smaller than 128 KB.
- *
+ * varies_by_storage_class - Objects smaller than 128 KB will transition to Glacier
+ * Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes
+ * will prevent transitions smaller than 128 KB.
*
*
- *
To customize the minimum object size for any transition you can add a filter that
- * specifies a custom ObjectSizeGreaterThan or ObjectSizeLessThan in
- * the body of your transition rule. Custom filters always take precedence over the default
- * transition behavior.
+ *
To customize the minimum object size for any transition you can add a filter that specifies a custom
+ * ObjectSizeGreaterThan or ObjectSizeLessThan in the body of your transition
+ * rule. Custom filters always take precedence over the default transition behavior.
Specifies the lifecycle configuration for objects in an Amazon S3 bucket. For more
- * information, see Object Lifecycle Management
- * in the Amazon S3 User Guide.
+ *
Specifies the lifecycle configuration for objects in an Amazon S3 bucket. For more information, see
+ * Object Lifecycle
+ * Management in the Amazon S3 User Guide.
* @public
*/
export interface BucketLifecycleConfiguration {
@@ -237,8 +1525,8 @@ export interface PutBucketLifecycleConfigurationRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied).
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
Indicates which default minimum object size behavior is applied to the lifecycle
- * configuration.
+ * configuration.
*
- *
This parameter applies to general purpose buckets only. It is not supported for
- * directory bucket lifecycle configurations.
+ *
This parameter applies to general purpose buckets only. It is not supported for directory bucket
+ * lifecycle configurations.
*
*
*
*
- * all_storage_classes_128K - Objects smaller than 128 KB will not
- * transition to any storage class by default.
+ * all_storage_classes_128K - Objects smaller than 128 KB will not transition to
+ * any storage class by default.
*
*
*
- * varies_by_storage_class - Objects smaller than 128 KB will
- * transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By
- * default, all other storage classes will prevent transitions smaller than 128 KB.
- *
+ * varies_by_storage_class - Objects smaller than 128 KB will transition to Glacier
+ * Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes
+ * will prevent transitions smaller than 128 KB.
*
*
- *
To customize the minimum object size for any transition you can add a filter that
- * specifies a custom ObjectSizeGreaterThan or ObjectSizeLessThan in
- * the body of your transition rule. Custom filters always take precedence over the default
- * transition behavior.
+ *
To customize the minimum object size for any transition you can add a filter that specifies a custom
+ * ObjectSizeGreaterThan or ObjectSizeLessThan in the body of your transition
+ * rule. Custom filters always take precedence over the default transition behavior.
Describes where logs are stored and the prefix that Amazon S3 assigns to all log object keys
- * for a bucket. For more information, see PUT Bucket logging in the
- * Amazon S3 API Reference.
+ *
Describes where logs are stored and the prefix that Amazon S3 assigns to all log object keys for a
+ * bucket. For more information, see PUT Bucket logging in the
+ * Amazon S3 API Reference.
* @public
*/
LoggingEnabled?: LoggingEnabled | undefined;
@@ -326,8 +1612,8 @@ export interface PutBucketLoggingRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
The ID used to identify the metrics configuration. The ID has a 64 character limit and
- * can only contain letters, numbers, periods, dashes, and underscores.
+ *
The ID used to identify the metrics configuration. The ID has a 64 character limit and can only
+ * contain letters, numbers, periods, dashes, and underscores.
Indicates the algorithm used to create the checksum for the object when you use the
- * SDK. This header will not provide any additional functionality if you don't use the
- * SDK. When you send this header, there must be a corresponding
- * x-amz-checksum-algorithm
- * 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.
+ *
Indicates the algorithm used to create the checksum for the object when you use the SDK. This
+ * header will not provide any additional functionality if you don't use the SDK. When you send this
+ * header, there must be a corresponding x-amz-checksum-algorithm
+ * 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.
The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a message
- * integrity check to verify that the request body was not corrupted in transit. For more
- * information, see RFC 1864.
+ *
The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a
+ * message integrity check to verify that the request body was not corrupted in transit. For more
+ * information, see RFC 1864.
*
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
* @public
*/
@@ -559,14 +1846,14 @@ export interface PutBucketReplicationRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a message
- * integrity check to verify that the request body was not corrupted in transit. For more
- * information, see RFC 1864.
+ *
The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a
+ * message integrity check to verify that the request body was not corrupted in transit. For more
+ * information, see RFC 1864.
*
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
* @public
*/
@@ -617,8 +1904,8 @@ export interface PutBucketRequestPaymentRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a message
- * integrity check to verify that the request body was not corrupted in transit. For more
- * information, see RFC 1864.
+ *
The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a
+ * message integrity check to verify that the request body was not corrupted in transit. For more
+ * information, see RFC 1864.
*
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
* @public
*/
@@ -669,8 +1956,8 @@ export interface PutBucketTaggingRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
Specifies whether MFA delete is enabled in the bucket versioning configuration. This
- * element is only returned if the bucket has been configured with MFA delete. If the bucket
- * has never been so configured, this element is not returned.
+ *
Specifies whether MFA delete is enabled in the bucket versioning configuration. This element is only
+ * returned if the bucket has been configured with MFA delete. If the bucket has never been so configured,
+ * this element is not returned.
>The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a
- * message integrity check to verify that the request body was not corrupted in transit. For
- * more information, see RFC
- * 1864.
+ * message integrity check to verify that the request body was not corrupted in transit. For more
+ * information, see RFC 1864.
*
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
* @public
*/
@@ -742,14 +2028,14 @@ export interface PutBucketVersioningRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a message
- * integrity check to verify that the request body was not corrupted in transit. For more
- * information, see RFC 1864.
+ *
The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a
+ * message integrity check to verify that the request body was not corrupted in transit. For more
+ * information, see RFC 1864.
*
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
* @public
*/
@@ -818,8 +2104,8 @@ export interface PutBucketWebsiteRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
- * The existing object was created with a different encryption type.
- * Subsequent write requests must include the appropriate encryption
- * parameters in the request or while creating the session.
- *
+ *
The existing object was created with a different encryption type. Subsequent write requests must
+ * include the appropriate encryption parameters in the request or while creating the session.
If the expiration is configured for the object (see PutBucketLifecycleConfiguration) in the Amazon S3 User Guide,
- * the response includes this header. It includes the expiry-date and
- * rule-id key-value pairs that provide information about object expiration.
- * The value of the rule-id is URL-encoded.
+ *
If the expiration is configured for the object (see PutBucketLifecycleConfiguration) in the Amazon S3 User Guide, the response
+ * includes this header. It includes the expiry-date and rule-id key-value pairs
+ * that provide information about object expiration. The value of the rule-id is
+ * URL-encoded.
*
- *
Object expiration information is not returned in directory buckets and this header returns the value "NotImplemented" in all responses for directory buckets.
+ *
Object expiration information is not returned in directory buckets and this header returns the
+ * value "NotImplemented" in all responses for directory buckets.
- * General purpose buckets - To ensure that data is not
- * corrupted traversing the network, for objects where the ETag is the MD5 digest of the
- * object, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned
- * ETag to the calculated MD5 value.
+ * General purpose buckets - To ensure that data is not corrupted
+ * traversing the network, for objects where the ETag is the MD5 digest of the object, you can calculate
+ * the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5
+ * value.
*
- * Directory buckets - The ETag for the object in
- * a directory bucket isn't the MD5 digest of the object.
+ * Directory buckets - The ETag for the object in a
+ * directory bucket isn't the MD5 digest of the object.
* @public
*/
ETag?: string | undefined;
@@ -932,12 +2217,11 @@ export interface PutObjectOutput {
*/
ChecksumCRC32C?: string | undefined;
/**
- *
The Base64 encoded, 64-bit CRC64NVME checksum of the object. This header
- * is present if the object was uploaded with the CRC64NVME checksum algorithm, or if it
- * was uploaded without a checksum (and Amazon S3 added the default checksum,
- * CRC64NVME, to the uploaded object). For more information about how
- * checksums are calculated with multipart uploads, see Checking object integrity
- * in the Amazon S3 User Guide.
+ *
The Base64 encoded, 64-bit CRC64NVME checksum of the object. This header is present if
+ * the object was uploaded with the CRC64NVME checksum algorithm, or if it was uploaded
+ * without a checksum (and Amazon S3 added the default checksum, CRC64NVME, to the uploaded
+ * object). For more information about how checksums are calculated with multipart uploads, see Checking object
+ * integrity in the Amazon S3 User Guide.
This header specifies the checksum type of the object, which determines how part-level
- * checksums are combined to create an object-level checksum for multipart objects. For
- * PutObject uploads, the checksum type is always FULL_OBJECT. You can use this header as a
- * data integrity check to verify that the checksum type that is received is the same checksum
- * that was specified. For more information, see Checking object integrity in the Amazon S3 User Guide.
+ *
This header specifies the checksum type of the object, which determines how part-level checksums are
+ * combined to create an object-level checksum for multipart objects. For PutObject uploads,
+ * the checksum type is always FULL_OBJECT. You can use this header as a data integrity check
+ * to verify that the checksum type that is received is the same checksum that was specified. For more
+ * information, see Checking object integrity in
+ * the Amazon S3 User Guide.
If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID
- * for the object being stored. Amazon S3 returns this ID in the response. When you enable
- * versioning for a bucket, if Amazon S3 receives multiple write requests for the same object
- * simultaneously, it stores all of the objects. For more information about versioning, see
- * Adding Objects to
- * Versioning-Enabled Buckets in the Amazon S3 User Guide. For
- * information about returning the versioning state of a bucket, see GetBucketVersioning.
+ *
If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID for the
+ * object being stored. Amazon S3 returns this ID in the response. When you enable versioning for a bucket, if
+ * Amazon S3 receives multiple write requests for the same object simultaneously, it stores all of the objects.
+ * For more information about versioning, see Adding Objects to
+ * Versioning-Enabled Buckets in the Amazon S3 User Guide. For information about
+ * returning the versioning state of a bucket, see GetBucketVersioning.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to confirm the encryption algorithm that's used.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to confirm the encryption algorithm that's used.
*
*
This functionality is not supported for directory buckets.
If server-side encryption with a customer-provided encryption key was requested, the
- * response will include this header to provide the round-trip message integrity verification
- * of the customer-provided encryption key.
+ *
If server-side encryption with a customer-provided encryption key was requested, the response will
+ * include this header to provide the round-trip message integrity verification of the customer-provided
+ * encryption key.
*
*
This functionality is not supported for directory buckets.
The canned ACL to apply to the object. For more information, see Canned
- * ACL in the Amazon S3 User Guide.
- *
When adding a new object, you can use headers to grant ACL-based permissions to
- * individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are
- * then added to the ACL on the object. By default, all objects are private. Only the owner
- * has full access control. For more information, see Access Control List (ACL) Overview
- * and Managing
- * ACLs Using the REST API in the Amazon S3 User Guide.
- *
If the bucket that you're uploading objects to uses the bucket owner enforced setting
- * for S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that
- * use this setting only accept PUT requests that don't specify an ACL or PUT requests that
- * specify bucket owner full control ACLs, such as the bucket-owner-full-control
- * canned ACL or an equivalent form of this ACL expressed in the XML format. PUT requests that
- * contain other ACLs (for example, custom grants to certain Amazon Web Services accounts) fail and return a
- * 400 error with the error code AccessControlListNotSupported.
- * For more information, see Controlling ownership of
- * objects and disabling ACLs in the Amazon S3 User Guide.
+ *
The canned ACL to apply to the object. For more information, see Canned ACL in the
+ * Amazon S3 User Guide.
+ *
When adding a new object, you can use headers to grant ACL-based permissions to individual
+ * Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then added to the ACL on
+ * the object. By default, all objects are private. Only the owner has full access control. For more
+ * information, see Access Control
+ * List (ACL) Overview and Managing ACLs Using the REST API in the
+ * Amazon S3 User Guide.
+ *
If the bucket that you're uploading objects to uses the bucket owner enforced setting for S3 Object
+ * Ownership, ACLs are disabled and no longer affect permissions. Buckets that use this setting only accept
+ * PUT requests that don't specify an ACL or PUT requests that specify bucket owner full control ACLs, such
+ * as the bucket-owner-full-control canned ACL or an equivalent form of this ACL expressed in
+ * the XML format. PUT requests that contain other ACLs (for example, custom grants to certain
+ * Amazon Web Services accounts) fail and return a 400 error with the error code
+ * AccessControlListNotSupported. For more information, see Controlling ownership of objects and
+ * disabling ACLs in the Amazon S3 User Guide.
The bucket name to which the PUT action was initiated.
*
- * Directory buckets -
- * When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format
+ * Directory buckets - When you use this operation with a directory bucket, 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 Zone (Availability Zone or Local Zone). Bucket names must follow the format
* bucket-base-name--zone-id--x-s3 (for example,
* amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming
@@ -1113,8 +2396,8 @@ export interface PutObjectRequest {
*/
Bucket: string | undefined;
/**
- *
Specifies what content encodings have been applied to the object and thus what decoding
- * mechanisms must be applied to obtain the media-type referenced by the Content-Type header
- * field. For more information, see https://www.rfc-editor.org/rfc/rfc9110.html#field.content-encoding.
+ *
Specifies what content encodings have been applied to the object and thus what decoding mechanisms
+ * must be applied to obtain the media-type referenced by the Content-Type header field. For more
+ * information, see https://www.rfc-editor.org/rfc/rfc9110.html#field.content-encoding.
* @public
*/
ContentLength?: number | undefined;
/**
*
The Base64 encoded 128-bit MD5 digest of the message (without the headers) according to
- * RFC 1864. This header can be used as a message integrity check to verify that the data is
- * the same data that was originally sent. Although it is optional, we recommend using the
- * Content-MD5 mechanism as an end-to-end integrity check. For more information about REST
- * request authentication, see REST Authentication.
+ * RFC 1864. This header can be used as a message integrity check to verify that the data is the same data
+ * that was originally sent. Although it is optional, we recommend using the Content-MD5 mechanism as an
+ * end-to-end integrity check. For more information about REST request authentication, see REST
+ * Authentication.
*
- *
The Content-MD5 or x-amz-sdk-checksum-algorithm header is
- * required for any request to upload an object with a retention period configured using
- * Amazon S3 Object Lock. For more information, see Uploading objects to an Object Lock enabled bucket in the
- * Amazon S3 User Guide.
+ *
The Content-MD5 or x-amz-sdk-checksum-algorithm header is required for
+ * any request to upload an object with a retention period configured using Amazon S3 Object Lock. For more
+ * information, see Uploading objects
+ * to an Object Lock enabled bucket in the Amazon S3 User Guide.
*
*
*
This functionality is not supported for directory buckets.
If the individual checksum value you provide through x-amz-checksum-algorithm
* doesn't match the checksum algorithm you set through x-amz-sdk-checksum-algorithm, Amazon S3 fails the request with a BadDigest error.
*
- *
The Content-MD5 or x-amz-sdk-checksum-algorithm header is
- * required for any request to upload an object with a retention period configured using
- * Amazon S3 Object Lock. For more information, see Uploading objects to an Object Lock enabled bucket in the
- * Amazon S3 User Guide.
+ *
The Content-MD5 or x-amz-sdk-checksum-algorithm header is required for
+ * any request to upload an object with a retention period configured using Amazon S3 Object Lock. For more
+ * information, see Uploading objects
+ * to an Object Lock enabled bucket in the Amazon S3 User Guide.
*
*
For directory buckets, when you use Amazon Web Services SDKs, CRC32 is the default checksum algorithm that's used for performance.
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, 64-bit
- * CRC64NVME checksum of the object. The CRC64NVME checksum is
- * always a full object checksum. For more information, see Checking object integrity
- * in the Amazon S3 User Guide.
+ *
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, 64-bit CRC64NVME
+ * checksum of the object. The CRC64NVME checksum is always a full object checksum. For more
+ * information, see Checking object integrity in the Amazon S3
+ * User Guide.
Uploads the object only if the ETag (entity tag) value provided during the WRITE
- * operation matches the ETag of the object in S3. If the ETag values do not match, the
- * operation returns a 412 Precondition Failed error.
- *
If a conflicting operation occurs during the upload S3 returns a 409 ConditionalRequestConflict response. On a 409 failure you should fetch the object's ETag and retry the upload.
+ *
Uploads the object only if the ETag (entity tag) value provided during the WRITE operation matches
+ * the ETag of the object in S3. If the ETag values do not match, the operation returns a 412
+ * Precondition Failed error.
+ *
If a conflicting operation occurs during the upload S3 returns a 409
+ * ConditionalRequestConflict response. On a 409 failure you should fetch the object's ETag and
+ * retry the upload.
*
Expects the ETag value as a string.
- *
For more information about conditional requests, see RFC 7232, or Conditional requests in the Amazon S3 User Guide.
+ *
For more information about conditional requests, see RFC 7232, or Conditional requests in the
+ * Amazon S3 User Guide.
Uploads the object only if the object key name does not already exist in the bucket
- * specified. Otherwise, Amazon S3 returns a 412 Precondition Failed error.
+ *
Uploads the object only if the object key name does not already exist in the bucket specified.
+ * Otherwise, Amazon S3 returns a 412 Precondition Failed error.
*
If a conflicting operation occurs during the upload S3 returns a 409
- * ConditionalRequestConflict response. On a 409 failure you should retry the
- * upload.
+ * ConditionalRequestConflict response. On a 409 failure you should retry the upload.
*
Expects the '*' (asterisk) character.
- *
For more information about conditional requests, see RFC 7232, or Conditional requests in the Amazon S3 User Guide.
+ *
For more information about conditional requests, see RFC 7232, or Conditional requests in the
+ * Amazon S3 User Guide.
- * Specifies the offset for appending data to existing objects in bytes.
- * The offset must be equal to the size of the existing object being appended to.
- * If no object exists, setting this header to 0 will create a new object.
- *
+ *
Specifies the offset for appending data to existing objects in bytes. The offset must be equal to
+ * the size of the existing object being appended to. If no object exists, setting this header to 0 will
+ * create a new object.
*
- *
This functionality is only supported for objects in the Amazon S3 Express One Zone storage class in directory buckets.
+ *
This functionality is only supported for objects in the Amazon S3 Express One Zone storage class in
+ * directory buckets.
The server-side encryption algorithm that was used when you store this object in Amazon S3 or Amazon FSx.
+ *
The server-side encryption algorithm that was used when you store this object in Amazon S3 or
+ * Amazon FSx.
*
*
*
- * General purpose buckets - You have four mutually
- * exclusive options to protect data using server-side encryption in Amazon S3, depending on
- * how you choose to manage the encryption keys. Specifically, the encryption key
- * options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS or DSSE-KMS), and
- * customer-provided keys (SSE-C). Amazon S3 encrypts data with server-side encryption by
- * using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt
- * data at rest by using server-side encryption with other key options. For more
- * information, see Using Server-Side
- * Encryption in the Amazon S3 User Guide.
+ * General purpose buckets - You have four mutually exclusive
+ * options to protect data using server-side encryption in Amazon S3, depending on how you choose to manage
+ * the encryption keys. Specifically, the encryption key options are Amazon S3 managed keys (SSE-S3),
+ * Amazon Web Services KMS keys (SSE-KMS or DSSE-KMS), and customer-provided keys (SSE-C). Amazon S3 encrypts data with
+ * server-side encryption by using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3
+ * to encrypt data at rest by using server-side encryption with other key options. For more
+ * information, see Using Server-Side Encryption in
+ * the Amazon S3 User Guide.
*
*
*
* Directory buckets -
- * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+ * For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (AES256) and server-side encryption with KMS keys (SSE-KMS) (aws:kms). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
* CreateSession requests or PUT object requests. Then, new objects
* are automatically encrypted with the desired encryption settings. For more
* information, see Protecting data with server-side encryption in the Amazon S3 User Guide. For more information about the encryption overriding behaviors in directory buckets, see Specifying server-side encryption with KMS for new object uploads.
- * S3 access points for Amazon FSx - When accessing data stored in Amazon FSx file systems using S3 access points, the only valid server side encryption option is aws:fsx. All Amazon FSx file systems have encryption configured by default and are encrypted at rest. Data is automatically encrypted before being written to the file system, and automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
+ * S3 access points for Amazon FSx - When accessing data stored in
+ * Amazon FSx file systems using S3 access points, the only valid server side encryption option is
+ * aws:fsx. All Amazon FSx file systems have encryption configured by default and are
+ * encrypted at rest. Data is automatically encrypted before being written to the file system, and
+ * automatically decrypted as it is read. These processes are handled transparently by Amazon FSx.
*
By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The
- * STANDARD storage class provides high durability and high availability. Depending on
- * performance needs, you can specify a different Storage Class. For more information, see
- * Storage
- * Classes in the Amazon S3 User Guide.
+ *
By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The STANDARD
+ * storage class provides high durability and high availability. Depending on performance needs, you can
+ * specify a different Storage Class. For more information, see Storage Classes in the
+ * Amazon S3 User Guide.
*
*
*
- *
Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in Dedicated Local Zones.
+ *
Directory buckets only support EXPRESS_ONEZONE (the S3 Express One Zone storage class) in
+ * Availability Zones and ONEZONE_IA (the S3 One Zone-Infrequent Access storage class) in
+ * Dedicated Local Zones.
*
*
*
Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.
If the bucket is configured as a website, redirects requests for this object to another
- * object in the same bucket or to an external URL. Amazon S3 stores the value of this header in
- * the object metadata. For information about object metadata, see Object Key and Metadata in the
- * Amazon S3 User Guide.
- *
In the following example, the request header sets the redirect to an object
- * (anotherPage.html) in the same bucket:
+ *
If the bucket is configured as a website, redirects requests for this object to another object in
+ * the same bucket or to an external URL. Amazon S3 stores the value of this header in the object metadata. For
+ * information about object metadata, see Object Key and Metadata in the Amazon S3
+ * User Guide.
+ *
In the following example, the request header sets the redirect to an object (anotherPage.html) in
+ * the same bucket:
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.
+ *
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 functionality is not supported for directory buckets.
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 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.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Specifies whether a legal hold will be applied to this object. For more information
- * about S3 Object Lock, see Object Lock in the
- * Amazon S3 User Guide.
+ *
Specifies whether a legal hold will be applied to this object. For more information about S3 Object
+ * Lock, see Object Lock in
+ * the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
- * You have attempted to add more parts than the maximum of 10000
- * that are allowed for this object. You can use the CopyObject operation
- * to copy this object to another and then add more data to the newly copied object.
- *
+ *
You have attempted to add more parts than the maximum of 10000 that are allowed for this object.
+ * You can use the CopyObject operation to copy this object to another and then add more data to the newly
+ * copied object.
The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a message
- * integrity check to verify that the request body was not corrupted in transit. For more
- * information, go to RFC
- * 1864.>
+ *
The Base64 encoded 128-bit MD5 digest of the data. This header must be used as a
+ * message integrity check to verify that the request body was not corrupted in transit. For more
+ * information, go to RFC 1864.>
*
*
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
* @public
@@ -1660,14 +2940,13 @@ export interface PutObjectAclRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
*
@@ -1797,8 +3074,8 @@ export interface PutObjectLegalHoldRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
*
@@ -1868,8 +3145,8 @@ export interface PutObjectLockConfigurationRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
The bucket name that contains the object you want to apply this Object Retention
- * configuration to.
+ *
The bucket name that contains the object you want to apply this Object Retention configuration to.
*
* Access points - When you use this action with an access point for general purpose buckets, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When you use this action with an access point for directory buckets, you must provide the access point name in place of the bucket name. When using the access point ARN, 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.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
@@ -1908,8 +3185,7 @@ export interface PutObjectRetentionRequest {
*/
Bucket: string | undefined;
/**
- *
The key name for the object that you want to apply this Object Retention configuration
- * to.
+ *
The key name for the object that you want to apply this Object Retention configuration to.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
The version ID for the object that you want to apply this Object Retention configuration
- * to.
+ *
The version ID for the object that you want to apply this Object Retention configuration to.
* @public
*/
VersionId?: string | undefined;
@@ -1954,8 +3228,8 @@ export interface PutObjectRetentionRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
* @public
*/
ChecksumAlgorithm?: ChecksumAlgorithm | undefined;
@@ -2014,8 +3288,8 @@ export interface PutObjectTaggingRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
The name of the Amazon S3 bucket whose PublicAccessBlock configuration you want
- * to set.
+ *
The name of the Amazon S3 bucket whose PublicAccessBlock configuration you want to
+ * set.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
* @public
@@ -2067,15 +3340,15 @@ export interface PutPublicAccessBlockRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
The PublicAccessBlock configuration that you want to apply to this Amazon S3
- * bucket. You can enable the configuration options in any combination. For more information
- * about when Amazon S3 considers a bucket or object public, see The Meaning of "Public" in the Amazon S3 User Guide.
+ *
The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can
+ * enable the configuration options in any combination. For more information about when Amazon S3 considers a
+ * bucket or object public, see The Meaning of "Public" in the Amazon S3 User Guide.
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.
+ *
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.
+ *
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.
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 format bucket-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.
+ * 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 format bucket-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.
*
Note: To supply the Multi-region Access Point (MRAP) to Bucket, you need to install the "@aws-sdk/signature-v4-crt" package to your project dependencies.
* For more information, please go to https://github.com/aws/aws-sdk-js-v3#known-issues
Renames the object only if the ETag (entity tag) value provided during the operation
- * matches the ETag of the object in S3. The If-Match header field makes the
- * request method conditional on ETags. If the ETag values do not match, the operation returns
- * a 412 Precondition Failed error.
+ *
Renames the object only if the ETag (entity tag) value provided during the operation matches the
+ * ETag of the object in S3. The If-Match header field makes the request method conditional on
+ * ETags. If the ETag values do not match, the operation returns a 412 Precondition Failed
+ * error.
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 a 412 Precondition
- * Failed error, preventing an overwrite. The If-None-Match header
- * prevents overwrites of existing data by validating that there's not an object with the same
- * key name already in your directory bucket.
+ *
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 a 412 Precondition Failed error, preventing an overwrite. The
+ * If-None-Match header prevents overwrites of existing data by validating that there's not
+ * an object with the same key name already in your directory bucket.
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 a 412 Precondition Failed error.
+ *
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 a
+ * 412 Precondition Failed error.
A unique string with a max of 64 ASCII characters in the ASCII range of 33 - 126.
*
*
- * RenameObject supports idempotency using a client token. To make an
- * idempotent API request using RenameObject, 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 an IdempotentParameterMismatch error is returned.
+ * RenameObject supports idempotency using a client token. To make an idempotent API request
+ * using RenameObject, 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 an IdempotentParameterMismatch error is returned.
*
* @public
*/
@@ -2223,8 +3493,9 @@ export declare class ObjectAlreadyInActiveTierError extends __BaseException {
*/
export interface RestoreObjectOutput {
/**
- *
If the encryption type is aws:kms, this optional value specifies the ID of
- * the symmetric encryption customer managed key to use for encryption of job results. Amazon S3 only
- * supports symmetric encryption KMS keys. For more information, see Asymmetric keys in KMS in the Amazon Web Services Key Management Service
- * Developer Guide.
+ *
If the encryption type is aws:kms, this optional value specifies the ID of the
+ * symmetric encryption customer managed key to use for encryption of job results. Amazon S3 only supports symmetric
+ * encryption KMS keys. For more information, see Asymmetric keys in KMS in the
+ * Amazon Web Services Key Management Service Developer Guide.
- * IGNORE: First line is a header, but you can't use the header values
- * to indicate the column in an expression. You can use column position (such as _1, _2,
- * …) to indicate the column (SELECT s._1 FROM OBJECT s).
+ * IGNORE: First line is a header, but you can't use the header values to indicate the
+ * column in an expression. You can use column position (such as _1, _2, …) to indicate the column
+ * (SELECT s._1 FROM OBJECT s).
*
*
*
- * Use: First line is a header, and you can use the header value to
- * identify a column in an expression (SELECT "name" FROM OBJECT).
+ * Use: First line is a header, and you can use the header value to identify a column
+ * in an expression (SELECT "name" FROM OBJECT).
*
A single character used to indicate that a row should be ignored when the character is
- * present at the start of that row. You can specify any character to indicate a comment line.
- * The default character is #.
+ *
A single character used to indicate that a row should be ignored when the character is present at
+ * the start of that row. You can specify any character to indicate a comment line. The default character
+ * is #.
A single character used for escaping the quotation mark character inside an already
- * escaped value. For example, the value """ a , b """ is parsed as " a , b
- * ".
+ *
A single character used for escaping the quotation mark character inside an already escaped value.
+ * For example, the value """ a , b """ is parsed as " a , b ".
A single character used for escaping when the field delimiter is part of the value. For
- * example, if the value is a, b, Amazon S3 wraps this field value in quotation marks,
- * as follows: " a , b ".
+ *
A single character used for escaping when the field delimiter is part of the value. For example, if
+ * the value is a, b, Amazon S3 wraps this field value in quotation marks, as follows: " a ,
+ * b ".
Specifies that CSV field values may contain quoted record delimiters and such records
- * should be allowed. Default value is FALSE. Setting this value to TRUE may lower
- * performance.
+ *
Specifies that CSV field values may contain quoted record delimiters and such records should be
+ * allowed. Default value is FALSE. Setting this value to TRUE may lower performance.
A single character used for escaping when the field delimiter is part of the value. For
- * example, if the value is a, b, Amazon S3 wraps this field value in quotation marks,
- * as follows: " a , b ".
+ *
A single character used for escaping when the field delimiter is part of the value. For example, if
+ * the value is a, b, Amazon S3 wraps this field value in quotation marks, as follows: " a ,
+ * b ".
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can continue to use the feature as usual. Learn more
+ *
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can
+ * continue to use the feature as usual. Learn more
*
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can continue to use the feature as usual. Learn more
+ *
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can
+ * continue to use the feature as usual. Learn more
*
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can continue to use the feature as usual. Learn more
+ *
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can
+ * continue to use the feature as usual. Learn more
*
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can continue to use the feature as usual. Learn more
+ *
Amazon S3 Select is no longer available to new customers. Existing customers of Amazon S3 Select can
+ * continue to use the feature as usual. Learn more
*
Confirms that the requester knows that they will be charged for the request. Bucket
- * owners need not specify this parameter in their requests. If either the source or
- * destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
- * charges to copy the object. For information about downloading objects from Requester Pays
- * buckets, see Downloading Objects in
- * Requester Pays Buckets in the Amazon S3 User Guide.
+ *
Confirms that the requester knows that they will be charged for the request. Bucket owners need not
+ * specify this parameter in their requests. If either the source or destination S3 bucket has Requester
+ * Pays enabled, the requester will pay for corresponding charges to copy the object. For information about
+ * downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays
+ * Buckets in the Amazon S3 User Guide.
*
*
This functionality is not supported for directory buckets.
*
@@ -2768,8 +4038,8 @@ export interface RestoreObjectRequest {
* 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.
+ *
If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm
+ * parameter.
A message that indicates the request is complete and no more messages will be sent. You
- * should not assume that the request is complete until the client receives an
- * EndEvent.
+ *
A message that indicates the request is complete and no more messages will be sent. You should not
+ * assume that the request is complete until the client receives an EndEvent.
The byte array of partial, one or more result records. S3 Select doesn't guarantee that
- * a record will be self-contained in one record frame. To ensure continuous streaming of
- * data, S3 Select might split the same record across multiple record frames instead of
- * aggregating the results in memory. Some S3 clients (for example, the SDKforJava) handle this behavior by creating a ByteStream out of the response by
- * default. Other clients might not handle this behavior by default. In those cases, you must
- * aggregate the results on the client side and parse the response.
+ *
The byte array of partial, one or more result records. S3 Select doesn't guarantee that a record
+ * will be self-contained in one record frame. To ensure continuous streaming of data, S3 Select might
+ * split the same record across multiple record frames instead of aggregating the results in memory. Some
+ * S3 clients (for example, the SDKforJava) handle this behavior by creating a
+ * ByteStream out of the response by default. Other clients might not handle this behavior
+ * by default. In those cases, you must aggregate the results on the client side and parse the
+ * response.