Prerequisites for OTA updates using MQTT
Important
This is an archived version of the FreeRTOS User Guide for use with FreeRTOS release 202012.00. For the latest version of this document, see the FreeRTOS User Guide.
This section describes the general requirements for using MQTT to perform over-the-air (OTA updates).
To provide access, add permissions to your users, groups, or roles:
-
Users managed in IAM through an identity provider:
Create a role for identity federation. Follow the instructions in Create a role for a third-party identity provider (federation) in the IAM User Guide.
-
IAM users:
-
Create a role that your user can assume. Follow the instructions in Create a role for an IAM user in the IAM User Guide.
-
(Not recommended) Attach a policy directly to a user or add a user to a user group. Follow the instructions in Adding permissions to a user (console) in the IAM User Guide.
-
Minimum requirements
-
Device firmware must include the necessary FreeRTOS libraries (coreMQTT, OTA Agent, and their dependencies).
-
FreeRTOS version 1.4.0 or later is required. However, we recommend that you use the latest version when possible.
Configurations
Beginning with version 201912.00, FreeRTOS OTA can use either the HTTP or MQTT protocol to transfer firmware update images from Amazon IoT to devices. If you specify both protocols when you create an OTA update in FreeRTOS, each device will determine the protocol used to transfer the image. See Prerequisites for OTA updates using HTTP for more information.
By default, the configuration of the OTA protocols in
aws_ota_agent_config.h is to use the MQTT protocol:
/** * @brief The protocol selected for OTA control operations. * This configuration parameter sets the default protocol for all the OTA control * operations like requesting OTA job, updating the job status etc. * * Note - Only MQTT is supported at this time for control operations. */ #define configENABLED_CONTROL_PROTOCOL ( OTA_CONTROL_OVER_MQTT ) /** * @brief The protocol selected for OTA data operations. * This configuration parameter sets the protocols selected for the data operations * like requesting file blocks from the service. * * Note - Both MQTT and HTTP are supported for data transfer. This configuration parameter * can be set to the following - * Enable data over MQTT - ( OTA_DATA_OVER_MQTT ) * Enable data over HTTP - ( OTA_DATA_OVER_HTTP) * Enable data over both MQTT & HTTP ( OTA_DATA_OVER_MQTT | OTA_DATA_OVER_HTTP ) */ #define configENABLED_DATA_PROTOCOLS ( OTA_DATA_OVER_MQTT ) /** * @brief The preferred protocol selected for OTA data operations. * * Primary data protocol will be the protocol used for downloading files if more than * one protocol is selected while creating OTA job. Default primary data protocol is MQTT * and the following update here switches to HTTP as primary. * * Note - use OTA_DATA_OVER_HTTP for HTTP as primary data protocol. */ #define configOTA_PRIMARY_DATA_PROTOCOL ( OTA_DATA_OVER_MQTT )
Device specific configurations
None.
Memory usage
When MQTT is used for data transfer, no additional memory is required for the MQTT connection because it's shared between control and data operations.
Device policy
Each device that receives an OTA update using MQTT must be registered as a thing
in Amazon IoT and the thing must have an attached policy like the one listed here. You
can find more information about the items in the "Action" and
"Resource" objects at Amazon IoT
Core Policy Actions and Amazon IoT Core Action Resources.
Notes
-
The
iot:Connectpermissions allow your device to connect to Amazon IoT over MQTT. -
The
iot:Subscribeandiot:Publishpermissions on the topics of Amazon IoT jobs (.../jobs/*) allow the connected device to receive job notifications and job documents, and to publish the completion state of a job execution. -
The
iot:Subscribeandiot:Publishpermissions on the topics of Amazon IoT OTA streams (.../streams/*) allow the connected device to fetch OTA update data from Amazon IoT. These permissions are required to perform firmware updates over MQTT. -
The
iot:Receivepermissions allow Amazon IoT Core to publish messages on those topics to the connected device. This permission is checked on every delivery of an MQTT message. You can use this permission to revoke access to clients that are currently subscribed to a topic.