The AWS IoT sample demonstrates how an nRF9160-based device communicates with the AWS IoT message broker over MQTT. This sample showcases the use of the lib_aws_iot library. The sample implements lib_aws_fota through lib_aws_iot.

The sample supports the following development kits:

The sample publishes two different types of messages in JSON object string format to the AWS IoT message broker. These messages are sent to the AWS IoT shadow topic $aws/things/<thingname>/shadow/update.

Below are the two types of messages that are published:

• Type 1: The message comprises of a battery voltage value sampled from the nRF9160 SiP and a corresponding timestamp in milliseconds (UNIX time), that is retrieved from the lib_date_time library.
• Type 2: The message adds a configurable firmware version number to type 1 messages. This firmware version number is used in correlation with FOTA DFU, which is supported by the sample and the lib_aws_iot library. See the lib_aws_fota library for information on how to create FOTA jobs.

A type 2 message is only published upon an initial connection to the sample, while a type 1 message is published sequentially with a configurable time in between each publishing of the data. In addition to publishing data, the sample also subscribes to the AWS IoT shadow delta topic, and two customizable application-specific topics. The customizable topics are not part of the AWS IoT shadow service and must therefore be passed to the lib_aws_iot library using the :caws_iot_subscription_topics_add function.

To run this sample and connect to AWS IoT, complete the steps described in the lib_aws_iot documentation. This documentation retrieves the AWS IoT broker hostname, security tag, and client ID. The corresponding options that must be set for each of the aforementioned values are:

• :kconfigCONFIG_AWS_IOT_BROKER_HOST_NAME
• :kconfigCONFIG_AWS_IOT_SEC_TAG
• :kconfigCONFIG_AWS_IOT_CLIENT_ID_STATIC

Set these options in the project configuration file located at samples/nrf9160/aws_iot/prj.conf. For documentation related to FOTA DFU, see lib_aws_fota.

The application-specific configurations used in the sample are listed below. They are located in samples/nrf9160/aws_iot/Kconfig.

After building the sample, program it to your development kit.

3. Power on or reset the kit.
4. Observe the output in the terminal over UART.

When the sample runs, the device boots, and the sample displays the following output in the terminal over UART:

*** Booting Zephyr OS build v2.3.0-rc1-ncs1-snapshot1-6-gad0444b058ef  ***
<inf> aws_iot_sample: AWS IoT sample started, version: v1.0.0
<inf> aws_iot_sample: LTE cell changed: Cell ID: 33703711, Tracking area: 2305
<inf> aws_iot_sample: PSM parameter update: TAU: -1, Active time: -1
<inf> aws_iot_sample: RRC mode: Connected
<inf> aws_iot_sample: Network registration status: Connected - roaming
<inf> aws_iot_sample: PSM parameter update: TAU: 3600, Active time: 60
<inf> aws_iot_sample: RRC mode: Idle
<inf> aws_iot_sample: AWS_IOT_EVT_CONNECTING
<inf> aws_iot_sample: RRC mode: Connected
<inf> aws_iot_sample: RRC mode: Idle
<inf> aws_iot_sample: RRC mode: Connected
<inf> aws_iot_sample: AWS_IOT_EVT_CONNECTED
<inf> aws_iot_sample: Publishing: {
"state":    {
        "reported":    {
        "app_version":    "v1.0.0",
        "batv":    4304,
        "ts":    1592305354579
        }
}
} to AWS IoT broker
<inf> aws_iot_sample: AWS_IOT_EVT_READY
<inf> aws_iot_sample: RRC mode: Idle
<inf> aws_iot_sample: LTE cell changed: Cell ID: 34237195, Tracking area: 2305
<inf> aws_iot_sample: Publishing: {
"state":    {
        "reported":    {
        "batv":    4308,
        "ts":    1592305414579
        }
}
} to AWS IoT broker
<inf> aws_iot_sample: Next data publication in 60 seconds
<inf> aws_iot_sample: RRC mode: Connected
<inf> aws_iot_sample: RRC mode: Idle
<inf> aws_iot_sample: LTE cell changed: Cell ID: 33703711, Tracking area: 2305
<inf> aws_iot_sample: RRC mode: Connected
<inf> aws_iot_sample: Publishing: {
"state":    {
        "reported":    {
        "batv":    4308,
        "ts":    1592305474596
        }
}
} to AWS IoT broker
<inf> aws_iot_sample: Next data publication in 60 seconds

To observe incoming messages in the AWS IoT console, navigate to the AWS IoT Core service and click MQTT test client. To observe messages that are sent from the device, subscribe to the $aws/things/<client_id>/shadow/update shadow topic or the wild card token #.

If you have issues with the sample, refer to gs_testing.

This sample uses the following libraries and drivers:

• lib_aws_iot
• lib_date_time
• lte_lc_readme
• modem_info_readme

It uses the following sdk-nrfxlib library:

• nrfxlib:nrf_modem

In addition, it uses the following secure firmware component:

• Trusted Firmware-M <ug_tfm>