- Overview
- Versioning
- Releases and Documentation
- Porting Guide for 202009.00 and newer releases
- Migration guide from v3.1.5 to 202009.00 and newer releases
- Branches
- Getting Started
- Cloning
- Configuring Demos
- Prerequisites
- AWS IoT Account Setup
- Configuring mutual authentication demos of MQTT and HTTP
- Configuring AWS IoT Device Defender and AWS IoT Device Shadow demos
- Configuring the AWS IoT Fleet Provisioning demo
- Configuring the S3 demos
- Setup for AWS IoT Jobs demo
- Setup for the Greengrass local auth demo
- Building and Running Demos
- Generating Documentation
The AWS IoT Device SDK for Embedded C (C-SDK) is a collection of C source files under the MIT open source license that can be used in embedded applications to securely connect IoT devices to AWS IoT Core. It contains MQTT client, HTTP client, JSON Parser, AWS IoT Device Shadow, AWS IoT Jobs, and AWS IoT Device Defender libraries. This SDK is distributed in source form, and can be built into customer firmware along with application code, other libraries and an operating system (OS) of your choice. These libraries are only dependent on standard C libraries, so they can be ported to various OS's - from embedded Real Time Operating Systems (RTOS) to Linux/Mac/Windows. You can find sample usage of C-SDK libraries on POSIX systems using OpenSSL (e.g. Linux demos in this repository), and on FreeRTOS using mbedTLS (e.g. FreeRTOS demos in FreeRTOS repository).
For the latest release of C-SDK, please see the section for Releases and Documentation.
C-SDK includes libraries that are part of the FreeRTOS 202210.01 LTS release. Learn more about the FreeRTOS 202210.01 LTS libraries by clicking here.
The C-SDK libraries are licensed under the MIT open source license.
C-SDK simplifies access to various AWS IoT services. C-SDK has been tested to work with AWS IoT Core and an open source MQTT broker to ensure interoperability. The AWS IoT Device Shadow, AWS IoT Jobs, and AWS IoT Device Defender libraries are flexible to work with any MQTT client and JSON parser. The MQTT client and JSON parser libraries are offered as choices without being tightly coupled with the rest of the SDK. C-SDK contains the following libraries:
The coreMQTT library provides the ability to establish an MQTT connection with a broker over a customer-implemented transport layer, which can either be a secure channel like a TLS session (mutually authenticated or server-only authentication) or a non-secure channel like a plaintext TCP connection. This MQTT connection can be used for performing publish operations to MQTT topics and subscribing to MQTT topics. The library provides a mechanism to register customer-defined callbacks for receiving incoming PUBLISH, acknowledgement and keep-alive response events from the broker. The library has been refactored for memory optimization and is compliant with the MQTT 3.1.1 standard. It has no dependencies on any additional libraries other than the standard C library, a customer-implemented network transport interface, and optionally a customer-implemented platform time function. The refactored design embraces different use-cases, ranging from resource-constrained platforms using only QoS 0 MQTT PUBLISH messages to resource-rich platforms using QoS 2 MQTT PUBLISH over TLS connections.
See memory requirements for the latest release here.
The coreHTTP library provides the ability to establish an HTTP connection with a server over a customer-implemented transport layer, which can either be a secure channel like a TLS session (mutually authenticated or server-only authentication) or a non-secure channel like a plaintext TCP connection. The HTTP connection can be used to make "GET" (include range requests), "PUT", "POST" and "HEAD" requests. The library provides a mechanism to register a customer-defined callback for receiving parsed header fields in an HTTP response. The library has been refactored for memory optimization, and is a client implementation of a subset of the HTTP/1.1 standard.
See memory requirements for the latest release here.
The coreJSON library is a JSON parser that strictly enforces the ECMA-404 JSON standard. It provides a function to validate a JSON document, and a function to search for a key and return its value. A search can descend into nested structures using a compound query key. A JSON document validation also checks for illegal UTF8 encodings and illegal Unicode escape sequences.
See memory requirements for the latest release here.
The corePKCS11 library is an implementation of the PKCS #11 interface (API) that makes it easier to develop applications that rely on cryptographic operations. Only a subset of the PKCS #11 v2.4 standard has been implemented, with a focus on operations involving asymmetric keys, random number generation, and hashing.
The Cryptoki or PKCS #11 standard defines a platform-independent API to manage and use cryptographic tokens. The name, "PKCS #11", is used interchangeably to refer to the API itself and the standard which defines it.
The PKCS #11 API is useful for writing software without taking a dependency on any particular implementation or hardware. By writing against the PKCS #11 standard interface, code can be used interchangeably with multiple algorithms, implementations and hardware.
Generally vendors for secure cryptoprocessors such as Trusted Platform Module (TPM), Hardware Security Module (HSM), Secure Element, or any other type of secure hardware enclave, distribute a PKCS #11 implementation with the hardware. The purpose of corePKCS11 mock is therefore to provide a PKCS #11 implementation that allows for rapid prototyping and development before switching to a cryptoprocessor specific PKCS #11 implementation in production devices.
Since the PKCS #11 interface is defined as part of the PKCS #11 specification replacing corePKCS11 with another implementation should require little porting effort, as the interface will not change. The system tests distributed in corePKCS11 repository can be leveraged to verify the behavior of a different implementation is similar to corePKCS11.
See memory requirements for the latest release here.
The AWS IoT Device Shadow library enables you to store and retrieve the current state one or more shadows of every registered device. A device’s shadow is a persistent, virtual representation of your device that you can interact with from AWS IoT Core even if the device is offline. The device state is captured in its "shadow" is represented as a JSON document. The device can send commands over MQTT to get, update and delete its latest state as well as receive notifications over MQTT about changes in its state. The device’s shadow(s) are uniquely identified by the name of the corresponding "thing", a representation of a specific device or logical entity on the AWS Cloud. See Managing Devices with AWS IoT for more information on IoT "thing". This library supports named shadows, a feature of the AWS IoT Device Shadow service that allows you to create multiple shadows for a single IoT device. More details about AWS IoT Device Shadow can be found in AWS IoT documentation.
The AWS IoT Device Shadow library has no dependencies on additional libraries other than the standard C library. It also doesn’t have any platform dependencies, such as threading or synchronization. It can be used with any MQTT library and any JSON library (see demos with coreMQTT and coreJSON).
See memory requirements for the latest release here.
The AWS IoT Jobs library enables you to interact with the AWS IoT Jobs service which notifies one or more connected devices of a pending “Job”. A Job can be used to manage your fleet of devices, update firmware and security certificates on your devices, or perform administrative tasks such as restarting devices and performing diagnostics. For documentation of the service, please see the AWS IoT Developer Guide. Interactions with the Jobs service use the MQTT protocol. This library provides an API to compose and recognize the MQTT topic strings used by the Jobs service.
The AWS IoT Jobs library has no dependencies on additional libraries other than the standard C library. It also doesn’t have any platform dependencies, such as threading or synchronization. It can be used with any MQTT library and any JSON library (see demos with libmosquitto and coreJSON).
See memory requirements for the latest release here.
The AWS IoT Device Defender library enables you to interact with the AWS IoT Device Defender service to continuously monitor security metrics from devices for deviations from what you have defined as appropriate behavior for each device. If something doesn’t look right, AWS IoT Device Defender sends out an alert so you can take action to remediate the issue. More details about Device Defender can be found in AWS IoT Device Defender documentation. This library supports custom metrics, a feature that helps you monitor operational health metrics that are unique to your fleet or use case. For example, you can define a new metric to monitor the memory usage or CPU usage on your devices.
The AWS IoT Device Defender library has no dependencies on additional libraries other than the standard C library. It also doesn’t have any platform dependencies, such as threading or synchronization. It can be used with any MQTT library and any JSON library (see demos with coreMQTT and coreJSON).
See memory requirements for the latest release here.
Removed since v2022412.00. We recommend transitioning to the new modular and composable OTA approach . To get started, see the new OTA reference demo.
The AWS IoT Fleet Provisioning library enables you to interact with the AWS IoT Fleet Provisioning MQTT APIs in order to provison IoT devices without preexisting device certificates. With AWS IoT Fleet Provisioning, devices can securely receive unique device certificates from AWS IoT when they connect for the first time. For an overview of all provisioning options offered by AWS IoT, see device provisioning documentation. For details about Fleet Provisioning, refer to the AWS IoT Fleet Provisioning documentation.
See memory requirements for the latest release here.
The AWS SigV4 library enables you to sign HTTP requests with Signature Version 4 Signing Process. Signature Version 4 (SigV4) is the process to add authentication information to HTTP requests to AWS services. For security, most requests to AWS must be signed with an access key. The access key consists of an access key ID and secret access key.
See memory requirements for the latest release here.
The backoffAlgorithm library is a utility library to calculate backoff period using an exponential backoff with jitter algorithm for retrying network operations (like failed network connection with server). This library uses the "Full Jitter" strategy for the exponential backoff with jitter algorithm. More information about the algorithm can be seen in the Exponential Backoff and Jitter AWS blog.
Exponential backoff with jitter is typically used when retrying a failed connection or network request to the server. An exponential backoff with jitter helps to mitigate the failed network operations with servers, that are caused due to network congestion or high load on the server, by spreading out retry requests across multiple devices attempting network operations. Besides, in an environment with poor connectivity, a client can get disconnected at any time. A backoff strategy helps the client to conserve battery by not repeatedly attempting reconnections when they are unlikely to succeed.
The backoffAlgorithm library has no dependencies on libraries other than the standard C library.
See memory requirements for the latest release here.
When establishing a connection with AWS IoT, users can optionally report the Operating System, Hardware Platform and MQTT client version information of their device to AWS. This information can help AWS IoT provide faster issue resolution and technical support. If users want to report this information, they can send a specially formatted string (see below) in the username field of the MQTT CONNECT packet.
Format
The format of the username string with metrics is:
<Actual_Username>?SDK=<OS_Name>&Version=<OS_Version>&Platform=<Hardware_Platform>&MQTTLib=<MQTT_Library_name>@<MQTT_Library_version>
Where
- <Actual_Username> is the actual username used for authentication, if username and password are used for authentication. When username and password based authentication is not used, this is an empty value.
- <OS_Name> is the Operating System the application is running on (e.g. Ubuntu)
- <OS_Version> is the version number of the Operating System (e.g. 20.10)
- <Hardware_Platform> is the Hardware Platform the application is running on (e.g. RaspberryPi)
- <MQTT_Library_name> is the MQTT Client library being used (e.g. coreMQTT)
- <MQTT_Library_version> is the version of the MQTT Client library being used (e.g. 1.1.0)
Example
- Actual_Username = “iotuser”, OS_Name = Ubuntu, OS_Version = 20.10, Hardware_Platform_Name = RaspberryPi, MQTT_Library_Name = coremqtt, MQTT_Library_version = 1.1.0. If username is not used, then “iotuser” can be removed.
/* Username string:
* iotuser?SDK=Ubuntu&Version=20.10&Platform=RaspberryPi&[email protected]
*/
#define OS_NAME "Ubuntu"
#define OS_VERSION "20.10"
#define HARDWARE_PLATFORM_NAME "RaspberryPi"
#define MQTT_LIB "[email protected]"
#define USERNAME_STRING "iotuser?SDK=" OS_NAME "&Version=" OS_VERSION "&Platform=" HARDWARE_PLATFORM_NAME "&MQTTLib=" MQTT_LIB
#define USERNAME_STRING_LENGTH ( ( uint16_t ) ( sizeof( USERNAME_STRING ) - 1 ) )
MQTTConnectInfo_t connectInfo;
connectInfo.pUserName = USERNAME_STRING;
connectInfo.userNameLength = USERNAME_STRING_LENGTH;
mqttStatus = MQTT_Connect( pMqttContext, &connectInfo, NULL, CONNACK_RECV_TIMEOUT_MS, pSessionPresent );
C-SDK releases will now follow a date based versioning scheme with the format YYYYMM.NN, where:
- Y represents the year.
- M represents the month.
- N represents the release order within the designated month (00 being the first release).
For example, a second release in June 2021 would be 202106.01. Although the SDK releases have moved to date-based versioning, each library within the SDK will still retain semantic versioning. In semantic versioning, the version number itself (X.Y.Z) indicates whether the release is a major, minor, or point release. You can use the semantic version of a library to assess the scope and impact of a new release on your application.
All of the released versions of the C-SDK libraries are available as git tags. For example, the last release of the v3 SDK version is available at tag 3.1.5.
API documentation of 202412.00 release
This release includes 202406.01-LTS versions of coreMQTT, corePKCS11, coreHTTP, coreJSON, backoffAlgorithm, AWS IoT Device Shadow, AWS IoT Jobs, AWS IoT Device Defender, AWS IoT Fleet Provisioning and SigV4 libraries.
Additionally it updates the MbedTLS version to v3.5.1 and removes the OTA library and its associated demo. We recommend transitioning to the new modular and composable OTA approach . To get started, see the new OTA reference demo.
API documentation of 202211.00 release
This release includes an update to how the Coverity static analysis scans are performed. There is now a tools/coverity/README.md file in each library with instructions on how to perform a scan with 0 MISRA coding standard warnings or errors.
Additionally, this release brings in major version upgrades to coreMQTT and coreHTTP. It also brings in minor version upgrades to all other libraries.
API documentation of 202108.00 release
This release introduces the refactored AWS IoT Fleet Provisioning library and the new AWS SigV4 library.
Additionally, this release brings minor version updates in the AWS IoT Over-the-Air Update and corePKCS11 libraries.
API documentation of 202103.00 release
This release includes a major update to the APIs of the AWS IoT Over-the-air Update library.
Additionally, AWS IoT Device Shadow library introduces a minor update by adding support for named shadow, a feature of the AWS IoT Device Shadow service that allows you to create multiple shadows for a single IoT device. AWS IoT Jobs library introduces a minor update by introducing macros for $next job ID and compile-time generation of topic strings. AWS IoT Device Defender library introduces a minor update that adds macros to API for custom metrics feature of AWS IoT Device Defender service.
corePKCS11 also introduces a patch update by removing the pkcs11configPAL_DESTROY_SUPPORTED config and mbedTLS platform abstraction layer of DestroyObject. Lastly, no code changes are introduced for backoffAlgorithm, coreHTTP, coreMQTT, and coreJSON; however, patch updates are made to improve documentation and CI.
API documentation of 202012.01 release
This release includes AWS IoT Over-the-air Update(Release Candidate), backoffAlgorithm, and PKCS #11 libraries. Additionally, there is a major update to the coreJSON and coreHTTP APIs. All libraries continue to undergo code quality checks (e.g. MISRA-C compliance), and Coverity static analysis. In addition, all libraries except AWS IoT Over-the-air Update and backoffAlgorithm undergo validation of memory safety with the C Bounded Model Checker (CBMC) automated reasoning tool.
API documentation of 202011.00 release
This release includes refactored HTTP client, AWS IoT Device Defender, and AWS IoT Jobs libraries. Additionally, there is a major update to the coreJSON API. All libraries continue to undergo code quality checks (e.g. MISRA-C compliance), Coverity static analysis, and validation of memory safety with the C Bounded Model Checker (CBMC) automated reasoning tool.
API documentation of 202009.00 release
This release includes refactored MQTT, JSON Parser, and AWS IoT Device Shadow libraries for optimized memory usage and modularity. These libraries are included in the SDK via Git submoduling. These libraries have gone through code quality checks including verification that no function has a GNU Complexity score over 8, and checks against deviations from mandatory rules in the MISRA coding standard. Deviations from the MISRA C:2012 guidelines are documented under MISRA Deviations. These libraries have also undergone both static code analysis from Coverity static analysis, and validation of memory safety and data structure invariance through the CBMC automated reasoning tool.
If you are upgrading from v3.x API of the C-SDK to the 202009.00 release, please refer to Migration guide from v3.1.5 to 202009.00 and newer releases. If you are using the C-SDK v4_beta_deprecated branch, note that we will continue to maintain this branch for critical bug fixes and security patches but will not add new features to it. See the C-SDK v4_beta_deprecated branch README for additional details.
Details available here.
All libraries depend on the ISO C90 standard library and additionally on the stdint.h library for fixed-width integers, including uint8_t, int8_t, uint16_t, uint32_t and int32_t, and constant macros like UINT16_MAX. If your platform does not support the stdint.h library, definitions of the mentioned fixed-width integer types will be required for porting any C-SDK library to your platform.
Guide for porting coreMQTT library to your platform is available here.
Guide for porting coreHTTP library is available here.
Guide for porting AWS IoT Device Shadow library is available here.
Guide for porting AWS IoT Device Defender library is available here.
Migration guide for MQTT library is available here.
Migration guide for Shadow library is available here.
Migration guide for Jobs library is available here.
The main branch hosts the continuous development of the AWS IoT Embedded C SDK (C-SDK) libraries. Please be aware that the development at the tip of the main branch is continuously in progress, and may have bugs. Consider using the tagged releases of the C-SDK for production ready software.
The v4_beta_deprecated branch contains a beta version of the C-SDK libraries, which is now deprecated. This branch was earlier named as v4_beta, and was renamed to v4_beta_deprecated. The libraries in this branch will not be released. However, critical bugs will be fixed and tested. No new features will be added to this branch.
This repository uses Git Submodules to bring in the C-SDK libraries (eg, MQTT ) and third-party dependencies (eg, mbedtls for POSIX platform transport layer). Note: If you download the ZIP file provided by GitHub UI, you will not get the contents of the submodules (The ZIP file is also not a valid git repository). If you download from the 202012.00 Release Page page, you will get the entire repository (including the submodules) in the ZIP file, aws-iot-device-sdk-embedded-c-202012.00.zip. To clone the latest commit to main branch using HTTPS:
git clone --recurse-submodules https://github.com/aws/aws-iot-device-sdk-embedded-C.gitUsing SSH:
git clone --recurse-submodules [email protected]:aws/aws-iot-device-sdk-embedded-C.gitIf you have downloaded the repo without using the --recurse-submodules argument, you need to run:
git submodule update --init --recursiveWhen building with CMake, submodules are also recursively cloned automatically. However, -DBUILD_CLONE_SUBMODULES=0
can be passed as a CMake flag to disable this functionality. This is useful when you'd like to build CMake while using a
different commit from a submodule.
The libraries in this SDK are not dependent on any operating system. However, the demos for the libraries in this SDK are built and tested on a Linux platform. The demos build with CMake, a cross-platform build tool.
- CMake 3.2.0 or any newer version for utilizing the build system of the repository.
- C90 compiler such as gcc
- Due to the use of mbedtls in corePKCS11, a C99 compiler is required if building the PKCS11 demos.
- Although not a part of the ISO C90 standard,
stdint.his required for fixed-width integer types that includeuint8_t,int8_t,uint16_t,uint32_tandint32_t, and constant macros likeUINT16_MAX, whilestdbool.his required for boolean parameters in coreMQTT. For compilers that do not provide these header files, coreMQTT provides the files stdint.readme and stdbool.readme, which can be renamed tostdint.handstdbool.h, respectively, to provide the required type definitions. - A supported operating system. The ports provided with this repo are expected to work with all recent versions of the following operating systems, although we cannot guarantee the behavior on all systems.
- Linux system with POSIX sockets, threads, RT, and timer APIs. (We have tested on Ubuntu 18.04).
The follow table shows libraries that need to be installed in your system to run certain demos. If a dependency is
not installed and cannot be built from source, demos that require that dependency will be excluded
from the default all target.
| Dependency | Version | Usage |
|---|---|---|
| OpenSSL | 1.1.0 or later | All TLS demos and tests with the exception of PKCS11 |
| Mosquitto Client | 1.4.10 or later | AWS IoT Jobs Mosquitto demo |
You need to setup an AWS account and access the AWS IoT console for running the AWS IoT Device Shadow library, AWS IoT Device Defender library, AWS IoT Jobs library, and coreHTTP S3 download demos. Also, the AWS account can be used for running the MQTT mutual auth demo against AWS IoT broker. Note that running the AWS IoT Device Defender, AWS IoT Jobs and AWS IoT Device Shadow library demos require the setup of a Thing resource for the device running the demo. Follow the links to:
- Setup an AWS account.
- Sign-in to the AWS IoT Console after setting up the AWS account.
- Create a Thing resource.
The MQTT Mutual Authentication and AWS IoT Shadow demos include example AWS IoT policy documents to run each respective demo with AWS IoT. You may use the MQTT Mutual auth and Shadow example policies by replacing [AWS_REGION] and [AWS_ACCOUNT_ID] with the strings of your region and account identifier. While the IoT Thing name and MQTT client identifier do not need to match for the demos to run, the example policies have the Thing name and client identifier identical as per AWS IoT best practices.
It can be very helpful to also have the AWS Command Line Interface tooling installed.
You can pass the following configuration settings as command line options in order to run the mutual auth demos. Make sure to run the following command in the root directory of the C-SDK:
## optionally find your-aws-iot-endpoint from the command line
aws iot describe-endpoint --endpoint-type iot:Data-ATS
cmake -S . -Bbuild
-DAWS_IOT_ENDPOINT="<your-aws-iot-endpoint>" -DCLIENT_CERT_PATH="<your-client-certificate-path>" -DCLIENT_PRIVATE_KEY_PATH="<your-client-private-key-path>"In order to set these configurations manually, edit demo_config.h in demos/mqtt/mqtt_demo_mutual_auth/ and demos/http/http_demo_mutual_auth/ to #define the following:
- Set
AWS_IOT_ENDPOINTto your custom endpoint. This is found on the Settings page of the AWS IoT Console and has a format ofABCDEFG1234567.iot.<aws-region>.amazonaws.comwhere<aws-region>can be an AWS region likeus-east-2.- Optionally, it can also be found with the AWS CLI command
aws iot describe-endpoint --endpoint-type iot:Data-ATS.
- Optionally, it can also be found with the AWS CLI command
- Set
CLIENT_CERT_PATHto the path of the client certificate downloaded when setting up the device certificate in AWS IoT Account Setup. - Set
CLIENT_PRIVATE_KEY_PATHto the path of the private key downloaded when setting up the device certificate in AWS IoT Account Setup.
It is possible to configure ROOT_CA_CERT_PATH to any PEM-encoded Root CA Certificate.
However, this is optional because CMake will download and set it to AmazonRootCA1.pem when unspecified.
If unspecified, the default Root CA path will be interpreted relative to where the demo binary is executed.
For many demos, you can change this path by modifying it in the corresponding demo_config.h.
To build the AWS IoT Device Defender and AWS IoT Device Shadow demos, you can pass the following configuration settings as command line options. Make sure to run the following command in the root directory of the C-SDK:
cmake -S . -Bbuild -DAWS_IOT_ENDPOINT="<your-aws-iot-endpoint>" -DROOT_CA_CERT_PATH="<your-path-to-amazon-root-ca>" -DCLIENT_CERT_PATH="<your-client-certificate-path>" -DCLIENT_PRIVATE_KEY_PATH="<your-client-private-key-path>" -DTHING_NAME="<your-registered-thing-name>"An Amazon Root CA certificate can be downloaded from here.
In order to set these configurations manually, edit demo_config.h in the demo folder to #define the following:
- Set
AWS_IOT_ENDPOINTto your custom endpoint. This is found on the Settings page of the AWS IoT Console and has a format ofABCDEFG1234567.iot.us-east-2.amazonaws.com. - Set
ROOT_CA_CERT_PATHto the path of the root CA certificate downloaded when setting up the device certificate in AWS IoT Account Setup. - Set
CLIENT_CERT_PATHto the path of the client certificate downloaded when setting up the device certificate in AWS IoT Account Setup. - Set
CLIENT_PRIVATE_KEY_PATHto the path of the private key downloaded when setting up the device certificate in AWS IoT Account Setup. - Set
THING_NAMEto the name of the Thing created in AWS IoT Account Setup.
To build the AWS IoT Fleet Provisioning Demo, you can pass the following configuration settings as command line options. Make sure to run the following command in the root directory of the C-SDK:
cmake -S . -Bbuild -DAWS_IOT_ENDPOINT="<your-aws-iot-endpoint>" -DROOT_CA_CERT_PATH="<your-path-to-amazon-root-ca>" -DCLAIM_CERT_PATH="<your-claim-certificate-path>" -DCLAIM_PRIVATE_KEY_PATH="<your-claim-private-key-path>" -DPROVISIONING_TEMPLATE_NAME="<your-template-name>" -DDEVICE_SERIAL_NUMBER="<your-serial-number>"An Amazon Root CA certificate can be downloaded from here.
To create a provisioning template and claim credentials, sign into your AWS account and follow the steps given in the readme.md in the demo folder and visit here. Make sure to enable the "Use the AWS IoT registry to manage your device fleet" option. Once you have created the template and credentials, modify the claim certificate's policy to match the sample policy.
In order to set these configurations manually, edit demo_config.h in the demo folder to #define the following:
- Set
AWS_IOT_ENDPOINTto your custom endpoint. This is found on the Settings page of the AWS IoT Console and has a format ofABCDEFG1234567.iot.us-east-2.amazonaws.com. - Set
ROOT_CA_CERT_PATHto the path of the root CA certificate downloaded when setting up the device certificate in AWS IoT Account Setup. - Set
CLAIM_CERT_PATHto the path of the claim certificate downloaded when setting up the template and claim credentials. - Set
CLAIM_PRIVATE_KEY_PATHto the path of the private key downloaded when setting up the template and claim credentials. - Set
PROVISIONING_TEMPLATE_NAMEto the name of the provisioning template created. - Set
DEVICE_SERIAL_NUMBERto an arbitrary string representing a device identifier.
You can pass the following configuration settings as command line options in order to run the S3 demos. Make sure to run the following command in the root directory of the C-SDK:
cmake -S . -Bbuild -DS3_PRESIGNED_GET_URL="s3-get-url" -DS3_PRESIGNED_PUT_URL="s3-put-url"S3_PRESIGNED_PUT_URL is only needed for the S3 upload demo.
In order to set these configurations manually, edit demo_config.h in demos/http/http_demo_s3_download_multithreaded, and demos/http/http_demo_s3_upload to #define the following:
- Set
S3_PRESIGNED_GET_URLto a S3 presigned URL with GET access. - Set
S3_PRESIGNED_PUT_URLto a S3 presigned URL with PUT access.
You can generate the presigned urls using demos/http/common/src/presigned_urls_gen.py. More info can be found here.
Refer this demos/http/http_demo_s3_download/README.md to follow the steps needed to configure and run the S3 Download HTTP Demo using SigV4 Library that generates the authorization HTTP header needed to authenticate the HTTP requests send to S3.
Refer this demos/http/http_demo_s3_generate_presigned_url/README.md to follow the steps needed to configure and run the S3 Generate Pre-signed URL HTTP Demo using SigV4 Library that generates the authorization HTTP header needed to authenticate the HTTP requests send to S3.
- The demo requires the Linux platform to contain curl and libmosquitto. On a Debian platform, these dependencies can be installed with:
apt install curl libmosquitto-dev
If the platform does not contain the libmosquitto library, the demo will build the library from source.
libmosquitto 1.4.10 or any later version of the first major release is required to run this demo.
- A job that specifies the URL to download for the demo needs to be created on the AWS account for the Thing resource that will be used by the demo. The job can be created directly from the AWS IoT console or using the aws cli tool.
The following creates a job that specifies a Linux Kernel link for downloading.
aws iot create-job \
--job-id 'job_1' \
--targets arn:aws:iot:us-west-2:<account-id>:thing/<thing-name> \
--document '{"url":"https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.8.5.tar.xz"}'
- Run the demo using this command:
./build/bin/jobs_demo_mosquitto \
-n <thing-name> \
-h <aws-iot endpoint> \
--certfile <device certificate of the thing> \
--keyfile <private key of the thing>
Note: Replace the placeholders in angle brackets with your specific information.
For setting up the Greengrass local auth demo, see the README in the demo folder.
Before building the demos, ensure you have installed the prerequisite software. On Ubuntu 18.04 and 20.04, gcc, cmake, and OpenSSL can be installed with:
sudo apt install build-essential cmake libssl-dev- Go to the root directory of the C-SDK.
- Run cmake to generate the Makefiles:
cmake -S . -Bbuild && cd build - Choose a demo from the list below or alternatively, run
make help | grep demo:
defender_demo
http_demo_basic_tls
http_demo_mutual_auth
http_demo_plaintext
http_demo_s3_download
http_demo_s3_generate_presigned_url
http_demo_s3_download_multithreaded
http_demo_s3_upload
jobs_demo_mosquitto
mqtt_demo_basic_tls
mqtt_demo_mutual_auth
mqtt_demo_plaintext
mqtt_demo_serializer
mqtt_demo_subscription_manager
pkcs11_demo_management_and_rng
pkcs11_demo_mechanisms_and_digests
pkcs11_demo_objects
pkcs11_demo_sign_and_verify
shadow_demo_main
- Replace
demo_namewith your desired demo then build it:make demo_name - Go to the
build/bindirectory and run any demo executables from there.
- Go to the root directory of the C-SDK.
- Run cmake to generate the Makefiles:
cmake -S . -Bbuild && cd build - Run this command to build all configured demos:
make - Go to the
build/bindirectory and run any demo executables from there.
The corePKCS11 demos do not require any AWS IoT resources setup, and are standalone. The demos build upon each other to introduce concepts in PKCS #11 sequentially. Below is the recommended order.
pkcs11_demo_management_and_rngpkcs11_demo_mechanisms_and_digestspkcs11_demo_objectspkcs11_demo_sign_and_verify- Please note that this demo requires the private and public key generated from
pkcs11_demo_objectsto be in the directory the demo is executed from.
- Please note that this demo requires the private and public key generated from
Install Docker:
curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.shThe following instructions have been tested on an Ubuntu 18.04 environment with Docker and OpenSSL installed.
-
Download the official Docker image for Mosquitto 1.6.14. This version is deliberately chosen so that the Docker container can load certificates from the host system. Any version after 1.6.14 will drop privileges as soon as the configuration file has been read (before TLS certificates are loaded).
docker pull eclipse-mosquitto:1.6.14
-
If a Mosquitto broker with TLS communication needs to be run, ignore this step and proceed to the next step. A Mosquitto broker with plain text communication can be run by executing the command below.
docker run -it -p 1883:1883 --name mosquitto-plain-text eclipse-mosquitto:1.6.14 -
Set
BROKER_ENDPOINTdefined indemos/mqtt/mqtt_demo_plaintext/demo_config.htolocalhost.Ignore the remaining steps unless a Mosquitto broker with TLS communication also needs to be run.
-
For TLS communication with Mosquitto broker, server and CA credentials need to be created. Use OpenSSL commands to generate the credentials for the Mosquitto server.
Note: Make sure to use different Common Name (CN) detail between the CA and server certificates; otherwise, SSL handshake fails with exactly same Common Name (CN) detail in both the certificates.
# Generate CA key and certificate. Provide the Subject field information as appropriate for CA certificate. openssl req -x509 -nodes -sha256 -days 365 -newkey rsa:2048 -keyout ca.key -out ca.crtYou will be prompted to configure the Common Name (CN) after running the following command. It's crucial to enter the same value that was specified for the
BROKER_ENDPOINTmacro in the demo_config.h file. In this particular instance, the correct value to enter is simply "localhost".# Generate server key and certificate.# Provide the Subject field information as appropriate for Server certificate. Make sure the Common Name (CN) field is different from the root CA certificate. openssl req -nodes -sha256 -new -keyout server.key -out server.csr # Sign with the CA cert. openssl x509 -req -sha256 -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt -days 365
-
Create a mosquitto.conf file to use port 8883 (for TLS communication) and providing path to the generated credentials.
port 8883 cafile /mosquitto/config/ca.crt certfile /mosquitto/config/server.crt keyfile /mosquitto/config/server.key # Use this option for TLS mutual authentication (where client will provide CA signed certificate) #require_certificate true tls_version tlsv1.2 #use_identity_as_username true -
Run the docker container from the local directory containing the generated credential and mosquitto.conf files.
docker run -it -p 8883:8883 -v $(pwd):/mosquitto/config/ --name mosquitto-basic-tls eclipse-mosquitto:1.6.14 -
Update
demos/mqtt/mqtt_demo_basic_tls/demo_config.hto the following: SetBROKER_ENDPOINTtolocalhost. SetROOT_CA_CERT_PATHto the absolute path of the CA certificate created in step 4. for the local Mosquitto server.
Run httpbin through port 80:
docker pull kennethreitz/httpbin
docker run -p 80:80 kennethreitz/httpbinThe kennetheitz/httpbin docker image is not compatible with linux/arm64 platform that is used by Mac machines. Hence instead of that use mccutchen/go-httpbin.
#To install the image run:
$ docker pull mccutchen/go-httpbin
#To run the server on local host on port 80 run
$ docker run -p 80:8080 mccutchen/go-httpbinSERVER_HOST defined in demos/http/http_demo_plaintext/demo_config.h can now be set to localhost.
To run http_demo_basic_tls, you could use either Tunnelmole, an open source tunneling tool, or ngrok, a popular closed source tunneling tool, to create an HTTPS tunnel to the httpbin server currently hosted on port 80:
Using Tunnelmole
First, install Tunnelmole. On Linux, Mac and Windows Subsystem for Linux, use
curl -O https://tunnelmole.com/sh/install.sh && sudo bash install.shThe above may not function correctly on ARM machines like mac. As an alternative, you can clone the repository and build the application from its source code. For Windows without WSL, download tmole.exe and add it to your PATH.
Then run tmole 80
tmole 80Tunnelmole will provide a https link that can be substituted in demos/http/http_demo_basic_tls/demo_config.h and has a format of https://bvdo5f-ip-49-183-170-144.tunnelmole.net.
Set SERVER_HOST in demos/http/http_demo_basic_tls/demo_config.h to the https link provided by Tunnelmole, without https:// preceding it.
Using ngrok
./ngrok http 80 # May have to use ./ngrok.exe depending on OS or filename of the executablengrok will provide an https link that can be substituted in demos/http/http_demo_basic_tls/demo_config.h and has a format of https://ABCDEFG12345.ngrok.io.
Set SERVER_HOST in demos/http/http_demo_basic_tls/demo_config.h to the https link provided by ngrok, without https:// preceding it.
Getting the Root CA
Download the Root CA certificate from the obtained https link. To obtain this:
- Open the https link in your browser.
- Click on the https lock button in the url bar.
- Download the chain of certificates.
- Locate the last certificate in the chain - this is your required Root CA certificate.
- Copy this certificate and paste it into a new .pem file.
Set the macro ROOT_CA_CERT_PATH in demo_config.h to the file path of your newly created Root CA certificate.
Note: For pre-generated documentation, please visit Releases and Documentation section.
The Doxygen references were created using Doxygen version 1.9.2. To generate the Doxygen pages, use the provided Python script at tools/doxygen/generate_docs.py. Please ensure that each of the library submodules under libraries/standard/ and libraries/aws/ are cloned before using this script.
cd <CSDK_ROOT>
git submodule update --init --recursive --checkout
python3 tools/doxygen/generate_docs.pyThe generated documentation landing page is located at docs/doxygen/output/html/index.html.