Update generated code

manifest.json

@@ -1,6 +1,6 @@
 {
     "variables": {
-        "${LATEST}": "3.351.5"
+        "${LATEST}": "3.351.7"
     },
     "endpoints": "https://raw.githubusercontent.com/aws/aws-sdk-php/${LATEST}/src/data/endpoints.json",
     "services": {

src/Service/Kms/CHANGELOG.md

@@ -8,6 +8,10 @@
 - AWS api-change: Rework regions configuration
 - AWS api-change: AWS KMS announces the support of ML-DSA key pairs that creates post-quantum safe digital signatures.
 
+### Changed
+
+- AWS enhancement: Documentation updates.
+
 ## 1.9.0
 
 ### Added

src/Service/Kms/src/Input/CreateAliasRequest.php

@@ -19,7 +19,7 @@ final class CreateAliasRequest extends Input
      * slashes (/), underscores (_), and dashes (-). The alias name cannot begin with `alias/aws/`. The `alias/aws/` prefix
      * is reserved for Amazon Web Services managed keys [^1].
      *
-     * [^1]: https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk
+     * [^1]: https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-key
      *
      * @required
      *
@@ -45,7 +45,7 @@ final class CreateAliasRequest extends Input
      *
      * To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
      *
-     * [^1]: https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk
+     * [^1]: https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-mgn-key
      * [^2]: https://docs.aws.amazon.com/kms/latest/developerguide/find-cmk-id-arn.html
      *
      * @required

src/Service/Kms/src/KmsClient.php

@@ -158,8 +158,8 @@ public function createAlias($input): Result
      * Use the parameters of `CreateKey` to specify the type of KMS key, the source of its key material, its key policy,
      * description, tags, and other properties.
      *
-     * > KMS has replaced the term *customer master key (CMK)* with *KMS key* and *KMS key*. The concept has not changed. To
-     * > prevent breaking changes, KMS is keeping some variations of this term.
+     * > KMS has replaced the term *customer master key (CMK)* with *Key Management Service key* and *KMS key*. The concept
+     * > has not changed. To prevent breaking changes, KMS is keeping some variations of this term.
      *
      * To create different types of KMS keys, use the following guidance:
      *

src/Service/Sqs/CHANGELOG.md

@@ -6,6 +6,10 @@
 
 - AWS api-change: Rework regions configuration
 
+### Changed
+
+- AWS enhancement: Documentation updates.
+
 ## 2.6.0
 
 ### Added

src/Service/Sqs/src/Input/ReceiveMessageRequest.php

@@ -47,8 +47,7 @@ final class ReceiveMessageRequest extends Input
      * - `SqsManagedSseEnabled` – Enables server-side queue encryption using SQS owned encryption keys. Only one
      *   server-side encryption option is supported per queue (for example, SSE-KMS [^3] or SSE-SQS [^4]).
      * - `MessageDeduplicationId` – Returns the value provided by the producer that calls the `SendMessage` action.
-     * - `MessageGroupId` – Returns the value provided by the producer that calls the `SendMessage` action. Messages with
-     *   the same `MessageGroupId` are returned in sequence.
+     * - `MessageGroupId` – Returns the value provided by the producer that calls the `SendMessage` action.
      * - `SequenceNumber` – Returns the value provided by Amazon SQS.
      *
      * [^1]: http://en.wikipedia.org/wiki/Unix_time
@@ -157,7 +156,7 @@ final class ReceiveMessageRequest extends Input
      *
      * - While messages with a particular `MessageGroupId` are invisible, no more messages belonging to the same
      *   `MessageGroupId` are returned until the visibility timeout expires. You can still receive messages with another
-     *   `MessageGroupId` as long as it is also visible.
+     *   `MessageGroupId` from your FIFO queue as long as they are visible.
      * - If a caller of `ReceiveMessage` can't track the `ReceiveRequestAttemptId`, no retries work until the original
      *   visibility timeout expires. As a result, delays might occur but the messages in the queue remain in a strict order.
      *

src/Service/Sqs/src/Input/SendMessageRequest.php

@@ -32,7 +32,7 @@ final class SendMessageRequest extends Input
      * ! `#x9` | `#xA` | `#xD` | `#x20` to `#xD7FF` | `#xE000` to `#xFFFD` | `#x10000` to `#x10FFFF`
      * !
      * ! Amazon SQS does not throw an exception or completely reject the message if it contains invalid characters. Instead,
-     * ! it replaces those invalid characters with `U+FFFD` before storing the message in the queue, as long as the message
+     * ! it replaces those invalid characters with U+FFFD before storing the message in the queue, as long as the message
      * ! body contains at least one valid character.
      *
      * [^1]: http://www.w3.org/TR/REC-xml/#charsets
@@ -123,27 +123,37 @@ final class SendMessageRequest extends Input
     private $messageDeduplicationId;
 
     /**
-     * This parameter applies only to FIFO (first-in-first-out) queues.
+     * `MessageGroupId` is an attribute used in Amazon SQS FIFO (First-In-First-Out) and standard queues. In FIFO queues,
+     * `MessageGroupId` organizes messages into distinct groups. Messages within the same message group are always processed
+     * one at a time, in strict order, ensuring that no two messages from the same group are processed simultaneously. In
+     * standard queues, using `MessageGroupId` enables fair queues. It is used to identify the tenant a message belongs to,
+     * helping maintain consistent message dwell time across all tenants during noisy neighbor events. Unlike FIFO queues,
+     * messages with the same `MessageGroupId` can be processed in parallel, maintaining the high throughput of standard
+     * queues.
+     *
+     * - **FIFO queues:**`MessageGroupId` acts as the tag that specifies that a message belongs to a specific message group.
+     *   Messages that belong to the same message group are processed in a FIFO manner (however, messages in different
+     *   message groups might be processed out of order). To interleave multiple ordered streams within a single queue, use
+     *   `MessageGroupId` values (for example, session data for multiple users). In this scenario, multiple consumers can
+     *   process the queue, but the session data of each user is processed in a FIFO fashion.
      *
-     * The tag that specifies that a message belongs to a specific message group. Messages that belong to the same message
-     * group are processed in a FIFO manner (however, messages in different message groups might be processed out of order).
-     * To interleave multiple ordered streams within a single queue, use `MessageGroupId` values (for example, session data
-     * for multiple users). In this scenario, multiple consumers can process the queue, but the session data of each user is
-     * processed in a FIFO fashion.
+     *   If you do not provide a `MessageGroupId` when sending a message to a FIFO queue, the action fails.
      *
-     * - You must associate a non-empty `MessageGroupId` with a message. If you don't provide a `MessageGroupId`, the action
-     *   fails.
-     * - `ReceiveMessage` might return messages with multiple `MessageGroupId` values. For each `MessageGroupId`, the
-     *   messages are sorted by time sent. The caller can't specify a `MessageGroupId`.
+     *   `ReceiveMessage` might return messages with multiple `MessageGroupId` values. For each `MessageGroupId`, the
+     *   messages are sorted by time sent.
+     * - **Standard queues:**Use `MessageGroupId` in standard queues to enable fair queues. The `MessageGroupId` identifies
+     *   the tenant a message belongs to. A tenant can be any entity that shares a queue with others, such as your customer,
+     *   a client application, or a request type. When one tenant sends a disproportionately large volume of messages or has
+     *   messages that require longer processing time, fair queues ensure other tenants' messages maintain low dwell time.
+     *   This preserves quality of service for all tenants while maintaining the scalability and throughput of standard
+     *   queues. We recommend that you include a `MessageGroupId` in all messages when using fair queues.
      *
-     * The maximum length of `MessageGroupId` is 128 characters. Valid values: alphanumeric characters and punctuation
+     * The length of `MessageGroupId` is 128 characters. Valid values: alphanumeric characters and punctuation
      * `(!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~)`.
      *
      * For best practices of using `MessageGroupId`, see Using the MessageGroupId Property [^1] in the *Amazon SQS Developer
      * Guide*.
      *
-     * ! `MessageGroupId` is required for FIFO queues. You can't use it for Standard queues.
-     *
      * [^1]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/using-messagegroupid-property.html
      *
      * @var string|null

src/Service/Sqs/src/SqsClient.php

@@ -257,7 +257,7 @@ public function changeMessageVisibilityBatch($input): ChangeMessageVisibilityBat
      *
      *   > You can't change the queue type after you create it and you can't convert an existing standard queue into a FIFO
      *   > queue. You must either create a new FIFO queue for your application or delete your existing standard queue and
-     *   > recreate it as a FIFO queue. For more information, see Moving From a Standard Queue to a FIFO Queue [^1] in the
+     *   > recreate it as a FIFO queue. For more information, see Moving From a standard queue to a FIFO queue [^1] in the
      *   > *Amazon SQS Developer Guide*.
      *
      * - If you don't provide a value for an attribute, the queue is created with the default value for the attribute.
@@ -745,7 +745,7 @@ public function receiveMessage($input): ReceiveMessageResult
      * ! `#x9` | `#xA` | `#xD` | `#x20` to `#xD7FF` | `#xE000` to `#xFFFD` | `#x10000` to `#x10FFFF`
      * !
      * ! Amazon SQS does not throw an exception or completely reject the message if it contains invalid characters. Instead,
-     * ! it replaces those invalid characters with `U+FFFD` before storing the message in the queue, as long as the message
+     * ! it replaces those invalid characters with U+FFFD before storing the message in the queue, as long as the message
      * ! body contains at least one valid character.
      *
      * [^1]: http://www.w3.org/TR/REC-xml/#charsets
@@ -818,7 +818,7 @@ public function sendMessage($input): SendMessageResult
      * ! `#x9` | `#xA` | `#xD` | `#x20` to `#xD7FF` | `#xE000` to `#xFFFD` | `#x10000` to `#x10FFFF`
      * !
      * ! Amazon SQS does not throw an exception or completely reject the message if it contains invalid characters. Instead,
-     * ! it replaces those invalid characters with `U+FFFD` before storing the message in the queue, as long as the message
+     * ! it replaces those invalid characters with U+FFFD before storing the message in the queue, as long as the message
      * ! body contains at least one valid character.
      *
      * If you don't specify the `DelaySeconds` parameter for an entry, Amazon SQS uses the default value for the queue.

src/Service/Sqs/src/ValueObject/SendMessageBatchRequestEntry.php

@@ -109,27 +109,37 @@ final class SendMessageBatchRequestEntry
     private $messageDeduplicationId;
 
     /**
-     * This parameter applies only to FIFO (first-in-first-out) queues.
+     * `MessageGroupId` is an attribute used in Amazon SQS FIFO (First-In-First-Out) and standard queues. In FIFO queues,
+     * `MessageGroupId` organizes messages into distinct groups. Messages within the same message group are always processed
+     * one at a time, in strict order, ensuring that no two messages from the same group are processed simultaneously. In
+     * standard queues, using `MessageGroupId` enables fair queues. It is used to identify the tenant a message belongs to,
+     * helping maintain consistent message dwell time across all tenants during noisy neighbor events. Unlike FIFO queues,
+     * messages with the same `MessageGroupId` can be processed in parallel, maintaining the high throughput of standard
+     * queues.
+     *
+     * - **FIFO queues:**`MessageGroupId` acts as the tag that specifies that a message belongs to a specific message group.
+     *   Messages that belong to the same message group are processed in a FIFO manner (however, messages in different
+     *   message groups might be processed out of order). To interleave multiple ordered streams within a single queue, use
+     *   `MessageGroupId` values (for example, session data for multiple users). In this scenario, multiple consumers can
+     *   process the queue, but the session data of each user is processed in a FIFO fashion.
      *
-     * The tag that specifies that a message belongs to a specific message group. Messages that belong to the same message
-     * group are processed in a FIFO manner (however, messages in different message groups might be processed out of order).
-     * To interleave multiple ordered streams within a single queue, use `MessageGroupId` values (for example, session data
-     * for multiple users). In this scenario, multiple consumers can process the queue, but the session data of each user is
-     * processed in a FIFO fashion.
+     *   If you do not provide a `MessageGroupId` when sending a message to a FIFO queue, the action fails.
      *
-     * - You must associate a non-empty `MessageGroupId` with a message. If you don't provide a `MessageGroupId`, the action
-     *   fails.
-     * - `ReceiveMessage` might return messages with multiple `MessageGroupId` values. For each `MessageGroupId`, the
-     *   messages are sorted by time sent. The caller can't specify a `MessageGroupId`.
+     *   `ReceiveMessage` might return messages with multiple `MessageGroupId` values. For each `MessageGroupId`, the
+     *   messages are sorted by time sent.
+     * - **Standard queues:**Use `MessageGroupId` in standard queues to enable fair queues. The `MessageGroupId` identifies
+     *   the tenant a message belongs to. A tenant can be any entity that shares a queue with others, such as your customer,
+     *   a client application, or a request type. When one tenant sends a disproportionately large volume of messages or has
+     *   messages that require longer processing time, fair queues ensure other tenants' messages maintain low dwell time.
+     *   This preserves quality of service for all tenants while maintaining the scalability and throughput of standard
+     *   queues. We recommend that you include a `MessageGroupId` in all messages when using fair queues.
      *
      * The length of `MessageGroupId` is 128 characters. Valid values: alphanumeric characters and punctuation
      * `(!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~)`.
      *
      * For best practices of using `MessageGroupId`, see Using the MessageGroupId Property [^1] in the *Amazon SQS Developer
      * Guide*.
      *
-     * ! `MessageGroupId` is required for FIFO queues. You can't use it for Standard queues.
-     *
      * [^1]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/using-messagegroupid-property.html
      *
      * @var string|null