AWS IoT Events Documentation
AWS IoT Events is a fully managed service that helps you detect and respond to events from IoT sensors and applications.
Key Features
Telemetry data ingestion
AWS IoT Events helps you evaluate telemetry data to detect events in equipment or a process. IoT Events is designed to ingest raw data from any device connected to AWS IoT, processed data from AWS IoT Analytics, and data from third party applications via IoT Events’ direct ingest APIs.
Event detection
AWS IoT Events is designed to evaluate multiple telemetry inputs to detect events and derive the state of processes, equipment, or products by applying user-defined, conditional logic. Events are patterns of data identifying more complicated circumstances than expected, such as changes in equipment when a belt is stuck or motion detectors using movement signals to activate lights and security cameras. You can schedule maintenance and send alarms or alerts in an effort to reduce the risk of unexpected device failure. If you have many devices using the same detector definition, the service is designed so you can launch a new instance of the detector for every unique value of the signal. The service is also designed so you can extend your event detection and action capabilities whenever a new device comes online allowing you take advantage of stateful complex event detection at scale. The service helps you detect events with simple ‘if-then-else’ statements applied to incoming sensor data streams.
Integration with analytics tools and other AWS services
AWS IoT Events is designed to leverage output from advanced analytics services to make better decisions. With integrations to and from other AWS services, you can further optimize operations. You can complete an event detector setup in AWS IoT Events, write your event logic using simple ‘if-then-else’ statements, and select the alert or custom action to trigger when the event occurs. Such conditional statements can receive inputs from either raw data or data first processed by AWS IoT Analytics (where you can apply machine learning models to aid in detection of more complex events). You can select a pre-built action designed to trigger on the basis of a detected event, such as sending a notification through Amazon Simple Notification Service (SNS) to a service technician, or you can build a custom action by setting up a function for AWS Lambda designed to send the event data to a third-party application.
Scalability
AWS IoT Events scales when you are connecting many devices. Define a model for a specific device, and the service is designed to scale and manage all devices of that model that connect to IoT Events. If an event is detected on one device or many, IoT Events is designed to trigger the appropriate reaction or alert.
Alarms
AWS IoT Events is designed to help you evaluate equipment behavior or identify equipment performance issues based on industrial data in the cloud. For an asset data property that you want to monitor, you can define an alarm rule to apply (e.g. rotations per minute is greater than a user defined value), select the severity for this alarm definition (e.g. severity values of 1, 2, 3 and 4), and configure the notifications so they are designed to send when an alarm is triggered (e.g. Email and SMS). Once an alarm has been defined, the service is designed to so operators can manage the alarm workflow by taking actions to acknowledge, snooze or disable the alarm. The service is also designed so you can configure additional actions to other AWS services including AWS Lambda, Amazon Simple Queue Service (SQS), and Amazon Simple Notification Service (SNS), to be executed when an alarm triggers. This helps you to integrate alarm notifications with your own ticketing or notification system.
Additional Information
For additional information about service controls, security features and functionalities, including, as applicable, information about storing, retrieving, modifying, restricting, and deleting data, please see https://docs.aws.amazon.com/index.html. This additional information does not form part of the Documentation for purposes of the AWS Customer Agreement available at http://aws.amazon.com/agreement, or other agreement between you and AWS governing your use of AWS’s services.