Review - IoT Lens


IOTPERF 6. How do you evolve your architecture based on the historical analysis of your IoT application?

When building complex IoT solutions, you can devote a large percentage of time on efforts that do not directly impact your business outcome. For example, managing IoT protocols, securing device identities, and transferring telemetry between devices and the cloud. Although these aspects of IoT are important, they do not directly lead to differentiating value. The pace of innovation in IoT can also be a challenge.

AWS regularly releases new features and services based on the common challenges of IoT. Perform a regular review of your data to see if new AWS IoT services can solve a current IoT gap in your architecture, or if they can replace components of your architecture that are not core business differentiators. Leverage services built to aggregate your IoT data, store your data, and then later visualize your data to implement historical analysis. You can leverage a combination of sending timestamp information from your IoT device with leveraging services like AWS IoT Analytics and time-based indexing to archive your data with associated timestamp information. Data in AWS IoT Analytics can be stored in your own Amazon S3 bucket along with additional IT or OT operational and efficiency logs from your devices. By combining this archival state of data in IoT with visualization tools, you can make data driven decisions about how new AWS services can provide additional value and measure how the services improve efficiency across your fleet.