Choosing a destination for your source server data - Amazon IoT SiteWise
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Choosing a destination for your source server data

You can use destinations to control where to send your source's incoming data. You can either send your data to Amazon IoT SiteWise, or you can use a Amazon IoT Greengrass stream to send your data to a different location. You configure a different source destination for each source server in your gateway.

  • Amazon IoT SiteWise – Send your source data to Amazon IoT SiteWise for storage and processing. This is the default option.

  • Amazon IoT Greengrass stream – You choose a custom Amazon IoT Greengrass stream to receive your source data. You can use the Amazon IoT Greengrass stream to forward received data to an on-premises application, or to another Amazon IoT service in the Amazon Cloud.

    You can choose an existing Amazon IoT Greengrass stream for your source destination, or you can create a new one. For more information about how to choose a custom Amazon IoT Greengrass stream as your destination, see Configuring data sources.

The following example shows the required data stream message structure. All fields are required.

{ "alias" : "string", "messages" : [ { "name": "string", "value": boolean|double|integer|string, "timestamp": number, "quality": "string" } ] }
alias

The alias of the data stream. See the following example.

/company/windfarm/3/turbine/7/temperature
messages

The list of tuples in this batch. Each tuple contains a timestamp, value, and quality.

name

The alias of the data stream. This must match the alias.

value

The type of value contained in this message. Valid values are boolean, double, integer, or string.

timestamp

The timestamp of the tag data. This is formatted as the number of milliseconds since the Unix epoch.

quality

The quality of the tag data. Valid values are GOOD, BAD, or UNCERTAIN.