AWS SQS

Send device events to AWS SQS

Introduction

Amazon Simple Queue Service (Amazon SQS) offers a secure, durable, and available hosted queue that lets you integrate and decouple distributed software systems and components.

The Blecon AWS SQS integration sends device messages to a SQS queue, from where they can be consumed by various AWS services or your own code.

Preparing your AWS account

Log into or create an AWS account.

Note Region

Note the region in use, which is found in the top right of the AWS Console.

Create SQS queue

Open SQS in the AWS Console, and create a new queue. Take note of the queue name and queue URL.

Create IAM Policy

Open IAM in the AWS Console, and create a policy like the below.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowSendingMessagesToSQS",
            "Effect": "Allow",
            "Action": "sqs:SendMessage",
            "Resource": "arn:aws:sqs:REGION:ACCOUNT_ID:QUEUE_NAME"
        }
    ]
}

For ease of creating, select the JSON editor, paste the above, and insert your region, account ID, and queue name where indicated.

Create IAM Role

Now that we've created the policy, we can create a role, and attach the policy to it.

Navigate to the IAM service in the AWS Console and select Create Role. For Trusted Entity, choose AWS account and enter 329599652485.

Creating a role for Blecon

Click next, then find the policy you created in the previous step, and attach it to the role.

Click next and note the below on role naming, or the integration will not work.

Ensure the role has a name that begins with the text BleconIntegrationRole

Now that the role is created, we need to get the ARN of the role.

Find the role in the list of roles, open it, and copy the ARN.

Obtaining the ARN for your new role

Configuring the Integration

Now you should have everything you need to configure the Blecon integration:

• IAM Role ARN

• Region

• Queue URL (found on the SQS queue in the AWS console)

The namespace is your choice. Device messages must use this namespace to be routed to this integration.

Matching device events will now be stored in the SQS queue consumed or expired.

If you have questions, feel free to contact us!