You can use the Send SQS Message action with the following integrations:
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 We recommend to consult with your resident AWS administrator, or refer to https://aws.amazon.com/blogs/security/techniques-for-writing-least-privilege-iam-policies/ for (very extensive) guidance on the subject. |
|
|
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.
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": "" } |
You can inject contextual variables with workflow entities into the remote action payload template – currently available entities are: