Encryption in transit - AWS IoT SiteWise

Encryption in transit

AWS IoT SiteWise has three modes of communication where data is in transit:

  • Over the internet – Communication between local devices (including gateways) and AWS IoT SiteWise is encrypted.

  • Over the local network – Communication between OpsHub for SiteWise application and gateways is always encrypted. Communication between the SiteWise monitor application running within your browser and gateways is always encrypted. Communication between gateways and OPC-UA sources can be encrypted.

  • Between components on gateways – Communication between AWS IoT Greengrass components on AWS IoT SiteWise gateways isn't encrypted.

Data in transit over the internet

AWS IoT SiteWise uses Transport Layer Security (TLS) to encrypt all communication over the internet. All data sent to the AWS Cloud is sent over a TLS connection using MQTT or HTTPS protocols, so it's secure by default. Gateways, which run on AWS IoT Greengrass, and property value notifications use the AWS IoT transport security model. For more information, see Transport security in the AWS IoT Developer Guide.

Data in transit over the local network

AWS IoT SiteWise gateways follow OPC-UA specifications for communication with local OPC-UA sources. It's your responsibility to configure your sources to use a message security mode that encrypts data in transit.

If you choose a sign message security mode, data in transit between gateways and sources is signed but not encrypted. If you choose a sign and encrypt message security mode, the data in transit between gateways and sources is signed and encrypted. For more information about configuring sources, see Configuring data sources.

The communication between the edge console application and gateways is always encrypted by TLS. The Sitewise Edge connector on the gateway generates and stores a self-signed certificate to be able to establish a TLS connection with the edge console for AWS IoT SiteWise application. You will need to copy this certificate from your gateway to the edge console for AWS IoT SiteWise application before you connect the application to the gateway. This ensures that the edge console for AWS IoT SiteWise application is able to verify that it has connected to your trusted gateway.

In addition to TLS for secrecy and server authenticity, Sitewise Edge uses the SigV4 protocol to establish the authenticity of the edge console application. The Sitewise Edge connector on the gateway accepts and stores a password to be able to verify incoming connections from the edge console application, SiteWise Monitor application running within browsers, and other clients based on the AWS IoT SiteWise SDK.

For more information about generating the password and server certificate, see Managing gateways.

Data in transit between local components on gateways

AWS IoT SiteWise gateways run on AWS IoT Greengrass, which doesn't encrypt data exchanged locally on the AWS IoT Greengrass core because the data doesn't leave the device. This includes communication between AWS IoT Greengrass components such as the AWS IoT SiteWise connector. For more information, see Data on the core device in the AWS IoT Greengrass Version 1 Developer Guide.