starter.wiki

Managed message queue

Amazon SQS

An AWS-managed pull queue with Standard and FIFO routes, visibility timeouts, retention, and redrive controls.

Visit official site

Editorial verdict

Choose SQS when AWS-native durable message transport is more valuable than HTTP push, Workers-native operation, or richer enterprise broker semantics.124710

Best for

  • AWS-native producer and consumer graphs
  • Managed Standard or FIFO queues
  • Teams owning idempotent consumers, redrive, and DLQs
124710

Not ideal for

  • HTTP push delivery
  • Replayable event streams
  • Applications requiring rich broker topics and sessions
124710
Main trade-off

Durable AWS-native transport trades against explicit delivery semantics, consumer ownership, and multi-service operations and cost.124710

Product boundary

Whether an AWS-managed pull queue fits the workload's delivery, ordering, retention, and consumer model.

SQS retains and delivers messages. It does not execute Background Jobs, retain workflow state, or replace consumer compute.1

For: AWS teams able to operate polling consumers and design for Standard or FIFO delivery semantics

  • The consumer must receive HTTP push rather than poll.
  • Duplicate delivery cannot be handled idempotently.
  • Topics, sessions, replay, or workflow state are actual requirements.

Why teams consider Amazon SQS

  • Managed transportAWS operates queue availability, retention, and delivery infrastructure.1
  • Standard and FIFOSeparate queue types address different ordering and throughput needs.1
  • Failure controlsVisibility, delay, retention, redrive, and DLQ settings shape failure handling.1

Pricing

API actions are billed in 64 KB request chunks, with queue type, transfer, KMS, observability, and consumer services accounted separately.3

Queue usage

Pay per request after monthly allowance

Verified 2026-07-25: the first 1 million SQS requests each month are free; requests are counted in 64 KB chunks and region/type rates apply.3

Primary meter
API actions and 64 KB payload chunks3
Separate costs
Transfer, KMS, consumer compute, CloudWatch, and support3
Pricing checked View official pricing

Amazon SQS vs alternatives

Cloudflare Queues

Choose when
Choose it for Workers-native producers and consumers.
Compared with Amazon SQS
Tighter runtime integration with Cloudflare coupling.46

Upstash QStash

Choose when
Choose it for managed HTTP push delivery.
Compared with Amazon SQS
Less consumer infrastructure with per-delivery and retry economics.79

Azure Service Bus

Choose when
Choose it for Azure enterprise topics, subscriptions, and sessions.
Compared with Amazon SQS
Richer broker semantics with more tier and capacity complexity.1012

Resources and sources

Official product, policy, and pricing

  • Amazon SQS developer guide
    Open
  • Amazon SQS at-least-once delivery
    Open
  • Amazon SQS pricing
    Open
  1. 1
    Amazon SQS developer guide

    Amazon Web Services · Accessed Official

  2. 2
    Amazon SQS at-least-once delivery

    Amazon Web Services · Accessed Official

  3. 3
    Amazon SQS pricing

    Amazon Web Services · Accessed Official

  4. 4
    Cloudflare Queues documentation

    Cloudflare · Accessed Official

  5. 5
    Cloudflare Queues delivery guarantees

    Cloudflare · Accessed Official

  6. 6
    Cloudflare Queues pricing

    Cloudflare · Accessed Official

  7. 7
    Upstash QStash queues

    Upstash · Accessed Official

  8. 8
    Upstash QStash retries

    Upstash · Accessed Official

  9. 9
    Upstash QStash pricing

    Upstash · Accessed Official

  10. 10
    Azure Service Bus overview

    Microsoft · Accessed Official

  11. 11
    Azure Service Bus sessions

    Microsoft · Accessed Official

  12. 12
    Azure Service Bus pricing

    Microsoft · Accessed Official