Enable logging

Logs are always an important source of information especially to find the cause of errors or the comprehend what’s going on in a service. To permit the IoT service to write to Amazon CloudWatch in your account a service role is needed. This role has been already created through CloudFormation.

You can find the role name in the AWS CloudFormation console in the outputs section as IoTServiceRoleName. The role name will look similar to SiteWiseWorkshop-IoTWSIoTServiceRole-UNIQUE_STRING.

Go to the AWS IoT Core console

  1. Get started (only if no resources are provisioned)
  2. Settings
  3. Logs (only if Level of verbosity is not set to Info) -> Edit
  4. Level of verbosity: Info
  5. Set role -> Select SiteWiseWorkshop-IoTWSIoTServiceRole-UNIQUE_STRING
  6. Update

The log files from AWS IoT are send to Amazon CloudWatch. The AWS console can be used to look at these logs.

The following exercise is optional and not required to work with AWS IoT SiteWise. We recommend to conduct this section if you don’t have any experience with connecting a device to AWS IoT Core.

In the following optional exercise you will provision a virtual device (thing) in the AWS IoT Core and send some messages through the MQTT protocol. The aim is to get an understanding how the connection between a device and the AWS IoT core works. This is important because AWS IoT Greengrass will also connect as a device to the AWS IoT Core.

If you know AWS IoT already or if this exercise is not important for you skip to AWS IoT Greengrass Setup.