- Go to the Queue Service menu and click Create queue.
- Name it (A-Z, a-z, 0-9, _ and -, up to 80 characters, unique in the Project), pick a Region, adjust the settings for the job and create it.
- To keep failed messages for inspection, first create another queue as the dead-letter queue (e.g.
orders-dlq), then choose it under Dead-letter queue on the main queue. - Click Create access key and choose permissions per queue: Send, Receive & delete and Purge. Tick Manage queues to let the key create or change queues over the API.
- Copy the Access key ID and Secret; the secret is shown only once. The dialog shows example code with your key filled in.
Give your site a key that can only send, and your workers one that can receive & delete. If one key leaks, you revoke only that one.
Try it without code: click a queue name, then use Send message and Show waiting messages (a look that does not receive them).
Creating a queue needs money in the Project wallet. While a Project is suspended for unpaid usage, messages cannot be sent or received, but you can still delete messages and queues.
If something goes wrong
I lost the secret
It cannot be shown again. Create a new key, switch your systems to it, then delete the old one.
Messages stay “in progress” for long
A worker received them but has not deleted them. Make sure workers call delete when done; the messages come back when the visibility timeout ends.
The same message is processed several times
The visibility timeout is shorter than the job takes. Raise it, or have the worker call visibility for more time while it works.