Simple Queue Service (SQS)

Explaining the different SQS providers and how to configure the service.

AWS SQS is a fully managed distributed message queuing service. SQS is shipped with the LocalStack Community version and is extensively supported.


Trying to run the examples in the official AWS developer guide against LocalStack is a great place to start. Assuming you have awslocal installed you can also try the following commands:

$ awslocal sqs create-queue --queue-name sample-queue
    "QueueUrl": "http://localhost:4566/000000000000/sample-queue"
$ awslocal sqs list-queues
    "QueueUrls": [
$ awslocal sqs send-message --queue-url http://localhost:4566/00000000000/sample-queue --message-body test
    "MD5OfMessageBody": "098f6bcd4621d373cade4e832627b4f6",
    "MessageId": "74861aab-05f8-0a75-ae20-74d109b7a76e"


LocalStack supports two third-party providers for SQS - namely, moto and elasticmq. By default, moto is used. Your desired provider can be set with the environment variable SQS_PROVIDER.
For instance, if you wish to use elasticmq you’d pass the environment variable as SQS_PROVIDER=elasticmq.

ElasticMQ only supports a subset of the SQS query (only the REST query interface). However, it provides better scalability for local development and test servers that wish to create realistic scenarios in which lots of messages are sent with a high throughput. On the other hand, moto has near-complete support for SQS but has limited scalability.