AWS iot-sitewise documentation change
Summary
Added documentation about destinations for Siemens devices and data handling methods
Security assessment
The changes document secure data handling practices (buffered vs real-time) and path filter configurations, which are security-adjacent features but do not address specific vulnerabilities.
Diff
diff --git a/iot-sitewise/latest/userguide/sitewise-edge-on-siemens.md b/iot-sitewise/latest/userguide/sitewise-edge-on-siemens.md index 9c450ebbb..5a32267d8 100644 --- a//iot-sitewise/latest/userguide/sitewise-edge-on-siemens.md +++ b//iot-sitewise/latest/userguide/sitewise-edge-on-siemens.md @@ -5 +5 @@ -SecuritySiemens Secure Storage and the AWS IoT SiteWise Edge applicationMigrate from the preview applicationTroubleshootingAWS IoT SiteWise Edge application changelog +SecuritySiemens Secure Storage and the AWS IoT SiteWise Edge applicationDestinations for Siemens Industrial Edge devicesMigrate from the preview applicationTroubleshootingAWS IoT SiteWise Edge application changelog @@ -22,0 +23,2 @@ Siemens is not a vendor or supplier for SiteWise Edge. The Siemens Industrial Ed + * Destinations for Siemens Industrial Edge devices + @@ -96,0 +99,60 @@ The AWS IoT SiteWise Edge application on Siemens Industrial Edge will not run un +## Destinations for Siemens Industrial Edge devices + +When using the AWS IoT SiteWise Edge application on Siemens Industrial Edge, destinations help prepare data before sending it to AWS IoT SiteWise for further analysis and distribution. You can configure data destination settings for buffered data ingestion using Amazon S3 or use real-time data ingestion. Both allow you to subscribe to MQTT topics using path filters on the Siemens Industrial Edge device deployment target. + +The Siemens Industrial Edge deployment target on your gateway supports two primary data handling methods: + + * **AWS IoT SiteWise real-time settings** \- Data is sent directly to AWS IoT SiteWise as it's collected + + * **AWS IoT SiteWise buffered using Amazon S3 settings** \- Data is collected and stored temporarily in batches before being sent to Amazon S3 + + + + +For more information about configuring these options, see [Add an AWS IoT SiteWise buffered destination using Amazon S3](./destinations-buffered.html) and [Add an AWS IoT SiteWise Edge real-time destination](./destinations-real-time.html). + +### Prefixes for path filters + +Path filters for gateways using Siemens Industrial Edge deployment targets combine both the topic and data stream name to create a unique identifier for your data. The combined topic with data stream name is called a **prefix** in Siemens Industrial Edge gateways. This differs from self-hosted gateways where path filters are based solely on MQTT topics. + +###### Example Path filter structure for Siemens data streams + +A typical path filter for a Siemens data stream includes both the topic path and the data stream name: + + + ie/d/device1/application1/datastream1 + +Where: + + * `ie/d/` is the required prefix for Siemens data streams + + * `device1/application1` represents the hierarchical path + + * `datastream1` is the specific data stream name + + + + +###### Note + +When working with Siemens Industrial Edge data streams, ensure that you include both the metadata (`ie/m/`) and data (`ie/d/`) topics in your path filters to receive complete information about your data streams. + +#### Destinations and path filters + +View the following topics to learn more about destinations and path filters in MQTT-enabled gateways: + + * [Understand AWS IoT SiteWise Edge destinations](./gw-destinations.html#source-destination) + + * [Add an AWS IoT SiteWise Edge real-time destination](./destinations-real-time.html) + + * [Add an AWS IoT SiteWise buffered destination using Amazon S3](./destinations-buffered.html) + + * [Understand path filters for AWS IoT SiteWise Edge destinations](./gw-destinations.html#destinations-path-filters) + + * [Add path filters to AWS IoT SiteWise Edge destinations](./destinations-add-path-filters.html) + + * [Manage AWS IoT SiteWise Edge destinations](./destinations-manage.html) + + + + @@ -124 +186 @@ After configuring the new gateway and Siemens Databus user, your data flows to y -You can also upgrade your SiteWise Edge application from version 1.0.1 to 2.0.0 directly. However, a new gateway configuration is still necessary. +You can also upgrade your SiteWise Edge application from version directly. However, a new gateway configuration is still necessary. @@ -137,0 +200 @@ The following table describes the changes in each version of the AWS IoT SiteWis +2.0.1 | Adds support for destinations and path filters to the gateway.