Skip to content

3.2.1. Design To Withstand Component and System Faults

ID Priority Best Practice
BP 3.2.1.1 Highly Recommended Use the services provided by your vendors for integration and error handling

Architecture Notes - BP 3.2.1.1 - Use the services provided by your vendors for integration and error handling

An IoT design consists of device software, connectivity and control services, and analytics services. Test the entire IoT ecosystem for resiliency, starting with device firmware, data flow, the cloud services used, and error handling. Vendors have services integrated with each other to provide a simplified integration and fault handling.

Recommendation 3.2.1.1.1 - Understand and apply the standard libraries available to manage your device firmware

Devices can be built on Amazon FreeRTOS, which provides connectivity, messaging, power management and device management libraries that are tested for reliability and designed for ease of use

Recommendation 3.2.1.1.2 - Use log levels appropriate to the lifecycle stage of your workload

  1. AWS IoT logs can be set up per Region and per account with the logging level set to DEBUG during product development phase to provide insights on data flow and resources used. This data can be used to improve the IoT system security and performance.
  2. AWS IoT Secure Tunneling can be used to test and debug devices that are behind a restrictive firewall in the field.

Additional Resources

  1. AWS IoT Core Developer Guide: Log AWS IoT API calls using AWS CloudTrail
  2. AWS IoT Core Developer Guide: Monitor AWS IoT using CloudWatch Logs
  3. AWS IoT Core Developer Guide: AWS IoT metrics and dimensions
  4. AWS IoT Core Developer Guide: Monitor AWS IoT alarms and metrics using Amazon CloudWatch
  5. AWS IoT Core Developer Guide: Rules for AWS IoT
  6. AWS IoT API Reference: SetLoggingOptions
Back to top