This operation aborts a multipart upload. After a multipart upload is aborted, no + * additional parts can be uploaded using that upload ID. The storage consumed by any + * previously uploaded parts will be freed. However, if any part uploads are currently in + * progress, those part uploads might or might not succeed. As a result, it might be necessary + * to abort a given multipart upload multiple times in order to completely free all storage + * consumed by all parts.
+ *To verify that all parts have been removed and prevent getting charged for the part + * storage, you should call the ListParts API operation and ensure + * that the parts list is empty.
+ *
+ * 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 -
+ * 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.
+ *
+ * Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the
+ * CreateSession
+ * API 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 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.
+ * 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
+ * .
+ * Directory buckets - The HTTP Host header syntax is
+ * Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to AbortMultipartUpload:
+ * CreateMultipartUpload + *
+ *+ * UploadPart + *
+ *+ * CompleteMultipartUpload + *
+ *+ * ListParts + *
+ *+ * ListMultipartUploads + *
+ *The specified multipart upload does not exist.
+ * + * @throws {@link S3ServiceException} + *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To abort a multipart upload + * ```javascript + * // The following example aborts a multipart upload. + * const input = { + * Bucket: "examplebucket", + * Key: "bigobject", + * UploadId: "xadcOB_7YPBOJuoFiQ9cz4P3Pe6FIZwO4f7wN93uHsNBEw97pl5eNwzExg0LAT2dUN91cOmrEQHDsP3WA60CEg--" + * }; + * const command = new AbortMultipartUploadCommand(input); + * const response = await client.send(command); + * /* response is + * { /* empty *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class AbortMultipartUploadCommand extends AbortMultipartUploadCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: AbortMultipartUploadRequest; + output: AbortMultipartUploadOutput; + }; + sdk: { + input: AbortMultipartUploadCommandInput; + output: AbortMultipartUploadCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/CompleteMultipartUploadCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/CompleteMultipartUploadCommand.d.ts new file mode 100644 index 00000000..9e952f7f --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/CompleteMultipartUploadCommand.d.ts @@ -0,0 +1,317 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { CompleteMultipartUploadOutput, CompleteMultipartUploadRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link CompleteMultipartUploadCommand}. + */ +export interface CompleteMultipartUploadCommandInput extends CompleteMultipartUploadRequest { +} +/** + * @public + * + * The output of {@link CompleteMultipartUploadCommand}. + */ +export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartUploadOutput, __MetadataBearer { +} +declare const CompleteMultipartUploadCommand_base: { + new (input: CompleteMultipartUploadCommandInput): import("@smithy/smithy-client").CommandImplCompletes 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 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.
For more information about multipart uploads, see Uploading Objects Using Multipart + * Upload 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
+ * . 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.
+ * Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the
+ * CreateSession
+ * API 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 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.
+ * 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 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.
Error Code: EntityTooSmall
+ *
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.
+ *HTTP Status Code: 400 Bad Request
+ *Error Code: InvalidPart
+ *
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.
+ *HTTP Status Code: 400 Bad Request
+ *Error Code: InvalidPartOrder
+ *
Description: The list of parts was not in ascending order. The + * parts list must be specified in order by part number.
+ *HTTP Status Code: 400 Bad Request
+ *Error Code: NoSuchUpload
+ *
Description: The specified multipart upload does not exist. The + * upload ID might be invalid, or the multipart upload might have been + * aborted or completed.
+ *HTTP Status Code: 404 Not Found
+ *
+ * Directory buckets - The HTTP Host header syntax is
+ * Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to CompleteMultipartUpload:
+ * CreateMultipartUpload + *
+ *+ * UploadPart + *
+ *+ * AbortMultipartUpload + *
+ *+ * ListParts + *
+ *+ * ListMultipartUploads + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To complete multipart upload + * ```javascript + * // The following example completes a multipart upload. + * const input = { + * Bucket: "examplebucket", + * Key: "bigobject", + * MultipartUpload: { + * Parts: [ + * { + * ETag: `"d8c2eafd90c266e19ab9dcacc479f8af"`, + * PartNumber: 1 + * }, + * { + * ETag: `"d8c2eafd90c266e19ab9dcacc479f8af"`, + * PartNumber: 2 + * } + * ] + * }, + * UploadId: "7YPBOJuoFiQ9cz4P3Pe6FIZwO4f7wN93uHsNBEw97pl5eNwzExg0LAT2dUN91cOmrEQHDsP3WA60CEg--" + * }; + * const command = new CompleteMultipartUploadCommand(input); + * const response = await client.send(command); + * /* response is + * { + * Bucket: "acexamplebucket", + * ETag: `"4d9031c7644d8081c2829f4ea23c55f7-2"`, + * Key: "bigobject", + * Location: "https://examplebucket.s3.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 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.
+ *
+ * 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.
+ *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.
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.
+ *You must have read access to the source object and + * 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.
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.
If the destination bucket is a general purpose bucket, you must have
+ *
+ * s3:PutObject
+ *
+ * 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.
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.
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.
+ *
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.
For example policies, see Example bucket policies for S3 Express One Zone and Amazon Web Services Identity and Access Management (IAM) identity-based policies for + * S3 Express One Zone in the Amazon S3 User Guide.
+ *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.
+ *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 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.
+ *
+ * Directory buckets - The HTTP Host header syntax is
+ * Bucket-name.s3express-zone-id.region-code.amazonaws.com.
+ * 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.
The following operations are related to CopyObject:
The source object of the COPY action is not in the active tier and is only stored in + * Amazon S3 Glacier.
+ * + * @throws {@link S3ServiceException} + *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To copy an object + * ```javascript + * // The following example copies an object from one bucket to another. + * const input = { + * Bucket: "destinationbucket", + * CopySource: "/sourcebucket/HappyFacejpg", + * Key: "HappyFaceCopyjpg" + * }; + * const command = new CopyObjectCommand(input); + * const response = await client.send(command); + * /* response is + * { + * CopyObjectResult: { + * ETag: `"6805f2cfc46c0f04559748bb039d69ae"`, + * LastModified: "2016-12-15T17:38:53.000Z" + * } + * } + * *\/ + * ``` + * + * @public + */ +export declare class CopyObjectCommand extends CopyObjectCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: CopyObjectRequest; + output: CopyObjectOutput; + }; + sdk: { + input: CopyObjectCommandInput; + output: CopyObjectCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateBucketCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateBucketCommand.d.ts new file mode 100644 index 00000000..b49c6d9e --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateBucketCommand.d.ts @@ -0,0 +1,282 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { CreateBucketOutput, CreateBucketRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link CreateBucketCommand}. + */ +export interface CreateBucketCommandInput extends CreateBucketRequest { +} +/** + * @public + * + * The output of {@link CreateBucketCommand}. + */ +export interface CreateBucketCommandOutput extends CreateBucketOutput, __MetadataBearer { +} +declare const CreateBucketCommand_base: { + new (input: CreateBucketCommandInput): import("@smithy/smithy-client").CommandImplThis action creates an Amazon S3 bucket. To create an Amazon S3 on Outposts bucket, see
+ * CreateBucket
+ * .
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.
+ *There are two types of buckets: general purpose buckets and directory buckets. For more + * information about these bucket types, see Creating, configuring, and + * working with Amazon S3 buckets in the Amazon S3 User Guide.
+ *
+ * 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.
+ * 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
+ * . Virtual-hosted-style requests aren't 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 - 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.
+ * 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.
+ * 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.
For the majority of modern use cases in S3, we recommend that + * you keep all Block Public Access settings enabled and keep ACLs + * disabled. If you would like to share data with users outside of + * your account, you can use bucket policies as needed. For more + * information, see Controlling ownership of objects and disabling ACLs for your + * bucket and Blocking public access to your Amazon S3 storage in + * the Amazon S3 User Guide.
+ *
+ * S3 Block Public Access - If
+ * your specific use case requires granting public access to your S3
+ * resources, you can disable Block Public Access. Specifically, you can
+ * create a new bucket with Block Public Access enabled, then separately
+ * call the
+ * DeletePublicAccessBlock
+ * API. To use this operation, you must have the
+ * s3:PutBucketPublicAccessBlock permission. For more
+ * information about S3 Block Public Access, see Blocking public access to your Amazon S3 storage 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.
+ *
+ * Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to CreateBucket:
+ * PutObject + *
+ *+ * DeleteBucket + *
+ *The requested bucket name is not available. The bucket namespace is shared by all users + * of the system. Select a different name and try again.
+ * + * @throws {@link BucketAlreadyOwnedByYou} (client fault) + *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.
+ * + * + * @example To create a bucket in a specific region + * ```javascript + * // The following example creates a bucket. The request specifies an AWS region where to create the bucket. + * const input = { + * Bucket: "examplebucket", + * CreateBucketConfiguration: { + * LocationConstraint: "eu-west-1" + * } + * }; + * const command = new CreateBucketCommand(input); + * const response = await client.send(command); + * /* response is + * { + * Location: "http://examplebucket.Creates a metadata table configuration for a general purpose bucket. For more + * information, see Accelerating data + * discovery with S3 Metadata in the Amazon S3 User Guide.
+ *To use this operation, you must have the following permissions. For more + * information, see Setting up + * permissions for configuring metadata tables in the + * Amazon S3 User Guide.
+ *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.
+ *
+ * s3:CreateBucketMetadataTableConfiguration
+ *
+ * s3tables:CreateNamespace
+ *
+ * s3tables:GetTable
+ *
+ * s3tables:CreateTable
+ *
+ * s3tables:PutTablePolicy
+ *
The following operations are related to CreateBucketMetadataTableConfiguration:
Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class CreateBucketMetadataTableConfigurationCommand extends CreateBucketMetadataTableConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: CreateBucketMetadataTableConfigurationRequest; + output: {}; + }; + sdk: { + input: CreateBucketMetadataTableConfigurationCommandInput; + output: CreateBucketMetadataTableConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateMultipartUploadCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateMultipartUploadCommand.d.ts new file mode 100644 index 00000000..a60b70e4 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateMultipartUploadCommand.d.ts @@ -0,0 +1,401 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { CreateMultipartUploadOutput, CreateMultipartUploadRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link CreateMultipartUploadCommand}. + */ +export interface CreateMultipartUploadCommandInput extends CreateMultipartUploadRequest { +} +/** + * @public + * + * The output of {@link CreateMultipartUploadCommand}. + */ +export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploadOutput, __MetadataBearer { +} +declare const CreateMultipartUploadCommand_base: { + new (input: CreateMultipartUploadCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
+ *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.
+ *
+ * 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.
+ *
+ * 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.
+ * Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the
+ * CreateSession
+ * API 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 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.
+ * 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
+ * .
+ * 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.
+ * x-amz-server-side-encryption
+ *
+ * x-amz-server-side-encryption-aws-kms-key-id
+ *
+ * x-amz-server-side-encryption-context
+ *
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.
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.
For more information about server-side encryption with KMS keys + * (SSE-KMS), see Protecting + * Data Using Server-Side Encryption with KMS keys 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.
+ *
+ * x-amz-server-side-encryption-customer-algorithm
+ *
+ * x-amz-server-side-encryption-customer-key
+ *
+ * x-amz-server-side-encryption-customer-key-MD5
+ *
For more information about server-side encryption with + * customer-provided encryption keys (SSE-C), see Protecting data using server-side encryption with + * customer-provided encryption keys (SSE-C) 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
+ * 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.
In the Zonal endpoint API calls (except CopyObject and UploadPartCopy) using the REST API, the encryption request headers must match the encryption settings that are specified in the CreateSession request.
+ * You can't override the values of the encryption settings (x-amz-server-side-encryption, x-amz-server-side-encryption-aws-kms-key-id, x-amz-server-side-encryption-context, and x-amz-server-side-encryption-bucket-key-enabled) that are specified in the CreateSession request.
+ * You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and
+ * Amazon S3 will use the encryption settings values from the CreateSession request to protect new objects in the directory bucket.
+ *
When you use the CLI or the Amazon Web Services SDKs, for CreateSession, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the
+ * CreateSession request. It's not supported to override the encryption settings values in the CreateSession request.
+ * So in the Zonal endpoint API calls (except CopyObject and UploadPartCopy),
+ * the encryption request headers must match the default encryption configuration of the directory 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.
+ * Directory buckets - The HTTP Host header syntax is
+ * Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to CreateMultipartUpload:
+ * UploadPart + *
+ *+ * CompleteMultipartUpload + *
+ *+ * AbortMultipartUpload + *
+ *+ * ListParts + *
+ *+ * ListMultipartUploads + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To initiate a multipart upload + * ```javascript + * // The following example initiates a multipart upload. + * const input = { + * Bucket: "examplebucket", + * Key: "largeobject" + * }; + * const command = new CreateMultipartUploadCommand(input); + * const response = await client.send(command); + * /* response is + * { + * Bucket: "examplebucket", + * Key: "largeobject", + * UploadId: "ibZBv_75gd9r8lH_gqXatLdxMVpAlj6ZQjEs.OwyF3953YdwbcQnMA2BLGn8Lx12fQNICtMw5KyteFeHw.Sjng--" + * } + * *\/ + * ``` + * + * @public + */ +export declare class CreateMultipartUploadCommand extends CreateMultipartUploadCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: CreateMultipartUploadRequest; + output: CreateMultipartUploadOutput; + }; + sdk: { + input: CreateMultipartUploadCommandInput; + output: CreateMultipartUploadCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateSessionCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateSessionCommand.d.ts new file mode 100644 index 00000000..5099bf79 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateSessionCommand.d.ts @@ -0,0 +1,197 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { CreateSessionOutput, CreateSessionRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link CreateSessionCommand}. + */ +export interface CreateSessionCommandInput extends CreateSessionRequest { +} +/** + * @public + * + * The output of {@link CreateSessionCommand}. + */ +export interface CreateSessionCommandOutput extends CreateSessionOutput, __MetadataBearer { +} +declare const CreateSessionCommand_base: { + new (input: CreateSessionCommandInput): import("@smithy/smithy-client").CommandImplCreates 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.
+ *You must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://bucket-name.s3express-zone-id.region-code.amazonaws.com. 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.
+ *
+ * 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.
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
+ * x-amz-create-session-mode
+ * . For example policies, see
+ * Example bucket policies for S3 Express One Zone and Amazon Web Services Identity and Access Management (IAM) identity-based policies for
+ * S3 Express One Zone in the Amazon S3 User Guide.
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.
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 Zonal endpoint (object-level) API operations except CopyObject and UploadPartCopy, + * you authenticate and authorize requests through CreateSession for low latency. + * To encrypt new objects in a directory bucket with SSE-KMS, you must specify SSE-KMS as the directory bucket's default encryption configuration with a KMS key (specifically, a customer managed key). Then, when a session is created for Zonal endpoint API operations, new objects are automatically encrypted and decrypted with SSE-KMS and S3 Bucket Keys during the session.
+ *
+ * Only 1 customer managed key is supported per directory bucket for the lifetime of the bucket. The Amazon Web Services managed key (aws/s3) isn't supported.
+ * After you specify SSE-KMS as your bucket's default encryption configuration with a customer managed key, you can't change the customer managed key for the bucket's SSE-KMS configuration.
+ *
In the Zonal endpoint API calls (except CopyObject and UploadPartCopy) using the REST API,
+ * you can't override the values of the encryption settings (x-amz-server-side-encryption, x-amz-server-side-encryption-aws-kms-key-id, x-amz-server-side-encryption-context, and x-amz-server-side-encryption-bucket-key-enabled) from the CreateSession request.
+ * You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and
+ * Amazon S3 will use the encryption settings values from the CreateSession request to protect new objects in the directory bucket.
+ *
When you use the CLI or the Amazon Web Services SDKs, for CreateSession, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the
+ * CreateSession request. It's not supported to override the encryption settings values in the CreateSession request.
+ * Also, in the Zonal endpoint API calls (except CopyObject and UploadPartCopy),
+ * it's not supported to override the values of the encryption settings from the CreateSession request.
+ *
+ *
+ * Directory buckets - The HTTP Host header syntax is
+ * Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The specified bucket does not exist.
+ * + * @throws {@link S3ServiceException} + *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class CreateSessionCommand extends CreateSessionCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: CreateSessionRequest; + output: CreateSessionOutput; + }; + sdk: { + input: CreateSessionCommandInput; + output: CreateSessionCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketAnalyticsConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketAnalyticsConfigurationCommand.d.ts new file mode 100644 index 00000000..ce3dfc55 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketAnalyticsConfigurationCommand.d.ts @@ -0,0 +1,102 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketAnalyticsConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketAnalyticsConfigurationCommand}. + */ +export interface DeleteBucketAnalyticsConfigurationCommandInput extends DeleteBucketAnalyticsConfigurationRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketAnalyticsConfigurationCommand}. + */ +export interface DeleteBucketAnalyticsConfigurationCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketAnalyticsConfigurationCommand_base: { + new (input: DeleteBucketAnalyticsConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Deletes an analytics configuration for the bucket (specified by the analytics + * configuration ID).
+ *To use this operation, you must have permissions to perform the
+ * s3:PutAnalyticsConfiguration action. 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 Subresource Operations and Managing
+ * Access Permissions to Your Amazon S3 Resources.
For information about the Amazon S3 analytics feature, see Amazon S3 Analytics – Storage Class + * Analysis.
+ *The following operations are related to
+ * DeleteBucketAnalyticsConfiguration:
+ * GetBucketAnalyticsConfiguration + *
+ *+ * PutBucketAnalyticsConfiguration + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class DeleteBucketAnalyticsConfigurationCommand extends DeleteBucketAnalyticsConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketAnalyticsConfigurationRequest; + output: {}; + }; + sdk: { + input: DeleteBucketAnalyticsConfigurationCommandInput; + output: DeleteBucketAnalyticsConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketCommand.d.ts new file mode 100644 index 00000000..5986988d --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketCommand.d.ts @@ -0,0 +1,141 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketCommand}. + */ +export interface DeleteBucketCommandInput extends DeleteBucketRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketCommand}. + */ +export interface DeleteBucketCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketCommand_base: { + new (input: DeleteBucketCommandInput): import("@smithy/smithy-client").CommandImplDeletes 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 - 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
+ * . Virtual-hosted-style requests aren't 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 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 buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to DeleteBucket:
+ * CreateBucket + *
+ *+ * DeleteObject + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete a bucket + * ```javascript + * // The following example deletes the specified bucket. + * const input = { + * Bucket: "forrandall2" + * }; + * const command = new DeleteBucketCommand(input); + * const response = await client.send(command); + * /* response is + * { /* metadata only *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteBucketCommand extends DeleteBucketCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketRequest; + output: {}; + }; + sdk: { + input: DeleteBucketCommandInput; + output: DeleteBucketCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketCorsCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketCorsCommand.d.ts new file mode 100644 index 00000000..21c3bf77 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketCorsCommand.d.ts @@ -0,0 +1,107 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketCorsRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketCorsCommand}. + */ +export interface DeleteBucketCorsCommandInput extends DeleteBucketCorsRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketCorsCommand}. + */ +export interface DeleteBucketCorsCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketCorsCommand_base: { + new (input: DeleteBucketCorsCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
For information about cors, see Enabling Cross-Origin Resource Sharing in
+ * the Amazon S3 User Guide.
+ * Related Resources + *
+ *+ * PutBucketCors + *
+ *+ * RESTOPTIONSobject + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete cors configuration on a bucket. + * ```javascript + * // The following example deletes CORS configuration on a bucket. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new DeleteBucketCorsCommand(input); + * const response = await client.send(command); + * /* response is + * { /* metadata only *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteBucketCorsCommand extends DeleteBucketCorsCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketCorsRequest; + output: {}; + }; + sdk: { + input: DeleteBucketCorsCommandInput; + output: DeleteBucketCorsCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketEncryptionCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketEncryptionCommand.d.ts new file mode 100644 index 00000000..50625693 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketEncryptionCommand.d.ts @@ -0,0 +1,131 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketEncryptionRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketEncryptionCommand}. + */ +export interface DeleteBucketEncryptionCommandInput extends DeleteBucketEncryptionRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketEncryptionCommand}. + */ +export interface DeleteBucketEncryptionCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketEncryptionCommand_base: { + new (input: DeleteBucketEncryptionCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
+ *+ * 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.
+ *
+ * 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.
+ * 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 buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to DeleteBucketEncryption:
+ * PutBucketEncryption + *
+ *+ * GetBucketEncryption + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class DeleteBucketEncryptionCommand extends DeleteBucketEncryptionCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketEncryptionRequest; + output: {}; + }; + sdk: { + input: DeleteBucketEncryptionCommandInput; + output: DeleteBucketEncryptionCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketIntelligentTieringConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketIntelligentTieringConfigurationCommand.d.ts new file mode 100644 index 00000000..66db5b4e --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketIntelligentTieringConfigurationCommand.d.ts @@ -0,0 +1,95 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketIntelligentTieringConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketIntelligentTieringConfigurationCommand}. + */ +export interface DeleteBucketIntelligentTieringConfigurationCommandInput extends DeleteBucketIntelligentTieringConfigurationRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketIntelligentTieringConfigurationCommand}. + */ +export interface DeleteBucketIntelligentTieringConfigurationCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketIntelligentTieringConfigurationCommand_base: { + new (input: DeleteBucketIntelligentTieringConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Deletes the S3 Intelligent-Tiering configuration from the specified 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.
+ *For more information, see Storage class for automatically optimizing frequently and infrequently accessed objects.
+ *Operations related to DeleteBucketIntelligentTieringConfiguration include:
Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class DeleteBucketIntelligentTieringConfigurationCommand extends DeleteBucketIntelligentTieringConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketIntelligentTieringConfigurationRequest; + output: {}; + }; + sdk: { + input: DeleteBucketIntelligentTieringConfigurationCommandInput; + output: DeleteBucketIntelligentTieringConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketInventoryConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketInventoryConfigurationCommand.d.ts new file mode 100644 index 00000000..d0c2a915 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketInventoryConfigurationCommand.d.ts @@ -0,0 +1,100 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketInventoryConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketInventoryConfigurationCommand}. + */ +export interface DeleteBucketInventoryConfigurationCommandInput extends DeleteBucketInventoryConfigurationRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketInventoryConfigurationCommand}. + */ +export interface DeleteBucketInventoryConfigurationCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketInventoryConfigurationCommand_base: { + new (input: DeleteBucketInventoryConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Deletes an inventory configuration (identified by the inventory ID) from the + * bucket.
+ *To use this operation, you must have permissions to perform the
+ * s3:PutInventoryConfiguration action. 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 Subresource Operations and Managing
+ * Access Permissions to Your Amazon S3 Resources.
For information about the Amazon S3 inventory feature, see Amazon S3 Inventory.
+ *Operations related to DeleteBucketInventoryConfiguration include:
+ * GetBucketInventoryConfiguration + *
+ *+ * PutBucketInventoryConfiguration + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class DeleteBucketInventoryConfigurationCommand extends DeleteBucketInventoryConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketInventoryConfigurationRequest; + output: {}; + }; + sdk: { + input: DeleteBucketInventoryConfigurationCommandInput; + output: DeleteBucketInventoryConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketLifecycleCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketLifecycleCommand.d.ts new file mode 100644 index 00000000..7947a455 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketLifecycleCommand.d.ts @@ -0,0 +1,153 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketLifecycleRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketLifecycleCommand}. + */ +export interface DeleteBucketLifecycleCommandInput extends DeleteBucketLifecycleRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketLifecycleCommand}. + */ +export interface DeleteBucketLifecycleCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketLifecycleCommand_base: { + new (input: DeleteBucketLifecycleCommandInput): import("@smithy/smithy-client").CommandImplDeletes 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.
+ *
+ * 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.
For more information about permissions, see Managing Access + * Permissions to Your Amazon S3 Resources.
+ *
+ * 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.
For more information about directory bucket policies and permissions, see + * Authorizing Regional endpoint APIs with IAM 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
+ * . Virtual-hosted-style requests aren't 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.
+ * Directory buckets - The HTTP Host
+ * header syntax is
+ * s3express-control.region.amazonaws.com.
For more information about the object expiration, see Elements to Describe Lifecycle Actions.
+ *Related actions include:
+ *+ * PutBucketLifecycleConfiguration + *
+ *+ * GetBucketLifecycleConfiguration + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete lifecycle configuration on a bucket. + * ```javascript + * // The following example deletes lifecycle configuration on a bucket. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new DeleteBucketLifecycleCommand(input); + * const response = await client.send(command); + * /* response is + * { /* metadata only *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteBucketLifecycleCommand extends DeleteBucketLifecycleCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketLifecycleRequest; + output: {}; + }; + sdk: { + input: DeleteBucketLifecycleCommandInput; + output: DeleteBucketLifecycleCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketMetadataTableConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketMetadataTableConfigurationCommand.d.ts new file mode 100644 index 00000000..e225ff8e --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketMetadataTableConfigurationCommand.d.ts @@ -0,0 +1,96 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketMetadataTableConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketMetadataTableConfigurationCommand}. + */ +export interface DeleteBucketMetadataTableConfigurationCommandInput extends DeleteBucketMetadataTableConfigurationRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketMetadataTableConfigurationCommand}. + */ +export interface DeleteBucketMetadataTableConfigurationCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketMetadataTableConfigurationCommand_base: { + new (input: DeleteBucketMetadataTableConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl+ * Deletes a metadata table configuration from a general purpose bucket. For more + * information, see Accelerating data + * discovery with S3 Metadata in the Amazon S3 User Guide.
+ *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:
Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class DeleteBucketMetadataTableConfigurationCommand extends DeleteBucketMetadataTableConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketMetadataTableConfigurationRequest; + output: {}; + }; + sdk: { + input: DeleteBucketMetadataTableConfigurationCommandInput; + output: DeleteBucketMetadataTableConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketMetricsConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketMetricsConfigurationCommand.d.ts new file mode 100644 index 00000000..b19c28bb --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketMetricsConfigurationCommand.d.ts @@ -0,0 +1,108 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketMetricsConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketMetricsConfigurationCommand}. + */ +export interface DeleteBucketMetricsConfigurationCommandInput extends DeleteBucketMetricsConfigurationRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketMetricsConfigurationCommand}. + */ +export interface DeleteBucketMetricsConfigurationCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketMetricsConfigurationCommand_base: { + new (input: DeleteBucketMetricsConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
+ * To use this operation, you must have permissions to perform the
+ * s3:PutMetricsConfiguration action. 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 Subresource Operations and Managing
+ * Access Permissions to Your Amazon S3 Resources.
For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with + * Amazon CloudWatch.
+ *The following operations are related to
+ * DeleteBucketMetricsConfiguration:
+ * GetBucketMetricsConfiguration + *
+ *+ * PutBucketMetricsConfiguration + *
+ *+ * ListBucketMetricsConfigurations + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class DeleteBucketMetricsConfigurationCommand extends DeleteBucketMetricsConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketMetricsConfigurationRequest; + output: {}; + }; + sdk: { + input: DeleteBucketMetricsConfigurationCommandInput; + output: DeleteBucketMetricsConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketOwnershipControlsCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketOwnershipControlsCommand.d.ts new file mode 100644 index 00000000..bfc5ee1d --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketOwnershipControlsCommand.d.ts @@ -0,0 +1,92 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketOwnershipControlsRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketOwnershipControlsCommand}. + */ +export interface DeleteBucketOwnershipControlsCommandInput extends DeleteBucketOwnershipControlsRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketOwnershipControlsCommand}. + */ +export interface DeleteBucketOwnershipControlsCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketOwnershipControlsCommand_base: { + new (input: DeleteBucketOwnershipControlsCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
For information about Amazon S3 Object Ownership, see Using Object Ownership.
+ *The following operations are related to
+ * DeleteBucketOwnershipControls:
+ * GetBucketOwnershipControls + *
+ *+ * PutBucketOwnershipControls + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class DeleteBucketOwnershipControlsCommand extends DeleteBucketOwnershipControlsCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketOwnershipControlsRequest; + output: {}; + }; + sdk: { + input: DeleteBucketOwnershipControlsCommandInput; + output: DeleteBucketOwnershipControlsCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketPolicyCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketPolicyCommand.d.ts new file mode 100644 index 00000000..c6a22080 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketPolicyCommand.d.ts @@ -0,0 +1,150 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketPolicyRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketPolicyCommand}. + */ +export interface DeleteBucketPolicyCommandInput extends DeleteBucketPolicyRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketPolicyCommand}. + */ +export interface DeleteBucketPolicyCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketPolicyCommand_base: { + new (input: DeleteBucketPolicyCommandInput): import("@smithy/smithy-client").CommandImplDeletes the policy of a specified 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
+ * . Virtual-hosted-style requests aren't 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.
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.
+ * 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.
+ * 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 buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to DeleteBucketPolicy
+ *
+ * CreateBucket + *
+ *+ * DeleteObject + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete bucket policy + * ```javascript + * // The following example deletes bucket policy on the specified bucket. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new DeleteBucketPolicyCommand(input); + * const response = await client.send(command); + * /* response is + * { /* metadata only *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteBucketPolicyCommand extends DeleteBucketPolicyCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketPolicyRequest; + output: {}; + }; + sdk: { + input: DeleteBucketPolicyCommandInput; + output: DeleteBucketPolicyCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketReplicationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketReplicationCommand.d.ts new file mode 100644 index 00000000..23a1d35c --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketReplicationCommand.d.ts @@ -0,0 +1,111 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketReplicationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketReplicationCommand}. + */ +export interface DeleteBucketReplicationCommandInput extends DeleteBucketReplicationRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketReplicationCommand}. + */ +export interface DeleteBucketReplicationCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketReplicationCommand_base: { + new (input: DeleteBucketReplicationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Deletes the replication configuration from the bucket.
+ *To use this operation, you must have permissions to perform the
+ * s3:PutReplicationConfiguration action. The bucket owner has these
+ * permissions by default and can grant it to others. For more information about permissions,
+ * see Permissions Related to Bucket Subresource Operations and Managing
+ * Access Permissions to Your Amazon S3 Resources.
It can take a while for the deletion of a replication configuration to fully + * propagate.
+ *For information about replication configuration, see Replication in the + * Amazon S3 User Guide.
+ *The following operations are related to DeleteBucketReplication:
+ * PutBucketReplication + *
+ *+ * GetBucketReplication + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete bucket replication configuration + * ```javascript + * // The following example deletes replication configuration set on bucket. + * const input = { + * Bucket: "example" + * }; + * const command = new DeleteBucketReplicationCommand(input); + * const response = await client.send(command); + * /* response is + * { /* metadata only *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteBucketReplicationCommand extends DeleteBucketReplicationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketReplicationRequest; + output: {}; + }; + sdk: { + input: DeleteBucketReplicationCommandInput; + output: DeleteBucketReplicationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketTaggingCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketTaggingCommand.d.ts new file mode 100644 index 00000000..cd6d57c9 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketTaggingCommand.d.ts @@ -0,0 +1,103 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketTaggingRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketTaggingCommand}. + */ +export interface DeleteBucketTaggingCommandInput extends DeleteBucketTaggingRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketTaggingCommand}. + */ +export interface DeleteBucketTaggingCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketTaggingCommand_base: { + new (input: DeleteBucketTaggingCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
The following operations are related to DeleteBucketTagging:
+ * GetBucketTagging + *
+ *+ * PutBucketTagging + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete bucket tags + * ```javascript + * // The following example deletes bucket tags. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new DeleteBucketTaggingCommand(input); + * const response = await client.send(command); + * /* response is + * { /* metadata only *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteBucketTaggingCommand extends DeleteBucketTaggingCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketTaggingRequest; + output: {}; + }; + sdk: { + input: DeleteBucketTaggingCommandInput; + output: DeleteBucketTaggingCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketWebsiteCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketWebsiteCommand.d.ts new file mode 100644 index 00000000..a2ff59f8 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteBucketWebsiteCommand.d.ts @@ -0,0 +1,110 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteBucketWebsiteRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteBucketWebsiteCommand}. + */ +export interface DeleteBucketWebsiteCommandInput extends DeleteBucketWebsiteRequest { +} +/** + * @public + * + * The output of {@link DeleteBucketWebsiteCommand}. + */ +export interface DeleteBucketWebsiteCommandOutput extends __MetadataBearer { +} +declare const DeleteBucketWebsiteCommand_base: { + new (input: DeleteBucketWebsiteCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
For more information about hosting websites, see Hosting Websites on Amazon S3.
+ *The following operations are related to DeleteBucketWebsite:
+ * GetBucketWebsite + *
+ *+ * PutBucketWebsite + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete bucket website configuration + * ```javascript + * // The following example deletes bucket website configuration. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new DeleteBucketWebsiteCommand(input); + * const response = await client.send(command); + * /* response is + * { /* metadata only *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteBucketWebsiteCommand extends DeleteBucketWebsiteCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteBucketWebsiteRequest; + output: {}; + }; + sdk: { + input: DeleteBucketWebsiteCommandInput; + output: DeleteBucketWebsiteCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectCommand.d.ts new file mode 100644 index 00000000..8b6a69ee --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectCommand.d.ts @@ -0,0 +1,210 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteObjectOutput, DeleteObjectRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteObjectCommand}. + */ +export interface DeleteObjectCommandInput extends DeleteObjectRequest { +} +/** + * @public + * + * The output of {@link DeleteObjectCommand}. + */ +export interface DeleteObjectCommandOutput extends DeleteObjectOutput, __MetadataBearer { +} +declare const DeleteObjectCommand_base: { + new (input: DeleteObjectCommandInput): import("@smithy/smithy-client").CommandImplRemoves an object from a bucket. The behavior depends on the bucket's versioning state:
+ *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 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 - 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.
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.
+ * 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.
+ * 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.
+ *
+ * s3:DeleteObject
+ * - 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.
+ * Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the
+ * CreateSession
+ * API 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 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.
+ * 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
+ * .
+ * Directory buckets - The HTTP Host header syntax is
+ * Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following action is related to DeleteObject:
+ * PutObject + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete an object (from a non-versioned bucket) + * ```javascript + * // The following example deletes an object from a non-versioned bucket. + * const input = { + * Bucket: "ExampleBucket", + * Key: "HappyFace.jpg" + * }; + * const command = new DeleteObjectCommand(input); + * const response = await client.send(command); + * /* response is + * { /* metadata only *\/ } + * *\/ + * ``` + * + * @example To delete an object + * ```javascript + * // The following example deletes an object from an S3 bucket. + * const input = { + * Bucket: "examplebucket", + * Key: "objectkey.jpg" + * }; + * const command = new DeleteObjectCommand(input); + * const response = await client.send(command); + * /* response is + * { /* empty *\/ } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteObjectCommand extends DeleteObjectCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteObjectRequest; + output: DeleteObjectOutput; + }; + sdk: { + input: DeleteObjectCommandInput; + output: DeleteObjectCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectTaggingCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectTaggingCommand.d.ts new file mode 100644 index 00000000..3c207688 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectTaggingCommand.d.ts @@ -0,0 +1,130 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteObjectTaggingOutput, DeleteObjectTaggingRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteObjectTaggingCommand}. + */ +export interface DeleteObjectTaggingCommandInput extends DeleteObjectTaggingRequest { +} +/** + * @public + * + * The output of {@link DeleteObjectTaggingCommand}. + */ +export interface DeleteObjectTaggingCommandOutput extends DeleteObjectTaggingOutput, __MetadataBearer { +} +declare const DeleteObjectTaggingCommand_base: { + new (input: DeleteObjectTaggingCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
The following operations are related to DeleteObjectTagging:
+ * PutObjectTagging + *
+ *+ * GetObjectTagging + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To remove tag set from an object + * ```javascript + * // The following example removes tag set associated with the specified object. If the bucket is versioning enabled, the operation removes tag set from the latest object version. + * const input = { + * Bucket: "examplebucket", + * Key: "HappyFace.jpg" + * }; + * const command = new DeleteObjectTaggingCommand(input); + * const response = await client.send(command); + * /* response is + * { + * VersionId: "null" + * } + * *\/ + * ``` + * + * @example To remove tag set from an object version + * ```javascript + * // The following example removes tag set associated with the specified object version. The request specifies both the object key and object version. + * const input = { + * Bucket: "examplebucket", + * Key: "HappyFace.jpg", + * VersionId: "ydlaNkwWm0SfKJR.T1b1fIdPRbldTYRI" + * }; + * const command = new DeleteObjectTaggingCommand(input); + * const response = await client.send(command); + * /* response is + * { + * VersionId: "ydlaNkwWm0SfKJR.T1b1fIdPRbldTYRI" + * } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteObjectTaggingCommand extends DeleteObjectTaggingCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteObjectTaggingRequest; + output: DeleteObjectTaggingOutput; + }; + sdk: { + input: DeleteObjectTaggingCommandInput; + output: DeleteObjectTaggingCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectsCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectsCommand.d.ts new file mode 100644 index 00000000..92784e00 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeleteObjectsCommand.d.ts @@ -0,0 +1,315 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeleteObjectsOutput, DeleteObjectsRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeleteObjectsCommand}. + */ +export interface DeleteObjectsCommandInput extends DeleteObjectsRequest { +} +/** + * @public + * + * The output of {@link DeleteObjectsCommand}. + */ +export interface DeleteObjectsCommandOutput extends DeleteObjectsOutput, __MetadataBearer { +} +declare const DeleteObjectsCommand_base: { + new (input: DeleteObjectsCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
+ *
+ * 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.
+ *+ * 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.
+ *
+ * s3:DeleteObject
+ *
+ * - 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.
+ * Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the
+ * CreateSession
+ * API 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 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.
+ * 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
+ * .
+ * 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 buckets - The HTTP Host header syntax is
+ * Bucket-name.s3express-zone-id.region-code.amazonaws.com.
The following operations are related to DeleteObjects:
+ * CreateMultipartUpload + *
+ *+ * UploadPart + *
+ *+ * CompleteMultipartUpload + *
+ *+ * ListParts + *
+ *+ * AbortMultipartUpload + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To delete multiple object versions from a versioned bucket + * ```javascript + * // The following example deletes objects from a bucket. The request specifies object versions. S3 deletes specific object versions and returns the key and versions of deleted objects in the response. + * const input = { + * Bucket: "examplebucket", + * Delete: { + * Objects: [ + * { + * Key: "HappyFace.jpg", + * VersionId: "2LWg7lQLnY41.maGB5Z6SWW.dcq0vx7b" + * }, + * { + * Key: "HappyFace.jpg", + * VersionId: "yoz3HB.ZhCS_tKVEmIOr7qYyyAaZSKVd" + * } + * ], + * Quiet: false + * } + * }; + * const command = new DeleteObjectsCommand(input); + * const response = await client.send(command); + * /* response is + * { + * Deleted: [ + * { + * Key: "HappyFace.jpg", + * VersionId: "yoz3HB.ZhCS_tKVEmIOr7qYyyAaZSKVd" + * }, + * { + * Key: "HappyFace.jpg", + * VersionId: "2LWg7lQLnY41.maGB5Z6SWW.dcq0vx7b" + * } + * ] + * } + * *\/ + * ``` + * + * @example To delete multiple objects from a versioned bucket + * ```javascript + * // The following example deletes objects from a bucket. The bucket is versioned, and the request does not specify the object version to delete. In this case, all versions remain in the bucket and S3 adds a delete marker. + * const input = { + * Bucket: "examplebucket", + * Delete: { + * Objects: [ + * { + * Key: "objectkey1" + * }, + * { + * Key: "objectkey2" + * } + * ], + * Quiet: false + * } + * }; + * const command = new DeleteObjectsCommand(input); + * const response = await client.send(command); + * /* response is + * { + * Deleted: [ + * { + * DeleteMarker: true, + * DeleteMarkerVersionId: "A._w1z6EFiCF5uhtQMDal9JDkID9tQ7F", + * Key: "objectkey1" + * }, + * { + * DeleteMarker: true, + * DeleteMarkerVersionId: "iOd_ORxhkKe_e8G8_oSGxt2PjsCZKlkt", + * Key: "objectkey2" + * } + * ] + * } + * *\/ + * ``` + * + * @public + */ +export declare class DeleteObjectsCommand extends DeleteObjectsCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeleteObjectsRequest; + output: DeleteObjectsOutput; + }; + sdk: { + input: DeleteObjectsCommandInput; + output: DeleteObjectsCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/DeletePublicAccessBlockCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeletePublicAccessBlockCommand.d.ts new file mode 100644 index 00000000..bb522f14 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/DeletePublicAccessBlockCommand.d.ts @@ -0,0 +1,101 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { DeletePublicAccessBlockRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link DeletePublicAccessBlockCommand}. + */ +export interface DeletePublicAccessBlockCommandInput extends DeletePublicAccessBlockRequest { +} +/** + * @public + * + * The output of {@link DeletePublicAccessBlockCommand}. + */ +export interface DeletePublicAccessBlockCommandOutput extends __MetadataBearer { +} +declare const DeletePublicAccessBlockCommand_base: { + new (input: DeletePublicAccessBlockCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Removes the PublicAccessBlock configuration for an Amazon S3 bucket. To use this
+ * operation, you must have the s3:PutBucketPublicAccessBlock permission. For
+ * more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing
+ * Access Permissions to Your Amazon S3 Resources.
The following operations are related to DeletePublicAccessBlock:
+ * GetPublicAccessBlock + *
+ *+ * PutPublicAccessBlock + *
+ *+ * GetBucketPolicyStatus + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class DeletePublicAccessBlockCommand extends DeletePublicAccessBlockCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: DeletePublicAccessBlockRequest; + output: {}; + }; + sdk: { + input: DeletePublicAccessBlockCommandInput; + output: DeletePublicAccessBlockCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAccelerateConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAccelerateConfigurationCommand.d.ts new file mode 100644 index 00000000..61c7656f --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAccelerateConfigurationCommand.d.ts @@ -0,0 +1,103 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketAccelerateConfigurationOutput, GetBucketAccelerateConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketAccelerateConfigurationCommand}. + */ +export interface GetBucketAccelerateConfigurationCommandInput extends GetBucketAccelerateConfigurationRequest { +} +/** + * @public + * + * The output of {@link GetBucketAccelerateConfigurationCommand}. + */ +export interface GetBucketAccelerateConfigurationCommandOutput extends GetBucketAccelerateConfigurationOutput, __MetadataBearer { +} +declare const GetBucketAccelerateConfigurationCommand_base: { + new (input: GetBucketAccelerateConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
To use this operation, you must have permission to perform the
+ * s3:GetAccelerateConfiguration action. 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 Subresource Operations and Managing
+ * Access Permissions to your Amazon S3 Resources in the
+ * Amazon S3 User Guide.
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:
+ * PutBucketAccelerateConfiguration + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketAccelerateConfigurationCommand extends GetBucketAccelerateConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketAccelerateConfigurationRequest; + output: GetBucketAccelerateConfigurationOutput; + }; + sdk: { + input: GetBucketAccelerateConfigurationCommandInput; + output: GetBucketAccelerateConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAclCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAclCommand.d.ts new file mode 100644 index 00000000..fd2df777 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAclCommand.d.ts @@ -0,0 +1,116 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketAclOutput, GetBucketAclRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketAclCommand}. + */ +export interface GetBucketAclCommandInput extends GetBucketAclRequest { +} +/** + * @public + * + * The output of {@link GetBucketAclCommand}. + */ +export interface GetBucketAclCommandOutput extends GetBucketAclOutput, __MetadataBearer { +} +declare const GetBucketAclCommand_base: { + new (input: GetBucketAclCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
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.
The following operations are related to GetBucketAcl:
+ * ListObjects + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketAclCommand extends GetBucketAclCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketAclRequest; + output: GetBucketAclOutput; + }; + sdk: { + input: GetBucketAclCommandInput; + output: GetBucketAclCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAnalyticsConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAnalyticsConfigurationCommand.d.ts new file mode 100644 index 00000000..8a5dc515 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketAnalyticsConfigurationCommand.d.ts @@ -0,0 +1,136 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketAnalyticsConfigurationOutput, GetBucketAnalyticsConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketAnalyticsConfigurationCommand}. + */ +export interface GetBucketAnalyticsConfigurationCommandInput extends GetBucketAnalyticsConfigurationRequest { +} +/** + * @public + * + * The output of {@link GetBucketAnalyticsConfigurationCommand}. + */ +export interface GetBucketAnalyticsConfigurationCommandOutput extends GetBucketAnalyticsConfigurationOutput, __MetadataBearer { +} +declare const GetBucketAnalyticsConfigurationCommand_base: { + new (input: GetBucketAnalyticsConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *This implementation of the GET action returns an analytics configuration (identified by + * the analytics configuration ID) from the bucket.
+ *To use this operation, you must have permissions to perform the
+ * s3:GetAnalyticsConfiguration action. 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 Subresource Operations and Managing
+ * Access Permissions to Your Amazon S3 Resources in the
+ * Amazon S3 User Guide.
For information about Amazon S3 analytics feature, see Amazon S3 Analytics – Storage Class + * Analysis in the Amazon S3 User Guide.
+ *The following operations are related to
+ * GetBucketAnalyticsConfiguration:
+ * PutBucketAnalyticsConfiguration + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketAnalyticsConfigurationCommand extends GetBucketAnalyticsConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketAnalyticsConfigurationRequest; + output: GetBucketAnalyticsConfigurationOutput; + }; + sdk: { + input: GetBucketAnalyticsConfigurationCommandInput; + output: GetBucketAnalyticsConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketCorsCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketCorsCommand.d.ts new file mode 100644 index 00000000..53d1ed34 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketCorsCommand.d.ts @@ -0,0 +1,145 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketCorsOutput, GetBucketCorsRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketCorsCommand}. + */ +export interface GetBucketCorsCommandInput extends GetBucketCorsRequest { +} +/** + * @public + * + * The output of {@link GetBucketCorsCommand}. + */ +export interface GetBucketCorsCommandOutput extends GetBucketCorsOutput, __MetadataBearer { +} +declare const GetBucketCorsCommand_base: { + new (input: GetBucketCorsCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
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.
For more information about CORS, see Enabling Cross-Origin Resource + * Sharing.
+ *The following operations are related to GetBucketCors:
+ * PutBucketCors + *
+ *+ * DeleteBucketCors + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To get cors configuration set on a bucket + * ```javascript + * // The following example returns cross-origin resource sharing (CORS) configuration set on a bucket. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new GetBucketCorsCommand(input); + * const response = await client.send(command); + * /* response is + * { + * CORSRules: [ + * { + * AllowedHeaders: [ + * "Authorization" + * ], + * AllowedMethods: [ + * "GET" + * ], + * AllowedOrigins: [ + * "*" + * ], + * MaxAgeSeconds: 3000 + * } + * ] + * } + * *\/ + * ``` + * + * @public + */ +export declare class GetBucketCorsCommand extends GetBucketCorsCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketCorsRequest; + output: GetBucketCorsOutput; + }; + sdk: { + input: GetBucketCorsCommandInput; + output: GetBucketCorsCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketEncryptionCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketEncryptionCommand.d.ts new file mode 100644 index 00000000..ef597d77 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketEncryptionCommand.d.ts @@ -0,0 +1,144 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketEncryptionOutput, GetBucketEncryptionRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketEncryptionCommand}. + */ +export interface GetBucketEncryptionCommandInput extends GetBucketEncryptionRequest { +} +/** + * @public + * + * The output of {@link GetBucketEncryptionCommand}. + */ +export interface GetBucketEncryptionCommandOutput extends GetBucketEncryptionOutput, __MetadataBearer { +} +declare const GetBucketEncryptionCommand_base: { + new (input: GetBucketEncryptionCommandInput): import("@smithy/smithy-client").CommandImplReturns 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.
+ *+ * 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.
+ *
+ * General purpose bucket permissions - The
+ * s3:GetEncryptionConfiguration 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.
+ * 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 buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following operations are related to GetBucketEncryption:
+ * PutBucketEncryption + *
+ *+ * DeleteBucketEncryption + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketEncryptionCommand extends GetBucketEncryptionCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketEncryptionRequest; + output: GetBucketEncryptionOutput; + }; + sdk: { + input: GetBucketEncryptionCommandInput; + output: GetBucketEncryptionCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketIntelligentTieringConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketIntelligentTieringConfigurationCommand.d.ts new file mode 100644 index 00000000..a0234083 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketIntelligentTieringConfigurationCommand.d.ts @@ -0,0 +1,122 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketIntelligentTieringConfigurationOutput, GetBucketIntelligentTieringConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketIntelligentTieringConfigurationCommand}. + */ +export interface GetBucketIntelligentTieringConfigurationCommandInput extends GetBucketIntelligentTieringConfigurationRequest { +} +/** + * @public + * + * The output of {@link GetBucketIntelligentTieringConfigurationCommand}. + */ +export interface GetBucketIntelligentTieringConfigurationCommandOutput extends GetBucketIntelligentTieringConfigurationOutput, __MetadataBearer { +} +declare const GetBucketIntelligentTieringConfigurationCommand_base: { + new (input: GetBucketIntelligentTieringConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Gets the S3 Intelligent-Tiering configuration from the specified 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.
+ *For more information, see Storage class for automatically optimizing frequently and infrequently accessed objects.
+ *Operations related to GetBucketIntelligentTieringConfiguration include:
Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketIntelligentTieringConfigurationCommand extends GetBucketIntelligentTieringConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketIntelligentTieringConfigurationRequest; + output: GetBucketIntelligentTieringConfigurationOutput; + }; + sdk: { + input: GetBucketIntelligentTieringConfigurationCommandInput; + output: GetBucketIntelligentTieringConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketInventoryConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketInventoryConfigurationCommand.d.ts new file mode 100644 index 00000000..ba2aac0f --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketInventoryConfigurationCommand.d.ts @@ -0,0 +1,130 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketInventoryConfigurationOutput, GetBucketInventoryConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketInventoryConfigurationCommand}. + */ +export interface GetBucketInventoryConfigurationCommandInput extends GetBucketInventoryConfigurationRequest { +} +/** + * @public + * + * The output of {@link GetBucketInventoryConfigurationCommand}. + */ +export interface GetBucketInventoryConfigurationCommandOutput extends GetBucketInventoryConfigurationOutput, __MetadataBearer { +} +declare const GetBucketInventoryConfigurationCommand_base: { + new (input: GetBucketInventoryConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Returns an inventory configuration (identified by the inventory configuration ID) from + * the bucket.
+ *To use this operation, you must have permissions to perform the
+ * s3:GetInventoryConfiguration 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.
For information about the Amazon S3 inventory feature, see Amazon S3 Inventory.
+ *The following operations are related to
+ * GetBucketInventoryConfiguration:
+ * PutBucketInventoryConfiguration + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketInventoryConfigurationCommand extends GetBucketInventoryConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketInventoryConfigurationRequest; + output: GetBucketInventoryConfigurationOutput; + }; + sdk: { + input: GetBucketInventoryConfigurationCommandInput; + output: GetBucketInventoryConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLifecycleConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLifecycleConfigurationCommand.d.ts new file mode 100644 index 00000000..58c3c5fc --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLifecycleConfigurationCommand.d.ts @@ -0,0 +1,254 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketLifecycleConfigurationOutput, GetBucketLifecycleConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketLifecycleConfigurationCommand}. + */ +export interface GetBucketLifecycleConfigurationCommandInput extends GetBucketLifecycleConfigurationRequest { +} +/** + * @public + * + * The output of {@link GetBucketLifecycleConfigurationCommand}. + */ +export interface GetBucketLifecycleConfigurationCommandOutput extends GetBucketLifecycleConfigurationOutput, __MetadataBearer { +} +declare const GetBucketLifecycleConfigurationCommand_base: { + new (input: GetBucketLifecycleConfigurationCommandInput): import("@smithy/smithy-client").CommandImplReturns 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.
+ *
+ * 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.
For more information about permissions, see Managing Access + * Permissions to Your Amazon S3 Resources.
+ *
+ * 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.
For more information about directory bucket policies and permissions, see + * Authorizing Regional endpoint APIs with IAM 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
+ * . Virtual-hosted-style requests aren't 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.
+ * Directory buckets - The HTTP Host
+ * header syntax is
+ * s3express-control.region.amazonaws.com.
+ * GetBucketLifecycleConfiguration has the following special error:
Error code: NoSuchLifecycleConfiguration
+ *
Description: The lifecycle configuration does not exist.
+ *HTTP Status Code: 404 Not Found
+ *SOAP Fault Code Prefix: Client
+ *The following operations are related to
+ * GetBucketLifecycleConfiguration:
+ * GetBucketLifecycle + *
+ *+ * PutBucketLifecycle + *
+ *+ * DeleteBucketLifecycle + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To get lifecycle configuration on a bucket + * ```javascript + * // The following example retrieves lifecycle configuration on set on a bucket. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new GetBucketLifecycleConfigurationCommand(input); + * const response = await client.send(command); + * /* response is + * { + * Rules: [ + * { + * ID: "Rule for TaxDocs/", + * Prefix: "TaxDocs", + * Status: "Enabled", + * Transitions: [ + * { + * Days: 365, + * StorageClass: "STANDARD_IA" + * } + * ] + * } + * ] + * } + * *\/ + * ``` + * + * @public + */ +export declare class GetBucketLifecycleConfigurationCommand extends GetBucketLifecycleConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketLifecycleConfigurationRequest; + output: GetBucketLifecycleConfigurationOutput; + }; + sdk: { + input: GetBucketLifecycleConfigurationCommandInput; + output: GetBucketLifecycleConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLocationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLocationCommand.d.ts new file mode 100644 index 00000000..564bd490 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLocationCommand.d.ts @@ -0,0 +1,116 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketLocationOutput, GetBucketLocationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketLocationCommand}. + */ +export interface GetBucketLocationCommandInput extends GetBucketLocationRequest { +} +/** + * @public + * + * The output of {@link GetBucketLocationCommand}. + */ +export interface GetBucketLocationCommandOutput extends GetBucketLocationOutput, __MetadataBearer { +} +declare const GetBucketLocationCommand_base: { + new (input: GetBucketLocationCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
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.
+ *The following operations are related to GetBucketLocation:
+ * GetObject + *
+ *+ * CreateBucket + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To get bucket location + * ```javascript + * // The following example returns bucket location. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new GetBucketLocationCommand(input); + * const response = await client.send(command); + * /* response is + * { + * LocationConstraint: "us-west-2" + * } + * *\/ + * ``` + * + * @public + */ +export declare class GetBucketLocationCommand extends GetBucketLocationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketLocationRequest; + output: GetBucketLocationOutput; + }; + sdk: { + input: GetBucketLocationCommandInput; + output: GetBucketLocationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLoggingCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLoggingCommand.d.ts new file mode 100644 index 00000000..ab3ccbfd --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketLoggingCommand.d.ts @@ -0,0 +1,111 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketLoggingOutput, GetBucketLoggingRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketLoggingCommand}. + */ +export interface GetBucketLoggingCommandInput extends GetBucketLoggingRequest { +} +/** + * @public + * + * The output of {@link GetBucketLoggingCommand}. + */ +export interface GetBucketLoggingCommandOutput extends GetBucketLoggingOutput, __MetadataBearer { +} +declare const GetBucketLoggingCommand_base: { + new (input: GetBucketLoggingCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Returns the logging status of a bucket and the permissions users have to view and modify + * that status.
+ *The following operations are related to GetBucketLogging:
+ * CreateBucket + *
+ *+ * PutBucketLogging + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketLoggingCommand extends GetBucketLoggingCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketLoggingRequest; + output: GetBucketLoggingOutput; + }; + sdk: { + input: GetBucketLoggingCommandInput; + output: GetBucketLoggingCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketMetadataTableConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketMetadataTableConfigurationCommand.d.ts new file mode 100644 index 00000000..f8339cb9 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketMetadataTableConfigurationCommand.d.ts @@ -0,0 +1,112 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketMetadataTableConfigurationOutput, GetBucketMetadataTableConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketMetadataTableConfigurationCommand}. + */ +export interface GetBucketMetadataTableConfigurationCommandInput extends GetBucketMetadataTableConfigurationRequest { +} +/** + * @public + * + * The output of {@link GetBucketMetadataTableConfigurationCommand}. + */ +export interface GetBucketMetadataTableConfigurationCommandOutput extends GetBucketMetadataTableConfigurationOutput, __MetadataBearer { +} +declare const GetBucketMetadataTableConfigurationCommand_base: { + new (input: GetBucketMetadataTableConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl+ * Retrieves the metadata table configuration for a general purpose bucket. For more + * information, see Accelerating data + * discovery with S3 Metadata in the Amazon S3 User Guide.
+ *To use this operation, you must have the s3:GetBucketMetadataTableConfiguration permission. For more
+ * information, see Setting up
+ * permissions for configuring metadata tables in the
+ * Amazon S3 User Guide.
The following operations are related to GetBucketMetadataTableConfiguration:
Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketMetadataTableConfigurationCommand extends GetBucketMetadataTableConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketMetadataTableConfigurationRequest; + output: GetBucketMetadataTableConfigurationOutput; + }; + sdk: { + input: GetBucketMetadataTableConfigurationCommandInput; + output: GetBucketMetadataTableConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketMetricsConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketMetricsConfigurationCommand.d.ts new file mode 100644 index 00000000..80437b38 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketMetricsConfigurationCommand.d.ts @@ -0,0 +1,129 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketMetricsConfigurationOutput, GetBucketMetricsConfigurationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketMetricsConfigurationCommand}. + */ +export interface GetBucketMetricsConfigurationCommandInput extends GetBucketMetricsConfigurationRequest { +} +/** + * @public + * + * The output of {@link GetBucketMetricsConfigurationCommand}. + */ +export interface GetBucketMetricsConfigurationCommandOutput extends GetBucketMetricsConfigurationOutput, __MetadataBearer { +} +declare const GetBucketMetricsConfigurationCommand_base: { + new (input: GetBucketMetricsConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
+ * To use this operation, you must have permissions to perform the
+ * s3:GetMetricsConfiguration action. 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 Subresource Operations and Managing
+ * Access Permissions to Your Amazon S3 Resources.
For information about CloudWatch request metrics for Amazon S3, see Monitoring + * Metrics with Amazon CloudWatch.
+ *The following operations are related to
+ * GetBucketMetricsConfiguration:
+ * PutBucketMetricsConfiguration + *
+ *+ * DeleteBucketMetricsConfiguration + *
+ *+ * ListBucketMetricsConfigurations + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketMetricsConfigurationCommand extends GetBucketMetricsConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketMetricsConfigurationRequest; + output: GetBucketMetricsConfigurationOutput; + }; + sdk: { + input: GetBucketMetricsConfigurationCommandInput; + output: GetBucketMetricsConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketNotificationConfigurationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketNotificationConfigurationCommand.d.ts new file mode 100644 index 00000000..8b29de71 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketNotificationConfigurationCommand.d.ts @@ -0,0 +1,155 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketNotificationConfigurationRequest, NotificationConfiguration } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketNotificationConfigurationCommand}. + */ +export interface GetBucketNotificationConfigurationCommandInput extends GetBucketNotificationConfigurationRequest { +} +/** + * @public + * + * The output of {@link GetBucketNotificationConfigurationCommand}. + */ +export interface GetBucketNotificationConfigurationCommandOutput extends NotificationConfiguration, __MetadataBearer { +} +declare const GetBucketNotificationConfigurationCommand_base: { + new (input: GetBucketNotificationConfigurationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *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.
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.
For more information about setting and reading the notification configuration on a + * bucket, see Setting Up Notification of Bucket Events. For more information about bucket + * policies, see Using Bucket Policies.
+ *The following action is related to GetBucketNotification:
+ * PutBucketNotification + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketNotificationConfigurationCommand extends GetBucketNotificationConfigurationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketNotificationConfigurationRequest; + output: NotificationConfiguration; + }; + sdk: { + input: GetBucketNotificationConfigurationCommandInput; + output: GetBucketNotificationConfigurationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketOwnershipControlsCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketOwnershipControlsCommand.d.ts new file mode 100644 index 00000000..52000d65 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketOwnershipControlsCommand.d.ts @@ -0,0 +1,100 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketOwnershipControlsOutput, GetBucketOwnershipControlsRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketOwnershipControlsCommand}. + */ +export interface GetBucketOwnershipControlsCommandInput extends GetBucketOwnershipControlsRequest { +} +/** + * @public + * + * The output of {@link GetBucketOwnershipControlsCommand}. + */ +export interface GetBucketOwnershipControlsCommandOutput extends GetBucketOwnershipControlsOutput, __MetadataBearer { +} +declare const GetBucketOwnershipControlsCommand_base: { + new (input: GetBucketOwnershipControlsCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
For information about Amazon S3 Object Ownership, see Using Object + * Ownership.
+ *The following operations are related to GetBucketOwnershipControls:
+ * PutBucketOwnershipControls + *
+ *+ * DeleteBucketOwnershipControls + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketOwnershipControlsCommand extends GetBucketOwnershipControlsCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketOwnershipControlsRequest; + output: GetBucketOwnershipControlsOutput; + }; + sdk: { + input: GetBucketOwnershipControlsCommandInput; + output: GetBucketOwnershipControlsCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketPolicyCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketPolicyCommand.d.ts new file mode 100644 index 00000000..7f0b4448 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketPolicyCommand.d.ts @@ -0,0 +1,159 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketPolicyOutput, GetBucketPolicyRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketPolicyCommand}. + */ +export interface GetBucketPolicyCommandInput extends GetBucketPolicyRequest { +} +/** + * @public + * + * The output of {@link GetBucketPolicyCommand}. + */ +export interface GetBucketPolicyCommandOutput extends GetBucketPolicyOutput, __MetadataBearer { +} +declare const GetBucketPolicyCommand_base: { + new (input: GetBucketPolicyCommandInput): import("@smithy/smithy-client").CommandImplReturns the policy of a specified 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
+ * . Virtual-hosted-style requests aren't 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.
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.
+ * 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.
+ * 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.
+ * General purpose buckets example bucket policies + * - See Bucket policy + * examples in the Amazon S3 User Guide.
+ *+ * Directory bucket example bucket policies + * - See Example bucket policies for S3 Express One Zone in the + * Amazon S3 User Guide.
+ *
+ * Directory buckets - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
The following action is related to GetBucketPolicy:
+ * GetObject + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To get bucket policy + * ```javascript + * // The following example returns bucket policy associated with a bucket. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new GetBucketPolicyCommand(input); + * const response = await client.send(command); + * /* response is + * { + * Policy: `{"Version":"2008-10-17","Id":"LogPolicy","Statement":[{"Sid":"Enables the log delivery group to publish logs to your bucket ","Effect":"Allow","Principal":{"AWS":"111122223333"},"Action":["s3:GetBucketAcl","s3:GetObjectAcl","s3:PutObject"],"Resource":["arn:aws:s3:::policytest1/*","arn:aws:s3:::policytest1"]}]}` + * } + * *\/ + * ``` + * + * @public + */ +export declare class GetBucketPolicyCommand extends GetBucketPolicyCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketPolicyRequest; + output: GetBucketPolicyOutput; + }; + sdk: { + input: GetBucketPolicyCommandInput; + output: GetBucketPolicyCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketPolicyStatusCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketPolicyStatusCommand.d.ts new file mode 100644 index 00000000..3bc5ec9e --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketPolicyStatusCommand.d.ts @@ -0,0 +1,106 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketPolicyStatusOutput, GetBucketPolicyStatusRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketPolicyStatusCommand}. + */ +export interface GetBucketPolicyStatusCommandInput extends GetBucketPolicyStatusRequest { +} +/** + * @public + * + * The output of {@link GetBucketPolicyStatusCommand}. + */ +export interface GetBucketPolicyStatusCommandOutput extends GetBucketPolicyStatusOutput, __MetadataBearer { +} +declare const GetBucketPolicyStatusCommand_base: { + new (input: GetBucketPolicyStatusCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
For more information about when Amazon S3 considers a bucket public, see The Meaning of "Public".
+ *The following operations are related to GetBucketPolicyStatus:
+ * GetPublicAccessBlock + *
+ *+ * PutPublicAccessBlock + *
+ *+ * DeletePublicAccessBlock + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @public + */ +export declare class GetBucketPolicyStatusCommand extends GetBucketPolicyStatusCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketPolicyStatusRequest; + output: GetBucketPolicyStatusOutput; + }; + sdk: { + input: GetBucketPolicyStatusCommandInput; + output: GetBucketPolicyStatusCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketReplicationCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketReplicationCommand.d.ts new file mode 100644 index 00000000..64005d50 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketReplicationCommand.d.ts @@ -0,0 +1,195 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketReplicationOutput, GetBucketReplicationRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketReplicationCommand}. + */ +export interface GetBucketReplicationCommandInput extends GetBucketReplicationRequest { +} +/** + * @public + * + * The output of {@link GetBucketReplicationCommand}. + */ +export interface GetBucketReplicationCommandOutput extends GetBucketReplicationOutput, __MetadataBearer { +} +declare const GetBucketReplicationCommand_base: { + new (input: GetBucketReplicationCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *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.
+ *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.
For information about GetBucketReplication errors, see List of
+ * replication-related error codes
+ *
The following operations are related to GetBucketReplication:
+ * PutBucketReplication + *
+ *+ * DeleteBucketReplication + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To get replication configuration set on a bucket + * ```javascript + * // The following example returns replication configuration set on a bucket. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new GetBucketReplicationCommand(input); + * const response = await client.send(command); + * /* response is + * { + * ReplicationConfiguration: { + * Role: "arn:aws:iam::acct-id:role/example-role", + * Rules: [ + * { + * Destination: { + * Bucket: "arn:aws:s3:::destination-bucket" + * }, + * ID: "MWIwNTkwZmItMTE3MS00ZTc3LWJkZDEtNzRmODQwYzc1OTQy", + * Prefix: "Tax", + * Status: "Enabled" + * } + * ] + * } + * } + * *\/ + * ``` + * + * @public + */ +export declare class GetBucketReplicationCommand extends GetBucketReplicationCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketReplicationRequest; + output: GetBucketReplicationOutput; + }; + sdk: { + input: GetBucketReplicationCommandInput; + output: GetBucketReplicationCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketRequestPaymentCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketRequestPaymentCommand.d.ts new file mode 100644 index 00000000..3c83ccc3 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketRequestPaymentCommand.d.ts @@ -0,0 +1,101 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketRequestPaymentOutput, GetBucketRequestPaymentRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketRequestPaymentCommand}. + */ +export interface GetBucketRequestPaymentCommandInput extends GetBucketRequestPaymentRequest { +} +/** + * @public + * + * The output of {@link GetBucketRequestPaymentCommand}. + */ +export interface GetBucketRequestPaymentCommandOutput extends GetBucketRequestPaymentOutput, __MetadataBearer { +} +declare const GetBucketRequestPaymentCommand_base: { + new (input: GetBucketRequestPaymentCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
+ *The following operations are related to GetBucketRequestPayment:
+ * ListObjects + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To get bucket versioning configuration + * ```javascript + * // The following example retrieves bucket versioning configuration. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new GetBucketRequestPaymentCommand(input); + * const response = await client.send(command); + * /* response is + * { + * Payer: "BucketOwner" + * } + * *\/ + * ``` + * + * @public + */ +export declare class GetBucketRequestPaymentCommand extends GetBucketRequestPaymentCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketRequestPaymentRequest; + output: GetBucketRequestPaymentOutput; + }; + sdk: { + input: GetBucketRequestPaymentCommandInput; + output: GetBucketRequestPaymentCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketTaggingCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketTaggingCommand.d.ts new file mode 100644 index 00000000..d692b1fc --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketTaggingCommand.d.ts @@ -0,0 +1,134 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketTaggingOutput, GetBucketTaggingRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketTaggingCommand}. + */ +export interface GetBucketTaggingCommandInput extends GetBucketTaggingRequest { +} +/** + * @public + * + * The output of {@link GetBucketTaggingCommand}. + */ +export interface GetBucketTaggingCommandOutput extends GetBucketTaggingOutput, __MetadataBearer { +} +declare const GetBucketTaggingCommand_base: { + new (input: GetBucketTaggingCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
+ * GetBucketTagging has the following special error:
Error code: NoSuchTagSet
+ *
Description: There is no tag set associated with the bucket.
+ *The following operations are related to GetBucketTagging:
+ * PutBucketTagging + *
+ *+ * DeleteBucketTagging + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To get tag set associated with a bucket + * ```javascript + * // The following example returns tag set associated with a bucket + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new GetBucketTaggingCommand(input); + * const response = await client.send(command); + * /* response is + * { + * TagSet: [ + * { + * Key: "key1", + * Value: "value1" + * }, + * { + * Key: "key2", + * Value: "value2" + * } + * ] + * } + * *\/ + * ``` + * + * @public + */ +export declare class GetBucketTaggingCommand extends GetBucketTaggingCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketTaggingRequest; + output: GetBucketTaggingOutput; + }; + sdk: { + input: GetBucketTaggingCommandInput; + output: GetBucketTaggingCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketVersioningCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketVersioningCommand.d.ts new file mode 100644 index 00000000..f074d8ee --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketVersioningCommand.d.ts @@ -0,0 +1,115 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketVersioningOutput, GetBucketVersioningRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketVersioningCommand}. + */ +export interface GetBucketVersioningCommandInput extends GetBucketVersioningRequest { +} +/** + * @public + * + * The output of {@link GetBucketVersioningCommand}. + */ +export interface GetBucketVersioningCommandOutput extends GetBucketVersioningOutput, __MetadataBearer { +} +declare const GetBucketVersioningCommand_base: { + new (input: GetBucketVersioningCommandInput): import("@smithy/smithy-client").CommandImplThis operation is not supported for directory buckets.
+ *Returns the versioning state of a bucket.
+ *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.
The following operations are related to GetBucketVersioning:
+ * GetObject + *
+ *+ * PutObject + *
+ *+ * DeleteObject + *
+ *Base exception class for all service exceptions from S3 service.
+ * + * + * @example To get bucket versioning configuration + * ```javascript + * // The following example retrieves bucket versioning configuration. + * const input = { + * Bucket: "examplebucket" + * }; + * const command = new GetBucketVersioningCommand(input); + * const response = await client.send(command); + * /* response is + * { + * MFADelete: "Disabled", + * Status: "Enabled" + * } + * *\/ + * ``` + * + * @public + */ +export declare class GetBucketVersioningCommand extends GetBucketVersioningCommand_base { + /** @internal type navigation helper, not in runtime. */ + protected static __types: { + api: { + input: GetBucketVersioningRequest; + output: GetBucketVersioningOutput; + }; + sdk: { + input: GetBucketVersioningCommandInput; + output: GetBucketVersioningCommandOutput; + }; + }; +} diff --git a/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketWebsiteCommand.d.ts b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketWebsiteCommand.d.ts new file mode 100644 index 00000000..d713d9d4 --- /dev/null +++ b/node_modules/@aws-sdk/client-s3/dist-types/commands/GetBucketWebsiteCommand.d.ts @@ -0,0 +1,139 @@ +import { Command as $Command } from "@smithy/smithy-client"; +import { MetadataBearer as __MetadataBearer } from "@smithy/types"; +import { GetBucketWebsiteOutput, GetBucketWebsiteRequest } from "../models/models_0"; +import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; +/** + * @public + */ +export type { __MetadataBearer }; +export { $Command }; +/** + * @public + * + * The input for {@link GetBucketWebsiteCommand}. + */ +export interface GetBucketWebsiteCommandInput extends GetBucketWebsiteRequest { +} +/** + * @public + * + * The output of {@link GetBucketWebsiteCommand}. + */ +export interface GetBucketWebsiteCommandOutput extends GetBucketWebsiteOutput, __MetadataBearer { +} +declare const GetBucketWebsiteCommand_base: { + new (input: GetBucketWebsiteCommandInput): import("@smithy/smithy-client").CommandImplThis 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.
The following operations are related to GetBucketWebsite:
+ *