SQS Queue
Using Amazon SQS in DuploCloud
Last updated
Using Amazon SQS in DuploCloud
Last updated
© DuploCloud, Inc. All rights reserved. DuploCloud trademarks used herein are registered trademarks of DuploCloud and affiliates
Amazon Simple Queue Service (Amazon SQS) offers a secure, durable, and available hosted queue to integrate and decouple distributed software systems and components. It provides a generic web service API that you can access using any programming language that AWS SDK supports.
The following Amazon SQS Queue types are supported.
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.
FIFO Queues - FIFO queues have all the capabilities of a Standard queue, but are designed to enhance messaging between applications when the order of operations and events is critical, or where duplicates cannot be tolerated.
in the DuploCloud portal, navigate to Cloud Services -> App Integration.
Click the SQS tab.
Click Add. The Create an SQS Queue pane displays.
Enter an SQS Queue Name (my-std-queue in the example below).
Select Standard from the Queue Type list box.
Enter Message Retention Period (in Seconds). For example, 345600 seconds in the example below equates to four days.
Enter the Visibility Timeout in seconds. In the example below, we specify 30 seconds.
Click Create.
in the DuploCloud portal, navigate to Cloud Services -> App Integration.
Click the SQS tab.
Click Add. The Create an SQS Queue pane displays.
Enter an SQS Queue Name.
Select FIFO from the Queue Type list box.
Enter Message Retention Period (in Seconds). For example, 345600 seconds in the example below equates to four days.
Enter the Visibility Timeout in seconds. In the example below, we specify 30 seconds.
Optionally, select Content-based deduplication. Selecting this option indicates that message deduplication IDs are used to ensure duplicate messages are not sent. If a message deduplication ID is sent successfully, any messages sent with the same message ID aren't delivered within five minutes.
Select either Queue or Message group from the Deduplication scope list box, indicating that you want deduplication processing at either the Queue level or at the Message group level, using Message group IDs.
If you selected Queue in the previous step, the only available option in the FIFO throughput limit list box is Per queue. However, if you selected Message group in the previous step, you have the option of selecting Per queue or Per message group ID. This option specifies whether the FIFO Throughput Quota applies to the FIFO Queue or per Message Group.
Click Create.