Integrations
You can use the Send SQS Message action with the following integrations:
Filter by label (Content by label) | ||||||
---|---|---|---|---|---|---|
|
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:
Expand | ||||
---|---|---|---|---|
|
|
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:
Info |
---|
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 |
. |
Tip |
---|
You can inject contextual variables into the remote action payload, refer to Entity Variables for details. |
Send SQS Message skeleton
Code Block |
---|
{
|
"QueueUrl": "", |
"MessageBody": "", |
"DelaySeconds": 0, |
"MessageAttributes": { |
"KeyName": { |
"StringValue": "", |
"BinaryValue": null, |
"StringListValues": [ |
"" |
], |
"BinaryListValues": [ |
null ], "DataType": "" |
} |
}, |
"MessageDeduplicationId": "", |
entities into the remote action payload template – currently available entities are:
Page Properties Report | ||||||
---|---|---|---|---|---|---|
|
Examples
Filter by label (Content by label) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
How-to Articles
Filter by label (Content by label) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Frequently Asked Questions (FAQ)
Include Page | ||||
---|---|---|---|---|
|
Questionslist macro | ||||||
---|---|---|---|---|---|---|
|