@alliander-opensource/aws-jwt-sts 0.3.5 → 0.3.6

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

@@ -1,7 +1,7 @@
 import { Command as $Command } from "@smithy/smithy-client";
-import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutObjectAclOutput, PutObjectAclRequest } from "../models/models_1";
-import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
+import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
+import type { PutObjectAclOutput, PutObjectAclRequest } from "../models/models_0";
+import type { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
  */
@@ -27,26 +27,30 @@ declare const PutObjectAclCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <note>
+ * <important>
+ *             <p>End of support notice: As of October 1, 2025, Amazon S3 has discontinued support for Email Grantee Access Control Lists (ACLs). If you attempt to use an Email Grantee ACL in a request after October 1, 2025,
+ *  the request will receive an <code>HTTP 405</code> (Method Not Allowed) error.</p>
+ *             <p>This change affects the following Amazon Web Services Regions: US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Ireland), and South America (São Paulo).</p>
+ *          </important>
+ *          <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Uses the <code>acl</code> subresource to set the access control list (ACL) permissions
- *          for a new or existing object in an S3 bucket. You must have the <code>WRITE_ACP</code>
- *          permission to set the ACL of an object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#permissions">What
- *             permissions can I grant?</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>Uses the <code>acl</code> subresource to set the access control list (ACL) permissions for a new or
+ *       existing object in an S3 bucket. You must have the <code>WRITE_ACP</code> permission to set the ACL of
+ *       an object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#permissions">What permissions can I grant?</a> in the
+ *         <i>Amazon S3 User Guide</i>.</p>
  *          <p>This functionality is not supported for Amazon S3 on Outposts.</p>
- *          <p>Depending on your application needs, you can choose to set the ACL on an object 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, you can continue to use that approach.
- *          For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL) Overview</a>
- *          in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>Depending on your application needs, you can choose to set the ACL on an object 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, you can continue to use that approach. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL)
+ *         Overview</a> in the <i>Amazon S3 User Guide</i>.</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>
  *          <dl>
  *             <dt>Permissions</dt>
@@ -54,42 +58,37 @@ declare const PutObjectAclCommand_base: {
  *                <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 canned ACLs. Each canned ACL has
- *                         a predefined set of grantees and permissions. Specify the canned ACL name as
- *                         the value of <code>x-amz-ac</code>l. 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>
+ *                      <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. Amazon S3 supports a set
+ *                 of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and
+ *                 permissions. Specify the canned ACL name as the value of <code>x-amz-ac</code>l. 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 <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>
+ *                      <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 <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>
+ *                               <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>
+ *                               <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>
+ *                               <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>
@@ -122,32 +121,30 @@ declare const PutObjectAclCommand_base: {
  *                            </note>
  *                         </li>
  *                      </ul>
- *                      <p>For example, the following <code>x-amz-grant-read</code> header grants
- *                         list objects permission to the two Amazon Web Services accounts identified by their email
- *                         addresses.</p>
+ *                      <p>For example, the following <code>x-amz-grant-read</code> header grants list objects
+ *                 permission to the two Amazon Web Services accounts identified by their email addresses.</p>
  *                      <p>
- *                         <code>x-amz-grant-read: emailAddress="xyz@amazon.com",
- *                            emailAddress="abc@amazon.com" </code>
+ *                         <code>x-amz-grant-read: emailAddress="xyz@amazon.com", emailAddress="abc@amazon.com"
+ *                 </code>
  *                      </p>
  *                   </li>
  *                </ul>
- *                <p>You can use either a canned ACL or specify access permissions explicitly. You
- *                   cannot do both.</p>
+ *                <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. For examples of how to specify these
- *                  grantee values in JSON format, see the Amazon Web Services CLI example in <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html">
- *                    Enabling Amazon S3 server access logging</a> in the
- *                  <i>Amazon S3 User Guide</i>.</p>
+ *                <p>You can specify the person (grantee) to whom you're assigning access rights (using request
+ *             elements) in the following ways. For examples of how to specify these grantee values in JSON
+ *             format, see the Amazon Web Services CLI example in <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html"> Enabling Amazon S3 server
+ *               access logging</a> in the <i>Amazon S3 User Guide</i>.</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>
+ *                   xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
+ *                   </Grantee></code>
  *                      </p>
  *                      <p>DisplayName is optional and ignored in the request.</p>
  *                   </li>
@@ -155,17 +152,17 @@ declare const PutObjectAclCommand_base: {
  *                      <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>
+ *                   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>
+ *                   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>
+ *                      <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>
@@ -201,9 +198,9 @@ declare const PutObjectAclCommand_base: {
  *             </dd>
  *             <dt>Versioning</dt>
  *             <dd>
- *                <p>The ACL of an object is set at the object version level. By default, PUT sets
- *                   the ACL of the current version of an object. To set the ACL of a different
- *                   version, use the <code>versionId</code> subresource.</p>
+ *                <p>The ACL of an object is set at the object version level. By default, PUT sets the ACL of the
+ *             current version of an object. To set the ACL of a different version, use the
+ *               <code>versionId</code> subresource.</p>
  *             </dd>
  *          </dl>
  *          <p>The following operations are related to <code>PutObjectAcl</code>:</p>
@@ -219,11 +216,16 @@ declare const PutObjectAclCommand_base: {
  *                </p>
  *             </li>
  *          </ul>
+ *          <important>
+ *             <p>You must URL encode any signed header values that contain spaces. For example, if your header value is <code>my  file.txt</code>, containing two spaces after <code>my</code>, you must URL encode this value to <code>my%20%20file.txt</code>.</p>
+ *          </important>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
  * import { S3Client, PutObjectAclCommand } from "@aws-sdk/client-s3"; // ES Modules import
  * // const { S3Client, PutObjectAclCommand } = require("@aws-sdk/client-s3"); // CommonJS import
+ * // import type { S3ClientConfig } from "@aws-sdk/client-s3";
+ * const config = {}; // type is S3ClientConfig
  * const client = new S3Client(config);
  * const input = { // PutObjectAclRequest
  *   ACL: "private" || "public-read" || "public-read-write" || "authenticated-read" || "aws-exec-read" || "bucket-owner-read" || "bucket-owner-full-control",

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

@@ -1,7 +1,7 @@
 import { Command as $Command } from "@smithy/smithy-client";
-import { MetadataBearer as __MetadataBearer, StreamingBlobPayloadInputTypes } from "@smithy/types";
-import { PutObjectOutput, PutObjectRequest } from "../models/models_1";
-import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
+import type { MetadataBearer as __MetadataBearer, StreamingBlobPayloadInputTypes } from "@smithy/types";
+import { type PutObjectOutput, PutObjectRequest } from "../models/models_0";
+import type { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
  */
@@ -29,31 +29,27 @@ declare const PutObjectCommand_base: {
 };
 /**
  * <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>
+ *             <p>End of support notice: As of October 1, 2025, Amazon S3 has discontinued support for Email Grantee Access Control Lists (ACLs). If you attempt to use an Email Grantee ACL in a request after October 1, 2025,
+ *  the request will receive an <code>HTTP 405</code> (Method Not Allowed) error.</p>
+ *             <p>This change affects the following Amazon Web Services Regions: US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Ireland), and South America (São Paulo).</p>
  *          </important>
  *          <p>Adds an object to a bucket.</p>
  *          <note>
  *             <ul>
  *                <li>
- *                   <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added
- *                   the entire object to the bucket. You cannot use <code>PutObject</code> to only
- *                   update a single piece of metadata for an existing object. You must put the entire
- *                   object with updated metadata if you want to update some values.</p>
+ *                   <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire
+ *             object to the bucket. You cannot use <code>PutObject</code> to only update a single piece of
+ *             metadata for an existing object. You must put the entire object with updated metadata if you want
+ *             to update some values.</p>
  *                </li>
  *                <li>
- *                   <p>If your bucket uses the bucket owner enforced setting for Object Ownership,
- *                   ACLs are disabled and no longer affect permissions. All objects written to the
- *                   bucket by any account will be owned by the bucket owner.</p>
+ *                   <p>If your bucket uses the bucket owner enforced setting for Object Ownership, ACLs are disabled
+ *             and no longer affect permissions. All objects written to the bucket by any account will be owned
+ *             by the bucket owner.</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>
@@ -61,39 +57,39 @@ declare const PutObjectCommand_base: {
  *             </ul>
  *          </note>
  *          <p>Amazon S3 is a distributed system. If it receives multiple write requests for the same object
- *          simultaneously, it overwrites all but the last object written. However, Amazon S3 provides
- *          features that can modify this behavior:</p>
+ *       simultaneously, it overwrites all but the last object written. However, Amazon S3 provides features that can
+ *       modify this behavior:</p>
  *          <ul>
  *             <li>
  *                <p>
- *                   <b>S3 Object Lock</b> - To prevent objects from
- *                being deleted or overwritten, you can use <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html">Amazon S3 Object
- *                   Lock</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                   <b>S3 Object Lock</b> - To prevent objects from being deleted
+ *           or overwritten, you can use <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html">Amazon S3 Object Lock</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                <note>
  *                   <p>This functionality is not supported for directory buckets.</p>
  *                </note>
  *             </li>
  *             <li>
  *                <p>
- *                   <b>If-None-Match</b> - Uploads the object only if the object key name does not already exist in the specified bucket. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error. If a conflicting operation occurs during the upload, S3 returns a <code>409 ConditionalRequestConflict</code> response. On a 409 failure, retry the upload.</p>
+ *                   <b>If-None-Match</b> - Uploads the object only if the object
+ *           key name does not already exist in the specified bucket. Otherwise, Amazon S3 returns a <code>412
+ *             Precondition Failed</code> error. If a conflicting operation occurs during the upload, S3 returns
+ *           a <code>409 ConditionalRequestConflict</code> response. On a 409 failure, retry the upload.</p>
  *                <p>Expects the * character (asterisk).</p>
- *                <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html">Add preconditions to S3 operations with conditional requests</a> in the <i>Amazon S3 User Guide</i> or <a href="https://datatracker.ietf.org/doc/rfc7232/">RFC 7232</a>.
- *             </p>
+ *                <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html">Add preconditions to S3 operations with
+ *             conditional requests</a> in the <i>Amazon S3 User Guide</i> or <a href="https://datatracker.ietf.org/doc/rfc7232/">RFC 7232</a>. </p>
  *                <note>
  *                   <p>This functionality is not supported for S3 on Outposts.</p>
  *                </note>
  *             </li>
  *             <li>
  *                <p>
- *                   <b>S3 Versioning</b> - When you enable versioning
- *                for a bucket, if Amazon S3 receives multiple write requests for the same object
- *                simultaneously, it stores all versions of the objects. For each write request that is
- *                made to the same object, Amazon S3 automatically generates a unique version ID of that
- *                object being stored in Amazon S3. You can retrieve, replace, or delete any version of the
- *                object. For more information about versioning, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html">Adding
- *                   Objects to Versioning-Enabled Buckets</a> in the <i>Amazon S3 User
- *                   Guide</i>. For information about returning the versioning state of a
- *                bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a>. </p>
+ *                   <b>S3 Versioning</b> - When you enable versioning for a bucket,
+ *           if Amazon S3 receives multiple write requests for the same object simultaneously, it stores all versions
+ *           of the objects. For each write request that is made to the same object, Amazon S3 automatically generates
+ *           a unique version ID of that object being stored in Amazon S3. You can retrieve, replace, or delete any
+ *           version of the object. For more information about versioning, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html">Adding Objects to
+ *             Versioning-Enabled Buckets</a> in the <i>Amazon S3 User Guide</i>. For information
+ *           about returning the versioning state of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a>. </p>
  *                <note>
  *                   <p>This functionality is not supported for directory buckets.</p>
  *                </note>
@@ -105,34 +101,31 @@ declare const PutObjectCommand_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - The
- *                         following permissions are required in your policies when your
- *                            <code>PutObject</code> request includes specific headers.</p>
+ *                         <b>General purpose bucket permissions</b> - The following
+ *                 permissions are required in your policies when your <code>PutObject</code> request includes
+ *                 specific headers.</p>
  *                      <ul>
  *                         <li>
  *                            <p>
  *                               <b>
  *                                  <code>s3:PutObject</code>
- *                               </b> -
- *                               To successfully complete the <code>PutObject</code> request, you must
- *                               always have the <code>s3:PutObject</code> permission on a bucket to
- *                               add an object to it.</p>
+ *                               </b> - To successfully
+ *                     complete the <code>PutObject</code> request, you must always have the
+ *                       <code>s3:PutObject</code> permission on a bucket to add an object to it.</p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <b>
  *                                  <code>s3:PutObjectAcl</code>
- *                               </b> - To successfully change the objects ACL of your
- *                                  <code>PutObject</code> request, you must have the
- *                                  <code>s3:PutObjectAcl</code>.</p>
+ *                               </b> - To successfully change the objects ACL of your <code>PutObject</code>
+ *                     request, you must have the <code>s3:PutObjectAcl</code>.</p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <b>
  *                                  <code>s3:PutObjectTagging</code>
- *                               </b> - To successfully set the tag-set with your
- *                                  <code>PutObject</code> request, you must have the
- *                                  <code>s3:PutObjectTagging</code>.</p>
+ *                               </b> - To successfully set the tag-set with your <code>PutObject</code>
+ *                     request, you must have the <code>s3:PutObjectTagging</code>.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -145,9 +138,8 @@ declare const PutObjectCommand_base: {
  *                            <code>CreateSession</code>
  *                         </a>.</p>
  *                      <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>
+ *                   <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM
+ *                 identity-based policies and KMS key policies for the KMS key.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -156,18 +148,17 @@ declare const PutObjectCommand_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket</b> - To ensure that
- *                         data is not corrupted traversing the network, use the
- *                            <code>Content-MD5</code> header. When you use this header, Amazon S3 checks
- *                         the object against the provided MD5 value and, if they do not match, Amazon S3
- *                         returns an error. Alternatively, when the object's ETag is its MD5 digest,
- *                         you can calculate the MD5 while putting the object to Amazon S3 and compare the
- *                         returned ETag to the calculated MD5 value.</p>
+ *                         <b>General purpose bucket</b> - To ensure that data is not
+ *                 corrupted traversing the network, use the <code>Content-MD5</code> header. When you use this
+ *                 header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, Amazon S3
+ *                 returns an error. Alternatively, when the object's ETag is its MD5 digest, you can calculate
+ *                 the MD5 while putting the object to Amazon S3 and compare the returned ETag to the calculated MD5
+ *                 value.</p>
  *                   </li>
  *                   <li>
  *                      <p>
  *                         <b>Directory bucket</b> -
- *                         This functionality is not supported for directory buckets.</p>
+ *                 This functionality is not supported for directory buckets.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -178,6 +169,29 @@ declare const PutObjectCommand_base: {
  *                      <i>Bucket-name</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com</code>.</p>
  *             </dd>
  *          </dl>
+ *          <dl>
+ *             <dt>Errors</dt>
+ *             <dd>
+ *                <ul>
+ *                   <li>
+ *                      <p>You might receive an <code>InvalidRequest</code> error for several reasons. Depending on the reason for the error, you might receive one of the following messages:</p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>Cannot specify both a write offset value and user-defined object metadata for existing
+ *                     objects.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>Checksum Type mismatch occurred, expected checksum Type: sha1, actual checksum Type:
+ *                     crc32c.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>Request body cannot be empty when 'write offset' is specified.</p>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                </ul>
+ *             </dd>
+ *          </dl>
  *          <p>For more information about related Amazon S3 APIs, see the following:</p>
  *          <ul>
  *             <li>
@@ -191,11 +205,16 @@ declare const PutObjectCommand_base: {
  *                </p>
  *             </li>
  *          </ul>
+ *          <important>
+ *             <p>You must URL encode any signed header values that contain spaces. For example, if your header value is <code>my  file.txt</code>, containing two spaces after <code>my</code>, you must URL encode this value to <code>my%20%20file.txt</code>.</p>
+ *          </important>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
  * import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3"; // ES Modules import
  * // const { S3Client, PutObjectCommand } = require("@aws-sdk/client-s3"); // CommonJS import
+ * // import type { S3ClientConfig } from "@aws-sdk/client-s3";
+ * const config = {}; // type is S3ClientConfig
  * const client = new S3Client(config);
  * const input = { // PutObjectRequest
  *   ACL: "private" || "public-read" || "public-read-write" || "authenticated-read" || "aws-exec-read" || "bucket-owner-read" || "bucket-owner-full-control",
@@ -227,7 +246,7 @@ declare const PutObjectCommand_base: {
  *     "<keys>": "STRING_VALUE",
  *   },
  *   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",
+ *   StorageClass: "STANDARD" || "REDUCED_REDUNDANCY" || "STANDARD_IA" || "ONEZONE_IA" || "INTELLIGENT_TIERING" || "GLACIER" || "DEEP_ARCHIVE" || "OUTPOSTS" || "GLACIER_IR" || "SNOW" || "EXPRESS_ONEZONE" || "FSX_OPENZFS" || "FSX_ONTAP",
  *   WebsiteRedirectLocation: "STRING_VALUE",
  *   SSECustomerAlgorithm: "STRING_VALUE",
  *   SSECustomerKey: "STRING_VALUE",
@@ -273,37 +292,20 @@ declare const PutObjectCommand_base: {
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
  * @throws {@link EncryptionTypeMismatch} (client fault)
- *  <p>
- *          The existing object was created with a different encryption type.
- *          Subsequent write requests must include the appropriate encryption
- *          parameters in the request or while creating the session.
- *       </p>
+ *  <p> The existing object was created with a different encryption type. Subsequent write requests must
+ *       include the appropriate encryption parameters in the request or while creating the session. </p>
  *
  * @throws {@link InvalidRequest} (client fault)
- *  <p>You may receive this error in multiple cases. Depending on the reason for the error, you may receive one of the messages below:</p>
- *          <ul>
- *             <li>
- *                <p>Cannot specify both a write offset value and user-defined object metadata for existing objects.</p>
- *             </li>
- *             <li>
- *                <p>Checksum Type mismatch occurred, expected checksum Type: sha1, actual checksum Type: crc32c.</p>
- *             </li>
- *             <li>
- *                <p>Request body cannot be empty when 'write offset' is specified.</p>
- *             </li>
- *          </ul>
+ *  <p>A parameter or header in your request isn't valid. For details, see the description of this API
+ *       operation.</p>
  *
  * @throws {@link InvalidWriteOffset} (client fault)
- *  <p>
- *          The write offset value that you specified does not match the current object size.
- *       </p>
+ *  <p> The write offset value that you specified does not match the current object size. </p>
  *
  * @throws {@link TooManyParts} (client fault)
- *  <p>
- *          You have attempted to add more parts than the maximum of 10000
- *          that are allowed for this object. You can use the CopyObject operation
- *          to copy this object to another and then add more data to the newly copied object.
- *       </p>
+ *  <p> You have attempted to add more parts than the maximum of 10000 that are allowed for this object.
+ *       You can use the CopyObject operation to copy this object to another and then add more data to the newly
+ *       copied object. </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/PutObjectLegalHoldCommand.d.ts

@@ -1,7 +1,7 @@
 import { Command as $Command } from "@smithy/smithy-client";
-import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutObjectLegalHoldOutput, PutObjectLegalHoldRequest } from "../models/models_1";
-import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
+import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
+import type { PutObjectLegalHoldOutput, PutObjectLegalHoldRequest } from "../models/models_0";
+import type { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
  */
@@ -30,15 +30,18 @@ declare const PutObjectLegalHoldCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Applies a legal hold configuration to the specified object. For more information, see
- *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">Locking
- *             Objects</a>.</p>
+ *          <p>Applies a legal hold configuration to the specified object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">Locking Objects</a>.</p>
  *          <p>This functionality is not supported for Amazon S3 on Outposts.</p>
+ *          <important>
+ *             <p>You must URL encode any signed header values that contain spaces. For example, if your header value is <code>my  file.txt</code>, containing two spaces after <code>my</code>, you must URL encode this value to <code>my%20%20file.txt</code>.</p>
+ *          </important>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
  * import { S3Client, PutObjectLegalHoldCommand } from "@aws-sdk/client-s3"; // ES Modules import
  * // const { S3Client, PutObjectLegalHoldCommand } = require("@aws-sdk/client-s3"); // CommonJS import
+ * // import type { S3ClientConfig } from "@aws-sdk/client-s3";
+ * const config = {}; // type is S3ClientConfig
  * const client = new S3Client(config);
  * const input = { // PutObjectLegalHoldRequest
  *   Bucket: "STRING_VALUE", // required