Posted On: May 30, 2019

AWS IoT Events is now generally available and supported for production use.  Customers already using IoT Events include BAI Communications, Moixa, and Ecofit. Launch partners include Deloitte, JIG-SAW, Brains Technology, and Onica.

AWS IoT Events is a fully managed IoT service that makes it easy to detect and respond to changes indicated by IoT sensors and applications – such as malfunctioning machinery, a stuck conveyor belt, or a slowdown in production output – and automatically trigger actions or alerts in response. AWS IoT Events helps you gain visibility across your equipment, applications, and fleets of devices allowing you to do things like build a monitoring application that triggers customer support when assets fail.

Events are patterns of data that identify changes in equipment or facilities like a robotic arm being misaligned on the factory floor or a motion sensor detecting movement after business hours. Industrial companies such as manufacturers, energy utilities, and food processors want to be able to analyze their device data to detect and respond to events from many different IoT sensors and applications to drive faster and better-informed decisions. Detecting events based on data from thousands of devices requires companies to write code to evaluate the data, deploy infrastructure to host the code, and secure the architecture from end-to-end, which is undifferentiated heavy lifting that customers want to avoid. Using AWS IoT Events, customers can now easily detect events like this at scale by analyzing data from a single sensor or across thousands of IoT sensors and hundreds of equipment management applications in real time. With AWS IoT Events, you use a simple interface to create detectors that evaluate device data and trigger AWS Lambda functions or notifications via Amazon SNS in response to events. The detectors can evaluate tens of thousands of input messages from devices every second, identify events when they occur, and trigger actions. For example, when temperature changes indicate that a freezer door is not sealing properly, AWS IoT Events can automatically trigger a text message to a service technician to address the issue.

To get started, go to the IoT Events console, select the sample detector model to learn, or create a new detector model. The detector model defines different states of your device, application, or a process, as well as the conditional logic to determine state transitions. From the console, you can create Inputs that receive the telemetry data (messages) you want to monitor and use in a detector model such as belt speed, motor voltage, or noise levels. Input values are then used in the conditional logic to understand events, such as when a motor might be stuck. Finally, you can select a pre-built action to trigger, such as sending a message to a motor to shut down, whenever an operational change is detected. You can learn more about typical use cases, API details, and examples in the documentation.

AWS IoT Events is priced per message evaluation. Message evaluations are metered each time the event detector logic evaluates an incoming message to determine whether an action or an alert should be triggered. The AWS Free Tier offers new customers their first 2,500 message evaluations per month free during the first 12 months. You can learn more about pricing on our pricing page.

AWS IoT Events is available to use in the US East (N. Virginia), US East (Ohio), US West (Oregon), and EU (Ireland) regions. To learn more about AWS IoT Events, visit our product page