@aws-sdk/client-s3 3.36.0 → 3.39.0

package/dist-cjs/commands/CreateBucketCommand.js

@@ -6,153 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Creates a new S3 bucket. To create a bucket, you must register with 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.</p>
- *          <p>Not every string is an acceptable bucket name. For information about bucket naming
- *          restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html">Bucket naming rules</a>.</p>
- *          <p>If you want to create an Amazon S3 on Outposts bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_control_CreateBucket.html">Create Bucket</a>. </p>
- *          <p>By default, the bucket is created in the US East (N. Virginia) Region. You can
- *          optionally specify a Region in the request body. You might choose a Region to optimize
- *          latency, minimize costs, or address regulatory requirements. For example, if you reside in
- *          Europe, you will probably find it advantageous to create buckets in the Europe (Ireland)
- *          Region. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro">Accessing a
- *          bucket</a>.</p>
- *          <note>
- *             <p>If you send your create bucket request to the <code>s3.amazonaws.com</code> endpoint,
- *             the request goes to the us-east-1 Region. Accordingly, 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 <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html">Virtual hosting of buckets</a>.</p>
- *          </note>
- *          <p>When creating a bucket using this operation, you can optionally specify the accounts or
- *          groups that should be granted specific permissions on the bucket. There are two ways to
- *          grant the appropriate permissions using the request headers.</p>
- *          <ul>
- *             <li>
- *                <p>Specify a canned ACL using the <code>x-amz-acl</code> request header. Amazon S3
- *                supports a set of predefined ACLs, known as <i>canned ACLs</i>. Each
- *                canned ACL has a predefined set of grantees and permissions. For more information,
- *                see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned ACL</a>.</p>
- *             </li>
- *             <li>
- *                <p>Specify access permissions explicitly using the <code>x-amz-grant-read</code>,
- *                   <code>x-amz-grant-write</code>, <code>x-amz-grant-read-acp</code>,
- *                   <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code>
- *                headers. These headers map to the set of permissions Amazon S3 supports in an ACL. For
- *                more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access control list
- *                   (ACL) overview</a>.</p>
- *                <p>You specify each grantee as a type=value pair, where the type is one of the
- *                following:</p>
- *                <ul>
- *                   <li>
- *                      <p>
- *                         <code>id</code> – if the value specified is the canonical user ID of an Amazon Web Services account</p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <code>uri</code> – if you are granting permissions to a predefined
- *                      group</p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <code>emailAddress</code> – if the value specified is the email address of
- *                      an Amazon Web Services account</p>
- *                      <note>
- *                         <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
- *                         <ul>
- *                            <li>
- *                               <p>US East (N. Virginia)</p>
- *                            </li>
- *                            <li>
- *                               <p>US West (N. California)</p>
- *                            </li>
- *                            <li>
- *                               <p> US West (Oregon)</p>
- *                            </li>
- *                            <li>
- *                               <p> Asia Pacific (Singapore)</p>
- *                            </li>
- *                            <li>
- *                               <p>Asia Pacific (Sydney)</p>
- *                            </li>
- *                            <li>
- *                               <p>Asia Pacific (Tokyo)</p>
- *                            </li>
- *                            <li>
- *                               <p>Europe (Ireland)</p>
- *                            </li>
- *                            <li>
- *                               <p>South America (São Paulo)</p>
- *                            </li>
- *                         </ul>
- *                         <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href="https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>
- *                      </note>
- *                   </li>
- *                </ul>
- *                <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>
- *                <p>
- *                   <code>x-amz-grant-read: id="11112222333", id="444455556666" </code>
- *                </p>
- *             </li>
- *          </ul>
- *          <note>
- *             <p>You can use either a canned ACL or specify access permissions explicitly. You cannot
- *             do both.</p>
- *          </note>
- *
- *          <p>
- *             <b>Permissions</b>
- *          </p>
- *          <p>If your <code>CreateBucket</code> request specifies ACL permissions and the ACL is public-read, public-read-write,
- *          authenticated-read, or if you specify access permissions explicitly through any other ACL, both
- *          <code>s3:CreateBucket</code> and <code>s3:PutBucketAcl</code> permissions are needed. If the ACL the
- *          <code>CreateBucket</code> request is private, only <code>s3:CreateBucket</code> permission is needed. </p>
- *          <p>If <code>ObjectLockEnabledForBucket</code> is set to true in your <code>CreateBucket</code> request,
- *          <code>s3:PutBucketObjectLockConfiguration</code> and <code>s3:PutBucketVersioning</code> permissions are required.</p>
- *
- *          <p>The following operations are related to <code>CreateBucket</code>:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html">PutObject</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html">DeleteBucket</a>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, CreateBucketCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, CreateBucketCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new CreateBucketCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateBucketCommandInput} for command's `input` shape.
- * @see {@link CreateBucketCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateBucketCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_location_constraint_1.getLocationConstraintPlugin(configuration));

package/dist-cjs/commands/CreateMultipartUploadCommand.js

@@ -7,292 +7,11 @@ const middleware_ssec_1 = require("@aws-sdk/middleware-ssec");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>This action initiates a multipart upload and returns an upload ID. This upload ID is
- *          used to associate all of the parts in the specific multipart upload. You specify this
- *          upload ID in each of your subsequent upload part requests (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>). You also include this
- *          upload ID in the final request to either complete or abort the multipart upload
- *          request.</p>
- *
- *          <p>For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a>.</p>
- *
- *          <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the
- *          upload must complete 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 <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config">Aborting
- *             Incomplete Multipart Uploads Using a Bucket Lifecycle Policy</a>.</p>
- *
- *          <p>For information about the permissions required to use the multipart upload API, see
- *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and
- *             Permissions</a>.</p>
- *
- *          <p>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 <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html">Authenticating
- *             Requests (Amazon Web Services Signature Version 4)</a>.</p>
- *
- *          <note>
- *             <p> 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 stop charging you for
- *             storing them only after you either complete or abort a multipart upload. </p>
- *          </note>
- *
- *          <p>You can optionally request server-side encryption. For server-side encryption, Amazon S3
- *          encrypts your data as it writes it to disks in its data centers and decrypts it when you
- *          access it. You can provide your own encryption key, or use Amazon Web Services KMS keys or Amazon S3-managed encryption keys. If you choose to provide
- *          your own encryption key, the request headers you provide in <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> requests must match the headers you used in the request to
- *          initiate the upload by using <code>CreateMultipartUpload</code>. </p>
- *          <p>To perform a multipart upload with encryption using an Amazon Web Services KMS key, the requester must
- *          have permission to the <code>kms:Decrypt</code> and <code>kms:GenerateDataKey*</code>
- *          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 <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions">Multipart upload API
- *             and permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
- *
- *          <p>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 belongs to a different account than the key, then you must have the
- *          permissions on both the key policy and your IAM user or role.</p>
- *
- *
- *          <p> For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Protecting
- *             Data Using Server-Side Encryption</a>.</p>
- *
- *          <dl>
- *             <dt>Access Permissions</dt>
- *             <dd>
- *                <p>When copying an object, you can optionally specify the accounts or groups that
- *                   should be granted specific permissions on the new object. There are two ways to
- *                   grant the permissions using the request headers:</p>
- *                <ul>
- *                   <li>
- *                      <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. For
- *                         more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned ACL</a>.</p>
- *                   </li>
- *                   <li>
- *                      <p>Specify access permissions explicitly with the
- *                            <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>,
- *                            <code>x-amz-grant-write-acp</code>, and
- *                            <code>x-amz-grant-full-control</code> headers. These parameters map to
- *                         the set of permissions that Amazon S3 supports in an ACL. For more information,
- *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL)
- *                            Overview</a>.</p>
- *                   </li>
- *                </ul>
- *                <p>You can use either a canned ACL or specify access permissions explicitly. You
- *                   cannot do both.</p>
- *             </dd>
- *             <dt>Server-Side- Encryption-Specific Request Headers</dt>
- *             <dd>
- *                <p>You can optionally tell Amazon S3 to encrypt data at rest using server-side
- *                   encryption. 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. The option you use depends on whether you want to use Amazon Web Services managed
- *                   encryption keys or provide your own encryption key. </p>
- *                <ul>
- *                   <li>
- *                      <p>Use encryption keys managed by Amazon S3 or customer managed key stored
- *                         in Amazon Web Services Key Management Service (Amazon Web Services KMS) – If you want Amazon Web Services to manage the keys
- *                         used to encrypt data, specify the following headers in the request.</p>
- *                      <ul>
- *                         <li>
- *                            <p>x-amz-server-side-encryption</p>
- *                         </li>
- *                         <li>
- *                            <p>x-amz-server-side-encryption-aws-kms-key-id</p>
- *                         </li>
- *                         <li>
- *                            <p>x-amz-server-side-encryption-context</p>
- *                         </li>
- *                      </ul>
- *                      <note>
- *                         <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but
- *                            don't provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>,
- *                            Amazon S3 uses the Amazon Web Services managed key in Amazon Web Services KMS to protect the data.</p>
- *                      </note>
- *                      <important>
- *                         <p>All GET and PUT requests for an object protected by Amazon Web Services KMS fail if
- *                            you don't make them with SSL or by using SigV4.</p>
- *                      </important>
- *                      <p>For more information about server-side encryption with KMS key (SSE-KMS),
- *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html">Protecting Data Using Server-Side Encryption with KMS keys</a>.</p>
- *                   </li>
- *                   <li>
- *                      <p>Use customer-provided encryption keys – If you want to manage your own
- *                         encryption keys, provide all the following headers in the request.</p>
- *                      <ul>
- *                         <li>
- *                            <p>x-amz-server-side-encryption-customer-algorithm</p>
- *                         </li>
- *                         <li>
- *                            <p>x-amz-server-side-encryption-customer-key</p>
- *                         </li>
- *                         <li>
- *                            <p>x-amz-server-side-encryption-customer-key-MD5</p>
- *                         </li>
- *                      </ul>
- *                      <p>For more information about server-side encryption with KMS keys (SSE-KMS),
- *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html">Protecting Data Using Server-Side Encryption with KMS keys</a>.</p>
- *                   </li>
- *                </ul>
- *             </dd>
- *             <dt>Access-Control-List (ACL)-Specific Request Headers</dt>
- *             <dd>
- *                <p>You also can use the following access control–related headers with this
- *                   operation. By default, all objects are private. Only the owner has full access
- *                   control. When adding a new object, you can grant permissions to individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then added
- *                   to the access control list (ACL) on the object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. With this
- *                   operation, you can grant access permissions using one of the following two
- *                   methods:</p>
- *                <ul>
- *                   <li>
- *                      <p>Specify a canned ACL (<code>x-amz-acl</code>) — Amazon S3 supports a set of
- *                         predefined ACLs, known as <i>canned ACLs</i>. Each canned ACL
- *                         has a predefined set of grantees and permissions. For more information, see
- *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned
- *                         ACL</a>.</p>
- *                   </li>
- *                   <li>
- *                      <p>Specify access permissions explicitly — To explicitly grant access
- *                         permissions to specific Amazon Web Services accounts or groups, use the following headers.
- *                         Each header maps to specific permissions that Amazon S3 supports in an ACL. For
- *                         more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access
- *                            Control List (ACL) Overview</a>. In the header, you specify a list of
- *                         grantees who get the specific permission. To grant permissions explicitly,
- *                         use:</p>
- *                      <ul>
- *                         <li>
- *                            <p>x-amz-grant-read</p>
- *                         </li>
- *                         <li>
- *                            <p>x-amz-grant-write</p>
- *                         </li>
- *                         <li>
- *                            <p>x-amz-grant-read-acp</p>
- *                         </li>
- *                         <li>
- *                            <p>x-amz-grant-write-acp</p>
- *                         </li>
- *                         <li>
- *                            <p>x-amz-grant-full-control</p>
- *                         </li>
- *                      </ul>
- *                      <p>You specify each grantee as a type=value pair, where the type is one of
- *                         the following:</p>
- *                      <ul>
- *                         <li>
- *                            <p>
- *                               <code>id</code> – if the value specified is the canonical user ID
- *                               of an Amazon Web Services account</p>
- *                         </li>
- *                         <li>
- *                            <p>
- *                               <code>uri</code> – if you are granting permissions to a predefined
- *                               group</p>
- *                         </li>
- *                         <li>
- *                            <p>
- *                               <code>emailAddress</code> – if the value specified is the email
- *                               address of an Amazon Web Services account</p>
- *                            <note>
- *                               <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
- *                               <ul>
- *                                  <li>
- *                                     <p>US East (N. Virginia)</p>
- *                                  </li>
- *                                  <li>
- *                                     <p>US West (N. California)</p>
- *                                  </li>
- *                                  <li>
- *                                     <p> US West (Oregon)</p>
- *                                  </li>
- *                                  <li>
- *                                     <p> Asia Pacific (Singapore)</p>
- *                                  </li>
- *                                  <li>
- *                                     <p>Asia Pacific (Sydney)</p>
- *                                  </li>
- *                                  <li>
- *                                     <p>Asia Pacific (Tokyo)</p>
- *                                  </li>
- *                                  <li>
- *                                     <p>Europe (Ireland)</p>
- *                                  </li>
- *                                  <li>
- *                                     <p>South America (São Paulo)</p>
- *                                  </li>
- *                               </ul>
- *                               <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href="https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>
- *                            </note>
- *                         </li>
- *                      </ul>
- *                      <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>
- *                      <p>
- *                         <code>x-amz-grant-read: id="11112222333", id="444455556666" </code>
- *                      </p>
- *                   </li>
- *                </ul>
- *
- *             </dd>
- *          </dl>
- *
- *          <p>The following operations are related to <code>CreateMultipartUpload</code>:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html">CompleteMultipartUpload</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html">AbortMultipartUpload</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html">ListParts</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html">ListMultipartUploads</a>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, CreateMultipartUploadCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, CreateMultipartUploadCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new CreateMultipartUploadCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateMultipartUploadCommandInput} for command's `input` shape.
- * @see {@link CreateMultipartUploadCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateMultipartUploadCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_ssec_1.getSsecPlugin(configuration));

package/dist-cjs/commands/DeleteBucketAnalyticsConfigurationCommand.js

@@ -6,64 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Deletes an analytics configuration for the bucket (specified by the analytics
- *          configuration ID).</p>
- *          <p>To use this operation, you must have permissions to perform the
- *             <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission
- *          by default. The bucket owner can grant this permission to others. For more information
- *          about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions Related to Bucket Subresource Operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing Access Permissions to Your Amazon S3
- *             Resources</a>.</p>
- *
- *          <p>For information about the Amazon S3 analytics feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html">Amazon S3 Analytics – Storage Class
- *             Analysis</a>. </p>
- *
- *          <p>The following operations are related to
- *          <code>DeleteBucketAnalyticsConfiguration</code>:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAnalyticsConfiguration.html">GetBucketAnalyticsConfiguration</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketAnalyticsConfigurations.html">ListBucketAnalyticsConfigurations</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAnalyticsConfiguration.html">PutBucketAnalyticsConfiguration</a>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, DeleteBucketAnalyticsConfigurationCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, DeleteBucketAnalyticsConfigurationCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new DeleteBucketAnalyticsConfigurationCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link DeleteBucketAnalyticsConfigurationCommandInput} for command's `input` shape.
- * @see {@link DeleteBucketAnalyticsConfigurationCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class DeleteBucketAnalyticsConfigurationCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_bucket_endpoint_1.getBucketEndpointPlugin(configuration));

package/dist-cjs/commands/DeleteBucketCommand.js

@@ -5,52 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Deletes the S3 bucket. All objects (including all object versions and delete markers) in
- *          the bucket must be deleted before the bucket itself can be deleted.</p>
- *
- *          <p class="title">
- *             <b>Related Resources</b>
- *          </p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html">CreateBucket</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html">DeleteObject</a>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, DeleteBucketCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, DeleteBucketCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new DeleteBucketCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link DeleteBucketCommandInput} for command's `input` shape.
- * @see {@link DeleteBucketCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class DeleteBucketCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/DeleteBucketCorsCommand.js

@@ -6,56 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Deletes the <code>cors</code> configuration information set for the bucket.</p>
- *          <p>To use this operation, you must have permission to perform the
- *             <code>s3:PutBucketCORS</code> action. The bucket owner has this permission by default
- *          and can grant this permission to others. </p>
- *          <p>For information about <code>cors</code>, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html">Enabling
- *             Cross-Origin Resource Sharing</a> in the <i>Amazon S3 User Guide</i>.</p>
- *
- *          <p class="title">
- *             <b>Related Resources:</b>
- *          </p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketCors.html">PutBucketCors</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/RESTOPTIONSobject.html">RESTOPTIONSobject</a>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, DeleteBucketCorsCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, DeleteBucketCorsCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new DeleteBucketCorsCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link DeleteBucketCorsCommandInput} for command's `input` shape.
- * @see {@link DeleteBucketCorsCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class DeleteBucketCorsCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_bucket_endpoint_1.getBucketEndpointPlugin(configuration));