aws-sdk-s3 1.120.1 → 1.122.0

data/lib/aws-sdk-s3/client.rb

@@ -956,166 +956,169 @@ module Aws::S3
     # endpoint, you get a 400 `Bad Request` error. For more information, see
     # [Transfer Acceleration][4].
     #
-    # **Metadata**
-    #
-    # When copying an object, you can preserve all metadata (default) or
-    # specify new metadata. However, the ACL is not preserved and is set to
-    # private for the user making the request. To override the default ACL
-    # setting, specify a new ACL when generating a copy request. For more
-    # information, see [Using ACLs][5].
-    #
-    # To specify whether you want the object metadata copied from the source
-    # object or replaced with metadata provided in the request, you can
-    # optionally add the `x-amz-metadata-directive` header. When you grant
-    # permissions, you can use the `s3:x-amz-metadata-directive` condition
-    # key to enforce certain metadata behavior when objects are uploaded.
-    # For more information, see [Specifying Conditions in a Policy][6] in
-    # the *Amazon S3 User Guide*. For a complete list of Amazon S3-specific
-    # condition keys, see [Actions, Resources, and Condition Keys for Amazon
-    # S3][7].
-    #
-    # <note markdown="1"> `x-amz-website-redirect-location` is unique to each object and must be
-    # specified in the request headers to copy the value.
+    # Metadata
+    #
+    # : When copying an object, you can preserve all metadata (default) or
+    #   specify new metadata. However, the ACL is not preserved and is set
+    #   to private for the user making the request. To override the default
+    #   ACL setting, specify a new ACL when generating a copy request. For
+    #   more information, see [Using ACLs][5].
+    #
+    #   To specify whether you want the object metadata copied from the
+    #   source object or replaced with metadata provided in the request, you
+    #   can optionally add the `x-amz-metadata-directive` header. When you
+    #   grant permissions, you can use the `s3:x-amz-metadata-directive`
+    #   condition key to enforce certain metadata behavior when objects are
+    #   uploaded. For more information, see [Specifying Conditions in a
+    #   Policy][6] in the *Amazon S3 User Guide*. For a complete list of
+    #   Amazon S3-specific condition keys, see [Actions, Resources, and
+    #   Condition Keys for Amazon S3][7].
+    #
+    #   <note markdown="1"> `x-amz-website-redirect-location` is unique to each object and must
+    #   be specified in the request headers to copy the value.
     #
-    #  </note>
-    #
-    # **x-amz-copy-source-if Headers**
-    #
-    # To only copy an object under certain conditions, such as whether the
-    # `Etag` matches or whether the object was modified before or after a
-    # specified date, use the following request parameters:
+    #    </note>
     #
-    # * `x-amz-copy-source-if-match`
+    # x-amz-copy-source-if Headers
     #
-    # * `x-amz-copy-source-if-none-match`
+    # : To only copy an object under certain conditions, such as whether the
+    #   `Etag` matches or whether the object was modified before or after a
+    #   specified date, use the following request parameters:
     #
-    # * `x-amz-copy-source-if-unmodified-since`
+    #   * `x-amz-copy-source-if-match`
     #
-    # * `x-amz-copy-source-if-modified-since`
+    #   * `x-amz-copy-source-if-none-match`
     #
-    # If both the `x-amz-copy-source-if-match` and
-    # `x-amz-copy-source-if-unmodified-since` headers are present in the
-    # request and evaluate as follows, Amazon S3 returns `200 OK` and copies
-    # the data:
+    #   * `x-amz-copy-source-if-unmodified-since`
     #
-    # * `x-amz-copy-source-if-match` condition evaluates to true
+    #   * `x-amz-copy-source-if-modified-since`
     #
-    # * `x-amz-copy-source-if-unmodified-since` condition evaluates to false
+    #   If both the `x-amz-copy-source-if-match` and
+    #   `x-amz-copy-source-if-unmodified-since` headers are present in the
+    #   request and evaluate as follows, Amazon S3 returns `200 OK` and
+    #   copies the data:
     #
-    # If both the `x-amz-copy-source-if-none-match` and
-    # `x-amz-copy-source-if-modified-since` headers are present in the
-    # request and evaluate as follows, Amazon S3 returns the `412
-    # Precondition Failed` response code:
+    #   * `x-amz-copy-source-if-match` condition evaluates to true
     #
-    # * `x-amz-copy-source-if-none-match` condition evaluates to false
+    #   * `x-amz-copy-source-if-unmodified-since` condition evaluates to
+    #     false
     #
-    # * `x-amz-copy-source-if-modified-since` condition evaluates to true
+    #   If both the `x-amz-copy-source-if-none-match` and
+    #   `x-amz-copy-source-if-modified-since` headers are present in the
+    #   request and evaluate as follows, Amazon S3 returns the `412
+    #   Precondition Failed` response code:
     #
-    # <note markdown="1"> All headers with the `x-amz-` prefix, including `x-amz-copy-source`,
-    # must be signed.
+    #   * `x-amz-copy-source-if-none-match` condition evaluates to false
     #
-    #  </note>
+    #   * `x-amz-copy-source-if-modified-since` condition evaluates to true
     #
-    # **Server-side encryption**
-    #
-    # Amazon S3 automatically encrypts all new objects that are copied to an
-    # S3 bucket. When copying an object, if you don't specify encryption
-    # information in your copy request, the encryption setting of the target
-    # object is set to the default encryption configuration of the
-    # destination bucket. By default, all buckets have a base level of
-    # encryption configuration that uses server-side encryption with Amazon
-    # S3 managed keys (SSE-S3). If the destination bucket has a default
-    # encryption configuration that uses server-side encryption with an Key
-    # Management Service (KMS) key (SSE-KMS), or a customer-provided
-    # encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a
-    # customer-provided key to encrypt the target object copy. When you
-    # perform a CopyObject operation, if you want to use a different type of
-    # encryption setting for the target object, you can use other
-    # appropriate encryption-related headers to encrypt the target object
-    # with a KMS key, an Amazon S3 managed key, or a customer-provided key.
-    # With server-side encryption, Amazon S3 encrypts your data as it writes
-    # it to disks in its data centers and decrypts the data when you access
-    # it. If the encryption setting in your request is different from the
-    # default encryption configuration of the destination bucket, the
-    # encryption setting in your request takes precedence. If the source
-    # object for the copy is stored in Amazon S3 using SSE-C, you must
-    # provide the necessary encryption information in your request so that
-    # Amazon S3 can decrypt the object for copying. For more information
-    # about server-side encryption, see [Using Server-Side Encryption][8].
-    #
-    # If a target object uses SSE-KMS, you can enable an S3 Bucket Key for
-    # the object. For more information, see [Amazon S3 Bucket Keys][9] in
-    # the *Amazon S3 User Guide*.
+    #   <note markdown="1"> All headers with the `x-amz-` prefix, including `x-amz-copy-source`,
+    #   must be signed.
     #
-    # **Access Control List (ACL)-Specific Request Headers**
+    #    </note>
     #
-    # When copying an object, you can optionally use headers to grant
-    # ACL-based permissions. By default, all objects are private. Only the
-    # owner has full access control. When adding a new object, you can grant
-    # permissions to individual Amazon Web Services accounts or to
-    # predefined groups defined by Amazon S3. These permissions are then
-    # added to the ACL on the object. For more information, see [Access
-    # Control List (ACL) Overview][10] and [Managing ACLs Using the REST
-    # API][11].
+    # Server-side encryption
+    #
+    # : Amazon S3 automatically encrypts all new objects that are copied to
+    #   an S3 bucket. When copying an object, if you don't specify
+    #   encryption information in your copy request, the encryption setting
+    #   of the target object is set to the default encryption configuration
+    #   of the destination bucket. By default, all buckets have a base level
+    #   of encryption configuration that uses server-side encryption with
+    #   Amazon S3 managed keys (SSE-S3). If the destination bucket has a
+    #   default encryption configuration that uses server-side encryption
+    #   with an Key Management Service (KMS) key (SSE-KMS), or a
+    #   customer-provided encryption key (SSE-C), Amazon S3 uses the
+    #   corresponding KMS key, or a customer-provided key to encrypt the
+    #   target object copy.
+    #
+    #   When you perform a CopyObject operation, if you want to use a
+    #   different type of encryption setting for the target object, you can
+    #   use other appropriate encryption-related headers to encrypt the
+    #   target object with a KMS key, an Amazon S3 managed key, or a
+    #   customer-provided key. With server-side encryption, Amazon S3
+    #   encrypts your data as it writes it to disks in its data centers and
+    #   decrypts the data when you access it. If the encryption setting in
+    #   your request is different from the default encryption configuration
+    #   of the destination bucket, the encryption setting in your request
+    #   takes precedence. If the source object for the copy is stored in
+    #   Amazon S3 using SSE-C, you must provide the necessary encryption
+    #   information in your request so that Amazon S3 can decrypt the object
+    #   for copying. For more information about server-side encryption, see
+    #   [Using Server-Side Encryption][8].
+    #
+    #   If a target object uses SSE-KMS, you can enable an S3 Bucket Key for
+    #   the object. For more information, see [Amazon S3 Bucket Keys][9] in
+    #   the *Amazon S3 User Guide*.
+    #
+    # Access Control List (ACL)-Specific Request Headers
+    #
+    # : When copying an object, you can optionally use headers to grant
+    #   ACL-based permissions. By default, all objects are private. Only the
+    #   owner has full access control. When adding a new object, you can
+    #   grant permissions to individual Amazon Web Services accounts or to
+    #   predefined groups defined by Amazon S3. These permissions are then
+    #   added to the ACL on the object. For more information, see [Access
+    #   Control List (ACL) Overview][10] and [Managing ACLs Using the REST
+    #   API][11].
     #
-    # If the bucket that you're copying objects to uses the bucket owner
-    # enforced setting for S3 Object Ownership, ACLs are disabled and no
-    # longer affect permissions. Buckets that use this setting only accept
-    # PUT requests that don't specify an ACL or PUT requests that specify
-    # bucket owner full control ACLs, such as the
-    # `bucket-owner-full-control` canned ACL or an equivalent form of this
-    # ACL expressed in the XML format.
+    #   If the bucket that you're copying objects to uses the bucket owner
+    #   enforced setting for S3 Object Ownership, ACLs are disabled and no
+    #   longer affect permissions. Buckets that use this setting only accept
+    #   PUT requests that don't specify an ACL or PUT requests that specify
+    #   bucket owner full control ACLs, such as the
+    #   `bucket-owner-full-control` canned ACL or an equivalent form of this
+    #   ACL expressed in the XML format.
     #
-    # For more information, see [ Controlling ownership of objects and
-    # disabling ACLs][12] in the *Amazon S3 User Guide*.
+    #   For more information, see [ Controlling ownership of objects and
+    #   disabling ACLs][12] in the *Amazon S3 User Guide*.
     #
-    # <note markdown="1"> If your bucket uses the bucket owner enforced setting for Object
-    # Ownership, all objects written to the bucket by any account will be
-    # owned by the bucket owner.
+    #   <note markdown="1"> If your bucket uses the bucket owner enforced setting for Object
+    #   Ownership, all objects written to the bucket by any account will be
+    #   owned by the bucket owner.
     #
-    #  </note>
+    #    </note>
     #
-    # **Checksums**
+    # Checksums
     #
-    # When copying an object, if it has a checksum, that checksum will be
-    # copied to the new object by default. When you copy the object over,
-    # you may optionally specify a different checksum algorithm to use with
-    # the `x-amz-checksum-algorithm` header.
+    # : When copying an object, if it has a checksum, that checksum will be
+    #   copied to the new object by default. When you copy the object over,
+    #   you may optionally specify a different checksum algorithm to use
+    #   with the `x-amz-checksum-algorithm` header.
     #
-    # **Storage Class Options**
+    # Storage Class Options
     #
-    # You can use the `CopyObject` action to change the storage class of an
-    # object that is already stored in Amazon S3 using the `StorageClass`
-    # parameter. For more information, see [Storage Classes][13] in the
-    # *Amazon S3 User Guide*.
+    # : You can use the `CopyObject` action to change the storage class of
+    #   an object that is already stored in Amazon S3 using the
+    #   `StorageClass` parameter. For more information, see [Storage
+    #   Classes][13] in the *Amazon S3 User Guide*.
     #
-    # **Versioning**
+    #   If the source object's storage class is GLACIER, you must restore a
+    #   copy of this object before you can use it as a source object for the
+    #   copy operation. For more information, see [RestoreObject][14]. For
+    #   more information, see [Copying Objects][15].
     #
-    # By default, `x-amz-copy-source` identifies the current version of an
-    # object to copy. If the current version is a delete marker, Amazon S3
-    # behaves as if the object was deleted. To copy a different version, use
-    # the `versionId` subresource.
+    # Versioning
     #
-    # If you enable versioning on the target bucket, Amazon S3 generates a
-    # unique version ID for the object being copied. This version ID is
-    # different from the version ID of the source object. Amazon S3 returns
-    # the version ID of the copied object in the `x-amz-version-id` response
-    # header in the response.
+    # : By default, `x-amz-copy-source` identifies the current version of an
+    #   object to copy. If the current version is a delete marker, Amazon S3
+    #   behaves as if the object was deleted. To copy a different version,
+    #   use the `versionId` subresource.
     #
-    # If you do not enable versioning or suspend it on the target bucket,
-    # the version ID that Amazon S3 generates is always null.
+    #   If you enable versioning on the target bucket, Amazon S3 generates a
+    #   unique version ID for the object being copied. This version ID is
+    #   different from the version ID of the source object. Amazon S3
+    #   returns the version ID of the copied object in the
+    #   `x-amz-version-id` response header in the response.
     #
-    # If the source object's storage class is GLACIER, you must restore a
-    # copy of this object before you can use it as a source object for the
-    # copy operation. For more information, see [RestoreObject][14].
+    #   If you do not enable versioning or suspend it on the target bucket,
+    #   the version ID that Amazon S3 generates is always null.
     #
     # The following operations are related to `CopyObject`:
     #
-    # * [PutObject][15]
-    #
-    # * [GetObject][16]
+    # * [PutObject][16]
     #
-    # For more information, see [Copying Objects][17].
+    # * [GetObject][17]
     #
     #
     #
@@ -1133,9 +1136,9 @@ module Aws::S3
     # [12]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html
     # [13]: https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html
     # [14]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html
-    # [15]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html
-    # [16]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html
-    # [17]: https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html
+    # [15]: https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html
+    # [16]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html
+    # [17]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html
     #
     # @option params [String] :acl
     #   The canned ACL to apply to the object.
@@ -1470,7 +1473,7 @@ module Aws::S3
     #     metadata_directive: "COPY", # accepts COPY, REPLACE
     #     tagging_directive: "COPY", # accepts COPY, REPLACE
     #     server_side_encryption: "AES256", # accepts AES256, aws:kms
-    #     storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR
+    #     storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR, SNOW
     #     website_redirect_location: "WebsiteRedirectLocation",
     #     sse_customer_algorithm: "SSECustomerAlgorithm",
     #     sse_customer_key: "SSECustomerKey",
@@ -1547,100 +1550,102 @@ module Aws::S3
     #
     #  </note>
     #
-    # **Access control lists (ACLs)**
+    # Access control lists (ACLs)
     #
-    # When creating a bucket using this operation, you can optionally
-    # configure the bucket ACL to specify the accounts or groups that should
-    # be granted specific permissions on the bucket.
+    # : When creating a bucket using this operation, you can optionally
+    #   configure the bucket ACL to specify the accounts or groups that
+    #   should be granted specific permissions on the bucket.
     #
-    # If your CreateBucket request sets bucket owner enforced for S3 Object
-    # Ownership and specifies a bucket ACL that provides access to an
-    # external Amazon Web Services account, your request fails with a `400`
-    # error and returns the `InvalidBucketAclWithObjectOwnership` error
-    # code. For more information, see [Controlling object ownership][5] in
-    # the *Amazon S3 User Guide*.
+    #   If your CreateBucket request sets bucket owner enforced for S3
+    #   Object Ownership and specifies a bucket ACL that provides access to
+    #   an external Amazon Web Services account, your request fails with a
+    #   `400` error and returns the `InvalidBucketAclWithObjectOwnership`
+    #   error code. For more information, see [Controlling object
+    #   ownership][5] in the *Amazon S3 User Guide*.
     #
-    # There are two ways to grant the appropriate permissions using the
-    # request headers.
+    #   There are two ways to grant the appropriate permissions using the
+    #   request headers.
     #
-    # * Specify a canned ACL using the `x-amz-acl` 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. For
-    #   more information, see [Canned ACL][6].
+    #   * Specify a canned ACL using the `x-amz-acl` 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. For
+    #     more information, see [Canned ACL][6].
     #
-    # * Specify access permissions explicitly using the `x-amz-grant-read`,
-    #   `x-amz-grant-write`, `x-amz-grant-read-acp`,
-    #   `x-amz-grant-write-acp`, and `x-amz-grant-full-control` headers.
-    #   These headers map to the set of permissions Amazon S3 supports in an
-    #   ACL. For more information, see [Access control list (ACL)
-    #   overview][7].
+    #   * Specify access permissions explicitly using the
+    #     `x-amz-grant-read`, `x-amz-grant-write`, `x-amz-grant-read-acp`,
+    #     `x-amz-grant-write-acp`, and `x-amz-grant-full-control` headers.
+    #     These headers map to the set of permissions Amazon S3 supports in
+    #     an ACL. For more information, see [Access control list (ACL)
+    #     overview][7].
     #
-    #   You specify each grantee as a type=value pair, where the type is one
-    #   of the following:
+    #     You specify each grantee as a type=value pair, where the type is
+    #     one of the following:
     #
-    #   * `id` – if the value specified is the canonical user ID of an
-    #     Amazon Web Services account
+    #     * `id` – if the value specified is the canonical user ID of an
+    #       Amazon Web Services account
     #
-    #   * `uri` – if you are granting permissions to a predefined group
+    #     * `uri` – if you are granting permissions to a predefined group
     #
-    #   * `emailAddress` – if the value specified is the email address of an
-    #     Amazon Web Services account
+    #     * `emailAddress` – if the value specified is the email address of
+    #       an Amazon Web Services account
     #
-    #     <note markdown="1"> Using email addresses to specify a grantee is only supported in
-    #     the following Amazon Web Services Regions:
+    #       <note markdown="1"> Using email addresses to specify a grantee is only supported in
+    #       the following Amazon Web Services Regions:
     #
-    #      * US East (N. Virginia)
+    #        * US East (N. Virginia)
     #
-    #     * US West (N. California)
+    #       * US West (N. California)
     #
-    #     * US West (Oregon)
+    #       * US West (Oregon)
     #
-    #     * Asia Pacific (Singapore)
+    #       * Asia Pacific (Singapore)
     #
-    #     * Asia Pacific (Sydney)
+    #       * Asia Pacific (Sydney)
     #
-    #     * Asia Pacific (Tokyo)
+    #       * Asia Pacific (Tokyo)
     #
-    #     * Europe (Ireland)
+    #       * Europe (Ireland)
     #
-    #     * South America (São Paulo)
+    #       * South America (São Paulo)
     #
-    #      For a list of all the Amazon S3 supported Regions and endpoints,
-    #     see [Regions and Endpoints][8] in the Amazon Web Services General
-    #     Reference.
+    #        For a list of all the Amazon S3 supported Regions and endpoints,
+    #       see [Regions and Endpoints][8] in the Amazon Web Services
+    #       General Reference.
     #
-    #      </note>
+    #        </note>
     #
-    #   For example, the following `x-amz-grant-read` header grants the
-    #   Amazon Web Services accounts identified by account IDs permissions
-    #   to read object data and its metadata:
+    #     For example, the following `x-amz-grant-read` header grants the
+    #     Amazon Web Services accounts identified by account IDs permissions
+    #     to read object data and its metadata:
     #
-    #   `x-amz-grant-read: id="11112222333", id="444455556666" `
+    #     `x-amz-grant-read: id="11112222333", id="444455556666" `
     #
-    # <note markdown="1"> You can use either a canned ACL or specify access permissions
-    # explicitly. You cannot do both.
+    #   <note markdown="1"> You can use either a canned ACL or specify access permissions
+    #   explicitly. You cannot do both.
     #
-    #  </note>
+    #    </note>
     #
-    # **Permissions**
+    # Permissions
     #
-    # In addition to `s3:CreateBucket`, the following permissions are
-    # required when your CreateBucket includes specific headers:
+    # : In addition to `s3:CreateBucket`, the following permissions are
+    #   required when your CreateBucket includes specific headers:
     #
-    # * **ACLs** - If your `CreateBucket` request specifies ACL permissions
-    #   and the ACL is public-read, public-read-write, authenticated-read,
-    #   or if you specify access permissions explicitly through any other
-    #   ACL, both `s3:CreateBucket` and `s3:PutBucketAcl` permissions are
-    #   needed. If the ACL the `CreateBucket` request is private or doesn't
-    #   specify any ACLs, only `s3:CreateBucket` permission is needed.
+    #   * **ACLs** - If your `CreateBucket` request specifies ACL
+    #     permissions and the ACL is public-read, public-read-write,
+    #     authenticated-read, or if you specify access permissions
+    #     explicitly through any other ACL, both `s3:CreateBucket` and
+    #     `s3:PutBucketAcl` permissions are needed. If the ACL the
+    #     `CreateBucket` request is private or doesn't specify any ACLs,
+    #     only `s3:CreateBucket` permission is needed.
     #
-    # * **Object Lock** - If `ObjectLockEnabledForBucket` is set to true in
-    #   your `CreateBucket` request, `s3:PutBucketObjectLockConfiguration`
-    #   and `s3:PutBucketVersioning` permissions are required.
+    #   * **Object Lock** - If `ObjectLockEnabledForBucket` is set to true
+    #     in your `CreateBucket` request,
+    #     `s3:PutBucketObjectLockConfiguration` and `s3:PutBucketVersioning`
+    #     permissions are required.
     #
-    # * **S3 Object Ownership** - If your CreateBucket request includes the
-    #   the `x-amz-object-ownership` header, `s3:PutBucketOwnershipControls`
-    #   permission is required.
+    #   * **S3 Object Ownership** - If your CreateBucket request includes
+    #     the `x-amz-object-ownership` header,
+    #     `s3:PutBucketOwnershipControls` permission is required.
     #
     # The following operations are related to `CreateBucket`:
     #
@@ -1716,33 +1721,33 @@ module Aws::S3
     #   * {Types::CreateBucketOutput#location #location} => String
     #
     #
-    # @example Example: To create a bucket in a specific region
+    # @example Example: To create a bucket 
     #
-    #   # The following example creates a bucket. The request specifies an AWS region where to create the bucket.
+    #   # The following example creates a bucket.
     #
     #   resp = client.create_bucket({
     #     bucket: "examplebucket", 
-    #     create_bucket_configuration: {
-    #       location_constraint: "eu-west-1", 
-    #     }, 
     #   })
     #
     #   resp.to_h outputs the following:
     #   {
-    #     location: "http://examplebucket.<Region>.s3.amazonaws.com/", 
+    #     location: "/examplebucket", 
     #   }
     #
-    # @example Example: To create a bucket 
+    # @example Example: To create a bucket in a specific region
     #
-    #   # The following example creates a bucket.
+    #   # The following example creates a bucket. The request specifies an AWS region where to create the bucket.
     #
     #   resp = client.create_bucket({
     #     bucket: "examplebucket", 
+    #     create_bucket_configuration: {
+    #       location_constraint: "eu-west-1", 
+    #     }, 
     #   })
     #
     #   resp.to_h outputs the following:
     #   {
-    #     location: "/examplebucket", 
+    #     location: "http://examplebucket.<Region>.s3.amazonaws.com/", 
     #   }
     #
     # @example Request syntax with placeholder values
@@ -1790,7 +1795,8 @@ module Aws::S3
     # in the bucket lifecycle configuration. Otherwise, the incomplete
     # multipart upload becomes eligible for an abort action and Amazon S3
     # aborts the multipart upload. For more information, see [Aborting
-    # Incomplete Multipart Uploads Using a Bucket Lifecycle Policy][3].
+    # Incomplete Multipart Uploads Using a Bucket Lifecycle
+    # Configuration][3].
     #
     # For information about the permissions required to use the multipart
     # upload API, see [Multipart Upload and Permissions][4].
@@ -1834,7 +1840,7 @@ module Aws::S3
     # you choose to provide your own encryption key, the request headers you
     # provide in [UploadPart][1] and [UploadPartCopy][6] requests must match
     # the headers you used in the request to initiate the upload by using
-    # `CreateMultipartUpload`. you can request that Amazon S3 save the
+    # `CreateMultipartUpload`. You can request that Amazon S3 save the
     # uploaded parts encrypted with server-side encryption with an Amazon S3
     # managed key (SSE-S3), an Key Management Service (KMS) key (SSE-KMS),
     # or a customer-provided encryption key (SSE-C).
@@ -2272,7 +2278,7 @@ module Aws::S3
     #       "MetadataKey" => "MetadataValue",
     #     },
     #     server_side_encryption: "AES256", # accepts AES256, aws:kms
-    #     storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR
+    #     storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR, SNOW
     #     website_redirect_location: "WebsiteRedirectLocation",
     #     sse_customer_algorithm: "SSECustomerAlgorithm",
     #     sse_customer_key: "SSECustomerKey",
@@ -2318,7 +2324,7 @@ module Aws::S3
     # delete markers) in the bucket must be deleted before the bucket itself
     # can be deleted.
     #
-    # **Related Resources**
+    # The following operations are related to `DeleteBucket`:
     #
     # * [CreateBucket][1]
     #
@@ -2435,7 +2441,7 @@ module Aws::S3
     # For information about `cors`, see [Enabling Cross-Origin Resource
     # Sharing][1] in the *Amazon S3 User Guide*.
     #
-    # **Related Resources:**
+    # The following operations are related to `DeleteBucketCors`:
     #
     # * [PutBucketCors][2]
     #
@@ -2496,7 +2502,7 @@ module Aws::S3
     # Permissions to your Amazon S3 Resources][3] in the *Amazon S3 User
     # Guide*.
     #
-    # **Related Resources**
+    # The following operations are related to `DeleteBucketEncryption`:
     #
     # * [PutBucketEncryption][4]
     #
@@ -2849,10 +2855,14 @@ module Aws::S3
     # you're not using an identity that belongs to the bucket owner's
     # account, Amazon S3 returns a `405 Method Not Allowed` error.
     #
-    # As a security precaution, the root user of the Amazon Web Services
-    # account that owns a bucket can always use this operation, even if the
-    # policy explicitly denies the root user the ability to perform this
-    # action.
+    # To ensure that bucket owners don't inadvertently lock themselves out
+    # of their own buckets, the root principal in a bucket owner's Amazon
+    # Web Services account can perform the `GetBucketPolicy`,
+    # `PutBucketPolicy`, and `DeleteBucketPolicy` API actions, even if their
+    # bucket policy explicitly denies the root principal's access. Bucket
+    # owner root principals can only be blocked from performing these API
+    # actions by VPC endpoint policies and Amazon Web Services Organizations
+    # policies.
     #
     # For more information about bucket policies, see [Using Bucket Policies
     # and UserPolicies][1].
@@ -3489,20 +3499,22 @@ module Aws::S3
     #   * {Types::DeleteObjectsOutput#errors #errors} => Array&lt;Types::Error&gt;
     #
     #
-    # @example Example: To delete multiple objects from a versioned bucket
+    # @example Example: To delete multiple object versions from a versioned bucket
     #
-    #   # The following example deletes objects from a bucket. The bucket is versioned, and the request does not specify the
-    #   # object version to delete. In this case, all versions remain in the bucket and S3 adds a delete marker.
+    #   # The following example deletes objects from a bucket. The request specifies object versions. S3 deletes specific object
+    #   # versions and returns the key and versions of deleted objects in the response.
     #
     #   resp = client.delete_objects({
     #     bucket: "examplebucket", 
     #     delete: {
     #       objects: [
     #         {
-    #           key: "objectkey1", 
+    #           key: "HappyFace.jpg", 
+    #           version_id: "2LWg7lQLnY41.maGB5Z6SWW.dcq0vx7b", 
     #         }, 
     #         {
-    #           key: "objectkey2", 
+    #           key: "HappyFace.jpg", 
+    #           version_id: "yoz3HB.ZhCS_tKVEmIOr7qYyyAaZSKVd", 
     #         }, 
     #       ], 
     #       quiet: false, 
@@ -3513,34 +3525,30 @@ module Aws::S3
     #   {
     #     deleted: [
     #       {
-    #         delete_marker: true, 
-    #         delete_marker_version_id: "A._w1z6EFiCF5uhtQMDal9JDkID9tQ7F", 
-    #         key: "objectkey1", 
+    #         key: "HappyFace.jpg", 
+    #         version_id: "yoz3HB.ZhCS_tKVEmIOr7qYyyAaZSKVd", 
     #       }, 
     #       {
-    #         delete_marker: true, 
-    #         delete_marker_version_id: "iOd_ORxhkKe_e8G8_oSGxt2PjsCZKlkt", 
-    #         key: "objectkey2", 
+    #         key: "HappyFace.jpg", 
+    #         version_id: "2LWg7lQLnY41.maGB5Z6SWW.dcq0vx7b", 
     #       }, 
     #     ], 
     #   }
     #
-    # @example Example: To delete multiple object versions from a versioned bucket
+    # @example Example: To delete multiple objects from a versioned bucket
     #
-    #   # The following example deletes objects from a bucket. The request specifies object versions. S3 deletes specific object
-    #   # versions and returns the key and versions of deleted objects in the response.
+    #   # The following example deletes objects from a bucket. The bucket is versioned, and the request does not specify the
+    #   # object version to delete. In this case, all versions remain in the bucket and S3 adds a delete marker.
     #
     #   resp = client.delete_objects({
     #     bucket: "examplebucket", 
     #     delete: {
     #       objects: [
     #         {
-    #           key: "HappyFace.jpg", 
-    #           version_id: "2LWg7lQLnY41.maGB5Z6SWW.dcq0vx7b", 
+    #           key: "objectkey1", 
     #         }, 
     #         {
-    #           key: "HappyFace.jpg", 
-    #           version_id: "yoz3HB.ZhCS_tKVEmIOr7qYyyAaZSKVd", 
+    #           key: "objectkey2", 
     #         }, 
     #       ], 
     #       quiet: false, 
@@ -3551,12 +3559,14 @@ module Aws::S3
     #   {
     #     deleted: [
     #       {
-    #         key: "HappyFace.jpg", 
-    #         version_id: "yoz3HB.ZhCS_tKVEmIOr7qYyyAaZSKVd", 
+    #         delete_marker: true, 
+    #         delete_marker_version_id: "A._w1z6EFiCF5uhtQMDal9JDkID9tQ7F", 
+    #         key: "objectkey1", 
     #       }, 
     #       {
-    #         key: "HappyFace.jpg", 
-    #         version_id: "2LWg7lQLnY41.maGB5Z6SWW.dcq0vx7b", 
+    #         delete_marker: true, 
+    #         delete_marker_version_id: "iOd_ORxhkKe_e8G8_oSGxt2PjsCZKlkt", 
+    #         key: "objectkey2", 
     #       }, 
     #     ], 
     #   }
@@ -3682,7 +3692,8 @@ module Aws::S3
     # For more information about transfer acceleration, see [Transfer
     # Acceleration][4] in the Amazon S3 User Guide.
     #
-    # **Related Resources**
+    # The following operations are related to
+    # `GetBucketAccelerateConfiguration`:
     #
     # * [PutBucketAccelerateConfiguration][3]
     #
@@ -3735,31 +3746,53 @@ module Aws::S3
     # can return the ACL of the bucket without using an authorization
     # header.
     #
-    # To use this API against an access point, provide the alias of the
-    # access point in place of the bucket name.
+    # To use this API operation against an access point, provide the alias
+    # of the access point in place of the bucket name.
+    #
+    # To use this API operation against an Object Lambda access point,
+    # provide the alias of the Object Lambda access point in place of the
+    # bucket name. If the Object Lambda access point alias in a request is
+    # not valid, the error code `InvalidAccessPointAliasError` is returned.
+    # For more information about `InvalidAccessPointAliasError`, see [List
+    # of Error Codes][1].
     #
     # <note markdown="1"> If your bucket uses the bucket owner enforced setting for S3 Object
     # Ownership, requests to read ACLs are still supported and return the
     # `bucket-owner-full-control` ACL with the owner being the account that
     # created the bucket. For more information, see [ Controlling object
-    # ownership and disabling ACLs][1] in the *Amazon S3 User Guide*.
+    # ownership and disabling ACLs][2] in the *Amazon S3 User Guide*.
     #
     #  </note>
     #
-    # **Related Resources**
+    # The following operations are related to `GetBucketAcl`:
     #
-    # * [ListObjects][2]
+    # * [ListObjects][3]
     #
     # ^
     #
     #
     #
-    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html
-    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html
+    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html
+    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html
     #
     # @option params [required, String] :bucket
     #   Specifies the S3 bucket whose ACL is being requested.
     #
+    #   To use this API operation against an access point, provide the alias
+    #   of the access point in place of the bucket name.
+    #
+    #   To use this API operation against an Object Lambda access point,
+    #   provide the alias of the Object Lambda access point in place of the
+    #   bucket name. If the Object Lambda access point alias in a request is
+    #   not valid, the error code `InvalidAccessPointAliasError` is returned.
+    #   For more information about `InvalidAccessPointAliasError`, see [List
+    #   of Error Codes][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    #
     # @option params [String] :expected_bucket_owner
     #   The account ID of the expected bucket owner. If the bucket is owned by
     #   a different account, the request fails with the HTTP status code `403
@@ -3813,7 +3846,8 @@ module Aws::S3
     # For information about Amazon S3 analytics feature, see [Amazon S3
     # Analytics – Storage Class Analysis][3] in the *Amazon S3 User Guide*.
     #
-    # **Related Resources**
+    # The following operations are related to
+    # `GetBucketAnalyticsConfiguration`:
     #
     # * [DeleteBucketAnalyticsConfiguration][4]
     #
@@ -3886,27 +3920,49 @@ module Aws::S3
     # `s3:GetBucketCORS` action. By default, the bucket owner has this
     # permission and can grant it to others.
     #
-    # To use this API against an access point, provide the alias of the
-    # access point in place of the bucket name.
+    # To use this API operation against an access point, provide the alias
+    # of the access point in place of the bucket name.
+    #
+    # To use this API operation against an Object Lambda access point,
+    # provide the alias of the Object Lambda access point in place of the
+    # bucket name. If the Object Lambda access point alias in a request is
+    # not valid, the error code `InvalidAccessPointAliasError` is returned.
+    # For more information about `InvalidAccessPointAliasError`, see [List
+    # of Error Codes][1].
     #
     # For more information about CORS, see [ Enabling Cross-Origin Resource
-    # Sharing][1].
+    # Sharing][2].
     #
     # The following operations are related to `GetBucketCors`:
     #
-    # * [PutBucketCors][2]
+    # * [PutBucketCors][3]
     #
-    # * [DeleteBucketCors][3]
+    # * [DeleteBucketCors][4]
     #
     #
     #
-    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html
-    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketCors.html
-    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketCors.html
+    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html
+    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketCors.html
+    # [4]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketCors.html
     #
     # @option params [required, String] :bucket
     #   The bucket name for which to get the cors configuration.
     #
+    #   To use this API operation against an access point, provide the alias
+    #   of the access point in place of the bucket name.
+    #
+    #   To use this API operation against an Object Lambda access point,
+    #   provide the alias of the Object Lambda access point in place of the
+    #   bucket name. If the Object Lambda access point alias in a request is
+    #   not valid, the error code `InvalidAccessPointAliasError` is returned.
+    #   For more information about `InvalidAccessPointAliasError`, see [List
+    #   of Error Codes][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    #
     # @option params [String] :expected_bucket_owner
     #   The account ID of the expected bucket owner. If the bucket is owned by
     #   a different account, the request fails with the HTTP status code `403
@@ -4449,33 +4505,52 @@ module Aws::S3
     # using the `LocationConstraint` request parameter in a `CreateBucket`
     # request. For more information, see [CreateBucket][1].
     #
-    # To use this implementation of the operation, you must be the bucket
-    # owner.
+    # To use this API operation against an access point, provide the alias
+    # of the access point in place of the bucket name.
     #
-    # To use this API against an access point, provide the alias of the
-    # access point in place of the bucket name.
+    # To use this API operation against an Object Lambda access point,
+    # provide the alias of the Object Lambda access point in place of the
+    # bucket name. If the Object Lambda access point alias in a request is
+    # not valid, the error code `InvalidAccessPointAliasError` is returned.
+    # For more information about `InvalidAccessPointAliasError`, see [List
+    # of Error Codes][2].
     #
-    # <note markdown="1"> For requests made using Amazon Web Services Signature Version 4
-    # (SigV4), we recommend that you use [HeadBucket][2] to return the
-    # bucket Region instead of GetBucketLocation.
+    # <note markdown="1"> We recommend that you use [HeadBucket][3] to return the Region that a
+    # bucket resides in. For backward compatibility, Amazon S3 continues to
+    # support GetBucketLocation.
     #
     #  </note>
     #
     # The following operations are related to `GetBucketLocation`:
     #
-    # * [GetObject][3]
+    # * [GetObject][4]
     #
     # * [CreateBucket][1]
     #
     #
     #
     # [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html
-    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html
-    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html
+    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html
+    # [4]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html
     #
     # @option params [required, String] :bucket
     #   The name of the bucket for which to get the location.
     #
+    #   To use this API operation against an access point, provide the alias
+    #   of the access point in place of the bucket name.
+    #
+    #   To use this API operation against an Object Lambda access point,
+    #   provide the alias of the Object Lambda access point in place of the
+    #   bucket name. If the Object Lambda access point alias in a request is
+    #   not valid, the error code `InvalidAccessPointAliasError` is returned.
+    #   For more information about `InvalidAccessPointAliasError`, see [List
+    #   of Error Codes][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    #
     # @option params [String] :expected_bucket_owner
     #   The account ID of the expected bucket owner. If the bucket is owned by
     #   a different account, the request fails with the HTTP status code `403
@@ -4665,6 +4740,20 @@ module Aws::S3
     #   The name of the bucket for which to get the notification
     #   configuration.
     #
+    #   To use this API operation against an access point, provide the alias
+    #   of the access point in place of the bucket name.
+    #
+    #   To use this API operation against an Object Lambda access point,
+    #   provide the alias of the Object Lambda access point in place of the
+    #   bucket name. If the Object Lambda access point alias in a request is
+    #   not valid, the error code `InvalidAccessPointAliasError` is returned.
+    #   For more information about `InvalidAccessPointAliasError`, see [List
+    #   of Error Codes][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    #
     # @option params [String] :expected_bucket_owner
     #   The account ID of the expected bucket owner. If the bucket is owned by
     #   a different account, the request fails with the HTTP status code `403
@@ -4778,30 +4867,52 @@ module Aws::S3
     # policy to grant permission to other users to read this configuration
     # with the `s3:GetBucketNotification` permission.
     #
-    # To use this API against an access point, provide the alias of the
-    # access point in place of the bucket name.
+    # To use this API operation against an access point, provide the alias
+    # of the access point in place of the bucket name.
+    #
+    # To use this API operation against an Object Lambda access point,
+    # provide the alias of the Object Lambda access point in place of the
+    # bucket name. If the Object Lambda access point alias in a request is
+    # not valid, the error code `InvalidAccessPointAliasError` is returned.
+    # For more information about `InvalidAccessPointAliasError`, see [List
+    # of Error Codes][1].
     #
     # For more information about setting and reading the notification
     # configuration on a bucket, see [Setting Up Notification of Bucket
-    # Events][1]. For more information about bucket policies, see [Using
-    # Bucket Policies][2].
+    # Events][2]. For more information about bucket policies, see [Using
+    # Bucket Policies][3].
     #
     # The following action is related to `GetBucketNotification`:
     #
-    # * [PutBucketNotification][3]
+    # * [PutBucketNotification][4]
     #
     # ^
     #
     #
     #
-    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html
-    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html
-    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketNotification.html
+    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html
+    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html
+    # [4]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketNotification.html
     #
     # @option params [required, String] :bucket
     #   The name of the bucket for which to get the notification
     #   configuration.
     #
+    #   To use this API operation against an access point, provide the alias
+    #   of the access point in place of the bucket name.
+    #
+    #   To use this API operation against an Object Lambda access point,
+    #   provide the alias of the Object Lambda access point in place of the
+    #   bucket name. If the Object Lambda access point alias in a request is
+    #   not valid, the error code `InvalidAccessPointAliasError` is returned.
+    #   For more information about `InvalidAccessPointAliasError`, see [List
+    #   of Error Codes][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    #
     # @option params [String] :expected_bucket_owner
     #   The account ID of the expected bucket owner. If the bucket is owned by
     #   a different account, the request fails with the HTTP status code `403
@@ -4921,31 +5032,57 @@ module Aws::S3
     # you're not using an identity that belongs to the bucket owner's
     # account, Amazon S3 returns a `405 Method Not Allowed` error.
     #
-    # As a security precaution, the root user of the Amazon Web Services
-    # account that owns a bucket can always use this operation, even if the
-    # policy explicitly denies the root user the ability to perform this
-    # action.
-    #
-    # To use this API against an access point, provide the alias of the
-    # access point in place of the bucket name.
+    # To ensure that bucket owners don't inadvertently lock themselves out
+    # of their own buckets, the root principal in a bucket owner's Amazon
+    # Web Services account can perform the `GetBucketPolicy`,
+    # `PutBucketPolicy`, and `DeleteBucketPolicy` API actions, even if their
+    # bucket policy explicitly denies the root principal's access. Bucket
+    # owner root principals can only be blocked from performing these API
+    # actions by VPC endpoint policies and Amazon Web Services Organizations
+    # policies.
+    #
+    # To use this API operation against an access point, provide the alias
+    # of the access point in place of the bucket name.
+    #
+    # To use this API operation against an Object Lambda access point,
+    # provide the alias of the Object Lambda access point in place of the
+    # bucket name. If the Object Lambda access point alias in a request is
+    # not valid, the error code `InvalidAccessPointAliasError` is returned.
+    # For more information about `InvalidAccessPointAliasError`, see [List
+    # of Error Codes][1].
     #
     # For more information about bucket policies, see [Using Bucket Policies
-    # and User Policies][1].
+    # and User Policies][2].
     #
     # The following action is related to `GetBucketPolicy`:
     #
-    # * [GetObject][2]
+    # * [GetObject][3]
     #
     # ^
     #
     #
     #
-    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html
-    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html
+    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html
+    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html
     #
     # @option params [required, String] :bucket
     #   The bucket name for which to get the bucket policy.
     #
+    #   To use this API operation against an access point, provide the alias
+    #   of the access point in place of the bucket name.
+    #
+    #   To use this API operation against an Object Lambda access point,
+    #   provide the alias of the Object Lambda access point in place of the
+    #   bucket name. If the Object Lambda access point alias in a request is
+    #   not valid, the error code `InvalidAccessPointAliasError` is returned.
+    #   For more information about `InvalidAccessPointAliasError`, see [List
+    #   of Error Codes][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    #
     # @option params [String] :expected_bucket_owner
     #   The account ID of the expected bucket owner. If the bucket is owned by
     #   a different account, the request fails with the HTTP status code `403
@@ -5151,7 +5288,7 @@ module Aws::S3
     #   resp.replication_configuration.rules[0].existing_object_replication.status #=> String, one of "Enabled", "Disabled"
     #   resp.replication_configuration.rules[0].destination.bucket #=> String
     #   resp.replication_configuration.rules[0].destination.account #=> String
-    #   resp.replication_configuration.rules[0].destination.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR"
+    #   resp.replication_configuration.rules[0].destination.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR", "SNOW"
     #   resp.replication_configuration.rules[0].destination.access_control_translation.owner #=> String, one of "Destination"
     #   resp.replication_configuration.rules[0].destination.encryption_configuration.replica_kms_key_id #=> String
     #   resp.replication_configuration.rules[0].destination.replication_time.status #=> String, one of "Enabled", "Disabled"
@@ -5397,7 +5534,7 @@ module Aws::S3
     # the website configuration by writing a bucket policy granting them the
     # `S3:GetBucketWebsite` permission.
     #
-    # The following operations are related to `DeleteBucketWebsite`:
+    # The following operations are related to `GetBucketWebsite`:
     #
     # * [DeleteBucketWebsite][2]
     #
@@ -5531,88 +5668,88 @@ module Aws::S3
     # [GetObjectTagging][6] to retrieve the tag set associated with an
     # object.
     #
-    # **Permissions**
+    # Permissions
     #
-    # You need the relevant read object (or version) permission for this
-    # operation. For more information, see [Specifying Permissions in a
-    # Policy][7]. If the object you request does not exist, the error Amazon
-    # S3 returns depends on whether you also have the `s3:ListBucket`
-    # permission.
+    # : You need the relevant read object (or version) permission for this
+    #   operation. For more information, see [Specifying Permissions in a
+    #   Policy][7]. If the object you request does not exist, the error
+    #   Amazon S3 returns depends on whether you also have the
+    #   `s3:ListBucket` permission.
     #
-    # * If you have the `s3:ListBucket` permission on the bucket, Amazon S3
-    #   will return an HTTP status code 404 ("no such key") error.
+    #   * If you have the `s3:ListBucket` permission on the bucket, Amazon
+    #     S3 will return an HTTP status code 404 ("no such key") error.
     #
-    # * If you don’t have the `s3:ListBucket` permission, Amazon S3 will
-    #   return an HTTP status code 403 ("access denied") error.
+    #   * If you don’t have the `s3:ListBucket` permission, Amazon S3 will
+    #     return an HTTP status code 403 ("access denied") error.
     #
-    # **Versioning**
+    # Versioning
     #
-    # By default, the GET action returns the current version of an object.
-    # To return a different version, use the `versionId` subresource.
+    # : By default, the GET action returns the current version of an object.
+    #   To return a different version, use the `versionId` subresource.
     #
-    # <note markdown="1"> * If you supply a `versionId`, you need the `s3:GetObjectVersion`
-    #   permission to access a specific version of an object. If you request
-    #   a specific version, you do not need to have the `s3:GetObject`
-    #   permission. If you request the current version without a specific
-    #   version ID, only `s3:GetObject` permission is required.
-    #   `s3:GetObjectVersion` permission won't be required.
+    #   <note markdown="1"> * If you supply a `versionId`, you need the `s3:GetObjectVersion`
+    #     permission to access a specific version of an object. If you
+    #     request a specific version, you do not need to have the
+    #     `s3:GetObject` permission. If you request the current version
+    #     without a specific version ID, only `s3:GetObject` permission is
+    #     required. `s3:GetObjectVersion` permission won't be required.
     #
-    # * If the current version of the object is a delete marker, Amazon S3
-    #   behaves as if the object was deleted and includes
-    #   `x-amz-delete-marker: true` in the response.
+    #   * If the current version of the object is a delete marker, Amazon S3
+    #     behaves as if the object was deleted and includes
+    #     `x-amz-delete-marker: true` in the response.
     #
-    #  </note>
+    #    </note>
     #
-    # For more information about versioning, see [PutBucketVersioning][8].
+    #   For more information about versioning, see [PutBucketVersioning][8].
     #
-    # **Overriding Response Header Values**
+    # Overriding Response Header Values
     #
-    # There are times when you want to override certain response header
-    # values in a GET response. For example, you might override the
-    # `Content-Disposition` response header value in your GET request.
+    # : There are times when you want to override certain response header
+    #   values in a GET response. For example, you might override the
+    #   `Content-Disposition` response header value in your GET request.
     #
-    # You can override values for a set of response headers using the
-    # following query parameters. These response header values are sent only
-    # on a successful request, that is, when status code 200 OK is returned.
-    # The set of headers you can override using these parameters is a subset
-    # of the headers that Amazon S3 accepts when you create an object. The
-    # response headers that you can override for the GET response are
-    # `Content-Type`, `Content-Language`, `Expires`, `Cache-Control`,
-    # `Content-Disposition`, and `Content-Encoding`. To override these
-    # header values in the GET response, you use the following request
-    # parameters.
+    #   You can override values for a set of response headers using the
+    #   following query parameters. These response header values are sent
+    #   only on a successful request, that is, when status code 200 OK is
+    #   returned. The set of headers you can override using these parameters
+    #   is a subset of the headers that Amazon S3 accepts when you create an
+    #   object. The response headers that you can override for the GET
+    #   response are `Content-Type`, `Content-Language`, `Expires`,
+    #   `Cache-Control`, `Content-Disposition`, and `Content-Encoding`. To
+    #   override these header values in the GET response, you use the
+    #   following request parameters.
     #
-    # <note markdown="1"> You must sign the request, either using an Authorization header or a
-    # presigned URL, when using these parameters. They cannot be used with
-    # an unsigned (anonymous) request.
+    #   <note markdown="1"> You must sign the request, either using an Authorization header or a
+    #   presigned URL, when using these parameters. They cannot be used with
+    #   an unsigned (anonymous) request.
     #
-    #  </note>
+    #    </note>
     #
-    # * `response-content-type`
+    #   * `response-content-type`
     #
-    # * `response-content-language`
+    #   * `response-content-language`
     #
-    # * `response-expires`
+    #   * `response-expires`
     #
-    # * `response-cache-control`
+    #   * `response-cache-control`
     #
-    # * `response-content-disposition`
+    #   * `response-content-disposition`
     #
-    # * `response-content-encoding`
+    #   * `response-content-encoding`
     #
-    # **Additional Considerations about Request Headers**
+    # Overriding Response Header Values
     #
-    # If both of the `If-Match` and `If-Unmodified-Since` headers are
-    # present in the request as follows: `If-Match` condition evaluates to
-    # `true`, and; `If-Unmodified-Since` condition evaluates to `false`;
-    # then, S3 returns 200 OK and the data requested.
+    # : If both of the `If-Match` and `If-Unmodified-Since` headers are
+    #   present in the request as follows: `If-Match` condition evaluates to
+    #   `true`, and; `If-Unmodified-Since` condition evaluates to `false`;
+    #   then, S3 returns 200 OK and the data requested.
     #
-    # If both of the `If-None-Match` and `If-Modified-Since` headers are
-    # present in the request as follows:` If-None-Match` condition evaluates
-    # to `false`, and; `If-Modified-Since` condition evaluates to `true`;
-    # then, S3 returns 304 Not Modified response code.
+    #   If both of the `If-None-Match` and `If-Modified-Since` headers are
+    #   present in the request as follows:` If-None-Match` condition
+    #   evaluates to `false`, and; `If-Modified-Since` condition evaluates
+    #   to `true`; then, S3 returns 304 Not Modified response code.
     #
-    # For more information about conditional requests, see [RFC 7232][9].
+    #   For more information about conditional requests, see [RFC 7232][9].
     #
     # The following operations are related to `GetObject`:
     #
@@ -5933,7 +6070,7 @@ module Aws::S3
     #   resp.sse_customer_key_md5 #=> String
     #   resp.ssekms_key_id #=> String
     #   resp.bucket_key_enabled #=> Boolean
-    #   resp.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR"
+    #   resp.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR", "SNOW"
     #   resp.request_charged #=> String, one of "requester"
     #   resp.replication_status #=> String, one of "COMPLETE", "PENDING", "FAILED", "REPLICA"
     #   resp.parts_count #=> Integer
@@ -5959,8 +6096,6 @@ module Aws::S3
     #
     # This action is not supported by Amazon S3 on Outposts.
     #
-    # **Versioning**
-    #
     # By default, GET returns ACL information about the current version of
     # an object. To return ACL information about a different version, use
     # the versionId subresource.
@@ -6175,23 +6310,26 @@ module Aws::S3
     #
     # For more information about conditional requests, see [RFC 7232][2].
     #
-    # **Permissions**
+    # Permissions
     #
-    # The permissions that you need to use this operation depend on whether
-    # the bucket is versioned. If the bucket is versioned, you need both the
-    # `s3:GetObjectVersion` and `s3:GetObjectVersionAttributes` permissions
-    # for this operation. If the bucket is not versioned, you need the
-    # `s3:GetObject` and `s3:GetObjectAttributes` permissions. For more
-    # information, see [Specifying Permissions in a Policy][3] in the
-    # *Amazon S3 User Guide*. If the object that you request does not exist,
-    # the error Amazon S3 returns depends on whether you also have the
-    # `s3:ListBucket` permission.
+    # : The permissions that you need to use this operation depend on
+    #   whether the bucket is versioned. If the bucket is versioned, you
+    #   need both the `s3:GetObjectVersion` and
+    #   `s3:GetObjectVersionAttributes` permissions for this operation. If
+    #   the bucket is not versioned, you need the `s3:GetObject` and
+    #   `s3:GetObjectAttributes` permissions. For more information, see
+    #   [Specifying Permissions in a Policy][3] in the *Amazon S3 User
+    #   Guide*. If the object that you request does not exist, the error
+    #   Amazon S3 returns depends on whether you also have the
+    #   `s3:ListBucket` permission.
     #
-    # * If you have the `s3:ListBucket` permission on the bucket, Amazon S3
-    #   returns an HTTP status code `404 Not Found` ("no such key") error.
+    #   * If you have the `s3:ListBucket` permission on the bucket, Amazon
+    #     S3 returns an HTTP status code `404 Not Found` ("no such key")
+    #     error.
     #
-    # * If you don't have the `s3:ListBucket` permission, Amazon S3 returns
-    #   an HTTP status code `403 Forbidden` ("access denied") error.
+    #   * If you don't have the `s3:ListBucket` permission, Amazon S3
+    #     returns an HTTP status code `403 Forbidden` ("access denied")
+    #     error.
     #
     # The following actions are related to `GetObjectAttributes`:
     #
@@ -6351,7 +6489,7 @@ module Aws::S3
     #   resp.object_parts.parts[0].checksum_crc32c #=> String
     #   resp.object_parts.parts[0].checksum_sha1 #=> String
     #   resp.object_parts.parts[0].checksum_sha256 #=> String
-    #   resp.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR"
+    #   resp.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR", "SNOW"
     #   resp.object_size #=> Integer
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/s3-2006-03-01/GetObjectAttributes AWS API Documentation
@@ -6927,19 +7065,29 @@ module Aws::S3
     # Operations][1] and [Managing Access Permissions to Your Amazon S3
     # Resources][2].
     #
-    # To use this API against an access point, you must provide the alias of
-    # the access point in place of the bucket name or specify the access
-    # point ARN. When using the access point ARN, you must direct requests
-    # to the access point hostname. The access point hostname takes the form
-    # AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When
-    # using the Amazon Web Services SDKs, you provide the ARN in place of
-    # the bucket name. For more information see, [Using access points][3].
+    # To use this API operation against an access point, you must provide
+    # the alias of the access point in place of the bucket name or specify
+    # the access point ARN. When using the access point ARN, you must direct
+    # requests to the access point hostname. The access point hostname takes
+    # the form
+    # *AccessPointName*-*AccountId*.s3-accesspoint.*Region*.amazonaws.com.
+    # When using the Amazon Web Services SDKs, you provide the ARN in place
+    # of the bucket name. For more information, see [Using access
+    # points][3].
+    #
+    # To use this API operation against an Object Lambda access point,
+    # provide the alias of the Object Lambda access point in place of the
+    # bucket name. If the Object Lambda access point alias in a request is
+    # not valid, the error code `InvalidAccessPointAliasError` is returned.
+    # For more information about `InvalidAccessPointAliasError`, see [List
+    # of Error Codes][4].
     #
     #
     #
     # [1]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources
     # [2]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html
     # [3]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html
+    # [4]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
     #
     # @option params [required, String] :bucket
     #   The bucket name.
@@ -6952,6 +7100,13 @@ module Aws::S3
     #   name. For more information about access point ARNs, see [Using access
     #   points][1] in the *Amazon S3 User Guide*.
     #
+    #   When you use this action with an Object Lambda access point, provide
+    #   the alias of the Object Lambda access point in place of the bucket
+    #   name. If the Object Lambda access point alias in a request is not
+    #   valid, the error code `InvalidAccessPointAliasError` is returned. For
+    #   more information about `InvalidAccessPointAliasError`, see [List of
+    #   Error Codes][2].
+    #
     #   When you use this action with Amazon S3 on Outposts, you must direct
     #   requests to the S3 on Outposts hostname. The S3 on Outposts hostname
     #   takes the form `
@@ -6959,12 +7114,13 @@ module Aws::S3
     #   When you use this action with S3 on Outposts through the Amazon Web
     #   Services SDKs, you provide the Outposts access point ARN in place of
     #   the bucket name. For more information about S3 on Outposts ARNs, see
-    #   [What is S3 on Outposts][2] in the *Amazon S3 User Guide*.
+    #   [What is S3 on Outposts][3] in the *Amazon S3 User Guide*.
     #
     #
     #
     #   [1]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html
-    #   [2]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html
+    #   [2]: https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList
+    #   [3]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html
     #
     # @option params [String] :expected_bucket_owner
     #   The account ID of the expected bucket owner. If the bucket is owned by
@@ -7066,19 +7222,19 @@ module Aws::S3
     #
     # For more information about conditional requests, see [RFC 7232][3].
     #
-    # **Permissions**
+    # Permissions
     #
-    # You need the relevant read object (or version) permission for this
-    # operation. For more information, see [Specifying Permissions in a
-    # Policy][4]. If the object you request does not exist, the error Amazon
-    # S3 returns depends on whether you also have the s3:ListBucket
-    # permission.
+    # : You need the relevant read object (or version) permission for this
+    #   operation. For more information, see [Actions, resources, and
+    #   condition keys for Amazon S3][4]. If the object you request does not
+    #   exist, the error Amazon S3 returns depends on whether you also have
+    #   the s3:ListBucket permission.
     #
-    # * If you have the `s3:ListBucket` permission on the bucket, Amazon S3
-    #   returns an HTTP status code 404 ("no such key") error.
+    #   * If you have the `s3:ListBucket` permission on the bucket, Amazon
+    #     S3 returns an HTTP status code 404 ("no such key") error.
     #
-    # * If you don’t have the `s3:ListBucket` permission, Amazon S3 returns
-    #   an HTTP status code 403 ("access denied") error.
+    #   * If you don’t have the `s3:ListBucket` permission, Amazon S3
+    #     returns an HTTP status code 403 ("access denied") error.
     #
     # The following actions are related to `HeadObject`:
     #
@@ -7091,7 +7247,7 @@ module Aws::S3
     # [1]: https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html
     # [2]: https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonRequestHeaders.html
     # [3]: https://tools.ietf.org/html/rfc7232
-    # [4]: https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html
+    # [4]: https://docs.aws.amazon.com/AmazonS3/latest/dev/list_amazons3.html
     # [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html
     # [6]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html
     #
@@ -7305,7 +7461,7 @@ module Aws::S3
     #   resp.sse_customer_key_md5 #=> String
     #   resp.ssekms_key_id #=> String
     #   resp.bucket_key_enabled #=> Boolean
-    #   resp.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR"
+    #   resp.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR", "SNOW"
     #   resp.request_charged #=> String, one of "requester"
     #   resp.replication_status #=> String, one of "COMPLETE", "PENDING", "FAILED", "REPLICA"
     #   resp.parts_count #=> Integer
@@ -8041,7 +8197,7 @@ module Aws::S3
     #   resp.uploads[0].upload_id #=> String
     #   resp.uploads[0].key #=> String
     #   resp.uploads[0].initiated #=> Time
-    #   resp.uploads[0].storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR"
+    #   resp.uploads[0].storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR", "SNOW"
     #   resp.uploads[0].owner.display_name #=> String
     #   resp.uploads[0].owner.id #=> String
     #   resp.uploads[0].initiator.id #=> String
@@ -8426,7 +8582,7 @@ module Aws::S3
     #   resp.contents[0].checksum_algorithm #=> Array
     #   resp.contents[0].checksum_algorithm[0] #=> String, one of "CRC32", "CRC32C", "SHA1", "SHA256"
     #   resp.contents[0].size #=> Integer
-    #   resp.contents[0].storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "GLACIER", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR"
+    #   resp.contents[0].storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "GLACIER", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR", "SNOW"
     #   resp.contents[0].owner.display_name #=> String
     #   resp.contents[0].owner.id #=> String
     #   resp.name #=> String
@@ -8633,7 +8789,7 @@ module Aws::S3
     #   resp.contents[0].checksum_algorithm #=> Array
     #   resp.contents[0].checksum_algorithm[0] #=> String, one of "CRC32", "CRC32C", "SHA1", "SHA256"
     #   resp.contents[0].size #=> Integer
-    #   resp.contents[0].storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "GLACIER", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR"
+    #   resp.contents[0].storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "GLACIER", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR", "SNOW"
     #   resp.contents[0].owner.display_name #=> String
     #   resp.contents[0].owner.id #=> String
     #   resp.name #=> String
@@ -8887,7 +9043,7 @@ module Aws::S3
     #   resp.initiator.display_name #=> String
     #   resp.owner.display_name #=> String
     #   resp.owner.id #=> String
-    #   resp.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR"
+    #   resp.storage_class #=> String, one of "STANDARD", "REDUCED_REDUNDANCY", "STANDARD_IA", "ONEZONE_IA", "INTELLIGENT_TIERING", "GLACIER", "DEEP_ARCHIVE", "OUTPOSTS", "GLACIER_IR", "SNOW"
     #   resp.request_charged #=> String, one of "requester"
     #   resp.checksum_algorithm #=> String, one of "CRC32", "CRC32C", "SHA1", "SHA256"
     #
@@ -9024,127 +9180,128 @@ module Aws::S3
     # still supported. For more information, see [Controlling object
     # ownership][2] in the *Amazon S3 User Guide*.
     #
-    # **Access Permissions**
+    # Permissions
     #
-    # You can set access permissions using one of the following methods:
+    # : You can set access permissions using one of the following methods:
     #
-    # * Specify a canned ACL with the `x-amz-acl` 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 `x-amz-acl`. If you use this
-    #   header, you cannot use other access control-specific headers in your
-    #   request. For more information, see [Canned ACL][3].
+    #   * Specify a canned ACL with the `x-amz-acl` 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 `x-amz-acl`. If you
+    #     use this header, you cannot use other access control-specific
+    #     headers in your request. For more information, see [Canned
+    #     ACL][3].
     #
-    # * Specify access permissions explicitly with the `x-amz-grant-read`,
-    #   `x-amz-grant-read-acp`, `x-amz-grant-write-acp`, and
-    #   `x-amz-grant-full-control` 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 `x-amz-acl` 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 [Access Control List (ACL) Overview][4].
+    #   * Specify access permissions explicitly with the `x-amz-grant-read`,
+    #     `x-amz-grant-read-acp`, `x-amz-grant-write-acp`, and
+    #     `x-amz-grant-full-control` 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 `x-amz-acl` 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 [Access Control List (ACL) Overview][4].
     #
-    #   You specify each grantee as a type=value pair, where the type is one
-    #   of the following:
+    #     You specify each grantee as a type=value pair, where the type is
+    #     one of the following:
     #
-    #   * `id` – if the value specified is the canonical user ID of an
-    #     Amazon Web Services account
+    #     * `id` – if the value specified is the canonical user ID of an
+    #       Amazon Web Services account
     #
-    #   * `uri` – if you are granting permissions to a predefined group
+    #     * `uri` – if you are granting permissions to a predefined group
     #
-    #   * `emailAddress` – if the value specified is the email address of an
-    #     Amazon Web Services account
+    #     * `emailAddress` – if the value specified is the email address of
+    #       an Amazon Web Services account
     #
-    #     <note markdown="1"> Using email addresses to specify a grantee is only supported in
-    #     the following Amazon Web Services Regions:
+    #       <note markdown="1"> Using email addresses to specify a grantee is only supported in
+    #       the following Amazon Web Services Regions:
     #
-    #      * US East (N. Virginia)
+    #        * US East (N. Virginia)
     #
-    #     * US West (N. California)
+    #       * US West (N. California)
     #
-    #     * US West (Oregon)
+    #       * US West (Oregon)
     #
-    #     * Asia Pacific (Singapore)
+    #       * Asia Pacific (Singapore)
     #
-    #     * Asia Pacific (Sydney)
+    #       * Asia Pacific (Sydney)
     #
-    #     * Asia Pacific (Tokyo)
+    #       * Asia Pacific (Tokyo)
     #
-    #     * Europe (Ireland)
+    #       * Europe (Ireland)
     #
-    #     * South America (São Paulo)
+    #       * South America (São Paulo)
     #
-    #      For a list of all the Amazon S3 supported Regions and endpoints,
-    #     see [Regions and Endpoints][5] in the Amazon Web Services General
-    #     Reference.
+    #        For a list of all the Amazon S3 supported Regions and endpoints,
+    #       see [Regions and Endpoints][5] in the Amazon Web Services
+    #       General Reference.
     #
-    #      </note>
+    #        </note>
     #
-    #   For example, the following `x-amz-grant-write` 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.
+    #     For example, the following `x-amz-grant-write` 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.
     #
-    #   `x-amz-grant-write:
-    #   uri="http://acs.amazonaws.com/groups/s3/LogDelivery",
-    #   id="111122223333", id="555566667777" `
+    #     `x-amz-grant-write:
+    #     uri="http://acs.amazonaws.com/groups/s3/LogDelivery",
+    #     id="111122223333", id="555566667777" `
     #
-    # You can use either a canned ACL or specify access permissions
-    # explicitly. You cannot do both.
+    #   You can use either a canned ACL or specify access permissions
+    #   explicitly. You cannot do both.
     #
-    # **Grantee Values**
+    # Grantee Values
     #
-    # You can specify the person (grantee) to whom you're assigning access
-    # rights (using request elements) in the following ways:
+    # : You can specify the person (grantee) to whom you're assigning
+    #   access rights (using request elements) in the following ways:
     #
-    # * By the person's ID:
+    #   * By the person's ID:
     #
-    #   `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
-    #   </Grantee>`
+    #     `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
+    #     </Grantee>`
     #
-    #   DisplayName is optional and ignored in the request
+    #     DisplayName is optional and ignored in the request
     #
-    # * By URI:
+    #   * By URI:
     #
-    #   `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>`
+    #     `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>`
     #
-    # * By Email address:
+    #   * By Email address:
     #
-    #   `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>&</Grantee>`
+    #     `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>&</Grantee>`
     #
-    #   The grantee is resolved to the CanonicalUser and, in a response to a
-    #   GET Object acl request, appears as the CanonicalUser.
+    #     The grantee is resolved to the CanonicalUser and, in a response to
+    #     a GET Object acl request, appears as the CanonicalUser.
     #
-    #   <note markdown="1"> Using email addresses to specify a grantee is only supported in the
-    #   following Amazon Web Services Regions:
+    #     <note markdown="1"> Using email addresses to specify a grantee is only supported in
+    #     the following Amazon Web Services Regions:
     #
-    #    * US East (N. Virginia)
+    #      * US East (N. Virginia)
     #
-    #   * US West (N. California)
+    #     * US West (N. California)
     #
-    #   * US West (Oregon)
+    #     * US West (Oregon)
     #
-    #   * Asia Pacific (Singapore)
+    #     * Asia Pacific (Singapore)
     #
-    #   * Asia Pacific (Sydney)
+    #     * Asia Pacific (Sydney)
     #
-    #   * Asia Pacific (Tokyo)
+    #     * Asia Pacific (Tokyo)
     #
-    #   * Europe (Ireland)
+    #     * Europe (Ireland)
     #
-    #   * South America (São Paulo)
+    #     * South America (São Paulo)
     #
-    #    For a list of all the Amazon S3 supported Regions and endpoints, see
-    #   [Regions and Endpoints][5] in the Amazon Web Services General
-    #   Reference.
+    #      For a list of all the Amazon S3 supported Regions and endpoints,
+    #     see [Regions and Endpoints][5] in the Amazon Web Services General
+    #     Reference.
     #
-    #    </note>
+    #      </note>
     #
-    # **Related Resources**
+    # The following operations are related to `PutBucketAcl`:
     #
     # * [CreateBucket][6]
     #
@@ -9310,7 +9467,7 @@ module Aws::S3
     # Related to Bucket Subresource Operations][3] and [Managing Access
     # Permissions to Your Amazon S3 Resources][4].
     #
-    # **Special Errors**
+    # `PutBucketAnalyticsConfiguration` has the following special errors:
     #
     # * * *HTTP Error: HTTP 400 Bad Request*
     #
@@ -9333,7 +9490,8 @@ module Aws::S3
     #     not have the s3:PutAnalyticsConfiguration bucket permission to set
     #     the configuration on the bucket.*
     #
-    # **Related Resources**
+    # The following operations are related to
+    # `PutBucketAnalyticsConfiguration`:
     #
     # * [GetBucketAnalyticsConfiguration][5]
     #
@@ -9454,7 +9612,7 @@ module Aws::S3
     # For more information about CORS, go to [Enabling Cross-Origin Resource
     # Sharing][1] in the *Amazon S3 User Guide*.
     #
-    # **Related Resources**
+    # The following operations are related to `PutBucketCors`:
     #
     # * [GetBucketCors][2]
     #
@@ -9617,7 +9775,7 @@ module Aws::S3
     # Permissions to Your Amazon S3 Resources][5] in the *Amazon S3 User
     # Guide*.
     #
-    # **Related Resources**
+    # The following operations are related to `PutBucketEncryption`:
     #
     # * [GetBucketEncryption][6]
     #
@@ -9748,28 +9906,27 @@ module Aws::S3
     #
     #  </note>
     #
-    # **Special Errors**
-    #
-    # * **HTTP 400 Bad Request Error**
+    # `PutBucketIntelligentTieringConfiguration` has the following special
+    # errors:
     #
-    #   * *Code:* InvalidArgument
+    # HTTP 400 Bad Request Error
     #
-    #   * *Cause:* Invalid Argument
+    # : *Code:* InvalidArgument
     #
-    # * **HTTP 400 Bad Request Error**
+    #   *Cause:* Invalid Argument
     #
-    #   * *Code:* TooManyConfigurations
+    # HTTP 400 Bad Request Error
     #
-    #   * *Cause:* You are attempting to create a new configuration but have
-    #     already reached the 1,000-configuration limit.
+    # : *Code:* TooManyConfigurations
     #
-    # * **HTTP 403 Forbidden Error**
+    #   *Cause:* You are attempting to create a new configuration but have
+    #   already reached the 1,000-configuration limit.
     #
-    #   * *Code:* AccessDenied
+    # HTTP 403 Forbidden Error
     #
-    #   * *Cause:* You are not the owner of the specified bucket, or you do
-    #     not have the `s3:PutIntelligentTieringConfiguration` bucket
-    #     permission to set the configuration on the bucket.
+    # : *Cause:* You are not the owner of the specified bucket, or you do
+    #   not have the `s3:PutIntelligentTieringConfiguration` bucket
+    #   permission to set the configuration on the bucket.
     #
     #
     #
@@ -9855,51 +10012,50 @@ module Aws::S3
     # location. For an example policy, see [ Granting Permissions for Amazon
     # S3 Inventory and Storage Class Analysis][2].
     #
-    # **Permissions**
-    #
-    # To use this operation, you must have permission to perform the
-    # `s3:PutInventoryConfiguration` action. The bucket owner has this
-    # permission by default and can grant this permission to others.
+    # Permissions
     #
-    # The `s3:PutInventoryConfiguration` permission allows a user to create
-    # an [S3 Inventory][3] report that includes all object metadata fields
-    # available and to specify the destination bucket to store the
-    # inventory. A user with read access to objects in the destination
-    # bucket can also access all object metadata fields that are available
-    # in the inventory report.
+    # : To use this operation, you must have permission to perform the
+    #   `s3:PutInventoryConfiguration` action. The bucket owner has this
+    #   permission by default and can grant this permission to others.
     #
-    # To restrict access to an inventory report, see [Restricting access to
-    # an Amazon S3 Inventory report][4] in the *Amazon S3 User Guide*. For
-    # more information about the metadata fields available in S3 Inventory,
-    # see [Amazon S3 Inventory lists][5] in the *Amazon S3 User Guide*. For
-    # more information about permissions, see [Permissions related to bucket
-    # subresource operations][6] and [Identity and access management in
-    # Amazon S3][7] in the *Amazon S3 User Guide*.
+    #   The `s3:PutInventoryConfiguration` permission allows a user to
+    #   create an [S3 Inventory][3] report that includes all object metadata
+    #   fields available and to specify the destination bucket to store the
+    #   inventory. A user with read access to objects in the destination
+    #   bucket can also access all object metadata fields that are available
+    #   in the inventory report.
     #
-    # **Special Errors**
+    #   To restrict access to an inventory report, see [Restricting access
+    #   to an Amazon S3 Inventory report][4] in the *Amazon S3 User Guide*.
+    #   For more information about the metadata fields available in S3
+    #   Inventory, see [Amazon S3 Inventory lists][5] in the *Amazon S3 User
+    #   Guide*. For more information about permissions, see [Permissions
+    #   related to bucket subresource operations][6] and [Identity and
+    #   access management in Amazon S3][7] in the *Amazon S3 User Guide*.
     #
-    # * **HTTP 400 Bad Request Error**
+    # `PutBucketInventoryConfiguration` has the following special errors:
     #
-    #   * *Code:* InvalidArgument
+    # HTTP 400 Bad Request Error
     #
-    #   * *Cause:* Invalid Argument
+    # : *Code:* InvalidArgument
     #
-    # * **HTTP 400 Bad Request Error**
+    #   *Cause:* Invalid Argument
     #
-    #   * *Code:* TooManyConfigurations
+    # HTTP 400 Bad Request Error
     #
-    #   * *Cause:* You are attempting to create a new configuration but have
-    #     already reached the 1,000-configuration limit.
+    # : *Code:* TooManyConfigurations
     #
-    # * **HTTP 403 Forbidden Error**
+    #   *Cause:* You are attempting to create a new configuration but have
+    #   already reached the 1,000-configuration limit.
     #
-    #   * *Code:* AccessDenied
+    # HTTP 403 Forbidden Error
     #
-    #   * *Cause:* You are not the owner of the specified bucket, or you do
-    #     not have the `s3:PutInventoryConfiguration` bucket permission to
-    #     set the configuration on the bucket.
+    # : *Cause:* You are not the owner of the specified bucket, or you do
+    #   not have the `s3:PutInventoryConfiguration` bucket permission to set
+    #   the configuration on the bucket.
     #
-    # **Related Resources**
+    # The following operations are related to
+    # `PutBucketInventoryConfiguration`:
     #
     # * [GetBucketInventoryConfiguration][8]
     #
@@ -10018,7 +10174,7 @@ module Aws::S3
     # STANDARD\_IA or ONEZONE\_IA, see [Examples of Lifecycle
     # Configuration][4].
     #
-    # **Related Resources**
+    # The following operations are related to `PutBucketLifecycle`:
     #
     # * [GetBucketLifecycle][5](Deprecated)
     #
@@ -10145,56 +10301,58 @@ module Aws::S3
     #
     #  </note>
     #
-    # **Rules**
+    # Rules
     #
-    # You specify the lifecycle configuration in your request body. The
-    # lifecycle configuration is specified as XML consisting of one or more
-    # rules. An Amazon S3 Lifecycle configuration can have up to 1,000
-    # rules. This limit is not adjustable. Each rule consists of the
-    # following:
+    # : You specify the lifecycle configuration in your request body. The
+    #   lifecycle configuration is specified as XML consisting of one or
+    #   more rules. An Amazon S3 Lifecycle configuration can have up to
+    #   1,000 rules. This limit is not adjustable. Each rule consists of the
+    #   following:
     #
-    # * Filter identifying a subset of objects to which the rule applies.
-    #   The filter can be based on a key name prefix, object tags, or a
-    #   combination of both.
+    #   * Filter identifying a subset of objects to which the rule applies.
+    #     The filter can be based on a key name prefix, object tags, or a
+    #     combination of both.
     #
-    # * Status whether the rule is in effect.
+    #   * Status whether the rule is in effect.
     #
-    # * One or more lifecycle transition and expiration actions that you
-    #   want Amazon S3 to perform on the objects identified by the filter.
-    #   If the state of your bucket is versioning-enabled or
-    #   versioning-suspended, you can have many versions of the same object
-    #   (one current version and zero or more noncurrent versions). Amazon
-    #   S3 provides predefined actions that you can specify for current and
-    #   noncurrent object versions.
+    #   * One or more lifecycle transition and expiration actions that you
+    #     want Amazon S3 to perform on the objects identified by the filter.
+    #     If the state of your bucket is versioning-enabled or
+    #     versioning-suspended, you can have many versions of the same
+    #     object (one current version and zero or more noncurrent versions).
+    #     Amazon S3 provides predefined actions that you can specify for
+    #     current and noncurrent object versions.
     #
-    # For more information, see [Object Lifecycle Management][3] and
-    # [Lifecycle Configuration Elements][4].
+    #   For more information, see [Object Lifecycle Management][3] and
+    #   [Lifecycle Configuration Elements][4].
     #
-    # **Permissions**
+    # Permissions
     #
-    # By default, all Amazon S3 resources are private, including buckets,
-    # objects, and related subresources (for example, lifecycle
-    # configuration and website configuration). Only the resource owner
-    # (that is, the Amazon Web Services account that created it) can access
-    # the resource. The resource owner can optionally grant access
-    # permissions to others by writing an access policy. For this operation,
-    # a user must get the `s3:PutLifecycleConfiguration` permission.
+    # : By default, all Amazon S3 resources are private, including buckets,
+    #   objects, and related subresources (for example, lifecycle
+    #   configuration and website configuration). Only the resource owner
+    #   (that is, the Amazon Web Services account that created it) can
+    #   access the resource. The resource owner can optionally grant access
+    #   permissions to others by writing an access policy. For this
+    #   operation, a user must get the `s3:PutLifecycleConfiguration`
+    #   permission.
     #
-    # You can also explicitly deny permissions. Explicit deny also
-    # supersedes any other permissions. If you want to block users or
-    # accounts from removing or deleting objects from your bucket, you must
-    # deny them permissions for the following actions:
+    #   You can also explicitly deny permissions. Explicit deny also
+    #   supersedes any other permissions. If you want to block users or
+    #   accounts from removing or deleting objects from your bucket, you
+    #   must deny them permissions for the following actions:
     #
-    # * `s3:DeleteObject`
+    #   * `s3:DeleteObject`
     #
-    # * `s3:DeleteObjectVersion`
+    #   * `s3:DeleteObjectVersion`
     #
-    # * `s3:PutLifecycleConfiguration`
+    #   * `s3:PutLifecycleConfiguration`
     #
-    # For more information about permissions, see [Managing Access
-    # Permissions to Your Amazon S3 Resources][5].
+    #   For more information about permissions, see [Managing Access
+    #   Permissions to Your Amazon S3 Resources][5].
     #
-    # The following are related to `PutBucketLifecycleConfiguration`:
+    # The following operations are related to
+    # `PutBucketLifecycleConfiguration`:
     #
     # * [Examples of Lifecycle Configuration][6]
     #
@@ -10359,31 +10517,31 @@ module Aws::S3
     # using policies. For more information, see [Permissions for server
     # access log delivery][1] in the *Amazon S3 User Guide*.
     #
-    # **Grantee Values**
+    # Grantee Values
     #
-    # You can specify the person (grantee) to whom you're assigning access
-    # rights (using request elements) in the following ways:
+    # : You can specify the person (grantee) to whom you're assigning
+    #   access rights (using request elements) in the following ways:
     #
-    # * By the person's ID:
+    #   * By the person's ID:
     #
-    #   `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
-    #   </Grantee>`
+    #     `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
+    #     </Grantee>`
     #
-    #   DisplayName is optional and ignored in the request.
+    #     DisplayName is optional and ignored in the request.
     #
-    # * By Email address:
+    #   * By Email address:
     #
-    #   ` <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress></Grantee>`
+    #     ` <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress></Grantee>`
     #
-    #   The grantee is resolved to the CanonicalUser and, in a response to a
-    #   GET Object acl request, appears as the CanonicalUser.
+    #     The grantee is resolved to the CanonicalUser and, in a response to
+    #     a GET Object acl request, appears as the CanonicalUser.
     #
-    # * By URI:
+    #   * By URI:
     #
-    #   `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>`
+    #     `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>`
     #
     # To enable logging, you use LoggingEnabled and its children request
     # elements. To disable logging, you use an empty BucketLoggingStatus
@@ -10748,8 +10906,6 @@ module Aws::S3
     #
     #  </note>
     #
-    # **Responses**
-    #
     # If the configuration in the request body includes only one
     # `TopicConfiguration` specifying only the
     # `s3:ReducedRedundancyLostObject` event type, the response will also
@@ -10955,10 +11111,14 @@ module Aws::S3
     # you're not using an identity that belongs to the bucket owner's
     # account, Amazon S3 returns a `405 Method Not Allowed` error.
     #
-    # As a security precaution, the root user of the Amazon Web Services
-    # account that owns a bucket can always use this operation, even if the
-    # policy explicitly denies the root user the ability to perform this
-    # action.
+    # To ensure that bucket owners don't inadvertently lock themselves out
+    # of their own buckets, the root principal in a bucket owner's Amazon
+    # Web Services account can perform the `GetBucketPolicy`,
+    # `PutBucketPolicy`, and `DeleteBucketPolicy` API actions, even if their
+    # bucket policy explicitly denies the root principal's access. Bucket
+    # owner root principals can only be blocked from performing these API
+    # actions by VPC endpoint policies and Amazon Web Services Organizations
+    # policies.
     #
     # For more information, see [Bucket policy examples][1].
     #
@@ -11075,35 +11235,35 @@ module Aws::S3
     # For information about enabling versioning on a bucket, see [Using
     # Versioning][3].
     #
-    # **Handling Replication of Encrypted Objects**
+    # Handling Replication of Encrypted Objects
     #
-    # By default, Amazon S3 doesn't replicate objects that are stored at
-    # rest using server-side encryption with KMS keys. To replicate Amazon
-    # Web Services KMS-encrypted objects, add the following:
-    # `SourceSelectionCriteria`, `SseKmsEncryptedObjects`, `Status`,
-    # `EncryptionConfiguration`, and `ReplicaKmsKeyID`. For information
-    # about replication configuration, see [Replicating Objects Created with
-    # SSE Using KMS keys][4].
+    # : By default, Amazon S3 doesn't replicate objects that are stored at
+    #   rest using server-side encryption with KMS keys. To replicate Amazon
+    #   Web Services KMS-encrypted objects, add the following:
+    #   `SourceSelectionCriteria`, `SseKmsEncryptedObjects`, `Status`,
+    #   `EncryptionConfiguration`, and `ReplicaKmsKeyID`. For information
+    #   about replication configuration, see [Replicating Objects Created
+    #   with SSE Using KMS keys][4].
     #
-    # For information on `PutBucketReplication` errors, see [List of
-    # replication-related error codes][5]
+    #   For information on `PutBucketReplication` errors, see [List of
+    #   replication-related error codes][5]
     #
-    # **Permissions**
+    # Permissions
     #
-    # To create a `PutBucketReplication` request, you must have
-    # `s3:PutReplicationConfiguration` permissions for the bucket.
+    # : To create a `PutBucketReplication` request, you must have
+    #   `s3:PutReplicationConfiguration` permissions for the bucket.
     #
-    # By default, a resource owner, in this case the Amazon Web Services
-    # account that created the bucket, can perform this operation. The
-    # resource owner can also grant others permissions to perform the
-    # operation. For more information about permissions, see [Specifying
-    # Permissions in a Policy][6] and [Managing Access Permissions to Your
-    # Amazon S3 Resources][7].
+    #   By default, a resource owner, in this case the Amazon Web Services
+    #   account that created the bucket, can perform this operation. The
+    #   resource owner can also grant others permissions to perform the
+    #   operation. For more information about permissions, see [Specifying
+    #   Permissions in a Policy][6] and [Managing Access Permissions to Your
+    #   Amazon S3 Resources][7].
     #
-    # <note markdown="1"> To perform this operation, the user or role performing the action must
-    # have the [iam:PassRole][8] permission.
+    #   <note markdown="1"> To perform this operation, the user or role performing the action
+    #   must have the [iam:PassRole][8] permission.
     #
-    #  </note>
+    #    </note>
     #
     # The following operations are related to `PutBucketReplication`:
     #
@@ -11236,7 +11396,7 @@ module Aws::S3
     #           destination: { # required
     #             bucket: "BucketName", # required
     #             account: "AccountId",
-    #             storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR
+    #             storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR, SNOW
     #             access_control_translation: {
     #               owner: "Destination", # required, accepts Destination
     #             },
@@ -11552,16 +11712,16 @@ module Aws::S3
     # header and the `Status` and the `MfaDelete` request elements in a
     # request to set the versioning state of the bucket.
     #
-    # If you have an object expiration lifecycle policy in your
+    # If you have an object expiration lifecycle configuration in your
     # non-versioned bucket and you want to maintain the same permanent
     # delete behavior when you enable versioning, you must add a noncurrent
-    # expiration policy. The noncurrent expiration lifecycle policy will
-    # manage the deletes of the noncurrent object versions in the
+    # expiration policy. The noncurrent expiration lifecycle configuration
+    # will manage the deletes of the noncurrent object versions in the
     # version-enabled bucket. (A version-enabled bucket maintains one
     # current and zero or more noncurrent object versions.) For more
     # information, see [Lifecycle and Versioning][2].
     #
-    # **Related Resources**
+    # The following operations are related to `PutBucketVersioning`:
     #
     # * [CreateBucket][3]
     #
@@ -11925,9 +12085,9 @@ module Aws::S3
     # returns this ID in the response. When you enable versioning for a
     # bucket, if Amazon S3 receives multiple write requests for the same
     # object simultaneously, it stores all of the objects. For more
-    # information about versioning, see [Adding Objects to Versioning
-    # Enabled Buckets][8]. For information about returning the versioning
-    # state of a bucket, see [GetBucketVersioning][9].
+    # information about versioning, see [Adding Objects to
+    # Versioning-Enabled Buckets][8]. For information about returning the
+    # versioning state of a bucket, see [GetBucketVersioning][9].
     #
     # For more information about related Amazon S3 APIs, see the following:
     #
@@ -12284,27 +12444,6 @@ module Aws::S3
     #   * {Types::PutObjectOutput#request_charged #request_charged} => String
     #
     #
-    # @example Example: To upload object and specify user-defined metadata
-    #
-    #   # The following example creates an object. The request also specifies optional metadata. If the bucket is versioning
-    #   # enabled, S3 returns version ID in response.
-    #
-    #   resp = client.put_object({
-    #     body: "filetoupload", 
-    #     bucket: "examplebucket", 
-    #     key: "exampleobject", 
-    #     metadata: {
-    #       "metadata1" => "value1", 
-    #       "metadata2" => "value2", 
-    #     }, 
-    #   })
-    #
-    #   resp.to_h outputs the following:
-    #   {
-    #     etag: "\"6805f2cfc46c0f04559748bb039d69ae\"", 
-    #     version_id: "pSKidl4pHBiNwukdbcPXAIs.sshFFOc0", 
-    #   }
-    #
     # @example Example: To upload an object and specify optional tags
     #
     #   # The following example uploads an object. The request specifies optional object tags. The bucket is versioned, therefore
@@ -12341,6 +12480,26 @@ module Aws::S3
     #     version_id: "Kirh.unyZwjQ69YxcQLA8z4F5j3kJJKr", 
     #   }
     #
+    # @example Example: To upload an object and specify server-side encryption and object tags
+    #
+    #   # The following example uploads an object. The request specifies the optional server-side encryption option. The request
+    #   # also specifies optional object tags. If the bucket is versioning enabled, S3 returns version ID in response.
+    #
+    #   resp = client.put_object({
+    #     body: "filetoupload", 
+    #     bucket: "examplebucket", 
+    #     key: "exampleobject", 
+    #     server_side_encryption: "AES256", 
+    #     tagging: "key1=value1&key2=value2", 
+    #   })
+    #
+    #   resp.to_h outputs the following:
+    #   {
+    #     etag: "\"6805f2cfc46c0f04559748bb039d69ae\"", 
+    #     server_side_encryption: "AES256", 
+    #     version_id: "Ri.vC6qVlA4dEnjgRV4ZHsHoFIjqEMNt", 
+    #   }
+    #
     # @example Example: To create an object.
     #
     #   # The following example creates an object. If the bucket is versioning enabled, S3 returns version ID in response.
@@ -12394,24 +12553,25 @@ module Aws::S3
     #     version_id: "CG612hodqujkf8FaaNfp8U..FIhLROcp", 
     #   }
     #
-    # @example Example: To upload an object and specify server-side encryption and object tags
+    # @example Example: To upload object and specify user-defined metadata
     #
-    #   # The following example uploads an object. The request specifies the optional server-side encryption option. The request
-    #   # also specifies optional object tags. If the bucket is versioning enabled, S3 returns version ID in response.
+    #   # The following example creates an object. The request also specifies optional metadata. If the bucket is versioning
+    #   # enabled, S3 returns version ID in response.
     #
     #   resp = client.put_object({
     #     body: "filetoupload", 
     #     bucket: "examplebucket", 
     #     key: "exampleobject", 
-    #     server_side_encryption: "AES256", 
-    #     tagging: "key1=value1&key2=value2", 
+    #     metadata: {
+    #       "metadata1" => "value1", 
+    #       "metadata2" => "value2", 
+    #     }, 
     #   })
     #
     #   resp.to_h outputs the following:
     #   {
     #     etag: "\"6805f2cfc46c0f04559748bb039d69ae\"", 
-    #     server_side_encryption: "AES256", 
-    #     version_id: "Ri.vC6qVlA4dEnjgRV4ZHsHoFIjqEMNt", 
+    #     version_id: "pSKidl4pHBiNwukdbcPXAIs.sshFFOc0", 
     #   }
     #
     # @example Streaming a file from disk
@@ -12448,7 +12608,7 @@ module Aws::S3
     #       "MetadataKey" => "MetadataValue",
     #     },
     #     server_side_encryption: "AES256", # accepts AES256, aws:kms
-    #     storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR
+    #     storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR, SNOW
     #     website_redirect_location: "WebsiteRedirectLocation",
     #     sse_customer_algorithm: "SSECustomerAlgorithm",
     #     sse_customer_key: "SSECustomerKey",
@@ -12513,131 +12673,132 @@ module Aws::S3
     # still supported. For more information, see [Controlling object
     # ownership][3] in the *Amazon S3 User Guide*.
     #
-    # **Access Permissions**
+    # Permissions
     #
-    # You can set access permissions using one of the following methods:
+    # : You can set access permissions using one of the following methods:
     #
-    # * Specify a canned ACL with the `x-amz-acl` 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 `x-amz-ac`l. If you use this header,
-    #   you cannot use other access control-specific headers in your
-    #   request. For more information, see [Canned ACL][4].
+    #   * Specify a canned ACL with the `x-amz-acl` 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 `x-amz-ac`l. If you
+    #     use this header, you cannot use other access control-specific
+    #     headers in your request. For more information, see [Canned
+    #     ACL][4].
     #
-    # * Specify access permissions explicitly with the `x-amz-grant-read`,
-    #   `x-amz-grant-read-acp`, `x-amz-grant-write-acp`, and
-    #   `x-amz-grant-full-control` 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
-    #   `x-amz-acl` 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 [Access Control List (ACL) Overview][2].
+    #   * Specify access permissions explicitly with the `x-amz-grant-read`,
+    #     `x-amz-grant-read-acp`, `x-amz-grant-write-acp`, and
+    #     `x-amz-grant-full-control` 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
+    #     `x-amz-acl` 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 [Access Control List (ACL) Overview][2].
     #
-    #   You specify each grantee as a type=value pair, where the type is one
-    #   of the following:
+    #     You specify each grantee as a type=value pair, where the type is
+    #     one of the following:
     #
-    #   * `id` – if the value specified is the canonical user ID of an
-    #     Amazon Web Services account
+    #     * `id` – if the value specified is the canonical user ID of an
+    #       Amazon Web Services account
     #
-    #   * `uri` – if you are granting permissions to a predefined group
+    #     * `uri` – if you are granting permissions to a predefined group
     #
-    #   * `emailAddress` – if the value specified is the email address of an
-    #     Amazon Web Services account
+    #     * `emailAddress` – if the value specified is the email address of
+    #       an Amazon Web Services account
     #
-    #     <note markdown="1"> Using email addresses to specify a grantee is only supported in
-    #     the following Amazon Web Services Regions:
+    #       <note markdown="1"> Using email addresses to specify a grantee is only supported in
+    #       the following Amazon Web Services Regions:
     #
-    #      * US East (N. Virginia)
+    #        * US East (N. Virginia)
     #
-    #     * US West (N. California)
+    #       * US West (N. California)
     #
-    #     * US West (Oregon)
+    #       * US West (Oregon)
     #
-    #     * Asia Pacific (Singapore)
+    #       * Asia Pacific (Singapore)
     #
-    #     * Asia Pacific (Sydney)
+    #       * Asia Pacific (Sydney)
     #
-    #     * Asia Pacific (Tokyo)
+    #       * Asia Pacific (Tokyo)
     #
-    #     * Europe (Ireland)
+    #       * Europe (Ireland)
     #
-    #     * South America (São Paulo)
+    #       * South America (São Paulo)
     #
-    #      For a list of all the Amazon S3 supported Regions and endpoints,
-    #     see [Regions and Endpoints][5] in the Amazon Web Services General
-    #     Reference.
+    #        For a list of all the Amazon S3 supported Regions and endpoints,
+    #       see [Regions and Endpoints][5] in the Amazon Web Services
+    #       General Reference.
     #
-    #      </note>
+    #        </note>
     #
-    #   For example, the following `x-amz-grant-read` header grants list
-    #   objects permission to the two Amazon Web Services accounts
-    #   identified by their email addresses.
+    #     For example, the following `x-amz-grant-read` header grants list
+    #     objects permission to the two Amazon Web Services accounts
+    #     identified by their email addresses.
     #
-    #   `x-amz-grant-read: emailAddress="xyz@amazon.com",
-    #   emailAddress="abc@amazon.com" `
+    #     `x-amz-grant-read: emailAddress="xyz@amazon.com",
+    #     emailAddress="abc@amazon.com" `
     #
-    # You can use either a canned ACL or specify access permissions
-    # explicitly. You cannot do both.
+    #   You can use either a canned ACL or specify access permissions
+    #   explicitly. You cannot do both.
     #
-    # **Grantee Values**
+    # Grantee Values
     #
-    # You can specify the person (grantee) to whom you're assigning access
-    # rights (using request elements) in the following ways:
+    # : You can specify the person (grantee) to whom you're assigning
+    #   access rights (using request elements) in the following ways:
     #
-    # * By the person's ID:
+    #   * By the person's ID:
     #
-    #   `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
-    #   </Grantee>`
+    #     `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
+    #     </Grantee>`
     #
-    #   DisplayName is optional and ignored in the request.
+    #     DisplayName is optional and ignored in the request.
     #
-    # * By URI:
+    #   * By URI:
     #
-    #   `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>`
+    #     `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>`
     #
-    # * By Email address:
+    #   * By Email address:
     #
-    #   `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    #   xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>lt;/Grantee>`
+    #     `<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    #     xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>lt;/Grantee>`
     #
-    #   The grantee is resolved to the CanonicalUser and, in a response to a
-    #   GET Object acl request, appears as the CanonicalUser.
+    #     The grantee is resolved to the CanonicalUser and, in a response to
+    #     a GET Object acl request, appears as the CanonicalUser.
     #
-    #   <note markdown="1"> Using email addresses to specify a grantee is only supported in the
-    #   following Amazon Web Services Regions:
+    #     <note markdown="1"> Using email addresses to specify a grantee is only supported in
+    #     the following Amazon Web Services Regions:
     #
-    #    * US East (N. Virginia)
+    #      * US East (N. Virginia)
     #
-    #   * US West (N. California)
+    #     * US West (N. California)
     #
-    #   * US West (Oregon)
+    #     * US West (Oregon)
     #
-    #   * Asia Pacific (Singapore)
+    #     * Asia Pacific (Singapore)
     #
-    #   * Asia Pacific (Sydney)
+    #     * Asia Pacific (Sydney)
     #
-    #   * Asia Pacific (Tokyo)
+    #     * Asia Pacific (Tokyo)
     #
-    #   * Europe (Ireland)
+    #     * Europe (Ireland)
     #
-    #   * South America (São Paulo)
+    #     * South America (São Paulo)
     #
-    #    For a list of all the Amazon S3 supported Regions and endpoints, see
-    #   [Regions and Endpoints][5] in the Amazon Web Services General
-    #   Reference.
+    #      For a list of all the Amazon S3 supported Regions and endpoints,
+    #     see [Regions and Endpoints][5] in the Amazon Web Services General
+    #     Reference.
     #
-    #    </note>
+    #      </note>
     #
-    # **Versioning**
+    # Versioning
     #
-    # 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 `versionId` subresource.
+    # : 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 `versionId` subresource.
     #
-    # **Related Resources**
+    # The following operations are related to `PutObjectAcl`:
     #
     # * [CopyObject][6]
     #
@@ -13207,7 +13368,7 @@ module Aws::S3
     # For information about the Amazon S3 object tagging feature, see
     # [Object Tagging][3].
     #
-    # **Special Errors**
+    # `PutObjectTagging` has the following special errors:
     #
     # * * <i>Code: InvalidTagError </i>
     #
@@ -13229,7 +13390,7 @@ module Aws::S3
     #   * *Cause: The service was unable to apply the provided tag to the
     #     object.*
     #
-    # **Related Resources**
+    # The following operations are related to `PutObjectTagging`:
     #
     # * [GetObjectTagging][1]
     #
@@ -13395,7 +13556,7 @@ module Aws::S3
     # For more information about when Amazon S3 considers a bucket or an
     # object public, see [The Meaning of "Public"][2].
     #
-    # **Related Resources**
+    # The following operations are related to `PutPublicAccessBlock`:
     #
     # * [GetPublicAccessBlock][3]
     #
@@ -13493,44 +13654,37 @@ module Aws::S3
     #
     # * `restore an archive` - Restore an archived object
     #
-    # To use this operation, you must have permissions to perform the
-    # `s3:RestoreObject` action. The bucket owner has this permission by
-    # default and can grant this permission to others. For more information
-    # about permissions, see [Permissions Related to Bucket Subresource
-    # Operations][1] and [Managing Access Permissions to Your Amazon S3
-    # Resources][2] in the *Amazon S3 User Guide*.
-    #
     # For more information about the `S3` structure in the request body, see
     # the following:
     #
-    # * * [PutObject][3]
+    # * [PutObject][1]
     #
-    #   * [Managing Access with ACLs][4] in the *Amazon S3 User Guide*
+    # * [Managing Access with ACLs][2] in the *Amazon S3 User Guide*
     #
-    #   * [Protecting Data Using Server-Side Encryption][5] in the *Amazon
-    #     S3 User Guide*
+    # * [Protecting Data Using Server-Side Encryption][3] in the *Amazon S3
+    #   User Guide*
     #
-    # * Define the SQL expression for the `SELECT` type of restoration for
-    #   your query in the request body's `SelectParameters` structure. You
-    #   can use expressions like the following examples.
+    # Define the SQL expression for the `SELECT` type of restoration for
+    # your query in the request body's `SelectParameters` structure. You
+    # can use expressions like the following examples.
     #
-    #   * The following expression returns all records from the specified
-    #     object.
+    # * The following expression returns all records from the specified
+    #   object.
     #
-    #     `SELECT * FROM Object`
+    #   `SELECT * FROM Object`
     #
-    #   * Assuming that you are not using any headers for data stored in the
-    #     object, you can specify columns with positional headers.
+    # * Assuming that you are not using any headers for data stored in the
+    #   object, you can specify columns with positional headers.
     #
-    #     `SELECT s._1, s._2 FROM Object s WHERE s._3 > 100`
+    #   `SELECT s._1, s._2 FROM Object s WHERE s._3 > 100`
     #
-    #   * If you have headers and you set the `fileHeaderInfo` in the `CSV`
-    #     structure in the request body to `USE`, you can specify headers in
-    #     the query. (If you set the `fileHeaderInfo` field to `IGNORE`, the
-    #     first row is skipped for the query.) You cannot mix ordinal
-    #     positions with header column names.
+    # * If you have headers and you set the `fileHeaderInfo` in the `CSV`
+    #   structure in the request body to `USE`, you can specify headers in
+    #   the query. (If you set the `fileHeaderInfo` field to `IGNORE`, the
+    #   first row is skipped for the query.) You cannot mix ordinal
+    #   positions with header column names.
     #
-    #     `SELECT s.Id, s.FirstName, s.SSN FROM S3Object s`
+    #   `SELECT s.Id, s.FirstName, s.SSN FROM S3Object s`
     #
     # When making a select request, you can also do the following:
     #
@@ -13546,7 +13700,7 @@ module Aws::S3
     #
     # * The output results are new Amazon S3 objects. Unlike archive
     #   retrievals, they are stored until explicitly deleted-manually or
-    #   through a lifecycle policy.
+    #   through a lifecycle configuration.
     #
     # * You can issue more than one select request on the same Amazon S3
     #   object. Amazon S3 doesn't duplicate requests, so avoid issuing
@@ -13555,128 +13709,141 @@ module Aws::S3
     # * Amazon S3 accepts a select request even if the object has already
     #   been restored. A select request doesn’t return error response `409`.
     #
-    # **Restoring objects**
-    #
-    # Objects that you archive to the S3 Glacier Flexible Retrieval or S3
-    # Glacier Deep Archive storage class, and S3 Intelligent-Tiering Archive
-    # or S3 Intelligent-Tiering Deep Archive tiers, are not accessible in
-    # real time. For objects in the S3 Glacier Flexible Retrieval or S3
-    # Glacier Deep Archive storage classes, you must first initiate a
-    # restore request, and then wait until a temporary copy of the object is
-    # available. If you want a permanent copy of the object, create a copy
-    # of it in the Amazon S3 Standard storage class in your S3 bucket. To
-    # access an archived object, you must restore the object for the
-    # duration (number of days) that you specify. For objects in the Archive
-    # Access or Deep Archive Access tiers of S3 Intelligent-Tiering, you
-    # must first initiate a restore request, and then wait until the object
-    # is moved into the Frequent Access tier.
-    #
-    # To restore a specific object version, you can provide a version ID. If
-    # you don't provide a version ID, Amazon S3 restores the current
-    # version.
-    #
-    # When restoring an archived object, you can specify one of the
-    # following data access tier options in the `Tier` element of the
-    # request body:
-    #
-    # * `Expedited` - Expedited retrievals allow you to quickly access your
-    #   data stored in the S3 Glacier Flexible Retrieval storage class or S3
-    #   Intelligent-Tiering Archive tier when occasional urgent requests for
-    #   a subset of archives are required. For all but the largest archived
-    #   objects (250 MB+), data accessed using Expedited retrievals is
-    #   typically made available within 1–5 minutes. Provisioned capacity
-    #   ensures that retrieval capacity for Expedited retrievals is
-    #   available when you need it. Expedited retrievals and provisioned
-    #   capacity are not available for objects stored in the S3 Glacier Deep
-    #   Archive storage class or S3 Intelligent-Tiering Deep Archive tier.
-    #
-    # * `Standard` - Standard retrievals allow you to access any of your
-    #   archived objects within several hours. This is the default option
-    #   for retrieval requests that do not specify the retrieval option.
-    #   Standard retrievals typically finish within 3–5 hours for objects
-    #   stored in the S3 Glacier Flexible Retrieval storage class or S3
-    #   Intelligent-Tiering Archive tier. They typically finish within 12
-    #   hours for objects stored in the S3 Glacier Deep Archive storage
-    #   class or S3 Intelligent-Tiering Deep Archive tier. Standard
-    #   retrievals are free for objects stored in S3 Intelligent-Tiering.
-    #
-    # * `Bulk` - Bulk retrievals free for objects stored in the S3 Glacier
-    #   Flexible Retrieval and S3 Intelligent-Tiering storage classes,
-    #   enabling you to retrieve large amounts, even petabytes, of data at
-    #   no cost. Bulk retrievals typically finish within 5–12 hours for
-    #   objects stored in the S3 Glacier Flexible Retrieval storage class or
-    #   S3 Intelligent-Tiering Archive tier. Bulk retrievals are also the
-    #   lowest-cost retrieval option when restoring objects from S3 Glacier
-    #   Deep Archive. They typically finish within 48 hours for objects
-    #   stored in the S3 Glacier Deep Archive storage class or S3
-    #   Intelligent-Tiering Deep Archive tier.
-    #
-    # For more information about archive retrieval options and provisioned
-    # capacity for `Expedited` data access, see [Restoring Archived
-    # Objects][6] in the *Amazon S3 User Guide*.
-    #
-    # You can use Amazon S3 restore speed upgrade to change the restore
-    # speed to a faster speed while it is in progress. For more information,
-    # see [ Upgrading the speed of an in-progress restore][7] in the *Amazon
-    # S3 User Guide*.
+    # Permissions
+    #
+    # : To use this operation, you must have permissions to perform the
+    #   `s3:RestoreObject` action. The bucket owner has this permission by
+    #   default and can grant this permission to others. For more
+    #   information about permissions, see [Permissions Related to Bucket
+    #   Subresource Operations][4] and [Managing Access Permissions to Your
+    #   Amazon S3 Resources][5] in the *Amazon S3 User Guide*.
+    #
+    # Restoring objects
+    #
+    # : Objects that you archive to the S3 Glacier Flexible Retrieval or S3
+    #   Glacier Deep Archive storage class, and S3 Intelligent-Tiering
+    #   Archive or S3 Intelligent-Tiering Deep Archive tiers, are not
+    #   accessible in real time. For objects in the S3 Glacier Flexible
+    #   Retrieval or S3 Glacier Deep Archive storage classes, you must first
+    #   initiate a restore request, and then wait until a temporary copy of
+    #   the object is available. If you want a permanent copy of the object,
+    #   create a copy of it in the Amazon S3 Standard storage class in your
+    #   S3 bucket. To access an archived object, you must restore the object
+    #   for the duration (number of days) that you specify. For objects in
+    #   the Archive Access or Deep Archive Access tiers of S3
+    #   Intelligent-Tiering, you must first initiate a restore request, and
+    #   then wait until the object is moved into the Frequent Access tier.
+    #
+    #   To restore a specific object version, you can provide a version ID.
+    #   If you don't provide a version ID, Amazon S3 restores the current
+    #   version.
+    #
+    #   When restoring an archived object, you can specify one of the
+    #   following data access tier options in the `Tier` element of the
+    #   request body:
+    #
+    #   * `Expedited` - Expedited retrievals allow you to quickly access
+    #     your data stored in the S3 Glacier Flexible Retrieval storage
+    #     class or S3 Intelligent-Tiering Archive tier when occasional
+    #     urgent requests for restoring archives are required. For all but
+    #     the largest archived objects (250 MB+), data accessed using
+    #     Expedited retrievals is typically made available within 1–5
+    #     minutes. Provisioned capacity ensures that retrieval capacity for
+    #     Expedited retrievals is available when you need it. Expedited
+    #     retrievals and provisioned capacity are not available for objects
+    #     stored in the S3 Glacier Deep Archive storage class or S3
+    #     Intelligent-Tiering Deep Archive tier.
+    #
+    #   * `Standard` - Standard retrievals allow you to access any of your
+    #     archived objects within several hours. This is the default option
+    #     for retrieval requests that do not specify the retrieval option.
+    #     Standard retrievals typically finish within 3–5 hours for objects
+    #     stored in the S3 Glacier Flexible Retrieval storage class or S3
+    #     Intelligent-Tiering Archive tier. They typically finish within 12
+    #     hours for objects stored in the S3 Glacier Deep Archive storage
+    #     class or S3 Intelligent-Tiering Deep Archive tier. Standard
+    #     retrievals are free for objects stored in S3 Intelligent-Tiering.
+    #
+    #   * `Bulk` - Bulk retrievals free for objects stored in the S3 Glacier
+    #     Flexible Retrieval and S3 Intelligent-Tiering storage classes,
+    #     enabling you to retrieve large amounts, even petabytes, of data at
+    #     no cost. Bulk retrievals typically finish within 5–12 hours for
+    #     objects stored in the S3 Glacier Flexible Retrieval storage class
+    #     or S3 Intelligent-Tiering Archive tier. Bulk retrievals are also
+    #     the lowest-cost retrieval option when restoring objects from S3
+    #     Glacier Deep Archive. They typically finish within 48 hours for
+    #     objects stored in the S3 Glacier Deep Archive storage class or S3
+    #     Intelligent-Tiering Deep Archive tier.
+    #
+    #   For more information about archive retrieval options and provisioned
+    #   capacity for `Expedited` data access, see [Restoring Archived
+    #   Objects][6] in the *Amazon S3 User Guide*.
+    #
+    #   You can use Amazon S3 restore speed upgrade to change the restore
+    #   speed to a faster speed while it is in progress. For more
+    #   information, see [ Upgrading the speed of an in-progress restore][7]
+    #   in the *Amazon S3 User Guide*.
     #
-    # To get the status of object restoration, you can send a `HEAD`
-    # request. Operations return the `x-amz-restore` header, which provides
-    # information about the restoration status, in the response. You can use
-    # Amazon S3 event notifications to notify you when a restore is
-    # initiated or completed. For more information, see [Configuring Amazon
-    # S3 Event Notifications][8] in the *Amazon S3 User Guide*.
+    #   To get the status of object restoration, you can send a `HEAD`
+    #   request. Operations return the `x-amz-restore` header, which
+    #   provides information about the restoration status, in the response.
+    #   You can use Amazon S3 event notifications to notify you when a
+    #   restore is initiated or completed. For more information, see
+    #   [Configuring Amazon S3 Event Notifications][8] in the *Amazon S3
+    #   User Guide*.
     #
-    # After restoring an archived object, you can update the restoration
-    # period by reissuing the request with a new period. Amazon S3 updates
-    # the restoration period relative to the current time and charges only
-    # for the request-there are no data transfer charges. You cannot update
-    # the restoration period when Amazon S3 is actively processing your
-    # current restore request for the object.
+    #   After restoring an archived object, you can update the restoration
+    #   period by reissuing the request with a new period. Amazon S3 updates
+    #   the restoration period relative to the current time and charges only
+    #   for the request-there are no data transfer charges. You cannot
+    #   update the restoration period when Amazon S3 is actively processing
+    #   your current restore request for the object.
     #
-    # If your bucket has a lifecycle configuration with a rule that includes
-    # an expiration action, the object expiration overrides the life span
-    # that you specify in a restore request. For example, if you restore an
-    # object copy for 10 days, but the object is scheduled to expire in 3
-    # days, Amazon S3 deletes the object in 3 days. For more information
-    # about lifecycle configuration, see
-    # [PutBucketLifecycleConfiguration][9] and [Object Lifecycle
-    # Management][10] in *Amazon S3 User Guide*.
+    #   If your bucket has a lifecycle configuration with a rule that
+    #   includes an expiration action, the object expiration overrides the
+    #   life span that you specify in a restore request. For example, if you
+    #   restore an object copy for 10 days, but the object is scheduled to
+    #   expire in 3 days, Amazon S3 deletes the object in 3 days. For more
+    #   information about lifecycle configuration, see
+    #   [PutBucketLifecycleConfiguration][9] and [Object Lifecycle
+    #   Management][10] in *Amazon S3 User Guide*.
     #
-    # **Responses**
+    # Responses
     #
-    # A successful action returns either the `200 OK` or `202 Accepted`
-    # status code.
+    # : A successful action returns either the `200 OK` or `202 Accepted`
+    #   status code.
     #
-    # * If the object is not previously restored, then Amazon S3 returns
-    #   `202 Accepted` in the response.
+    #   * If the object is not previously restored, then Amazon S3 returns
+    #     `202 Accepted` in the response.
     #
-    # * If the object is previously restored, Amazon S3 returns `200 OK` in
-    #   the response.
+    #   * If the object is previously restored, Amazon S3 returns `200 OK`
+    #     in the response.
+    #   ^
     #
-    # **Special Errors**
+    #   * Special errors:
     #
-    # * * *Code: RestoreAlreadyInProgress*
+    #     * *Code: RestoreAlreadyInProgress*
     #
-    #   * *Cause: Object restore is already in progress. (This error does
-    #     not apply to SELECT type requests.)*
+    #     * *Cause: Object restore is already in progress. (This error does
+    #       not apply to SELECT type requests.)*
     #
-    #   * *HTTP Status Code: 409 Conflict*
+    #     * *HTTP Status Code: 409 Conflict*
     #
-    #   * *SOAP Fault Code Prefix: Client*
+    #     * *SOAP Fault Code Prefix: Client*
     #
-    # * * *Code: GlacierExpeditedRetrievalNotAvailable*
+    #   * * *Code: GlacierExpeditedRetrievalNotAvailable*
     #
-    #   * *Cause: expedited retrievals are currently not available. Try
-    #     again later. (Returned if there is insufficient capacity to
-    #     process the Expedited request. This error applies only to
-    #     Expedited retrievals and not to S3 Standard or Bulk retrievals.)*
+    #     * *Cause: expedited retrievals are currently not available. Try
+    #       again later. (Returned if there is insufficient capacity to
+    #       process the Expedited request. This error applies only to
+    #       Expedited retrievals and not to S3 Standard or Bulk
+    #       retrievals.)*
     #
-    #   * *HTTP Status Code: 503*
+    #     * *HTTP Status Code: 503*
     #
-    #   * *SOAP Fault Code Prefix: N/A*
+    #     * *SOAP Fault Code Prefix: N/A*
     #
-    # **Related Resources**
+    # The following operations are related to `RestoreObject`:
     #
     # * [PutBucketLifecycleConfiguration][9]
     #
@@ -13684,11 +13851,11 @@ module Aws::S3
     #
     #
     #
-    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources
-    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html
-    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html
-    # [4]: https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html
-    # [5]: https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html
+    # [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html
+    # [2]: https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html
+    # [3]: https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html
+    # [4]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources
+    # [5]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html
     # [6]: https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html
     # [7]: https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html#restoring-objects-upgrade-tier.title.html
     # [8]: https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html
@@ -13870,7 +14037,7 @@ module Aws::S3
     #               value: "MetadataValue",
     #             },
     #           ],
-    #           storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR
+    #           storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR, SNOW
     #         },
     #       },
     #     },
@@ -13909,80 +14076,76 @@ module Aws::S3
     #
     #
     #
-    # **Permissions**
+    # Permissions
     #
-    # You must have `s3:GetObject` permission for this operation. Amazon S3
-    # Select does not support anonymous access. For more information about
-    # permissions, see [Specifying Permissions in a Policy][3] in the
-    # *Amazon S3 User Guide*.
+    # : You must have `s3:GetObject` permission for this operation. Amazon
+    #   S3 Select does not support anonymous access. For more information
+    #   about permissions, see [Specifying Permissions in a Policy][3] in
+    #   the *Amazon S3 User Guide*.
     #
+    # Object Data Formats
     #
+    # : You can use Amazon S3 Select to query objects that have the
+    #   following format properties:
     #
-    # *Object Data Formats*
+    #   * *CSV, JSON, and Parquet* - Objects must be in CSV, JSON, or
+    #     Parquet format.
     #
-    # You can use Amazon S3 Select to query objects that have the following
-    # format properties:
+    #   * *UTF-8* - UTF-8 is the only encoding type Amazon S3 Select
+    #     supports.
     #
-    # * *CSV, JSON, and Parquet* - Objects must be in CSV, JSON, or Parquet
-    #   format.
+    #   * *GZIP or BZIP2* - CSV and JSON files can be compressed using GZIP
+    #     or BZIP2. GZIP and BZIP2 are the only compression formats that
+    #     Amazon S3 Select supports for CSV and JSON files. Amazon S3 Select
+    #     supports columnar compression for Parquet using GZIP or Snappy.
+    #     Amazon S3 Select does not support whole-object compression for
+    #     Parquet objects.
     #
-    # * *UTF-8* - UTF-8 is the only encoding type Amazon S3 Select supports.
+    #   * *Server-side encryption* - Amazon S3 Select supports querying
+    #     objects that are protected with server-side encryption.
     #
-    # * *GZIP or BZIP2* - CSV and JSON files can be compressed using GZIP or
-    #   BZIP2. GZIP and BZIP2 are the only compression formats that Amazon
-    #   S3 Select supports for CSV and JSON files. Amazon S3 Select supports
-    #   columnar compression for Parquet using GZIP or Snappy. Amazon S3
-    #   Select does not support whole-object compression for Parquet
-    #   objects.
+    #     For objects that are encrypted with customer-provided encryption
+    #     keys (SSE-C), you must use HTTPS, and you must use the headers
+    #     that are documented in the [GetObject][4]. For more information
+    #     about SSE-C, see [Server-Side Encryption (Using Customer-Provided
+    #     Encryption Keys)][5] in the *Amazon S3 User Guide*.
     #
-    # * *Server-side encryption* - Amazon S3 Select supports querying
-    #   objects that are protected with server-side encryption.
+    #     For objects that are encrypted with Amazon S3 managed keys
+    #     (SSE-S3) and Amazon Web Services KMS keys (SSE-KMS), server-side
+    #     encryption is handled transparently, so you don't need to specify
+    #     anything. For more information about server-side encryption,
+    #     including SSE-S3 and SSE-KMS, see [Protecting Data Using
+    #     Server-Side Encryption][6] in the *Amazon S3 User Guide*.
     #
-    #   For objects that are encrypted with customer-provided encryption
-    #   keys (SSE-C), you must use HTTPS, and you must use the headers that
-    #   are documented in the [GetObject][4]. For more information about
-    #   SSE-C, see [Server-Side Encryption (Using Customer-Provided
-    #   Encryption Keys)][5] in the *Amazon S3 User Guide*.
+    # Working with the Response Body
     #
-    #   For objects that are encrypted with Amazon S3 managed keys (SSE-S3)
-    #   and Amazon Web Services KMS keys (SSE-KMS), server-side encryption
-    #   is handled transparently, so you don't need to specify anything.
-    #   For more information about server-side encryption, including SSE-S3
-    #   and SSE-KMS, see [Protecting Data Using Server-Side Encryption][6]
-    #   in the *Amazon S3 User Guide*.
+    # : Given the response size is unknown, Amazon S3 Select streams the
+    #   response as a series of messages and includes a `Transfer-Encoding`
+    #   header with `chunked` as its value in the response. For more
+    #   information, see [Appendix: SelectObjectContent Response][7].
     #
-    # **Working with the Response Body**
+    # GetObject Support
     #
-    # Given the response size is unknown, Amazon S3 Select streams the
-    # response as a series of messages and includes a `Transfer-Encoding`
-    # header with `chunked` as its value in the response. For more
-    # information, see [Appendix: SelectObjectContent Response][7].
+    # : The `SelectObjectContent` action does not support the following
+    #   `GetObject` functionality. For more information, see [GetObject][4].
     #
+    #   * `Range`: Although you can specify a scan range for an Amazon S3
+    #     Select request (see [SelectObjectContentRequest - ScanRange][8] in
+    #     the request parameters), you cannot specify the range of bytes of
+    #     an object to return.
     #
+    #   * GLACIER, DEEP\_ARCHIVE and REDUCED\_REDUNDANCY storage classes:
+    #     You cannot specify the GLACIER, DEEP\_ARCHIVE, or
+    #     `REDUCED_REDUNDANCY` storage classes. For more information, about
+    #     storage classes see [Storage Classes][9] in the *Amazon S3 User
+    #     Guide*.
     #
-    # **GetObject Support**
+    # Special Errors
     #
-    # The `SelectObjectContent` action does not support the following
-    # `GetObject` functionality. For more information, see [GetObject][4].
+    # : For a list of special errors for this operation, see [List of SELECT
+    #   Object Content Error Codes][10]
     #
-    # * `Range`: Although you can specify a scan range for an Amazon S3
-    #   Select request (see [SelectObjectContentRequest - ScanRange][8] in
-    #   the request parameters), you cannot specify the range of bytes of an
-    #   object to return.
-    #
-    # * GLACIER, DEEP\_ARCHIVE and REDUCED\_REDUNDANCY storage classes: You
-    #   cannot specify the GLACIER, DEEP\_ARCHIVE, or `REDUCED_REDUNDANCY`
-    #   storage classes. For more information, about storage classes see
-    #   [Storage Classes][9] in the *Amazon S3 User Guide*.
-    #
-    #
-    #
-    # **Special Errors**
-    #
-    # For a list of special errors for this operation, see [List of SELECT
-    # Object Content Error Codes][10]
-    #
-    # **Related Resources**
+    # The following operations are related to `SelectObjectContent`:
     #
     # * [GetObject][4]
     #
@@ -14389,7 +14552,7 @@ module Aws::S3
     #
     # * x-amz-server-side-encryption-customer-key-MD5
     #
-    # **Special Errors**
+    # `UploadPart` has the following special errors:
     #
     # * * *Code: NoSuchUpload*
     #
@@ -14401,7 +14564,7 @@ module Aws::S3
     #
     #   * *SOAP Fault Code Prefix: Client*
     #
-    # **Related Resources**
+    # The following operations are related to `UploadPart`:
     #
     # * [CreateMultipartUpload][2]
     #
@@ -14717,42 +14880,41 @@ module Aws::S3
     #
     #   Amazon S3 returns `412 Precondition Failed` response code.
     #
-    # **Versioning**
+    # Versioning
     #
-    # If your bucket has versioning enabled, you could have multiple
-    # versions of the same object. By default, `x-amz-copy-source`
-    # identifies the current version of the object to copy. If the current
-    # version is a delete marker and you don't specify a versionId in the
-    # `x-amz-copy-source`, Amazon S3 returns a 404 error, because the object
-    # does not exist. If you specify versionId in the `x-amz-copy-source`
-    # and the versionId is a delete marker, Amazon S3 returns an HTTP 400
-    # error, because you are not allowed to specify a delete marker as a
-    # version for the `x-amz-copy-source`.
+    # : If your bucket has versioning enabled, you could have multiple
+    #   versions of the same object. By default, `x-amz-copy-source`
+    #   identifies the current version of the object to copy. If the current
+    #   version is a delete marker and you don't specify a versionId in the
+    #   `x-amz-copy-source`, Amazon S3 returns a 404 error, because the
+    #   object does not exist. If you specify versionId in the
+    #   `x-amz-copy-source` and the versionId is a delete marker, Amazon S3
+    #   returns an HTTP 400 error, because you are not allowed to specify a
+    #   delete marker as a version for the `x-amz-copy-source`.
     #
-    # You can optionally specify a specific version of the source object to
-    # copy by adding the `versionId` subresource as shown in the following
-    # example:
+    #   You can optionally specify a specific version of the source object
+    #   to copy by adding the `versionId` subresource as shown in the
+    #   following example:
     #
-    # `x-amz-copy-source: /bucket/object?versionId=version id`
+    #   `x-amz-copy-source: /bucket/object?versionId=version id`
     #
-    # **Special Errors**
+    # Special errors
+    # : * * *Code: NoSuchUpload*
     #
-    # * * *Code: NoSuchUpload*
-    #
-    #   * *Cause: The specified multipart upload does not exist. The upload
-    #     ID might be invalid, or the multipart upload might have been
-    #     aborted or completed.*
+    #     * *Cause: The specified multipart upload does not exist. The
+    #       upload ID might be invalid, or the multipart upload might have
+    #       been aborted or completed.*
     #
-    #   * *HTTP Status Code: 404 Not Found*
+    #     * *HTTP Status Code: 404 Not Found*
     #
-    # * * *Code: InvalidRequest*
+    #   * * *Code: InvalidRequest*
     #
-    #   * *Cause: The specified copy source is not supported as a byte-range
-    #     copy source.*
+    #     * *Cause: The specified copy source is not supported as a
+    #       byte-range copy source.*
     #
-    #   * *HTTP Status Code: 400 Bad Request*
+    #     * *HTTP Status Code: 400 Bad Request*
     #
-    # **Related Resources**
+    # The following operations are related to `UploadPartCopy`:
     #
     # * [CreateMultipartUpload][7]
     #
@@ -15108,9 +15270,7 @@ module Aws::S3
     #
     # @option params [Integer] :status_code
     #   The integer status code for an HTTP response of a corresponding
-    #   `GetObject` request.
-    #
-    #   **Status Codes**
+    #   `GetObject` request. The following is a list of status codes.
     #
     #   * `200 - OK`
     #
@@ -15408,7 +15568,7 @@ module Aws::S3
     #     sse_customer_algorithm: "SSECustomerAlgorithm",
     #     ssekms_key_id: "SSEKMSKeyId",
     #     sse_customer_key_md5: "SSECustomerKeyMD5",
-    #     storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR
+    #     storage_class: "STANDARD", # accepts STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, DEEP_ARCHIVE, OUTPOSTS, GLACIER_IR, SNOW
     #     tag_count: 1,
     #     version_id: "ObjectVersionId",
     #     bucket_key_enabled: false,
@@ -15436,7 +15596,7 @@ module Aws::S3
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-s3'
-      context[:gem_version] = '1.120.1'
+      context[:gem_version] = '1.122.0'
       Seahorse::Client::Request.new(handlers, context)
     end