Using the Send SQS Message action

Use the Send SQS Message action to relay Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions via the Amazon Simple Queue (SQS), a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications:

SQS offers two types of message queues. Standard queues offer maximum throughput, best-effort ordering, and at-least-once delivery. SQS FIFO queues are designed to guarantee that messages are processed exactly once, in the exact order that they are sent.

On this page:

1 Integrations
2 Requirements
3 Configuration
4 Entity Variables
5 Examples
6 How-to Articles
7 Frequently Asked Questions (FAQ)

Related pages:

Integrations

You can use the Send SQS Message action with the following integrations:

Requirements

The Send SQS Message action requires sufficient IAM permissions - an adequate IAM policy similar to the one provisioned by the Automation with AWS (Core) CloudFormation template might look as follows:

As usual, please consider to scope-down the Resource statement from a wildcard * to a more specific ARN that matches your use case, e.g. just targeting a single queue like arn:aws:sqs:eu-west-1:123456789012:examplequeue.

We recommend to consult with your resident AWS administrator, or refer to Techniques for writing least privilege IAM policies | Amazon Web Services for (very extensive) guidance on the subject.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "sqs:GetQueueAttributes",
                "sqs:ListQueues",
                "sqs:SendMessage"
            ],
            "Effect": "Allow",
            "Resource": "*",
            "Sid": "SQSSendMessageAndDiscoverQueues"
        }
    ]
}

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "sqs:SendMessage"
            ],
            "Effect": "Allow",
            "Resource": "*",
            "Sid": "SQSSendMessage"
        },
        {
           "Action": [
              "kms:Decrypt",
              "kms:GenerateDataKey"
           ],
           "Effect": "Allow",
           "Resource": "*",
           "Sid": "KMSDecrypt"
        }
    ]
}

Refer to Using Identity-Based (IAM) Policies for Amazon SQS for details on how to create more granular/secure policies, including a few Basic Amazon SQS Policy Examples.

Configuration

To configure a Send SQS Message action:

Complete the following settings:

Parameters

Specify the action parameters according to the following skeleton in JSON format – refer to sqs . send-message for details:

A message can include only XML, JSON, and unformatted text. The following Unicode characters are allowed:

#x9 | #xA | #xD | #x20 to #xD7FF | #xE000 to #xFFFD | #x10000 to #x10FFFF

Any characters not included in this list will be rejected. For more information, see the W3C specification for characters.

You can inject contextual variables into the remote action payload, refer to Entity Variables for details.

Send SQS Message skeleton

{
    "QueueUrl": "",
    "MessageBody": "",
    "DelaySeconds": 0,
    "MessageAttributes": {
        "KeyName": {
            "StringValue": "",
            "BinaryValue": null,
            "StringListValues": [
                ""
            ],
            "BinaryListValues": [
                null
            ],
            "DataType": ""
        }
    },
    "MessageDeduplicationId": "",
    "MessageGroupId": ""
}

Entity Variables

You can inject contextual variables with workflow entities into the remote action payload template – currently available entities are:

Using the Send SQS Message action

Integrations

Requirements

Configuration

Entity Variables

Examples

How-to Articles

Filter by label

Frequently Asked Questions (FAQ)