Best Practice 21.3 – Use shadow only for slowly changing data - IoT Lens Checklist

Best Practice 21.3 – Use shadow only for slowly changing data

Shadow is used in IoT applications as a persistence mechanism of device state. The shadow maintains data that remains consistent across multiple points in time. Device shadow operations can be billed and metered differently than publish/subscribe messages. Reducing the shadow update frequency from the device can reduce the number of billed operations while maintaining an acceptable level of data freshness.

Recommendation 21.3.1 – Avoid using shadow as a guaranteed-delivery mechanism or for continuously fluctuating data

  • As a workload scales up, the cost of frequent shadow updates could exceed the value of the data.

  • Consider MQTT Last Will and Testament (LWT) as a mitigation for the risk of loss of device communication instead of using shadow.

  • Use the AWS Pricing Calculator to compare device shadow interactions versus telemetry messages understand cost implications.

  • For more: