sqs egress connector

SQS Egress Connector

Version: 17.07

Supported Since: 17.07

What is SQS Egress Connector?

SQS Egress Connector can be used to push messages to Amazon AWS SQS queues.

AWS SQS credentials associated with an account which has write permission to the target queue will be necessary when configuring this connector.
In order to use the SQS Egress Connector, you must first select the AWS Connector dependency from the connector list when you are creating an empty Ultra project. If you have already created a project, you can add the AWS Connector dependency via Component Registry. From Tools menu, select Ultra Studio → Component Registry and from the Connectors list, select the AWS Connector dependency.
sqs egress ports

Out Ports

On Exception

The message will be emitted from this out port if the processing element fails to push the message content to target SQS queue.

Response Processor

The message will be sent to this out port if the Complete Flow property is disabled and the message has been enqueued in the SQS queue successfully.

Side Ports

Connector Operation

This port is used to connect operational elements to the Egress Connector. By-default, user does not have to connect any operational element and the default connector operation will be used.


* marked fields are mandatory

SQS Region *


The region of the target SQS Queue

Destination bucket name *


Name of the AWS SQS queue, which is located in the configured AWS SQS region.

Use profile Credentials


If selected, profile credentials will be used, credentials will be picked from ~/.aws/credentials (Linux/Mac) or C:\Users\USER_NAME\.aws\credentials (Windows)

AWS Access Key Id


AWS Access Key Id is required only if profile credentials are not going to be used.

AWS Access Secret Key


AWS Access Secret Key is required only if profile credentials are not going to be used.

URL of the destination queue


The URL of the Amazon SQS queue to which a message is sent. Queue URLs are case-sensitive.

Message group id


This parameter applies only to FIFO (first-in-first-out) queues.The tag that specifies that a message belongs to a specific message group. Messages that belong to the same message group are processed in a FIFO manner (however, messages in different message groups might be processed out of order). To interleave multiple ordered streams within a single queue, use Message group id values (for example, session data for multiple users). In this scenario, multiple readers can process the queue, but the session data of each user is processed in a FIFO fashion.

Delay in seconds


The length of time, in seconds, for which to delay a specific message. Valid values: 0 to 900. Maximum: 15 minutes. Messages with a positive delay value become available for processing after the delay period is finished. If you don’t specify a value, the default value for the queue applies.When you set FifoQueue, you can’t set DelaySeconds per message. You can set this parameter only on a queue level.

Sample Use Case

This use case is a continuation of the use case in SQS Ingress connector

KarokeMagic allows users to upload their mp3 files over http to their primary server. Form the primary server, they upload MP3s to SQS, so processing nodes in the cluster can share the processing load of MP3s.

sqs egress flow
Figure 1. Integration flow to push files from uploaded location to SQS
sqs egress flow config
Figure 2. Configuration of SQS Egress connector

Product and company names and marks mentioned are the property of their respective owners and are mentioned for identification purposes only.

In this topic
In this topic
Contact Us