Appian -> AWS SNS -> AWS SQS

Hi, 

Since Appian doesn't natively integrate with SQS, using SNS as an intermediary with filter-based forwarding is a clever workaround.

Understanding Message Attributes

• Message Attributes add metadata to SNS messages.
• They are key-value pairs (string name, string value).
• Some attributes have special meaning for filtering                

Postman Setup

1. Endpoint: Find your SNS Topic ARN (looks like arn:aws:sns:region:account-id:topic-name)
2. Method: POST
3. Authorization: Use AWS Signature Version 4 (Postman can help generate this based on your credentials)
4. Headers:
   • Content-Type: application/x-www-form-urlencoded
5. Body: (form-urlencoded)
   • Action: "Publish"
   • Version: "2010-03-31"
   • Message: Your JSON payload string
   • MessageAttributes.entry.1.Name: (attribute name, e.g., "eventType")
   • MessageAttributes.entry.1.Value.StringValue: (attribute value)
   • MessageAttributes.entry.1.Value.DataType: "String"
   • ... (add more attributes as needed)

Appian Integration (HTTP Connected System)

1. Create Connected System:
   • Type: HTTP
   • Authentication: AWS Signature Version 4
2. Create Integration:
   • Method: POST
   • Endpoint URL: Substitute your SNS Topic ARN
   • Headers:
     • Content-Type: application/x-www-form-urlencoded
   • Parameters
     • Use Appian expressions to dynamically construct parameters listed in the Postman body section

Note:

• SQS Subscription: Ensure your SQS queue is subscribed to the SNS topic with an appropriate filter policy based on your Message Attributes.
• Error Handling: Implement robust error handling on the Appian side.

Hi, 

Since Appian doesn't natively integrate with SQS, using SNS as an intermediary with filter-based forwarding is a clever workaround.

Understanding Message Attributes

• Message Attributes add metadata to SNS messages.
• They are key-value pairs (string name, string value).
• Some attributes have special meaning for filtering                

Postman Setup

1. Endpoint: Find your SNS Topic ARN (looks like arn:aws:sns:region:account-id:topic-name)
2. Method: POST
3. Authorization: Use AWS Signature Version 4 (Postman can help generate this based on your credentials)
4. Headers:
   • Content-Type: application/x-www-form-urlencoded
5. Body: (form-urlencoded)
   • Action: "Publish"
   • Version: "2010-03-31"
   • Message: Your JSON payload string
   • MessageAttributes.entry.1.Name: (attribute name, e.g., "eventType")
   • MessageAttributes.entry.1.Value.StringValue: (attribute value)
   • MessageAttributes.entry.1.Value.DataType: "String"
   • ... (add more attributes as needed)

Appian Integration (HTTP Connected System)

1. Create Connected System:
   • Type: HTTP
   • Authentication: AWS Signature Version 4
2. Create Integration:
   • Method: POST
   • Endpoint URL: Substitute your SNS Topic ARN
   • Headers:
     • Content-Type: application/x-www-form-urlencoded
   • Parameters
     • Use Appian expressions to dynamically construct parameters listed in the Postman body section

Note:

• SQS Subscription: Ensure your SQS queue is subscribed to the SNS topic with an appropriate filter policy based on your Message Attributes.
• Error Handling: Implement robust error handling on the Appian side.

Thank you for taking the time to respond with such a detailed answer!  The development team who are implementing this have reported success based upon your advice with respect to the header for "Content-Type": "application/x-www-form-urlencoded".  
Very much appreciated!

Thank you

Richard Nolan  were you able to implement this? If so, do you have x-ray enabled in your SNS topic? We are trying to integrate our SNS with x-ray where the event starts from Appian.

erickp0002 I wasn't the developer involved, but researching for another.  I've asked him and he indicates that there wasn't an X-Ray configuration at play.