In this article:
To receive messages sent from your Myriota-enabled device, you need to assign at least one Destination.
Destinations represent the programmatic message end points for devices on the Myriota Network. You will be requested to assign a Destination whenever you register a new device.
Destinations can be added or removed using Device Manager, or programmatically using the Destination Management API.
Message Delivery
Once message data is received by the ground station network, it is forwarded to the Myriota Cloud for processing. The Myriota Cloud decodes individual messages and pushes them to the configured Destinations for the source device.
To get up and running quickly, you can use the Myriota Message Store as the Destination for your test and POC devices. Alternatively you can configure custom AWS and HTTP Destinations.
The Message Store is a repository, hosted by Myriota and made available to all Customers for use during testing. As this is a public resource, it should be used with discretion and not for production data.
Messages older than four weeks may be removed from the Message Store without notice for storage optimization.
In Production, Customers should have their own Destinations configured.
Destination Types
The following Destination types are currently supported:
- AWS Lambda (Not sure what this is? Read more at AWS)
- HTTP
Destination Management via Device Manager
To create a new Destination via the Device Manager, do the following:
- Log into Device Manager
- Select Destinations in the left bar, then click the Create button
- Select your preferred type from the drop down, and populate the URL
- Lambda - enter the ARN for the Lambda Function and Role into the respective fields
- HTTP - enter your URL
- Click Create to complete the creation process
Assign your new Destination to one of your devices to begin receiving message data.
Destination Management via Cloud API
Destinations can also be configured and using the Myriota Cloud API.
For details view the Cloud API Overview and Destination Management code examples for AWS Lambda and HTTP.