Use an AWS Standard Queue for a B2B SaaS worker pool draining independent failed jobs, provided the consumer is idempotent. Choose FIFO only when the order of state changes is part of correctness. The important boundary is not the queue label; it is the point where delivery ends and an auditable side effect begins.
The bill is mainly repeated worker work and downstream calls, not the queue name. A retry can consume compute, wait behind an ordered group, and still need a durable record after acknowledgement removes the message. For a rate-limited pool, Standard gives the least restrictive path to a high-throughput drain. FIFO prevents ordering mistakes, but its higher latency, throughput limits, and additional charges are a real trade-off.
This is a reliability decision before it is a vendor decision. The worker must make a remote write idempotent, record the result outside the queue, and distinguish a lost response from a failed operation.…