Queues are message queues that work like Amazon SQS: one part of an application sends work to a queue and returns, another receives it when it has time. Standard queues deliver at least once in best-effort order; FIFO queues deliver each message group in order and drop repeated sends. Dead-letter queues catch messages that keep failing, and an SQS endpoint lets the AWS SDKs and the AWS CLI use them unchanged.
Queues holds messages between the part of an application that produces work and the part that does it, with the names and behaviour of Amazon SQS.
Create a queue with a dead-letter queue, send a message, receive and delete it, and delete both queues again, in about ten minutes.
How a message travels through a queue, from send to delete, and what the visibility timeout, receipt handles, long polling, delays and retention do to it.
Create a standard or FIFO queue, with or without a dead-letter queue, and choose its delivery settings.
Put a message on a queue, or up to ten in one request, with attributes, a delay, or a FIFO message group.
Take up to ten messages off a queue, long-polling for them, and delete each one with its receipt handle once it is processed.
Point the AWS SDKs, boto3 or the AWS CLI at the SQS endpoint and use your queues with code written for Amazon SQS.
Who may do what with a queue (IAM), which calls are audited, and how API and SQS clients authenticate.
See how many messages a queue holds now and over time, in the console, through the API and from an SQS client.
How many queues and messages you can have, how fast you can call the service, and how to raise the queues quota.
User Guide
22 pages: concepts, tasks, security, quotas, troubleshooting.
API Reference
15 operations, with their parameters and IAM actions.
CLI Command Reference
15 commands, one per API operation, with their arguments and flags.
Terraform resources
1 resources and data sources of the provider.
Document history
What changed in these docs.