AWS IoT Greengrass Version 1 entered the extended life phase on June 30, 2023. For more information, see the AWS IoT Greengrass V1 maintenance policy. After this date, AWS IoT Greengrass V1 won't release updates that provide features, enhancements, bug fixes, or security patches. Devices that run on AWS IoT Greengrass V1 won't be disrupted and will continue to operate and to connect to the cloud. We strongly recommend that you migrate to AWS IoT Greengrass Version 2, which adds significant new features and support for additional platforms.
IoT SiteWise connector
The IoT SiteWise connector sends local device and equipment data to asset properties in AWS IoT SiteWise. You can use this connector to collect data from multiple OPC-UA servers and publish it to IoT SiteWise. The connector sends the data to asset properties in the current AWS account and Region.
Note
IoT SiteWise is a fully managed service that collects, processes, and visualizes data from industrial devices and equipment. You can configure asset properties that process raw data sent from this connector to your assets' measurement properties. For example, you can define a transform property that converts a device's Celsius temperature data points to Fahrenheit, or you can define a metric property that calculates the average hourly temperature. For more information, see What is AWS IoT SiteWise? in the AWS IoT SiteWise User Guide.
The connector sends data to IoT SiteWise with the OPC-UA data stream paths sent from the OPC-UA servers. For example, the data stream path /company/windfarm/3/turbine/7/temperature
might represent the
temperature sensor of turbine #7 at wind farm #3. If the AWS IoT Greengrass core loses connection to the internet, the connector caches data until it can successfully connect to the AWS Cloud. You can configure the maximum disk
buffer size used for caching data. If the cache size exceeds the maximum disk buffer size, the connector discards the oldest data from the queue.
After you configure and deploy the IoT SiteWise connector, you can add a gateway
and OPC-UA sources in the IoT SiteWise console
IoT SiteWise receives data only from data streams that you have mapped to the measurement properties of IoT SiteWise assets. To map data streams to asset properties, you can set a property's alias to be equivalent to an OPC-UA data stream path. To learn about defining asset models and creating assets, see Modeling industrial assets in the AWS IoT SiteWise User Guide.
Notes
You can use stream manager to upload data to IoT SiteWise from sources other than OPC-UA servers. Stream manager also provides customizable support for persistence and bandwidth management. For more information, see Manage data streams on the AWS IoT Greengrass core.
This connector runs in No container isolation mode, so you can deploy it to a Greengrass group running in a Docker container.
This connector has the following versions.
Version |
ARN |
---|---|
12 (recommended) |
|
11 |
|
10 |
|
9 |
|
8 |
|
7 |
|
6 |
|
5 |
|
4 |
|
3 |
|
2 |
|
1 |
|
For information about version changes, see the Changelog.
Requirements
This connector has the following requirements:
Parameters
Create Connector Example (AWS CLI)
The following AWS CLI command creates a ConnectorDefinition
with an initial version that contains the IoT SiteWise connector.
aws greengrass create-connector-definition --name MyGreengrassConnectors --initial-version '{ "Connectors": [ { "Id": "MyIoTSiteWiseConnector", "ConnectorArn": "
arn:aws:greengrass:
11" } ] }'region
::/connectors/IoTSiteWise/versions/
Note
The Lambda functions in this connector have a long-lived lifecycle.
In the AWS IoT Greengrass console, you can add a connector from the group's Connectors page. For more information, see Getting started with Greengrass connectors (console).
Input data
This connector doesn't accept MQTT messages as input data.
Output data
This connector doesn't publish MQTT messages as output data.
Limits
This connector is subject to the following all limits imposed by IoT SiteWise, including the following. For more informatison, see AWS IoT SiteWise endpoints and quotas in the AWS General Reference.
-
Maximum number of gateways per AWS account.
-
Maximum number of OPC-UA sources per gateway.
-
Maximum rate of timestamp-quality-value (TQV) data points stored per AWS account.
-
Maximum rate of TQV data points stored per asset property.
Licenses
Changelog
The following table describes the changes in each version of the connector.
Version |
Changes |
Date |
---|---|---|
12 |
|
December 22, 2021 |
11 |
|
March 24, 2021 |
10 |
Configured |
January 22, 2021 |
9 |
Support launched for custom Greengrass |
December 15, 2020 |
8 |
Improved stability when the connector experiences intermittent network connectivity. |
November 19, 2020 |
7 |
Fixed an issue with gateway metrics. |
August 14, 2020 |
6 |
Added support for CloudWatch metrics and automatic discovery of new OPC-UA tags. This version requires stream manager and AWS IoT Greengrass Core software v1.10.0 or higher. |
April 29, 2020 |
5 |
Fixed a compatibility issue with AWS IoT Greengrass Core software v1.9.4. |
February 12, 2020 |
4 |
Fixed an issue with OPC-UA server reconnection. |
February 7, 2020 |
3 |
Removed |
December 17, 2019 |
2 |
Added support for multiple OPC-UA secret resources. |
December 10, 2019 |
1 |
Initial release. |
December 2, 2019 |
A Greengrass group can contain only one version of the connector at a time. For information about upgrading a connector version, see Upgrading connector versions.
See also
-
Integrate with services and protocols using Greengrass connectors
-
See the following topics in the AWS IoT SiteWise User Guide: