Amazon SQS – Fully managed message queues

Setup:

1. Sign-up for an AWS account and setup the SQS queue(s).

2. Sign-up for a PubNub account, if you don't have one already.

3. Import the Integration Block into your PubNub account. You can choose to add this to an existing application or create a new one.

4. Configure the Integration Block module code, connecting it to your AWS account:

   1. Create a Secret in PubNub Vault, named AWS_ACCESS_KEY_ID, with value equal to your AWS Access Key ID for this service.

   2. Create a Secret in PubNub Vault, named AWS_SECRET_KEY, with value equal to your AWS Secret Key for this service.

   3. Create a Secret in PubNub Vault, named AWS_REGION, with value equal to your AWS Region for the target queue .

   4. Create a Secret in PubNub Vault, named AWS_ACCOUNT_NUMBER, with value equal to your AWS Account ID for this service.

5. Start the Integration Block module.

6. Try a test message (you can click on Publish to do this).

Walkthrough:

This Integration Block is setup to listen to a specific PubNub channel (CHANNEL-to-send-to-SQS) but you can configure it to listen to all channels or a subset, using wildcards, e.g. chat.*. Thus, you can route message data sent through PubNub over to an Amazon SQS for fan-in use cases, for example. The target queue name can be set in the functions code or controlled through message metadata. In publish metadata, the customization properties are set as part of a JSON object specific for the function named aws-sqs-v1.

1. TARGET_QUEUE_NAME: name of the queue that the message should be sent to

Example publish metadata:

{"functions": {"aws-sqs-v1": {"input": {"TARGET_QUEUE_NAME": "pn_test_q"}}}}