Limits¶
What it cannot do¶
| Limit | Detail |
|---|---|
| no patterns | A subscription is one queue on one exact subject. * and > are refused |
| no replay | A queue has no position. StartAt: AllAvailable is refused |
| no request and reply | Capabilities.RequestReply is false |
no at-most-once on Standard |
A standard queue may deliver a message after it has been deleted |
no ordering on Standard |
Best effort only. FIFO orders per subject, never across subjects |
FIFO: one message in flight per subject per queue |
The cost of strict ordering. A wedged consumer holds its subject |
no deduplication on Standard |
A retried publish is stored twice |
| nothing is created | Except an at-most-once fan-out queue. Why |
| a delay or lease beyond twelve hours is cut | Unless FIFO with MaxHeadroom. Counted in DelayShortened and LeaseExpired |
MaxProcessingTime over twelve hours is refused |
Unless FIFO with MaxHeadroom. Always on Standard |
| 10 message attributes | Binary mode only; structured carries more |
| 256 KiB per message | Attributes included. Refused at Publish |
| a payload that is not UTF-8 | Binary mode refuses it; structured carries it |
| no empty message | Refused at Publish |
| queue names up to 80 characters | Suffix included |
What it does not check¶
- That the queue is subscribed to the topic.
- That the subscription uses raw message delivery. A wrapped message is unreadable.
- That the redrive policy's dead-letter queue exists.
- That a topic name derived from a subject is a legal SNS name. The adapter does not translate any character but the dot.
- Two subjects that differ only in dots and underscores share a topic.
Ephemeral queues are not swept¶
An AtMostOnce fan-out queue is deleted at Retire. The adapter has no other path that deletes one, so
a process that dies before retiring leaves its queue and its SNS subscription behind, and the
subscription counts against the topic's cap below.
Binary attributes read as empty¶
The adapter reads each message attribute's String value. An attribute of the Binary
data type has no String value and arrives as an empty string. The adapter writes only String
attributes.
AWS quotas that bound it¶
| Quota | Value | Where it bites |
|---|---|---|
| subscriptions per FIFO topic | 100 | About a hundred consumers per subject at once. Every durable queue consuming a subject holds one, and so does every live at-most-once fan-out subscriber. A fleet that scales those with its instance count reaches the ceiling at roughly a hundred instances per subject. It arrives at Subscribe as SubscriptionLimitExceeded |
| FIFO topics per account | 1,000 | One topic per subject makes this the ceiling on subjects |
| publish throughput, account-wide | 3,000 messages a second for FIFO in most regions, 30,000 in us-east-1 |
Counts Publish and PublishBatch across every topic of both varieties. Many quiet subjects share one budget, so throttling on publish is a likelier first symptom than any topic-count error |
All three are soft; an increase is a support request. They were read on 2026-09-07 from AWS's SNS endpoints and quotas, which is not date-stamped and varies by region. Check it rather than trusting these numbers for capacity planning. The adapter's README gives no figure for subscriptions per standard topic.
Emulator behaviour¶
On LocalStack, the queue policy and SNS's UTF-8 rule are not enforced, FIFO delivery from a topic lags far behind publishing (measured: a publish after a burst of three thousand arrived twelve seconds later), and the sweep of expired visibility runs about a second late. See Tested versions.