Interacting with other AWS services
AWS IoT SiteWise can publish asset data to the AWS IoT MQTT publish-subscribe message broker, so that you can interact with your asset data from other AWS services. AWS IoT SiteWise assigns each asset property a unique MQTT topic that you can use to route your asset data to other AWS services using AWS IoT Core rules. For example, you can configure AWS IoT Core rules to do the following tasks:
-
Identify equipment failure and notify appropriate personnel by sending data to AWS IoT Events.
-
Historize select asset data for use in external software solutions by sending data to Amazon DynamoDB.
-
Generate weekly reports by triggering an AWS Lambda function.
You can follow a tutorial that walks through the steps required to set up a rule that stores property values in DynamoDB. For more information, see Publishing property value updates to Amazon DynamoDB.
For more information about how to configure a rule, see Rules in the AWS IoT Developer Guide.
You can also consume data from other AWS services back into AWS IoT SiteWise. To ingest data through the AWS IoT SiteWise rule action, see Ingesting data using AWS IoT Core rules.
Understanding asset properties' MQTT topics
Every asset property has a unique MQTT topic path in the following format.
$aws/sitewise/asset-models/assetModelId/assets/assetId/properties/propertyId
AWS IoT SiteWise doesn't support the # (multi-level) topic filter wildcard in the
AWS IoT Core rules engine. You can use the + (single-level) wildcard. For
example, you can use the following topic filter to match all updates for a particular asset
model.
$aws/sitewise/asset-models/assetModelId/assets/+/properties/+
To learn more about topic filter wildcards, see Topics in the AWS IoT Core Developer Guide.
