@aws-sdk/client-s3 3.36.0 → 3.39.0

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

@@ -6,218 +6,11 @@ export interface PutBucketAclCommandInput extends PutBucketAclRequest {
 }
 export interface PutBucketAclCommandOutput extends __MetadataBearer {
 }
-/**
- * <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>
- *
- *          <p>You can use one of the following two ways to set a bucket's permissions:</p>
- *          <ul>
- *             <li>
- *                <p>Specify the ACL in the request body</p>
- *             </li>
- *             <li>
- *                <p>Specify permissions using request headers</p>
- *             </li>
- *          </ul>
- *
- *          <note>
- *             <p>You cannot specify access permission using both the body and the request
- *             headers.</p>
- *          </note>
- *
- *          <p>Depending on your application needs, you may choose to set the ACL on a bucket using
- *          either the request body or the headers. For example, if you have an existing application
- *          that updates a bucket ACL using the request body, then you can continue to use that
- *          approach.</p>
- *
- *
- *          <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>
- *                <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>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>
- *          <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_DeleteBucket.html">DeleteBucket</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAcl.html">GetObjectAcl</a>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, PutBucketAclCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, PutBucketAclCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new PutBucketAclCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link PutBucketAclCommandInput} for command's `input` shape.
- * @see {@link PutBucketAclCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class PutBucketAclCommand extends $Command<PutBucketAclCommandInput, PutBucketAclCommandOutput, S3ClientResolvedConfig> {
     readonly input: PutBucketAclCommandInput;
     constructor(input: PutBucketAclCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<PutBucketAclCommandInput, PutBucketAclCommandOutput>;
     private serialize;
     private deserialize;

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

@@ -6,144 +6,11 @@ export interface PutBucketAnalyticsConfigurationCommandInput extends PutBucketAn
 }
 export interface PutBucketAnalyticsConfigurationCommandOutput extends __MetadataBearer {
 }
-/**
- * <p>Sets an analytics configuration for the bucket (specified by the analytics configuration
- *          ID). You can have up to 1,000 analytics configurations per bucket.</p>
- *
- *          <p>You can choose to have storage class analysis export analysis reports sent to a
- *          comma-separated values (CSV) flat file. See the <code>DataExport</code> request element.
- *          Reports are updated daily and are based on the object filters that you configure. When
- *          selecting data export, you specify a destination bucket and an optional destination prefix
- *          where the file is written. You can export the data to a destination bucket in a different
- *          account. However, the destination bucket must be in the same Region as the bucket that you
- *          are making the PUT analytics configuration to. For more information, see <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
- *             policy, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html#example-bucket-policies-use-case-9">Granting Permissions for Amazon S3 Inventory and Storage Class Analysis</a>.</p>
- *          </important>
- *
- *          <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>
- *          <ul>
- *             <li>
- *                <ul>
- *                   <li>
- *                      <p>
- *                         <i>HTTP Error: HTTP 400 Bad Request</i>
- *                      </p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Code: InvalidArgument</i>
- *                      </p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Cause: Invalid argument.</i>
- *                      </p>
- *                   </li>
- *                </ul>
- *             </li>
- *             <li>
- *                <ul>
- *                   <li>
- *                      <p>
- *                         <i>HTTP Error: HTTP 400 Bad Request</i>
- *                      </p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Code: TooManyConfigurations</i>
- *                      </p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Cause: You are attempting to create a new configuration but have
- *                         already reached the 1,000-configuration limit.</i>
- *                      </p>
- *                   </li>
- *                </ul>
- *             </li>
- *             <li>
- *                <ul>
- *                   <li>
- *                      <p>
- *                         <i>HTTP Error: HTTP 403 Forbidden</i>
- *                      </p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Code: AccessDenied</i>
- *                      </p>
- *                   </li>
- *                   <li>
- *                      <p>
- *                         <i>Cause: You are not the owner of the specified bucket, or you do
- *                         not have the s3:PutAnalyticsConfiguration bucket permission to set the
- *                         configuration on the bucket.</i>
- *                      </p>
- *                   </li>
- *                </ul>
- *             </li>
- *          </ul>
- *
- *
- *
- *
- *
- *
- *          <p class="title">
- *             <b>Related Resources</b>
- *          </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_DeleteBucketAnalyticsConfiguration.html">DeleteBucketAnalyticsConfiguration</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketAnalyticsConfigurations.html">ListBucketAnalyticsConfigurations</a>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, PutBucketAnalyticsConfigurationCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, PutBucketAnalyticsConfigurationCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new PutBucketAnalyticsConfigurationCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link PutBucketAnalyticsConfigurationCommandInput} for command's `input` shape.
- * @see {@link PutBucketAnalyticsConfigurationCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class PutBucketAnalyticsConfigurationCommand extends $Command<PutBucketAnalyticsConfigurationCommandInput, PutBucketAnalyticsConfigurationCommandOutput, S3ClientResolvedConfig> {
     readonly input: PutBucketAnalyticsConfigurationCommandInput;
     constructor(input: PutBucketAnalyticsConfigurationCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<PutBucketAnalyticsConfigurationCommandInput, PutBucketAnalyticsConfigurationCommandOutput>;
     private serialize;
     private deserialize;

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

@@ -6,85 +6,11 @@ export interface PutBucketCorsCommandInput extends PutBucketCorsRequest {
 }
 export interface PutBucketCorsCommandOutput extends __MetadataBearer {
 }
-/**
- * <p>Sets the <code>cors</code> configuration for your bucket. If the configuration exists,
- *          Amazon S3 replaces it.</p>
- *          <p>To use this operation, you must be allowed to perform the <code>s3:PutBucketCORS</code>
- *          action. By default, the bucket owner has this permission and can grant it to others.</p>
- *          <p>You set this configuration on a bucket so that the bucket can service cross-origin
- *          requests. For example, you might want to enable a request whose origin is
- *             <code>http://www.example.com</code> to access your Amazon S3 bucket at
- *             <code>my.example.bucket.com</code> by using the browser's <code>XMLHttpRequest</code>
- *          capability.</p>
- *          <p>To enable cross-origin resource sharing (CORS) on a bucket, you add the
- *             <code>cors</code> subresource to the bucket. The <code>cors</code> subresource is an XML
- *          document in which you configure rules that identify origins and the HTTP methods that can
- *          be executed on your bucket. The document is limited to 64 KB in size. </p>
- *          <p>When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a
- *          bucket, it evaluates the <code>cors</code> configuration on the bucket and uses the first
- *             <code>CORSRule</code> rule that matches the incoming browser request to enable a
- *          cross-origin request. For a rule to match, the following conditions must be met:</p>
- *          <ul>
- *             <li>
- *                <p>The request's <code>Origin</code> header must match <code>AllowedOrigin</code>
- *                elements.</p>
- *             </li>
- *             <li>
- *                <p>The request method (for example, GET, PUT, HEAD, and so on) or the
- *                   <code>Access-Control-Request-Method</code> header in case of a pre-flight
- *                   <code>OPTIONS</code> request must be one of the <code>AllowedMethod</code>
- *                elements. </p>
- *             </li>
- *             <li>
- *                <p>Every header specified in the <code>Access-Control-Request-Headers</code> request
- *                header of a pre-flight request must match an <code>AllowedHeader</code> element.
- *             </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>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketCors.html">GetBucketCors</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketCors.html">DeleteBucketCors</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, PutBucketCorsCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, PutBucketCorsCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new PutBucketCorsCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link PutBucketCorsCommandInput} for command's `input` shape.
- * @see {@link PutBucketCorsCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class PutBucketCorsCommand extends $Command<PutBucketCorsCommandInput, PutBucketCorsCommandOutput, S3ClientResolvedConfig> {
     readonly input: PutBucketCorsCommandInput;
     constructor(input: PutBucketCorsCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<PutBucketCorsCommandInput, PutBucketCorsCommandOutput>;
     private serialize;
     private deserialize;

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

@@ -6,61 +6,11 @@ export interface PutBucketEncryptionCommandInput extends PutBucketEncryptionRequ
 }
 export interface PutBucketEncryptionCommandOutput extends __MetadataBearer {
 }
-/**
- * <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. 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>
- *          <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>
- *          </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>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketEncryption.html">GetBucketEncryption</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketEncryption.html">DeleteBucketEncryption</a>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, PutBucketEncryptionCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, PutBucketEncryptionCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new PutBucketEncryptionCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link PutBucketEncryptionCommandInput} for command's `input` shape.
- * @see {@link PutBucketEncryptionCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class PutBucketEncryptionCommand extends $Command<PutBucketEncryptionCommandInput, PutBucketEncryptionCommandOutput, S3ClientResolvedConfig> {
     readonly input: PutBucketEncryptionCommandInput;
     constructor(input: PutBucketEncryptionCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<PutBucketEncryptionCommandInput, PutBucketEncryptionCommandOutput>;
     private serialize;
     private deserialize;

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

@@ -6,111 +6,11 @@ export interface PutBucketIntelligentTieringConfigurationCommandInput extends Pu
 }
 export interface PutBucketIntelligentTieringConfigurationCommandOutput extends __MetadataBearer {
 }
-/**
- * <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 two low latency and high throughput access tiers. For data that can be accessed asynchronously, you can choose to activate automatic archiving capabilities within the S3 Intelligent-Tiering storage class.</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 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>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketIntelligentTieringConfiguration.html">DeleteBucketIntelligentTieringConfiguration</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketIntelligentTieringConfiguration.html">GetBucketIntelligentTieringConfiguration</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketIntelligentTieringConfigurations.html">ListBucketIntelligentTieringConfigurations</a>
- *                </p>
- *             </li>
- *          </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>
- *          </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>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { S3Client, PutBucketIntelligentTieringConfigurationCommand } from "@aws-sdk/client-s3"; // ES Modules import
- * // const { S3Client, PutBucketIntelligentTieringConfigurationCommand } = require("@aws-sdk/client-s3"); // CommonJS import
- * const client = new S3Client(config);
- * const command = new PutBucketIntelligentTieringConfigurationCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link PutBucketIntelligentTieringConfigurationCommandInput} for command's `input` shape.
- * @see {@link PutBucketIntelligentTieringConfigurationCommandOutput} for command's `response` shape.
- * @see {@link S3ClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class PutBucketIntelligentTieringConfigurationCommand extends $Command<PutBucketIntelligentTieringConfigurationCommandInput, PutBucketIntelligentTieringConfigurationCommandOutput, S3ClientResolvedConfig> {
     readonly input: PutBucketIntelligentTieringConfigurationCommandInput;
     constructor(input: PutBucketIntelligentTieringConfigurationCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<PutBucketIntelligentTieringConfigurationCommandInput, PutBucketIntelligentTieringConfigurationCommandOutput>;
     private serialize;
     private deserialize;