Amazon SQS

AWS queue priced per request, with standard and first-in-first-out types. In our guide to message queue software it is ranked #12 of 13.

Paid placement exists here and is disclosed. Whatever the arrangement, the Amazon SQS link carries the same marker as all others (details).

Visit Amazon SQS See it in the message queue software ranking

01

At a glance

HeadquartersUnited States
APIAmazon SQS mentions an API in the material we reviewed
Best forTeams already on AWS wanting a queue with nothing to operate
DeploymentNot stated in the material we reviewed
Pricing modelPer request with a free tier of one million monthly requests; no minimum fee
Free planYes
02

What is Amazon SQS?

Amazon Simple Queue Service, listed here as Amazon SQS, is the queue service inside Amazon Web Services. Billing is per request, and every SQS action counts as one request, with FIFO queue requests and fair queue requests billed at their own rates. The free tier covers 1 million requests a month and the pricing page states there is no minimum fee.

Standard queues offer near-unlimited transactions per second per API action with at-least-once delivery and best-effort ordering, while FIFO queues give exactly-once processing and first-in, first-out ordering. Messages can be retained for up to 14 days, and payloads reach 256 KB of text in any format. It is delivered as an AWS API with no software to install. Amazon Web Services, Inc. is located in the United States, with a mailing address in Seattle, Washington.

03

Amazon SQS key features

  • Standard queues. Near-unlimited transactions per second per API action, with at-least-once delivery and best-effort ordering. Messages may arrive more than once or out of order, so consumers should be written to tolerate both.
  • FIFO queues. Exactly-once processing and first-in, first-out ordering. Default throughput is up to 3,000 messages per second with batching or 300 without, and high throughput mode reaches up to 70,000 messages per second without batching.
  • Payloads and retention. A message holds up to 256 KB of text in any format and is retained for up to 14 days. Larger payloads can go to Amazon S3 through the SQS Extended Client Library for Java.
  • Long polling. Long polling waits up to 20 seconds for a message when the queue is empty. That reduces the number of empty requests, which matters because billing is counted per request.
  • Dead-letter queues. Messages move to a dead-letter queue after exceeding the maximum receive count. The dead-letter queue must match the type of its source queue, and messages can be moved back to the source later.
  • KMS encryption and sharing controls. Messages are encrypted with AWS KMS keys, stored encrypted and decrypted only for authorised consumers. Queues can be shared anonymously or with specific AWS accounts, restricted by IP address and time of day.
  • Fanout with SNS and AWS services. Amazon SNS can send copies of one message to several queues in parallel. The features page names Lambda, S3, DynamoDB, RDS, EC2, ECS and Redshift among the services that work with SQS.
04

Who Amazon SQS suits

  • An AWS-based team decoupling microservices. One service writes work to a queue and another processes it later. With Lambda and ECS named on the features page, a team already in AWS can connect them without running a broker.
  • A small product with spiky, low traffic. The 1 million monthly free requests and the absence of a minimum fee mean a modest application can run queues at little or no cost. Unused free usage does not roll over.
  • A team ordering financial or inventory events. FIFO queues provide first-in, first-out ordering and exactly-once processing, with 300 messages per second without batching by default. Higher volumes need batching or high throughput mode.
05

Getting started with Amazon SQS

The pages we read describe features and pricing rather than a setup procedure. SQS is part of AWS, so an AWS account is the starting point, and queues are used through AWS API actions. The first design choice is between a standard queue and a FIFO queue, as ordering, duplicates and throughput differ.

A dead-letter queue must match the type of its source queue, so choose it alongside the main queue. Long polling for up to 20 seconds is available to cut empty requests. For payloads above 256 KB, the features page points to the SQS Extended Client Library for Java with Amazon S3. Consult AWS documentation for console and SDK instructions.

06

Strengths and limits of Amazon SQS

What Amazon SQS does well
  • Amazon SQS bills per request, and each 64 KB of payload counts as one, so a 1 MiB message costs 16.
  • Marked in our records as AWS-managed.
  • Best for: Teams already on AWS wanting a queue with nothing to operate.
  • FIFO queues, one of the three traits the catalogue lists for Amazon SQS.
  • Per request is among the traits we single out for it.
Amazon SQS: limits
  • Messages are retained for at most 14 days, and standard queues give only best-effort ordering.
  • Less suited to: Organisations that need the broker to run outside one cloud.
  • Payloads above 256 KB need a separate S3 store reached through a Java client library.
07

Our verdict on Amazon SQS

Amazon SQS bills per request, and each 64 KB of payload counts as one, so a 1 MiB message costs 16. The free tier gives 1 million requests a month, with no minimum fee.

Standard queues deliver at least once with best-effort ordering; FIFO queues give exactly-once processing. Payloads stop at 256 KB unless S3 is added through a Java library. It is an AWS API, so portability is limited.

In our message queue software ranking Amazon SQS stands at #12 of 13: Apache ActiveMQ sits directly above it and IBM MQ directly below. After the challenger places, Amazon SQS is one of the established names, ranked in order and without a score.

Home market: the United States, one of 5 North America bases among the 13 products here.

08

Amazon SQS pros and cons in practice

Works well
  • The free tier of 1 million requests a month suits small workloads.
  • No minimum fee and no servers to run.
  • Standard and FIFO types cover both throughput and ordering needs.
  • KMS encryption and account-level sharing controls are part of the service.
Gets in the way
  • Payloads above 256 KB need S3 and a Java library.
  • Each 64 KB chunk bills as a request, so large messages cost more.
  • It is an AWS API, so moving to another provider means changing code.
  • The per-request rates were not visible on the pricing page content we read.
09

Amazon SQS pricing

In the catalogue: Per request with a free tier of one million monthly requests; no minimum fee.

Pricing is billed per request, with each SQS action counting as one request; FIFO queue requests and fair queue requests are billed at their own rates. The pricing page content we read did not show the per-request rate figures, so we state no amounts. The free tier covers 1 million requests a month for all customers in every region except GovCloud, and unused free usage does not roll over to the next month. The pricing page states there is no minimum fee. Each 64 KB chunk of a payload bills as one request, so a 1 MiB payload bills as 16 requests, and one request can carry 1 to 10 messages up to 1 MiB in total. Transfer between SQS and services in the same region is not charged; cross-region and internet transfer use standard AWS Data Transfer charges.

Basis: aws.amazon.com, read for the Best Message Queue Software in 2026 guide (reviewed 15 November 2026).

10

Amazon SQS in practice

FIFO throughput defaults to 3,000 messages a second with batching, or 300 without, rising to 70,000 in high throughput mode.

Long polling waits up to 20 seconds, and dead-letter queues must match the type of their source queue.

KMS encryption is stated, and SNS fanout copies a message to several queues.

The features page lists no compliance certifications, and the privacy page names a separate controller for the European Economic Area.

11

Amazon SQS: data and security

Messages are encrypted with AWS KMS keys, stored encrypted and decrypted only for authorised consumers. Queues can be shared anonymously or with specific AWS accounts, optionally restricted by IP address and time of day. The features page lists no compliance certifications, and use is governed by the AWS Customer Agreement. Amazon Web Services, Inc.

is located in the United States, with a mailing address in Seattle, Washington, and the privacy page names a different controller for the European Economic Area. Cross-region transfer is charged as AWS Data Transfer, which reflects that data can move between regions when a team designs it that way. Region and residency choices are not described on the pages we read.

12

Amazon SQS fact sheet

ProductAmazon SQS
Vendor websiteaws.amazon.com
HeadquartersUnited States (North America)
Rank there#12 of 13
Alternatives pageNot written yet
Gaps in our recordsuptime history and customer numbers
Primary guideBest Message Queue Software in 2026
Head-to-head pagesNot paired so far
Catalogue tagsAWS-managed, Per request, FIFO queues
Price visibilityPublic on the vendor site
13

Integrations and ecosystem

Integrations the vendor names (10):

  • Amazon SNS
  • AWS Lambda
  • Amazon S3
  • Amazon DynamoDB
  • Amazon RDS
  • Amazon EC2
  • Amazon ECS
  • Amazon Redshift
  • SQS Extended Client Library for Java
  • AWS KMS
14

Every guide that lists Amazon SQS

15

Alternatives to Amazon SQS

The choice below rests on shared catalogue tags, price model, free plan and region, with rank distance as the tie-break.

  • CloudAMQP (#1 of 13): Not for: buyers who need a broker other than RabbitMQ or LavinMQ. Hosted RabbitMQ and LavinMQ clusters on the cloud provider you pick.
  • Upstash QStash (#2 of 13): Serverless messaging and scheduling delivered to your HTTP endpoints. Watch out: its table lists $420 per month for Fixed 10M while the plan card shows $180 for the range, and a footnote only flags the gap.
  • EMQX (#6 of 13): MQTT platform with serverless, dedicated and self-run editions. Suits: IoT and connected-vehicle teams wanting a hosted MQTT broker to start small.
  • Apache ActiveMQ (#11 of 13): Not for: teams wanting a managed broker without running Java services. Java broker that speaks AMQP, MQTT, STOMP and JMS.
16

Amazon SQS FAQ

9 answers
Is Amazon SQS one of the top message queue software?

The message queue software ranking has Amazon SQS at position 12 out of 13.

Is Amazon SQS a European company?

The united states is the home country of Amazon SQS, in the North America group. Country here means the contracting company, which can differ from where servers run.

Who should choose Amazon SQS?

Teams already on AWS wanting a queue with nothing to operate. Less suited to: organisations that need the broker to run outside one cloud.

What does Amazon SQS cost?

Our catalogue records Amazon SQS’s pricing as: Per request with a free tier of one million monthly requests; no minimum fee. On free access, it has a free tier or free plan.

What else should I look at besides Amazon SQS?

Start with CloudAMQP, Upstash QStash, EMQX and Apache ActiveMQ. All of them are reviewed in the same ranking.

How is SQS billed?

Per request. Each action counts as one request, each 64 KB chunk of a payload counts as one, and one request can carry 1 to 10 messages up to 1 MiB in total.

Is there a free tier?

Yes, 1 million requests a month for all customers in every region except GovCloud. Unused free usage does not roll over.

What is the difference between standard and FIFO?

Standard queues give at-least-once delivery and best-effort ordering. FIFO queues give exactly-once processing and first-in, first-out ordering.

How long are messages kept?

Up to 14 days, according to the features page.

17

Amazon SQS: sources

Read from the vendor’s own pages on 14 November 2026.

18

How we rank

We rank on what separates products after the demo: time to useful, the real price, the exit and who the product is for. The result for Amazon SQS: #12, out of 13 ranked. Method and commercial relationships are in our editorial process.