AWS AWSSimpleQueueService documentation change
Summary
Restructured documentation for fair queues, adding sections on 'How to use fair queues' and 'When to use fair queues', with clarifications about MessageGroupId behavior differences between standard and FIFO queues
Security assessment
The changes are documentation improvements and clarifications about fair queue functionality, including when to use them and how MessageGroupId works differently in standard vs FIFO queues. There's no mention of security vulnerabilities, incidents, or security features. The changes focus on functionality, performance, and multi-tenant queue management without security implications.
Diff
diff --git a/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-fair-queues.md b/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-fair-queues.md index 71884589b..378c5256d 100644 --- a//AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-fair-queues.md +++ b//AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-fair-queues.md @@ -7 +7 @@ -Difference with FIFO queuesUsing fair queuesFair queues CloudWatch metrics +How to use fair queuesWhen to use fair queuesFair queues CloudWatch metrics @@ -39 +39 @@ Amazon SQS does not limit the consumption rate per tenant. It allows consumers t -## Difference with FIFO queues +For details on how Amazon SQS detects noisy neighbors and manages message delivery order, see [How Amazon SQS fair queues work](./sqs-fair-queues-detailed.html). @@ -41 +41 @@ Amazon SQS does not limit the consumption rate per tenant. It allows consumers t -FIFO queues maintain strict ordering by limiting the number of in-flight messages from each tenant. While this prevents noisy neighbors, it limits throughput for each tenant. Fair queues are designed for multi-tenant scenarios where high throughput, low dwell time, and fair resource allocation are priorities. Fair queues allow multiple consumers to process messages from the same tenant concurrently while helping all tenants maintain consistent dwell times. +## How to use fair queues @@ -43,3 +43 @@ FIFO queues maintain strict ordering by limiting the number of in-flight message -## Using fair queues - -Your message producers can add a tenant identifier by setting a `MessageGroupId` on an outgoing message: +To enable fair queues, message producers should add a tenant identifier by setting a `MessageGroupId` on outgoing messages: @@ -57,0 +56,17 @@ The fairness capability will be applied automatically in all Amazon SQS standard +###### Note + +`MessageGroupId` on standard queues with fair queues does not have the same behavior as `MessageGroupId` on FIFO queues. On standard queues, `MessageGroupId` is used only as a tenant identifier for fair queues and does not enforce message ordering. For details on `MessageGroupId` on FIFO queues, see [Using the message group ID with Amazon SQS FIFO Queues](./using-messagegroupid-property.html). + +## When to use fair queues + +Consider using fair queues when all of the following apply to your queue: + + * **The queue is multi-tenant.** The queue carries messages that belong to multiple logical entities, such as customers, client applications, or request types, and you can identify each entity with a `MessageGroupId`. + + * **The queue is high-throughput.** At low throughput, one tenant's burst rarely creates a backlog that affects other tenants. At high throughput, over-scaling the consumer fleet to absorb every burst is impractical, and even with auto-scaling, the delay before new consumers come online can let backlogs form. + + * **Dwell time is part of your application's quality of service.** Fair queues protect quiet tenants from elevated dwell time caused by a noisy neighbor. If your application is not sensitive to dwell time, the noisy-neighbor protection fair queues provide may not be needed. + + + + @@ -76 +91 @@ Visibility timeout -Delay queues +How fair queues work