aws-sdk-s3 1.178.0 → 1.183.0

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

@@ -70,8 +70,10 @@ module Aws::S3
 
     # The class of storage used to store the object.
     #
-    # <note markdown="1"> **Directory buckets** - Only the S3 Express One Zone storage class is
-    # supported by directory buckets to store objects.
+    # <note markdown="1"> **Directory buckets** - Directory buckets only support
+    # `EXPRESS_ONEZONE` (the S3 Express One Zone storage class) in
+    # Availability Zones and `ONEZONE_IA` (the S3 One Zone-Infrequent Access
+    # storage class) in Dedicated Local Zones.
     #
     #  </note>
     # @return [String]
@@ -335,7 +337,7 @@ module Aws::S3
     # @option options [String] :checksum_crc32
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 32-bit `CRC-32` checksum of the object.
+    #   specifies the Base64 encoded, 32-bit `CRC32` checksum of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #
@@ -345,7 +347,7 @@ module Aws::S3
     # @option options [String] :checksum_crc32c
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 32-bit `CRC-32C` checksum of the object.
+    #   specifies the Base64 encoded, 32-bit `CRC32C` checksum of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #
@@ -355,10 +357,10 @@ module Aws::S3
     # @option options [String] :checksum_crc64nvme
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 64-bit `CRC-64NVME` checksum of the
-    #   object. The `CRC-64NVME` checksum is always a full object checksum.
-    #   For more information, see [Checking object integrity in the Amazon S3
-    #   User Guide][1].
+    #   specifies the Base64 encoded, 64-bit `CRC64NVME` checksum of the
+    #   object. The `CRC64NVME` checksum is always a full object checksum. For
+    #   more information, see [Checking object integrity in the Amazon S3 User
+    #   Guide][1].
     #
     #
     #
@@ -366,9 +368,9 @@ module Aws::S3
     # @option options [String] :checksum_sha1
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 160-bit `SHA-1` digest of the object.
-    #   For more information, see [Checking object integrity][1] in the
-    #   *Amazon S3 User Guide*.
+    #   specifies the Base64 encoded, 160-bit `SHA1` digest of the object. For
+    #   more information, see [Checking object integrity][1] in the *Amazon S3
+    #   User Guide*.
     #
     #
     #
@@ -376,7 +378,7 @@ module Aws::S3
     # @option options [String] :checksum_sha256
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 256-bit `SHA-256` digest of the object.
+    #   specifies the Base64 encoded, 256-bit `SHA256` digest of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #

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

@@ -76,10 +76,10 @@ module Aws::S3
       data[:size]
     end
 
-    # The Base64 encoded, 32-bit `CRC-32` checksum of the part. This
-    # checksum is present if the object was uploaded with the `CRC-32`
-    # checksum algorithm. For more information, see [Checking object
-    # integrity][1] in the *Amazon S3 User Guide*.
+    # The Base64 encoded, 32-bit `CRC32` checksum of the part. This checksum
+    # is present if the object was uploaded with the `CRC32` checksum
+    # algorithm. For more information, see [Checking object integrity][1] in
+    # the *Amazon S3 User Guide*.
     #
     #
     #
@@ -89,8 +89,8 @@ module Aws::S3
       data[:checksum_crc32]
     end
 
-    # The Base64 encoded, 32-bit `CRC-32C` checksum of the part. This
-    # checksum is present if the object was uploaded with the `CRC-32C`
+    # The Base64 encoded, 32-bit `CRC32C` checksum of the part. This
+    # checksum is present if the object was uploaded with the `CRC32C`
     # checksum algorithm. For more information, see [Checking object
     # integrity][1] in the *Amazon S3 User Guide*.
     #
@@ -102,11 +102,11 @@ module Aws::S3
       data[:checksum_crc32c]
     end
 
-    # The Base64 encoded, 64-bit `CRC-64NVME` checksum of the part. This
+    # The Base64 encoded, 64-bit `CRC64NVME` checksum of the part. This
     # checksum is present if the multipart upload request was created with
-    # the `CRC-64NVME` checksum algorithm, or if the object was uploaded
+    # the `CRC64NVME` checksum algorithm, or if the object was uploaded
     # without a checksum (and Amazon S3 added the default checksum,
-    # `CRC-64NVME`, to the uploaded object). For more information, see
+    # `CRC64NVME`, to the uploaded object). For more information, see
     # [Checking object integrity][1] in the *Amazon S3 User Guide*.
     #
     #
@@ -117,10 +117,10 @@ module Aws::S3
       data[:checksum_crc64nvme]
     end
 
-    # The Base64 encoded, 160-bit `SHA-1` checksum of the part. This
-    # checksum is present if the object was uploaded with the `SHA-1`
-    # checksum algorithm. For more information, see [Checking object
-    # integrity][1] in the *Amazon S3 User Guide*.
+    # The Base64 encoded, 160-bit `SHA1` checksum of the part. This checksum
+    # is present if the object was uploaded with the `SHA1` checksum
+    # algorithm. For more information, see [Checking object integrity][1] in
+    # the *Amazon S3 User Guide*.
     #
     #
     #
@@ -130,8 +130,8 @@ module Aws::S3
       data[:checksum_sha1]
     end
 
-    # The Base64 encoded, 256-bit `SHA-256` checksum of the part. This
-    # checksum is present if the object was uploaded with the `SHA-256`
+    # The Base64 encoded, 256-bit `SHA256` checksum of the part. This
+    # checksum is present if the object was uploaded with the `SHA256`
     # checksum algorithm. For more information, see [Checking object
     # integrity][1] in the *Amazon S3 User Guide*.
     #
@@ -564,7 +564,7 @@ module Aws::S3
     # @option options [String] :checksum_crc32
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 32-bit `CRC-32` checksum of the object.
+    #   specifies the Base64 encoded, 32-bit `CRC32` checksum of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #
@@ -574,7 +574,7 @@ module Aws::S3
     # @option options [String] :checksum_crc32c
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 32-bit `CRC-32C` checksum of the object.
+    #   specifies the Base64 encoded, 32-bit `CRC32C` checksum of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #
@@ -584,8 +584,8 @@ module Aws::S3
     # @option options [String] :checksum_crc64nvme
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 64-bit `CRC-64NVME` checksum of the
-    #   part. For more information, see [Checking object integrity][1] in the
+    #   specifies the Base64 encoded, 64-bit `CRC64NVME` checksum of the part.
+    #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #
     #
@@ -594,9 +594,9 @@ module Aws::S3
     # @option options [String] :checksum_sha1
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 160-bit `SHA-1` digest of the object.
-    #   For more information, see [Checking object integrity][1] in the
-    #   *Amazon S3 User Guide*.
+    #   specifies the Base64 encoded, 160-bit `SHA1` digest of the object. For
+    #   more information, see [Checking object integrity][1] in the *Amazon S3
+    #   User Guide*.
     #
     #
     #
@@ -604,7 +604,7 @@ module Aws::S3
     # @option options [String] :checksum_sha256
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 256-bit `SHA-256` digest of the object.
+    #   specifies the Base64 encoded, 256-bit `SHA256` digest of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #

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

@@ -97,9 +97,10 @@ module Aws::S3
     # For more information about archiving objects, see [Transitioning
     # Objects: General Considerations][2].
     #
-    # <note markdown="1"> This functionality is not supported for directory buckets. Only the S3
-    # Express One Zone storage class is supported by directory buckets to
-    # store objects.
+    # <note markdown="1"> This functionality is not supported for directory buckets. Directory
+    # buckets only support `EXPRESS_ONEZONE` (the S3 Express One Zone
+    # storage class) in Availability Zones and `ONEZONE_IA` (the S3 One
+    # Zone-Infrequent Access storage class) in Dedicated Local Zones.
     #
     #  </note>
     #
@@ -134,7 +135,7 @@ module Aws::S3
       data[:content_length]
     end
 
-    # The Base64 encoded, 32-bit `CRC-32 checksum` of the object. This
+    # The Base64 encoded, 32-bit `CRC32 checksum` of the object. This
     # checksum is only be present if the checksum was uploaded with the
     # object. When you use an API operation on an object that was uploaded
     # using multipart uploads, this value may not be a direct checksum value
@@ -151,7 +152,7 @@ module Aws::S3
       data[:checksum_crc32]
     end
 
-    # The Base64 encoded, 32-bit `CRC-32C` checksum of the object. This
+    # The Base64 encoded, 32-bit `CRC32C` checksum of the object. This
     # checksum is only present if the checksum was uploaded with the object.
     # When you use an API operation on an object that was uploaded using
     # multipart uploads, this value may not be a direct checksum value of
@@ -168,7 +169,7 @@ module Aws::S3
       data[:checksum_crc32c]
     end
 
-    # The Base64 encoded, 64-bit `CRC-64NVME` checksum of the object. For
+    # The Base64 encoded, 64-bit `CRC64NVME` checksum of the object. For
     # more information, see [Checking object integrity in the Amazon S3 User
     # Guide][1].
     #
@@ -180,7 +181,7 @@ module Aws::S3
       data[:checksum_crc64nvme]
     end
 
-    # The Base64 encoded, 160-bit `SHA-1` digest of the object. This will
+    # The Base64 encoded, 160-bit `SHA1` digest of the object. This will
     # only be present if the object was uploaded with the object. When you
     # use the API operation on an object that was uploaded using multipart
     # uploads, this value may not be a direct checksum value of the full
@@ -197,7 +198,7 @@ module Aws::S3
       data[:checksum_sha1]
     end
 
-    # The Base64 encoded, 256-bit `SHA-256` digest of the object. This will
+    # The Base64 encoded, 256-bit `SHA256` digest of the object. This will
     # only be present if the object was uploaded with the object. When you
     # use an API operation on an object that was uploaded using multipart
     # uploads, this value may not be a direct checksum value of the full
@@ -292,6 +293,13 @@ module Aws::S3
       data[:content_type]
     end
 
+    # The portion of the object returned in the response for a `GET`
+    # request.
+    # @return [String]
+    def content_range
+      data[:content_range]
+    end
+
     # The date and time at which the object is no longer cacheable.
     # @return [Time]
     def expires
@@ -373,8 +381,10 @@ module Aws::S3
     #
     # For more information, see [Storage Classes][1].
     #
-    # <note markdown="1"> <b>Directory buckets </b> - Only the S3 Express One Zone storage class
-    # is supported by directory buckets to store objects.
+    # <note markdown="1"> <b>Directory buckets </b> - Directory buckets only support
+    # `EXPRESS_ONEZONE` (the S3 Express One Zone storage class) in
+    # Availability Zones and `ONEZONE_IA` (the S3 One Zone-Infrequent Access
+    # storage class) in Dedicated Local Zones.
     #
     #  </note>
     #
@@ -1128,10 +1138,12 @@ module Aws::S3
     #   availability. Depending on performance needs, you can specify a
     #   different Storage Class.
     #
-    #   <note markdown="1"> * <b>Directory buckets </b> - For directory buckets, only the S3
-    #     Express One Zone storage class is supported to store newly created
-    #     objects. Unsupported storage class values won't write a destination
-    #     object and will respond with the HTTP status code `400 Bad Request`.
+    #   <note markdown="1"> * <b>Directory buckets </b> - Directory buckets only support
+    #     `EXPRESS_ONEZONE` (the S3 Express One Zone storage class) in
+    #     Availability Zones and `ONEZONE_IA` (the S3 One Zone-Infrequent
+    #     Access storage class) in Dedicated Local Zones. Unsupported storage
+    #     class values won't write a destination object and will respond with
+    #     the HTTP status code `400 Bad Request`.
     #
     #   * <b>Amazon S3 on Outposts </b> - S3 on Outposts only uses the
     #     `OUTPOSTS` Storage Class.
@@ -1219,20 +1231,17 @@ module Aws::S3
     #   Signature Version in Request Authentication][1] in the *Amazon S3 User
     #   Guide*.
     #
-    #   **Directory buckets** - If you specify `x-amz-server-side-encryption`
-    #   with `aws:kms`, the ` x-amz-server-side-encryption-aws-kms-key-id`
-    #   header is implicitly assigned the ID of the KMS symmetric encryption
-    #   customer managed key that's configured for your directory bucket's
-    #   default encryption setting. If you want to specify the `
-    #   x-amz-server-side-encryption-aws-kms-key-id` header explicitly, you
-    #   can only specify it with the ID (Key ID or Key ARN) of the KMS
-    #   customer managed key that's configured for your directory bucket's
-    #   default encryption setting. Otherwise, you get an HTTP `400 Bad
-    #   Request` error. Only use the key ID or key ARN. The key alias format
-    #   of the KMS key isn't supported. Your SSE-KMS configuration can only
-    #   support 1 [customer managed key][2] per directory bucket for the
-    #   lifetime of the bucket. The [Amazon Web Services managed key][3]
-    #   (`aws/s3`) isn't supported.
+    #   **Directory buckets** - To encrypt data using SSE-KMS, it's
+    #   recommended to specify the `x-amz-server-side-encryption` header to
+    #   `aws:kms`. Then, the `x-amz-server-side-encryption-aws-kms-key-id`
+    #   header implicitly uses the bucket's default KMS customer managed key
+    #   ID. If you want to explicitly set the `
+    #   x-amz-server-side-encryption-aws-kms-key-id` header, it must match the
+    #   bucket's default customer managed key (using key ID or ARN, not
+    #   alias). Your SSE-KMS configuration can only support 1 [customer
+    #   managed key][2] per directory bucket's lifetime. The [Amazon Web
+    #   Services managed key][3] (`aws/s3`) isn't supported. Incorrect key
+    #   specification results in an HTTP `400 Bad Request` error.
     #
     #
     #
@@ -1503,7 +1512,7 @@ module Aws::S3
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/https:/tools.ietf.org/html/rfc7232
+    #   [1]: https://tools.ietf.org/html/rfc7232
     # @option options [Time,DateTime,Date,Integer,String] :if_match_last_modified_time
     #   If present, the object is deleted only if its modification times
     #   matches the provided `Timestamp`. If the `Timestamp` values do not
@@ -1784,15 +1793,6 @@ module Aws::S3
     #   fails with the HTTP status code `403 Forbidden` (access denied).
     # @option options [String] :checksum_mode
     #   To retrieve the checksum, this mode must be enabled.
-    #
-    #   **General purpose buckets** - In addition, if you enable checksum mode
-    #   and the object is uploaded with a [checksum][1] and encrypted with an
-    #   Key Management Service (KMS) key, you must have permission to use the
-    #   `kms:Decrypt` action to retrieve the checksum.
-    #
-    #
-    #
-    #   [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html
     # @return [Types::GetObjectOutput]
     def get(options = {}, &block)
       options = options.merge(
@@ -2195,8 +2195,9 @@ module Aws::S3
     #   a different Storage Class. For more information, see [Storage
     #   Classes][1] in the *Amazon S3 User Guide*.
     #
-    #   <note markdown="1"> * For directory buckets, only the S3 Express One Zone storage class is
-    #     supported to store newly created objects.
+    #   <note markdown="1"> * Directory buckets only support `EXPRESS_ONEZONE` (the S3 Express One
+    #     Zone storage class) in Availability Zones and `ONEZONE_IA` (the S3
+    #     One Zone-Infrequent Access storage class) in Dedicated Local Zones.
     #
     #   * Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.
     #
@@ -2253,20 +2254,17 @@ module Aws::S3
     #   `x-amz-server-side-encryption-aws-kms-key-id`, Amazon S3 uses the
     #   Amazon Web Services managed key (`aws/s3`) to protect the data.
     #
-    #   **Directory buckets** - If you specify `x-amz-server-side-encryption`
-    #   with `aws:kms`, the ` x-amz-server-side-encryption-aws-kms-key-id`
-    #   header is implicitly assigned the ID of the KMS symmetric encryption
-    #   customer managed key that's configured for your directory bucket's
-    #   default encryption setting. If you want to specify the `
-    #   x-amz-server-side-encryption-aws-kms-key-id` header explicitly, you
-    #   can only specify it with the ID (Key ID or Key ARN) of the KMS
-    #   customer managed key that's configured for your directory bucket's
-    #   default encryption setting. Otherwise, you get an HTTP `400 Bad
-    #   Request` error. Only use the key ID or key ARN. The key alias format
-    #   of the KMS key isn't supported. Your SSE-KMS configuration can only
-    #   support 1 [customer managed key][1] per directory bucket for the
-    #   lifetime of the bucket. The [Amazon Web Services managed key][2]
-    #   (`aws/s3`) isn't supported.
+    #   **Directory buckets** - To encrypt data using SSE-KMS, it's
+    #   recommended to specify the `x-amz-server-side-encryption` header to
+    #   `aws:kms`. Then, the `x-amz-server-side-encryption-aws-kms-key-id`
+    #   header implicitly uses the bucket's default KMS customer managed key
+    #   ID. If you want to explicitly set the `
+    #   x-amz-server-side-encryption-aws-kms-key-id` header, it must match the
+    #   bucket's default customer managed key (using key ID or ARN, not
+    #   alias). Your SSE-KMS configuration can only support 1 [customer
+    #   managed key][1] per directory bucket's lifetime. The [Amazon Web
+    #   Services managed key][2] (`aws/s3`) isn't supported. Incorrect key
+    #   specification results in an HTTP `400 Bad Request` error.
     #
     #
     #
@@ -2552,15 +2550,15 @@ module Aws::S3
     #   For the `x-amz-checksum-algorithm ` header, replace ` algorithm ` with
     #   the supported algorithm from the following list:
     #
-    #   * `CRC-32`
+    #   * `CRC32`
     #
-    #   * `CRC-32C`
+    #   * `CRC32C`
     #
-    #   * `CRC-64NVME`
+    #   * `CRC64NVME`
     #
-    #   * `SHA-1`
+    #   * `SHA1`
     #
-    #   * `SHA-256`
+    #   * `SHA256`
     #
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
@@ -2588,7 +2586,7 @@ module Aws::S3
     # @option options [String] :checksum_crc32
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 32-bit `CRC-32` checksum of the object.
+    #   specifies the Base64 encoded, 32-bit `CRC32` checksum of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #
@@ -2598,7 +2596,7 @@ module Aws::S3
     # @option options [String] :checksum_crc32c
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 32-bit `CRC-32C` checksum of the object.
+    #   specifies the Base64 encoded, 32-bit `CRC32C` checksum of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #
@@ -2608,10 +2606,10 @@ module Aws::S3
     # @option options [String] :checksum_crc64nvme
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 64-bit `CRC-64NVME` checksum of the
-    #   object. The `CRC-64NVME` checksum is always a full object checksum.
-    #   For more information, see [Checking object integrity in the Amazon S3
-    #   User Guide][1].
+    #   specifies the Base64 encoded, 64-bit `CRC64NVME` checksum of the
+    #   object. The `CRC64NVME` checksum is always a full object checksum. For
+    #   more information, see [Checking object integrity in the Amazon S3 User
+    #   Guide][1].
     #
     #
     #
@@ -2619,9 +2617,9 @@ module Aws::S3
     # @option options [String] :checksum_sha1
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 160-bit `SHA-1` digest of the object.
-    #   For more information, see [Checking object integrity][1] in the
-    #   *Amazon S3 User Guide*.
+    #   specifies the Base64 encoded, 160-bit `SHA1` digest of the object. For
+    #   more information, see [Checking object integrity][1] in the *Amazon S3
+    #   User Guide*.
     #
     #
     #
@@ -2629,7 +2627,7 @@ module Aws::S3
     # @option options [String] :checksum_sha256
     #   This header can be used as a data integrity check to verify that the
     #   data received is the same data that was originally sent. This header
-    #   specifies the Base64 encoded, 256-bit `SHA-256` digest of the object.
+    #   specifies the Base64 encoded, 256-bit `SHA256` digest of the object.
     #   For more information, see [Checking object integrity][1] in the
     #   *Amazon S3 User Guide*.
     #
@@ -2797,8 +2795,9 @@ module Aws::S3
     #   a different Storage Class. For more information, see [Storage
     #   Classes][1] in the *Amazon S3 User Guide*.
     #
-    #   <note markdown="1"> * For directory buckets, only the S3 Express One Zone storage class is
-    #     supported to store newly created objects.
+    #   <note markdown="1"> * Directory buckets only support `EXPRESS_ONEZONE` (the S3 Express One
+    #     Zone storage class) in Availability Zones and `ONEZONE_IA` (the S3
+    #     One Zone-Infrequent Access storage class) in Dedicated Local Zones.
     #
     #   * Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.
     #
@@ -2876,20 +2875,17 @@ module Aws::S3
     #   `x-amz-server-side-encryption-aws-kms-key-id`, Amazon S3 uses the
     #   Amazon Web Services managed key (`aws/s3`) to protect the data.
     #
-    #   **Directory buckets** - If you specify `x-amz-server-side-encryption`
-    #   with `aws:kms`, the ` x-amz-server-side-encryption-aws-kms-key-id`
-    #   header is implicitly assigned the ID of the KMS symmetric encryption
-    #   customer managed key that's configured for your directory bucket's
-    #   default encryption setting. If you want to specify the `
-    #   x-amz-server-side-encryption-aws-kms-key-id` header explicitly, you
-    #   can only specify it with the ID (Key ID or Key ARN) of the KMS
-    #   customer managed key that's configured for your directory bucket's
-    #   default encryption setting. Otherwise, you get an HTTP `400 Bad
-    #   Request` error. Only use the key ID or key ARN. The key alias format
-    #   of the KMS key isn't supported. Your SSE-KMS configuration can only
-    #   support 1 [customer managed key][1] per directory bucket for the
-    #   lifetime of the bucket. The [Amazon Web Services managed key][2]
-    #   (`aws/s3`) isn't supported.
+    #   **Directory buckets** - To encrypt data using SSE-KMS, it's
+    #   recommended to specify the `x-amz-server-side-encryption` header to
+    #   `aws:kms`. Then, the `x-amz-server-side-encryption-aws-kms-key-id`
+    #   header implicitly uses the bucket's default KMS customer managed key
+    #   ID. If you want to explicitly set the `
+    #   x-amz-server-side-encryption-aws-kms-key-id` header, it must match the
+    #   bucket's default customer managed key (using key ID or ARN, not
+    #   alias). Your SSE-KMS configuration can only support 1 [customer
+    #   managed key][1] per directory bucket's lifetime. The [Amazon Web
+    #   Services managed key][2] (`aws/s3`) isn't supported. Incorrect key
+    #   specification results in an HTTP `400 Bad Request` error.
     #
     #
     #
@@ -3524,15 +3520,15 @@ module Aws::S3
       #   For the `x-amz-checksum-algorithm ` header, replace ` algorithm ` with
       #   the supported algorithm from the following list:
       #
-      #   * `CRC-32`
+      #   * `CRC32`
       #
-      #   * `CRC-32C`
+      #   * `CRC32C`
       #
-      #   * `CRC-64NVME`
+      #   * `CRC64NVME`
       #
-      #   * `SHA-1`
+      #   * `SHA1`
       #
-      #   * `SHA-256`
+      #   * `SHA256`
       #
       #   For more information, see [Checking object integrity][1] in the
       #   *Amazon S3 User Guide*.