Use AWS IoT SiteWise Edge destinations to determine where to send your source data. You can choose your data destination based on specific the characteristics you need, like cost-effectiveness, low latency, or storage requirements. Integrate device data captured by AWS IoT SiteWise, our partners, or custom applications to publish and subscribe to path filters (topics) at the edge. You can then model, transfer, and store your device data in the cloud.
Note
For full use of all destination features, upgrade to the latest versions of the IoT SiteWise publisher and IoT SiteWise OPC UA collector.
Note
Stream support is continued on Classic streams, V2 gateways to maintain compatibility with existing setups. For more information, see Classic streams, V2 gateways for AWS IoT SiteWise Edge.
Topics
How SiteWise Edge destinations enhance data management
Export data from the edge to AWS IoT SiteWise in real time, or in batches using Amazon S3.
Destinations enhance flexibility and scalability in your AWS IoT SiteWise environment. Destinations implement a centralized data management model, where sources publish data to a central system. Destinations determine where your data is sent using path filters. Destinations can subscribe to multiple path filters.
MQTT-enabled, V3 gateways use MQTT for local communication and come with a
default real-time destination which has filters set to #. This
means that, by default, all messages on all topics are published to the AWS IoT SiteWise
real-time destination. For more information, see Understand path filters for AWS IoT SiteWise Edge
destinations. You can add one real-time
destination in each gateway.
Destination types
When configuring a destination for your gateway, you have two main options: real-time configuration using AWS IoT SiteWise, and a buffered configuration using Amazon S3. Each destination type has its own set of settings and considerations.
- AWS IoT SiteWise real-time settings
-
Choose this to send data directly to AWS IoT SiteWise hot-tier storage to facilitate ingesting and monitoring data in real-time. The real-time settings manage data flow, particularly when a gateway experiences connectivity issues with the cloud. During connection loss, data is temporarily stored locally on the gateway. Once the connection is re-established, the stored data is automatically sent to the cloud.
You can adjust various aspects of the data publishing process, such as the maximum amount of data to be stored locally, the rate at which data is sent to the cloud upon reconnection, and when to delete data after the storage reaches its capacity.
For more information on AWS IoT SiteWise storage tiers, see, Manage data storage in AWS IoT SiteWise.
- AWS IoT SiteWise buffered using Amazon S3 settings
-
This destination type allows you to buffer data locally on the gateway and periodically send it to an Amazon S3 bucket in batches. The data is stored in the efficient Parquet format, which is optimized for analytical workloads. Once the data is in Amazon S3, you can import it into AWS IoT SiteWise for storage, processing, and analysis.
Choose this option to ingest data in batches, and store historical data in a cost-effective way. You can configure your preferred Amazon S3 bucket location, and the frequency at which you want data to be uploaded to Amazon S3. You can also choose what to do with the data after ingestion into AWS IoT SiteWise. You can choose to have the data available in both SiteWise and Amazon S3 or you can choose to delete it automatically from Amazon S3.
Compare destination functionality between gateway versions
The destinations feature in MQTT-enabled, V3 gateways streamlines data flow management. Destinations simplify data management through centralized configuration of data routing to various endpoints. This approach eliminates the need for complex individual stream setups, making the overall system more flexible and easier to manage.
By comparison, the Classic streams, V2 gateway, SiteWise Edge transmits data from data sources to publishers via AWS IoT Greengrass streams, configuring data destinations individually for each data source.
With the AWS IoT SiteWise destination feature, the publisher routing configuration is consolidated. Destination configuration allows you to manage destinations and path filters in a centralized manner. You can easily add a destination, manage path filters, delete unnecessary filters or destinations, depending on your needs.
Additionally, the destinations feature utilizes MQTT (Message Queuing Telemetry Transport), an industry-standard protocol widely used in industrial IoT applications. This adoption of MQTT helps AWS IoT SiteWise to facilitate easier integration with various devices and systems.
Destination limitations
Current limitations for destinations on SiteWise Edge gateways include:
-
The data processing pack isn't supported in MQTT-enabled, V3 gateways.
-
Data type support is limited to AWS IoT SiteWise data types. For information on enabling data type conversion, see Converting unsupported data types.
Use cases for SiteWise Edge
destinations
SiteWise Edge destinations are utilized in diverse applications. Here are some key examples:
- Industrial automation
- Real-time monitoring and predictive maintenance
-
In industrial settings, sensors and devices on the factory floor can publish data to SiteWise Edge. Destinations can be configured to filter and route relevant data, enabling real-time monitoring and analysis of machine performance. You can subscribe to relevant MQTT topics using path filters, process the data, and then publish the processed data. In this way, you can selectively route processed data to AWS cloud analytic services or on-premises systems. Manufacturers can then implement predictive maintenance strategies, optimize production processes, and reduce downtime.
- Smart buildings
- Energy efficiency and occupancy optimization
-
Building automation systems generate data streams to monitor and control various aspects of a building, such as HVAC systems, lighting, and access control. With SiteWise Edge, these data streams can be ingested, processed, and routed to different destinations. Facility managers can configure destinations to filter and forward relevant data, enabling advanced capabilities like energy efficiency measures and occupancy optimization while ensuring data privacy and compliance.
These use cases demonstrate how the Destinations feature in SiteWise Edge can be leveraged across various industries to ingest, process, and route data efficiently. This enables advanced capabilities such as real-time monitoring, predictive maintenance, energy efficiency, and remote diagnostics while ensuring data privacy and compliance.
