lambda-live-debugger 1.8.2 → 1.8.4

package/node_modules/@aws-sdk/client-s3/dist-types/commands/CopyObjectCommand.d.ts

@@ -27,167 +27,162 @@ declare const CopyObjectCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a copy of an object that is already stored in Amazon S3.</p>
+ * <important>
+ *             <p>End of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL).
+ *  Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs,
+ *  and REST API. However, you will no longer be able to create new Email Grantee ACLs.
+ * </p>
+ *             <p>This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region,
+ *  Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (São Paulo) Region.</p>
+ *          </important>
+ *          <p>Creates a copy of an object that is already stored in Amazon S3.</p>
  *          <note>
- *             <p>You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your
- *             object up to 5 GB in size in a single atomic action using this API. However, to copy an
- *             object greater than 5 GB, you must use the multipart upload Upload Part - Copy
- *             (UploadPartCopy) API. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjctsUsingRESTMPUapi.html">Copy Object Using the
- *                REST Multipart Upload API</a>.</p>
+ *             <p>You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your object up to 5
+ *         GB in size in a single atomic action using this API. However, to copy an object greater than 5 GB, you
+ *         must use the multipart upload Upload Part - Copy (UploadPartCopy) API. For more information, see
+ *           <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjctsUsingRESTMPUapi.html">Copy Object
+ *           Using the REST Multipart Upload API</a>.</p>
  *          </note>
- *          <p>You can copy individual objects between general purpose buckets, between directory buckets,
- *          and between general purpose buckets and directory buckets.</p>
+ *          <p>You can copy individual objects between general purpose buckets, between directory buckets, and between
+ *       general purpose buckets and directory buckets.</p>
  *          <note>
  *             <ul>
  *                <li>
- *                   <p>Amazon S3 supports copy operations using Multi-Region Access Points only as a
- *                   destination when using the Multi-Region Access Point ARN. </p>
+ *                   <p>Amazon S3 supports copy operations using Multi-Region Access Points only as a destination when
+ *             using the Multi-Region Access Point ARN. </p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets </b> -
- *                   For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com/<i>key-name</i>
+ *                      <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information about endpoints in Availability Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/endpoint-directory-buckets-AZ.html">Regional and Zonal endpoints for directory buckets in Availability Zones</a> in the
  *     <i>Amazon S3 User Guide</i>. For more information about endpoints in Local Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.html">Concepts for directory buckets in Local Zones</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *                </li>
  *                <li>
- *                   <p>VPC endpoints don't support cross-Region requests (including copies). If you're
- *                   using VPC endpoints, your source and destination buckets should be in the same
- *                   Amazon Web Services Region as your VPC endpoint.</p>
+ *                   <p>VPC endpoints don't support cross-Region requests (including copies). If you're using VPC
+ *             endpoints, your source and destination buckets should be in the same Amazon Web Services Region as your VPC
+ *             endpoint.</p>
  *                </li>
  *             </ul>
  *          </note>
- *          <p>Both the Region that you want to copy the object from and the Region that you want to
- *          copy the object to must be enabled for your account. For more information about how to
- *          enable a Region for your account, see <a href="https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html#manage-acct-regions-enable-standalone">Enable or disable a Region for standalone accounts</a> in the <i>Amazon Web Services
- *             Account Management Guide</i>.</p>
+ *          <p>Both the Region that you want to copy the object from and the Region that you want to copy the
+ *       object to must be enabled for your account. For more information about how to enable a Region for your
+ *       account, see <a href="https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html#manage-acct-regions-enable-standalone">Enable
+ *         or disable a Region for standalone accounts</a> in the <i>Amazon Web Services Account Management
+ *         Guide</i>.</p>
  *          <important>
- *             <p>Amazon S3 transfer acceleration does not support cross-Region copies. If you request a
- *             cross-Region copy using a transfer acceleration endpoint, you get a <code>400 Bad
- *                Request</code> error. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html">Transfer
- *             Acceleration</a>.</p>
+ *             <p>Amazon S3 transfer acceleration does not support cross-Region copies. If you request a cross-Region
+ *         copy using a transfer acceleration endpoint, you get a <code>400 Bad Request</code> error. For more
+ *         information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html">Transfer Acceleration</a>.</p>
  *          </important>
  *          <dl>
  *             <dt>Authentication and authorization</dt>
  *             <dd>
- *                <p>All <code>CopyObject</code> requests must be authenticated and signed by using
- *                   IAM credentials (access key ID and secret access key for the IAM identities).
- *                   All headers with the <code>x-amz-</code> prefix, including
- *                      <code>x-amz-copy-source</code>, must be signed. For more information, see
- *                      <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
+ *                <p>All <code>CopyObject</code> requests must be authenticated and signed by using IAM
+ *             credentials (access key ID and secret access key for the IAM identities). All headers with the
+ *               <code>x-amz-</code> prefix, including <code>x-amz-copy-source</code>, must be signed. For more
+ *             information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
  *                <p>
- *                   <b>Directory buckets</b> - You must use the
- *                   IAM credentials to authenticate and authorize your access to the
- *                      <code>CopyObject</code> API operation, instead of using the temporary security
- *                   credentials through the <code>CreateSession</code> API operation.</p>
- *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your
- *                   behalf.</p>
+ *                   <b>Directory buckets</b> - You must use the IAM
+ *             credentials to authenticate and authorize your access to the <code>CopyObject</code> API
+ *             operation, instead of using the temporary security credentials through the
+ *               <code>CreateSession</code> API operation.</p>
+ *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.</p>
  *             </dd>
  *             <dt>Permissions</dt>
  *             <dd>
  *                <p>You must have <i>read</i> access to the source object and
- *                      <i>write</i> access to the destination bucket.</p>
+ *               <i>write</i> access to the destination bucket.</p>
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - You
- *                         must have permissions in an IAM policy based on the source and destination
- *                         bucket types in a <code>CopyObject</code> operation.</p>
+ *                         <b>General purpose bucket permissions</b> - You must have
+ *                 permissions in an IAM policy based on the source and destination bucket types in a
+ *                   <code>CopyObject</code> operation.</p>
  *                      <ul>
  *                         <li>
- *                            <p>If the source object is in a general purpose bucket, you must have
- *                                  <b>
+ *                            <p>If the source object is in a general purpose bucket, you must have <b>
  *                                  <code>s3:GetObject</code>
- *                               </b>
- *                               permission to read the source object that is being copied. </p>
+ *                               </b> permission to read the source object that is
+ *                     being copied. </p>
  *                         </li>
  *                         <li>
- *                            <p>If the destination bucket is a general purpose bucket, you must have
- *                                  <b>
+ *                            <p>If the destination bucket is a general purpose bucket, you must have <b>
  *                                  <code>s3:PutObject</code>
- *                               </b>
- *                               permission to write the object copy to the destination bucket. </p>
+ *                               </b> permission to write the object copy to the
+ *                     destination bucket. </p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket permissions</b> -
- *                         You must have permissions in a bucket policy or an IAM identity-based policy based on the
- *                         source and destination bucket types in a <code>CopyObject</code>
- *                         operation.</p>
+ *                         <b>Directory bucket permissions</b> - You must have
+ *                 permissions in a bucket policy or an IAM identity-based policy based on the source and destination bucket types
+ *                 in a <code>CopyObject</code> operation.</p>
  *                      <ul>
  *                         <li>
- *                            <p>If the source object that you want to copy is in a
- *                               directory bucket, you must have the <b>
+ *                            <p>If the source object that you want to copy is in a directory bucket, you must have
+ *                     the <b>
  *                                  <code>s3express:CreateSession</code>
  *                               </b> permission in
- *                               the <code>Action</code> element of a policy to read the object. By
- *                               default, the session is in the <code>ReadWrite</code> mode. If you
- *                               want to restrict the access, you can explicitly set the
- *                                  <code>s3express:SessionMode</code> condition key to
- *                                  <code>ReadOnly</code> on the copy source bucket.</p>
+ *                     the <code>Action</code> element of a policy to read the object. By default, the session is
+ *                     in the <code>ReadWrite</code> mode. If you want to restrict the access, you can explicitly
+ *                     set the <code>s3express:SessionMode</code> condition key to <code>ReadOnly</code> on the
+ *                     copy source bucket.</p>
  *                         </li>
  *                         <li>
- *                            <p>If the copy destination is a directory bucket, you must have the
- *                                  <b>
+ *                            <p>If the copy destination is a directory bucket, you must have the <b>
  *                                  <code>s3express:CreateSession</code>
  *                               </b> permission in the
- *                                  <code>Action</code> element of a policy to write the object to the
- *                               destination. The <code>s3express:SessionMode</code> condition key
- *                               can't be set to <code>ReadOnly</code> on the copy destination bucket.
- *                            </p>
+ *                       <code>Action</code> element of a policy to write the object to the destination. The
+ *                       <code>s3express:SessionMode</code> condition key can't be set to <code>ReadOnly</code>
+ *                     on the copy destination bucket. </p>
  *                         </li>
  *                      </ul>
  *                      <p>If the object is encrypted with SSE-KMS, you must also have the
- *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
- *                         in IAM identity-based policies and KMS key policies for the KMS
- *                         key.</p>
- *                      <p>For example policies, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-example-bucket-policies.html">Example bucket policies for S3 Express One Zone</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for
- *                            S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                   <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM
+ *                 identity-based policies and KMS key policies for the KMS key.</p>
+ *                      <p>For example policies, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-example-bucket-policies.html">Example
+ *                   bucket policies for S3 Express One Zone</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services
+ *                   Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the
+ *                   <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                </ul>
  *             </dd>
  *             <dt>Response and special errors</dt>
  *             <dd>
- *                <p>When the request is an HTTP 1.1 request, the response is chunk encoded. When
- *                   the request is not an HTTP 1.1 request, the response would not contain the
- *                      <code>Content-Length</code>. You always need to read the entire response body
- *                   to check if the copy succeeds. </p>
+ *                <p>When the request is an HTTP 1.1 request, the response is chunk encoded. When the request is
+ *             not an HTTP 1.1 request, the response would not contain the <code>Content-Length</code>. You
+ *             always need to read the entire response body to check if the copy succeeds. </p>
  *                <ul>
  *                   <li>
- *                      <p>If the copy is successful, you receive a response with information about
- *                         the copied object.</p>
+ *                      <p>If the copy is successful, you receive a response with information about the copied
+ *                 object.</p>
  *                   </li>
  *                   <li>
- *                      <p>A copy request might return an error when Amazon S3 receives the copy request
- *                         or while Amazon S3 is copying the files. A <code>200 OK</code> response can
- *                         contain either a success or an error.</p>
+ *                      <p>A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3 is
+ *                 copying the files. A <code>200 OK</code> response can contain either a success or an
+ *                 error.</p>
  *                      <ul>
  *                         <li>
- *                            <p>If the error occurs before the copy action starts, you receive a
- *                               standard Amazon S3 error.</p>
+ *                            <p>If the error occurs before the copy action starts, you receive a standard Amazon S3
+ *                     error.</p>
  *                         </li>
  *                         <li>
- *                            <p>If the error occurs during the copy operation, the error response
- *                               is embedded in the <code>200 OK</code> response. For example, in a
- *                               cross-region copy, you may encounter throttling and receive a
- *                                  <code>200 OK</code> response. For more information, see <a href="https://repost.aws/knowledge-center/s3-resolve-200-internalerror">Resolve the Error 200 response when copying objects to
- *                                  Amazon S3</a>. The <code>200 OK</code> status code means the copy
- *                               was accepted, but it doesn't mean the copy is complete. Another
- *                               example is when you disconnect from Amazon S3 before the copy is complete,
- *                               Amazon S3 might cancel the copy and you may receive a <code>200 OK</code>
- *                               response. You must stay connected to Amazon S3 until the entire response is
- *                               successfully received and processed.</p>
- *                            <p>If you call this API operation directly, make sure to design your
- *                               application to parse the content of the response and handle it
- *                               appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The
- *                               SDKs detect the embedded error and apply error handling per your
- *                               configuration settings (including automatically retrying the request
- *                               as appropriate). If the condition persists, the SDKs throw an
- *                               exception (or, for the SDKs that don't use exceptions, they return an
- *                               error).</p>
+ *                            <p>If the error occurs during the copy operation, the error response is embedded in the
+ *                       <code>200 OK</code> response. For example, in a cross-region copy, you may encounter
+ *                     throttling and receive a <code>200 OK</code> response. For more information, see <a href="https://repost.aws/knowledge-center/s3-resolve-200-internalerror">Resolve the Error
+ *                       200 response when copying objects to Amazon S3</a>. The <code>200 OK</code> status code
+ *                     means the copy was accepted, but it doesn't mean the copy is complete. Another example is
+ *                     when you disconnect from Amazon S3 before the copy is complete, Amazon S3 might cancel the copy and
+ *                     you may receive a <code>200 OK</code> response. You must stay connected to Amazon S3 until the
+ *                     entire response is successfully received and processed.</p>
+ *                            <p>If you call this API operation directly, make sure to design your application to parse
+ *                     the content of the response and handle it appropriately. If you use Amazon Web Services SDKs, SDKs
+ *                     handle this condition. The SDKs detect the embedded error and apply error handling per
+ *                     your configuration settings (including automatically retrying the request as appropriate).
+ *                     If the condition persists, the SDKs throw an exception (or, for the SDKs that don't use
+ *                     exceptions, they return an error).</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -195,11 +190,10 @@ declare const CopyObjectCommand_base: {
  *             </dd>
  *             <dt>Charge</dt>
  *             <dd>
- *                <p>The copy request charge is based on the storage class and Region that you
- *                   specify for the destination object. The request can also result in a data
- *                   retrieval charge for the source if the source storage class bills for data
- *                   retrieval. If the copy source is in a different region, the data transfer is
- *                   billed to the copy source account. For pricing information, see <a href="http://aws.amazon.com/s3/pricing/">Amazon S3 pricing</a>.</p>
+ *                <p>The copy request charge is based on the storage class and Region that you specify for the
+ *             destination object. The request can also result in a data retrieval charge for the source if the
+ *             source storage class bills for data retrieval. If the copy source is in a different region, the
+ *             data transfer is billed to the copy source account. For pricing information, see <a href="http://aws.amazon.com/s3/pricing/">Amazon S3 pricing</a>.</p>
  *             </dd>
  *             <dt>HTTP Host header syntax</dt>
  *             <dd>
@@ -211,9 +205,12 @@ declare const CopyObjectCommand_base: {
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Amazon S3 on Outposts</b> - When you use this action with S3 on Outposts through the REST API, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the
- *                      form <code>
- *                            <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. The hostname isn't required when you use the Amazon Web Services CLI or SDKs.</p>
+ *                         <b>Amazon S3 on Outposts</b> - When you use this action with
+ *                 S3 on Outposts through the REST API, you must direct requests to the S3 on Outposts hostname. The
+ *                 S3 on Outposts hostname takes the form
+ *                     <code>
+ *                            <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>.
+ *                 The hostname isn't required when you use the Amazon Web Services CLI or SDKs.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -262,8 +259,8 @@ declare const CopyObjectCommand_base: {
  *   },
  *   MetadataDirective: "COPY" || "REPLACE",
  *   TaggingDirective: "COPY" || "REPLACE",
- *   ServerSideEncryption: "AES256" || "aws:kms" || "aws:kms:dsse",
- *   StorageClass: "STANDARD" || "REDUCED_REDUNDANCY" || "STANDARD_IA" || "ONEZONE_IA" || "INTELLIGENT_TIERING" || "GLACIER" || "DEEP_ARCHIVE" || "OUTPOSTS" || "GLACIER_IR" || "SNOW" || "EXPRESS_ONEZONE",
+ *   ServerSideEncryption: "AES256" || "aws:fsx" || "aws:kms" || "aws:kms:dsse",
+ *   StorageClass: "STANDARD" || "REDUCED_REDUNDANCY" || "STANDARD_IA" || "ONEZONE_IA" || "INTELLIGENT_TIERING" || "GLACIER" || "DEEP_ARCHIVE" || "OUTPOSTS" || "GLACIER_IR" || "SNOW" || "EXPRESS_ONEZONE" || "FSX_OPENZFS",
  *   WebsiteRedirectLocation: "STRING_VALUE",
  *   SSECustomerAlgorithm: "STRING_VALUE",
  *   SSECustomerKey: "STRING_VALUE",
@@ -298,7 +295,7 @@ declare const CopyObjectCommand_base: {
  * //   Expiration: "STRING_VALUE",
  * //   CopySourceVersionId: "STRING_VALUE",
  * //   VersionId: "STRING_VALUE",
- * //   ServerSideEncryption: "AES256" || "aws:kms" || "aws:kms:dsse",
+ * //   ServerSideEncryption: "AES256" || "aws:fsx" || "aws:kms" || "aws:kms:dsse",
  * //   SSECustomerAlgorithm: "STRING_VALUE",
  * //   SSECustomerKeyMD5: "STRING_VALUE",
  * //   SSEKMSKeyId: "STRING_VALUE",
@@ -316,8 +313,8 @@ declare const CopyObjectCommand_base: {
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
  * @throws {@link ObjectNotInActiveTierError} (client fault)
- *  <p>The source object of the COPY action is not in the active tier and is only stored in
- *          Amazon S3 Glacier.</p>
+ *  <p>The source object of the COPY action is not in the active tier and is only stored in Amazon S3
+ *       Glacier.</p>
  *
  * @throws {@link S3ServiceException}
  * <p>Base exception class for all service exceptions from S3 service.</p>

package/node_modules/@aws-sdk/client-s3/dist-types/commands/CreateBucketCommand.d.ts

@@ -27,30 +27,43 @@ declare const CreateBucketCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <note>
+ * <important>
+ *             <p>End of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL).
+ *  Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs,
+ *  and REST API. However, you will no longer be able to create new Email Grantee ACLs.
+ * </p>
+ *             <p>This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region,
+ *  Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (São Paulo) Region.</p>
+ *          </important>
+ *          <important>
+ *             <p>End of support notice: Beginning October 1, 2025, Amazon S3 will stop returning <code>DisplayName</code>. Update your applications to use canonical IDs (unique identifier for
+ *  Amazon Web Services accounts), Amazon Web Services account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of <code>DisplayName</code>.
+ * </p>
+ *             <p>This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region,
+ *  Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (São Paulo) Region.</p>
+ *          </important>
+ *          <note>
  *             <p>This action creates an Amazon S3 bucket. To create an Amazon S3 on Outposts bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_control_CreateBucket.html">
  *                   <code>CreateBucket</code>
  *                </a>.</p>
  *          </note>
- *          <p>Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a valid Amazon Web Services
- *          Access Key ID to authenticate requests. Anonymous requests are never allowed to create
- *          buckets. By creating the bucket, you become the bucket owner.</p>
- *          <p>There are two types of buckets: general purpose buckets and directory buckets. For more
- *          information about these bucket types, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html">Creating, configuring, and
- *             working with Amazon S3 buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a valid Amazon Web Services Access Key
+ *       ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the
+ *       bucket, you become the bucket owner.</p>
+ *          <p>There are two types of buckets: general purpose buckets and directory buckets. For more information about
+ *       these bucket types, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html">Creating, configuring, and working with Amazon S3
+ *         buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
  *             <ul>
  *                <li>
  *                   <p>
  *                      <b>General purpose buckets</b> - If you send your
- *                      <code>CreateBucket</code> request to the <code>s3.amazonaws.com</code> global
- *                   endpoint, the request goes to the <code>us-east-1</code> Region. So the signature
- *                   calculations in Signature Version 4 must use <code>us-east-1</code> 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> in the <i>Amazon S3 User Guide</i>.</p>
+ *               <code>CreateBucket</code> request to the <code>s3.amazonaws.com</code> global endpoint, the
+ *             request goes to the <code>us-east-1</code> Region. So the signature calculations in Signature
+ *             Version 4 must use <code>us-east-1</code> 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> in the <i>Amazon S3 User Guide</i>.</p>
  *                </li>
  *                <li>
  *                   <p>
@@ -68,91 +81,81 @@ declare const CreateBucketCommand_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - In
- *                         addition to the <code>s3:CreateBucket</code> permission, the following
- *                         permissions are required in a policy when your <code>CreateBucket</code>
- *                         request includes specific headers: </p>
+ *                         <b>General purpose bucket permissions</b> - In addition to the
+ *                   <code>s3:CreateBucket</code> permission, the following permissions are required in a policy
+ *                 when your <code>CreateBucket</code> request includes specific headers: </p>
  *                      <ul>
  *                         <li>
  *                            <p>
- *                               <b>Access control lists (ACLs)</b>
- *                               - In your <code>CreateBucket</code> request, if you specify an
- *                               access control list (ACL) and set it to <code>public-read</code>,
- *                                  <code>public-read-write</code>, <code>authenticated-read</code>, or
- *                               if you explicitly specify any other custom ACLs, both
- *                                  <code>s3:CreateBucket</code> and <code>s3:PutBucketAcl</code>
- *                               permissions are required. In your <code>CreateBucket</code> request,
- *                               if you set the ACL to <code>private</code>, or if you don't specify
- *                               any ACLs, only the <code>s3:CreateBucket</code> permission is
- *                               required. </p>
+ *                               <b>Access control lists (ACLs)</b> - In your
+ *                       <code>CreateBucket</code> request, if you specify an access control list (ACL) and set
+ *                     it to <code>public-read</code>, <code>public-read-write</code>,
+ *                       <code>authenticated-read</code>, or if you explicitly specify any other custom ACLs,
+ *                     both <code>s3:CreateBucket</code> and <code>s3:PutBucketAcl</code> permissions are
+ *                     required. In your <code>CreateBucket</code> request, if you set the ACL to
+ *                       <code>private</code>, or if you don't specify any ACLs, only the
+ *                       <code>s3:CreateBucket</code> permission is required. </p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <b>Object Lock</b> - In your
- *                                  <code>CreateBucket</code> request, if you set
- *                                  <code>x-amz-bucket-object-lock-enabled</code> to true, the
- *                                  <code>s3:PutBucketObjectLockConfiguration</code> and
- *                                  <code>s3:PutBucketVersioning</code> permissions are
- *                               required.</p>
+ *                       <code>CreateBucket</code> request, if you set
+ *                       <code>x-amz-bucket-object-lock-enabled</code> to true, the
+ *                       <code>s3:PutBucketObjectLockConfiguration</code> and <code>s3:PutBucketVersioning</code>
+ *                     permissions are required.</p>
  *                         </li>
  *                         <li>
  *                            <p>
- *                               <b>S3 Object Ownership</b> - If
- *                               your <code>CreateBucket</code> request includes the
- *                                  <code>x-amz-object-ownership</code> header, then the
- *                                  <code>s3:PutBucketOwnershipControls</code> permission is
- *                               required.</p>
+ *                               <b>S3 Object Ownership</b> - If your
+ *                       <code>CreateBucket</code> request includes the <code>x-amz-object-ownership</code>
+ *                     header, then the <code>s3:PutBucketOwnershipControls</code> permission is required.</p>
  *                            <important>
- *                               <p> To set an ACL on a bucket as part of a
- *                                     <code>CreateBucket</code> request, you must explicitly set S3
- *                                  Object Ownership for the bucket to a different value than the
- *                                  default, <code>BucketOwnerEnforced</code>. Additionally, if your
- *                                  desired bucket ACL grants public access, you must first create the
- *                                  bucket (without the bucket ACL) and then explicitly disable Block
- *                                  Public Access on the bucket before using <code>PutBucketAcl</code>
- *                                  to set the ACL. If you try to create a bucket with a public ACL,
- *                                  the request will fail. </p>
- *                               <p> For the majority of modern use cases in S3, we recommend that
- *                                  you keep all Block Public Access settings enabled and keep ACLs
- *                                  disabled. If you would like to share data with users outside of
- *                                  your account, you can use bucket policies as needed. For more
- *                                  information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your
- *                                     bucket </a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking public access to your Amazon S3 storage </a> in
- *                                  the <i>Amazon S3 User Guide</i>. </p>
+ *                               <p> To set an ACL on a bucket as part of a <code>CreateBucket</code> request, you must
+ *                       explicitly set S3 Object Ownership for the bucket to a different value than the default,
+ *                         <code>BucketOwnerEnforced</code>. Additionally, if your desired bucket ACL grants
+ *                       public access, you must first create the bucket (without the bucket ACL) and then
+ *                       explicitly disable Block Public Access on the bucket before using
+ *                         <code>PutBucketAcl</code> to set the ACL. If you try to create a bucket with a public
+ *                       ACL, the request will fail. </p>
+ *                               <p> For the majority of modern use cases in S3, we recommend that you keep all Block
+ *                       Public Access settings enabled and keep ACLs disabled. If you would like to share data
+ *                       with users outside of your account, you can use bucket policies as needed. For more
+ *                       information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of
+ *                         objects and disabling ACLs for your bucket </a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking
+ *                         public access to your Amazon S3 storage </a> in the
+ *                         <i>Amazon S3 User Guide</i>. </p>
  *                            </important>
  *                         </li>
  *                         <li>
  *                            <p>
- *                               <b>S3 Block Public Access</b> - If
- *                               your specific use case requires granting public access to your S3
- *                               resources, you can disable Block Public Access. Specifically, you can
- *                               create a new bucket with Block Public Access enabled, then separately
- *                               call the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html">
+ *                               <b>S3 Block Public Access</b> - If your specific use
+ *                     case requires granting public access to your S3 resources, you can disable Block Public
+ *                     Access. Specifically, you can create a new bucket with Block Public Access enabled, then
+ *                     separately call the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html">
  *                                  <code>DeletePublicAccessBlock</code>
  *                               </a> API. To use this operation, you must have the
- *                                  <code>s3:PutBucketPublicAccessBlock</code> permission. For more
- *                               information about S3 Block Public Access, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking public access to your Amazon S3 storage </a> in the
- *                                  <i>Amazon S3 User Guide</i>. </p>
+ *                       <code>s3:PutBucketPublicAccessBlock</code> permission. For more information about S3
+ *                     Block Public Access, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking public
+ *                       access to your Amazon S3 storage </a> in the <i>Amazon S3 User Guide</i>.
+ *                   </p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket permissions</b> -
- *                         You must have the <code>s3express:CreateBucket</code> permission in
- *                         an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- *                         For more information about directory bucket policies and permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                         <b>Directory bucket permissions</b> - You must have the
+ *                   <code>s3express:CreateBucket</code> permission in an IAM identity-based policy instead of a bucket policy.
+ *                 Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource. For more information about directory bucket policies and permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                      <important>
- *                         <p>The permissions for ACLs, Object Lock, S3 Object Ownership, and S3
- *                            Block Public Access are not supported for directory buckets. For
- *                            directory buckets, all Block Public Access settings are enabled at the
- *                            bucket level and S3 Object Ownership is set to Bucket owner enforced
- *                            (ACLs disabled). These settings can't be modified. </p>
- *                         <p>For more information about permissions for creating and working with
- *                            directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the
- *                               <i>Amazon S3 User Guide</i>. For more information about
- *                            supported S3 features for directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-one-zone.html#s3-express-features">Features of S3 Express One Zone</a> in the
- *                               <i>Amazon S3 User Guide</i>.</p>
+ *                         <p>The permissions for ACLs, Object Lock, S3 Object Ownership, and S3 Block Public Access
+ *                   are not supported for directory buckets. For directory buckets, all Block Public Access
+ *                   settings are enabled at the bucket level and S3 Object Ownership is set to Bucket owner
+ *                   enforced (ACLs disabled). These settings can't be modified. </p>
+ *                         <p>For more information about permissions for creating and working with directory buckets,
+ *                   see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a>
+ *                   in the <i>Amazon S3 User Guide</i>. For more information about supported S3
+ *                   features for directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-one-zone.html#s3-express-features">Features of
+ *                     S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                      </important>
  *                   </li>
  *                </ul>
@@ -195,6 +198,12 @@ declare const CreateBucketCommand_base: {
  *       DataRedundancy: "SingleAvailabilityZone" || "SingleLocalZone",
  *       Type: "Directory",
  *     },
+ *     Tags: [ // TagSet
+ *       { // Tag
+ *         Key: "STRING_VALUE", // required
+ *         Value: "STRING_VALUE", // required
+ *       },
+ *     ],
  *   },
  *   GrantFullControl: "STRING_VALUE",
  *   GrantRead: "STRING_VALUE",
@@ -208,6 +217,7 @@ declare const CreateBucketCommand_base: {
  * const response = await client.send(command);
  * // { // CreateBucketOutput
  * //   Location: "STRING_VALUE",
+ * //   BucketArn: "STRING_VALUE",
  * // };
  *
  * ```
@@ -219,14 +229,14 @@ declare const CreateBucketCommand_base: {
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
  * @throws {@link BucketAlreadyExists} (client fault)
- *  <p>The requested bucket name is not available. The bucket namespace is shared by all users
- *          of the system. Select a different name and try again.</p>
+ *  <p>The requested bucket name is not available. The bucket namespace is shared by all users of the
+ *       system. Select a different name and try again.</p>
  *
  * @throws {@link BucketAlreadyOwnedByYou} (client fault)
- *  <p>The bucket you tried to create already exists, and you own it. Amazon S3 returns this error
- *          in all Amazon Web Services Regions except in the North Virginia Region. For legacy compatibility, if you
- *          re-create an existing bucket that you already own in the North Virginia Region, Amazon S3
- *          returns 200 OK and resets the bucket access control lists (ACLs).</p>
+ *  <p>The bucket you tried to create already exists, and you own it. Amazon S3 returns this error in all Amazon Web Services
+ *       Regions except in the North Virginia Region. For legacy compatibility, if you re-create an existing
+ *       bucket that you already own in the North Virginia Region, Amazon S3 returns 200 OK and resets the bucket
+ *       access control lists (ACLs).</p>
  *
  * @throws {@link S3ServiceException}
  * <p>Base exception class for all service exceptions from S3 service.</p>