AWS Security ChangesHomeSearch

AWS AWSSimpleQueueService documentation change

Service: AWSSimpleQueueService · 2025-07-18 · Documentation low

File: AWSSimpleQueueService/latest/SQSDeveloperGuide/using-messagegroupid-property.md

Summary

Expanded documentation about MessageGroupId usage in standard queues with fair queuing

Security assessment

Describes multi-tenant queue management features without security-specific context

Diff

diff --git a/AWSSimpleQueueService/latest/SQSDeveloperGuide/using-messagegroupid-property.md b/AWSSimpleQueueService/latest/SQSDeveloperGuide/using-messagegroupid-property.md
index 192b79df2..1b94fd81f 100644
--- a//AWSSimpleQueueService/latest/SQSDeveloperGuide/using-messagegroupid-property.md
+++ b//AWSSimpleQueueService/latest/SQSDeveloperGuide/using-messagegroupid-property.md
@@ -7 +7,14 @@
-[`MessageGroupId`](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SendMessage.html) is an attribute used only in Amazon SQS FIFO (First-In-First-Out) queues to organize 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. Standard queues do not use `MessageGroupId` and do not provide ordering guarantees. If strict ordering is required, use a FIFO queue instead.
+[`MessageGroupId`](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SendMessage.html) is an attribute used in SQS FIFO (First-In-First-Out) queues and in standard queues with fair queuing enabled. Its purpose and behavior differ between these queue types: 
+
+  * **For 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.
+
+  * **For standard queues with fair queuing enabled** – `MessageGroupId` serves as a required identifier for distinguishing tenants in multi-tenant queues. It helps balance message processing across consumers in high-concurrency scenarios and enables the detection of "noisy neighbors" (tenants creating message backlogs).
+
+  * **For standard queues without fair queuing enabled** – `MessageGroupId` is not used and no ordering guarantees are provided.
+
+
+
+
+###### Note
+
+Fair queues require significant concurrency to be effective and cannot be demonstrated through individual actions. When using `MessageGroupId` with fair queues in standard queues, additional changes apply for sending and receiving messages.