This page contains detailed information about the AWS SQS service in the Tartabit IoT Bridge. This service lets you integrate LPWAN devices as devices in AWS SQS.
The AWS SQS service contains the information required to establish a service connection to AWS.
- Must have an SQS queue defined.
- Must have an IAM user with access to send and receive from the queue. For example, the AmazonSQSFullAccess IAM role will work.
- Access Key ID: The AWS Access Key ID (starts with AKI).
- Secret Key: The secret key associated with the credentials.
- Region: The AWS region where the SQS queue is located.
- Queue URL: The URL for the SQS queue.
- Operations: Configure the service connector to support send only, or send and receive of messages.
This event fires when a message is received from an event hub.
{
"id":"<messageid>",
"body":"<SQS payload>",
"attributes": {
"prop_a":"abc",
"prop_b":123,
}
}
- id: The ID associated with the SQS message.
- body: The body of the message. Can be a string, binary, or object.
- properties: Any properties that were sent along with the message.
Send messages to an SQS queue.
// Send message to the queue referenced in 'myservice'.
aws_sqs.send('myservice', {"field1": "abc", "field2": 456})
// Send message to the queue with properties.
eventhub.send('myservice', {"field1": "abc", "field2": 456},{attributes:{'prop1':'abc'}})
- serviceKey: The service key that you defined that references the Azure Event Hub.
- body: Body can be text or JSON data that is to be sent to the event hub.
- options: Optional object that contains key/value pairs to configure the message.
- attributes: An object with key/value pairs can be set to send attributes along with the sqs message.
- groupId: Set the group ID in the SQS message.
The following events are considered billable:
- Send message to an SQS queue
- Receive message from an SQS queue