...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Warning |
|---|
You have tried to access an archived page. Please go to the new https://root360.atlassian.net/wiki/spaces/KB to find more documents. |
| Excerpt | ||
|---|---|---|
| ||
This guide explains what SQS is and what you need to do in order to request SQS from Root360. |
...
| Table of Contents |
|---|
Standard queues
Standard queues support a nearly unlimited number of API calls per second, per API action (SendMessage, ReceiveMessage, or DeleteMessage). Standard queues support at-least-once message delivery. However, occasionally (because of the highly distributed architecture that allows nearly unlimited throughput), more than one copy of a message might be delivered out of order. Standard queues provide best-effort ordering which ensures that messages are generally delivered in the same order as they're sent.
Message ordering
A standard queue makes a best effort to preserve the order of messages, but more than one copy of a message might be delivered out of order.
At-least-once delivery
Amazon SQS stores copies of your messages on multiple servers for redundancy and high availability. On rare occasions, one of the servers that stores a copy of a message might be unavailable when you receive or delete a message.
...
The order in which messages are sent and received is strictly preserved and a message is delivered once and remains available until a consumer processes and deletes it. Duplicates aren't introduced into the queue.
Exactly-once processing
FIFO queues don't introduce duplicate messages. If you retry the SendMessage action within the 5-minute deduplication interval, Amazon SQS doesn't introduce any duplicates into the queue.
...
Both types of queues are provided with authentication. A distinction is made between two types:
Username / Password
Instance Profile
Only AWS CLI / AWS SDK commands are allowed for using a queue
Requesting SQS
If you want to request SQS, you can do so by sending an E-Mail to to service@root360.de or creating a ticket in the the ticket system.
Required information
Required Information | Explanation | Options |
|---|---|---|
Name of Queue | Queues have to follow our naming pattern "<company>-<project>-<env>-<suffix>" with a maximum length of 80 characters (alphanumeric characters, hyphens, or underscores) | Select a name matching our naming pattern (for fifo queue add ".fifo") |
Fifo queue or standard queue | We can setup standard and fifo queues. | Standard queue, Fifo queue (default: Standard queue) |
Maximum message size | Maximal size of a single message. | min 1 Byte, max 262 144 Bytes (default: 262 144 Bytes) |
Message retention period | Amount of time that a message is stored in SQS. Older messages are deleted automatically. | min 1 day, max 4 days (default: 1 day) |
Receive message wait time | The receive message wait time is the maximum amount of time that polling will wait for messages to become available to receive | min 0 seconds, max 20 seconds (default: 0 seconds) |
Visibility timeout | Visibility timeout sets the length of time that a message received from a queue (by one consumer) will not be visible to the other message consumers | min 0 seconds, max 12 hours (default: 30 seconds) |
Delivery delay | The delivery delay is the amount of time to delay the first delivery of each message added to the queue. Any messages that you send to the queue remain invisible to consumers for the duration of the delay period. | min 0 seconds, max 15 minutes (default: 0 seconds) |
User access | In case you have/request multiple queues, we can either create one dedicated user per queue or grant access to multiple (please provide names of all queues/users) queues to one user. | Dedicated user per queue, master user for multiple queues |
Pricing
For detailed AWS pricing see https://aws.amazon.com/sqs/pricing/?nc1=h_ls
...