@aws-sdk/client-s3 3.325.0 → 3.327.0

package/dist-types/commands/PutBucketAclCommand.d.ts

@@ -20,8 +20,8 @@ export interface PutBucketAclCommandOutput extends __MetadataBearer {
 /**
  * @public
  * <p>Sets the permissions on an existing bucket using access control lists (ACL). For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. To set
- *          the ACL of a bucket, you must have <code>WRITE_ACP</code> permission.</p>
+ *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. To set the ACL of a
+ *          bucket, you must have <code>WRITE_ACP</code> permission.</p>
  *          <p>You can use one of the following two ways to set a bucket's permissions:</p>
  *          <ul>
  *             <li>
@@ -40,49 +40,125 @@ export interface PutBucketAclCommandOutput extends __MetadataBearer {
  *          that updates a bucket ACL using the request body, then you can continue to use that
  *          approach.</p>
  *          <important>
- *             <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions.
- *             You must use policies to grant access to your bucket and the objects in it. Requests to set ACLs or update ACLs fail and
- *             return the <code>AccessControlListNotSupported</code> error code. Requests to read ACLs are still supported.
- *             For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling object ownership</a>
- *             in the <i>Amazon S3 User Guide</i>.</p>
+ *             <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs
+ *             are disabled and no longer affect permissions. You must use policies to grant access to
+ *             your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return
+ *             the <code>AccessControlListNotSupported</code> error code. Requests to read ACLs are
+ *             still supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling object
+ *                ownership</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          </important>
- *          <p>
- *             <b>Access Permissions</b>
- *          </p>
- *          <p>You can set access permissions using one of the following methods:</p>
- *          <ul>
- *             <li>
- *                <p>Specify a canned ACL with 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. Specify the canned ACL name as the
- *                value of <code>x-amz-acl</code>. If you use this header, you cannot use other access
- *                control-specific headers in your request. 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. When using these headers, you
- *                specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who
- *                will receive the permission. If you use these ACL-specific headers, you cannot use
- *                the <code>x-amz-acl</code> header to set a canned ACL. These parameters map to the
- *                set of permissions that Amazon S3 supports in an ACL. For more information, see <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>
+ *          <dl>
+ *             <dt>Permissions</dt>
+ *             <dd>
+ *                <p>You can set access permissions using one of the following methods:</p>
  *                <ul>
  *                   <li>
+ *                      <p>Specify a canned ACL with 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. Specify the canned ACL name as the
+ *                         value of <code>x-amz-acl</code>. If you use this header, you cannot use other access
+ *                         control-specific headers in your request. 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. When using these headers, you
+ *                         specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who
+ *                         will receive the permission. If you use these ACL-specific headers, you cannot use
+ *                         the <code>x-amz-acl</code> header to set a canned ACL. These parameters map to the
+ *                         set of permissions that Amazon S3 supports in an ACL. For more information, see <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-write</code> header grants create,
+ *                         overwrite, and delete objects permission to LogDelivery group predefined by Amazon S3 and
+ *                         two Amazon Web Services accounts identified by their email addresses.</p>
  *                      <p>
- *                         <code>id</code> – if the value specified is the canonical user ID of an Amazon Web Services account</p>
+ *                         <code>x-amz-grant-write: uri="http://acs.amazonaws.com/groups/s3/LogDelivery",
+ *                         id="111122223333", id="555566667777" </code>
+ *                      </p>
  *                   </li>
+ *                </ul>
+ *                <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do
+ *                   both.</p>
+ *             </dd>
+ *             <dt>Grantee Values</dt>
+ *             <dd>
+ *                <p>You can specify the person (grantee) to whom you're assigning access rights (using
+ *                   request elements) in the following ways:</p>
+ *                <ul>
  *                   <li>
+ *                      <p>By the person's ID:</p>
  *                      <p>
- *                         <code>uri</code> – if you are granting permissions to a predefined
- *                      group</p>
+ *                         <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ *                         xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
+ *                         </Grantee></code>
+ *                      </p>
+ *                      <p>DisplayName is optional and ignored in the request</p>
  *                   </li>
  *                   <li>
+ *                      <p>By URI:</p>
  *                      <p>
- *                         <code>emailAddress</code> – if the value specified is the email address of
- *                      an Amazon Web Services account</p>
+ *                         <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ *                         xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>By Email address:</p>
+ *                      <p>
+ *                         <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ *                         xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>&</Grantee></code>
+ *                      </p>
+ *                      <p>The grantee is resolved to the CanonicalUser and, in a response to a GET Object
+ *                         acl request, appears as the CanonicalUser. </p>
  *                      <note>
  *                         <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
  *                         <ul>
@@ -115,82 +191,9 @@ export interface PutBucketAclCommandOutput extends __MetadataBearer {
  *                      </note>
  *                   </li>
  *                </ul>
- *                <p>For example, the following <code>x-amz-grant-write</code> header grants create,
- *                overwrite, and delete objects permission to LogDelivery group predefined by Amazon S3 and
- *                two Amazon Web Services accounts identified by their email addresses.</p>
- *                <p>
- *                   <code>x-amz-grant-write: uri="http://acs.amazonaws.com/groups/s3/LogDelivery",
- *                   id="111122223333", id="555566667777" </code>
- *                </p>
- *             </li>
- *          </ul>
- *          <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do
- *          both.</p>
- *          <p>
- *             <b>Grantee Values</b>
- *          </p>
- *          <p>You can specify the person (grantee) to whom you're assigning access rights (using
- *          request elements) in the following ways:</p>
- *          <ul>
- *             <li>
- *                <p>By the person's ID:</p>
- *                <p>
- *                   <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                   xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
- *                   </Grantee></code>
- *                </p>
- *                <p>DisplayName is optional and ignored in the request</p>
- *             </li>
- *             <li>
- *                <p>By URI:</p>
- *                <p>
- *                   <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                   xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>
- *                </p>
- *             </li>
- *             <li>
- *                <p>By Email address:</p>
- *                <p>
- *                   <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                   xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>lt;/Grantee></code>
- *                </p>
- *                <p>The grantee is resolved to the CanonicalUser and, in a response to a GET Object
- *                acl request, appears as the CanonicalUser. </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 class="title">
- *             <b>Related Resources</b>
- *          </p>
+ *             </dd>
+ *          </dl>
+ *          <p>The following operations are related to <code>PutBucketAcl</code>:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -246,6 +249,8 @@ export interface PutBucketAclCommandOutput extends __MetadataBearer {
  * };
  * const command = new PutBucketAclCommand(input);
  * const response = await client.send(command);
+ * // {};
+ *
  * ```
  *
  * @param PutBucketAclCommandInput - {@link PutBucketAclCommandInput}
@@ -254,6 +259,8 @@ export interface PutBucketAclCommandOutput extends __MetadataBearer {
  * @see {@link PutBucketAclCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  * @example Put bucket acl
  * ```javascript

package/dist-types/commands/PutBucketAnalyticsConfigurationCommand.d.ts

@@ -27,8 +27,8 @@ export interface PutBucketAnalyticsConfigurationCommandOutput extends __Metadata
  *          selecting data export, you specify a destination bucket and an optional destination prefix
  *          where the file is written. You can export the data to a destination bucket in a different
  *          account. However, the destination bucket must be in the same Region as the bucket that you
- *          are making the PUT analytics configuration to. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html">Amazon S3 Analytics – Storage Class
- *             Analysis</a>. </p>
+ *          are making the PUT analytics configuration to. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html">Amazon S3
+ *             Analytics – Storage Class Analysis</a>. </p>
  *          <important>
  *             <p>You must create a bucket policy on the destination bucket where the exported file is
  *             written to grant permissions to Amazon S3 to write objects to the bucket. For an example
@@ -37,11 +37,10 @@ export interface PutBucketAnalyticsConfigurationCommandOutput extends __Metadata
  *          <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 class="title">
- *             <b>Special Errors</b>
- *          </p>
+ *          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>
+ *             <code>PutBucketAnalyticsConfiguration</code> has the following special errors:</p>
  *          <ul>
  *             <li>
  *                <ul>
@@ -104,9 +103,7 @@ export interface PutBucketAnalyticsConfigurationCommandOutput extends __Metadata
  *                </ul>
  *             </li>
  *          </ul>
- *          <p class="title">
- *             <b>Related Resources</b>
- *          </p>
+ *          <p>The following operations are related to <code>PutBucketAnalyticsConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -169,6 +166,8 @@ export interface PutBucketAnalyticsConfigurationCommandOutput extends __Metadata
  * };
  * const command = new PutBucketAnalyticsConfigurationCommand(input);
  * const response = await client.send(command);
+ * // {};
+ *
  * ```
  *
  * @param PutBucketAnalyticsConfigurationCommandInput - {@link PutBucketAnalyticsConfigurationCommandInput}
@@ -177,6 +176,8 @@ export interface PutBucketAnalyticsConfigurationCommandOutput extends __Metadata
  * @see {@link PutBucketAnalyticsConfigurationCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  */
 export declare class PutBucketAnalyticsConfigurationCommand extends $Command<PutBucketAnalyticsConfigurationCommandInput, PutBucketAnalyticsConfigurationCommandOutput, S3ClientResolvedConfig> {

package/dist-types/commands/PutBucketCorsCommand.d.ts

@@ -53,11 +53,9 @@ export interface PutBucketCorsCommandOutput extends __MetadataBearer {
  *             </p>
  *             </li>
  *          </ul>
- *          <p> For more information about CORS, go to <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>
+ *          <p> For more information about CORS, go to <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>The following operations are related to <code>PutBucketCors</code>:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -109,6 +107,8 @@ export interface PutBucketCorsCommandOutput extends __MetadataBearer {
  * };
  * const command = new PutBucketCorsCommand(input);
  * const response = await client.send(command);
+ * // {};
+ *
  * ```
  *
  * @param PutBucketCorsCommandInput - {@link PutBucketCorsCommandInput}
@@ -117,6 +117,8 @@ export interface PutBucketCorsCommandOutput extends __MetadataBearer {
  * @see {@link PutBucketCorsCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  * @example To set cors configuration on a bucket.
  * ```javascript

package/dist-types/commands/PutBucketEncryptionCommand.d.ts

@@ -19,28 +19,28 @@ export interface PutBucketEncryptionCommandOutput extends __MetadataBearer {
 }
 /**
  * @public
- * <p>This action uses the <code>encryption</code> subresource to configure default
- *          encryption and Amazon S3 Bucket Key for an existing bucket.</p>
- *          <p>Default encryption for a bucket can use server-side encryption with Amazon S3-managed keys
- *          (SSE-S3) or customer managed keys (SSE-KMS). If you specify default encryption
- *          using SSE-KMS, you can also configure Amazon S3 Bucket Key. When the default encryption is SSE-KMS, if
- *          you upload an object to the bucket and do not specify the KMS key to use for encryption, Amazon S3
- *          uses the default Amazon Web Services managed KMS key for your account. For information about default
- *          encryption, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">Amazon S3 default bucket encryption</a>
- *          in the <i>Amazon S3 User Guide</i>. For more information about S3 Bucket Keys,
- *          see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the <i>Amazon S3 User Guide</i>.</p>
+ * <p>This action uses the <code>encryption</code> subresource to configure default encryption
+ *          and Amazon S3 Bucket Keys for an existing bucket.</p>
+ *          <p>By default, all buckets have a default encryption configuration that
+ *          uses server-side encryption with Amazon S3 managed keys (SSE-S3).
+ *          You can optionally configure default encryption for a bucket by using server-side
+ *          encryption with an Amazon Web Services KMS key (SSE-KMS) or a customer-provided key (SSE-C). If you specify default encryption by using
+ *          SSE-KMS, you can also configure Amazon S3 Bucket Keys. For information about bucket default encryption,
+ *          see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">Amazon S3
+ *             bucket default encryption</a> in the <i>Amazon S3 User Guide</i>. For more
+ *          information about S3 Bucket Keys, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
  *          <important>
- *             <p>This action requires Amazon Web Services Signature Version 4. For more information, 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>
+ *             <p>This action requires Amazon Web Services Signature Version 4. For more information, 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>
  *          </important>
  *          <p>To use this operation, you must have permissions to perform the
  *             <code>s3:PutEncryptionConfiguration</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> in the Amazon S3 User Guide. </p>
- *          <p class="title">
- *             <b>Related Resources</b>
- *          </p>
+ *          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> in the
+ *             <i>Amazon S3 User Guide</i>. </p>
+ *          <p>The following operations are related to <code>PutBucketEncryption</code>:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -78,6 +78,8 @@ export interface PutBucketEncryptionCommandOutput extends __MetadataBearer {
  * };
  * const command = new PutBucketEncryptionCommand(input);
  * const response = await client.send(command);
+ * // {};
+ *
  * ```
  *
  * @param PutBucketEncryptionCommandInput - {@link PutBucketEncryptionCommandInput}
@@ -86,6 +88,8 @@ export interface PutBucketEncryptionCommandOutput extends __MetadataBearer {
  * @see {@link PutBucketEncryptionCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  */
 export declare class PutBucketEncryptionCommand extends $Command<PutBucketEncryptionCommandInput, PutBucketEncryptionCommandOutput, S3ClientResolvedConfig> {

package/dist-types/commands/PutBucketIntelligentTieringConfigurationCommand.d.ts

@@ -19,13 +19,12 @@ export interface PutBucketIntelligentTieringConfigurationCommandOutput extends _
 }
 /**
  * @public
- * <p>Puts a S3 Intelligent-Tiering configuration to the specified bucket.
- *       You can have up to 1,000 S3 Intelligent-Tiering configurations per bucket.</p>
+ * <p>Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to
+ *          1,000 S3 Intelligent-Tiering configurations per bucket.</p>
  *          <p>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.</p>
  *          <p>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.</p>
  *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html#sc-dynamic-data-access">Storage class for automatically optimizing frequently and infrequently accessed objects</a>.</p>
- *          <p>Operations related to
- *             <code>PutBucketIntelligentTieringConfiguration</code> include: </p>
+ *          <p>Operations related to <code>PutBucketIntelligentTieringConfiguration</code> include: </p>
  *          <ul>
  *             <li>
  *                <p>
@@ -45,62 +44,35 @@ export interface PutBucketIntelligentTieringConfigurationCommandOutput extends _
  *          </ul>
  *          <note>
  *             <p>You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically
- *             move objects stored in the S3 Intelligent-Tiering storage class to the
- *             Archive Access or Deep Archive Access tier.</p>
+ *             move objects stored in the S3 Intelligent-Tiering storage class to the Archive Access
+ *             or Deep Archive Access tier.</p>
  *          </note>
- *          <p class="title">
- *             <b>Special Errors</b>
- *          </p>
- *          <ul>
- *             <li>
- *                <p class="title">
- *                   <b>HTTP 400 Bad Request Error</b>
- *                </p>
- *                <ul>
- *                   <li>
- *                      <p>
- *                         <i>Code:</i> InvalidArgument</p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Cause:</i> Invalid Argument</p>
- *                   </li>
- *                </ul>
- *             </li>
- *             <li>
- *                <p class="title">
- *                   <b>HTTP 400 Bad Request Error</b>
- *                </p>
- *                <ul>
- *                   <li>
- *                      <p>
- *                         <i>Code:</i> TooManyConfigurations</p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Cause:</i> You are attempting to create a new configuration
- *                      but have already reached the 1,000-configuration limit. </p>
- *                   </li>
- *                </ul>
- *             </li>
- *             <li>
- *                <p class="title">
- *                   <b>HTTP 403 Forbidden Error</b>
- *                </p>
- *                <ul>
- *                   <li>
- *                      <p>
- *                         <i>Code:</i> AccessDenied</p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Cause:</i> You are not the owner of the specified bucket,
- *                      or you do not have the <code>s3:PutIntelligentTieringConfiguration</code> bucket
- *                      permission to set the configuration on the bucket. </p>
- *                   </li>
- *                </ul>
- *             </li>
- *          </ul>
+ *          <p>
+ *             <code>PutBucketIntelligentTieringConfiguration</code> has the following special errors:</p>
+ *          <dl>
+ *             <dt>HTTP 400 Bad Request Error</dt>
+ *             <dd>
+ *                <p>
+ *                   <i>Code:</i> InvalidArgument</p>
+ *                <p>
+ *                   <i>Cause:</i> Invalid Argument</p>
+ *             </dd>
+ *             <dt>HTTP 400 Bad Request Error</dt>
+ *             <dd>
+ *                <p>
+ *                   <i>Code:</i> TooManyConfigurations</p>
+ *                <p>
+ *                   <i>Cause:</i> You are attempting to create a new configuration
+ *                   but have already reached the 1,000-configuration limit. </p>
+ *             </dd>
+ *             <dt>HTTP 403 Forbidden Error</dt>
+ *             <dd>
+ *                <p>
+ *                   <i>Cause:</i> You are not the owner of the specified bucket,
+ *                   or you do not have the <code>s3:PutIntelligentTieringConfiguration</code>
+ *                   bucket permission to set the configuration on the bucket. </p>
+ *             </dd>
+ *          </dl>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -139,6 +111,8 @@ export interface PutBucketIntelligentTieringConfigurationCommandOutput extends _
  * };
  * const command = new PutBucketIntelligentTieringConfigurationCommand(input);
  * const response = await client.send(command);
+ * // {};
+ *
  * ```
  *
  * @param PutBucketIntelligentTieringConfigurationCommandInput - {@link PutBucketIntelligentTieringConfigurationCommandInput}
@@ -147,6 +121,8 @@ export interface PutBucketIntelligentTieringConfigurationCommandOutput extends _
  * @see {@link PutBucketIntelligentTieringConfigurationCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  */
 export declare class PutBucketIntelligentTieringConfigurationCommand extends $Command<PutBucketIntelligentTieringConfigurationCommandInput, PutBucketIntelligentTieringConfigurationCommandOutput, S3ClientResolvedConfig> {