AWS IoT Events Discontinuedsince 2018
[Ended May 20, 2026] Service that detected events in IoT sensor data and triggered automated actions. AWS officially recommends rebuilding with Kinesis Data Streams and Lambda
What It Does
[Discontinued] AWS IoT Events reached end of support on May 20, 2026. The following describes the service as it worked at the time. AWS IoT Events is a service that monitors data from IoT devices and applications, and automatically executes actions when specific conditions or patterns are detected. You define state machines called detector models, and based on device state transitions, you can trigger actions such as sending SNS notifications, invoking Lambda functions, or sending messages to IoT Core.
Use Cases
Used for automatic alerts when factory equipment temperature exceeds a threshold, coordinated control of smart home devices based on state changes, anomaly detection and automatic shutdown of industrial equipment, and complex condition evaluation combining values from multiple sensors.
Everyday Analogy
Think of it like a factory monitoring operator. They constantly watch the instrument panel and automatically respond according to rules like 'sound the alarm if temperature exceeds 80 degrees' or 'close the valve if pressure drops.' They can also handle complex decisions that combine readings from multiple instruments.
End of Support and Migration Paths
AWS IoT Events reached its end of support on May 20, 2026, and had stopped accepting new customers on May 20, 2025. The console and service resources are no longer accessible. The official AWS migration guidance shows how to re-implement detector-model style state monitoring with Amazon Kinesis Data Streams and AWS Lambda, and how to migrate AWS IoT SiteWise alarms. This page remains available as a historical reference and migration guide.
What Is AWS IoT Events?
AWS IoT Events is a service that monitors telemetry data sent from IoT devices and detects and responds to events based on defined conditions. Beyond simple threshold monitoring, you can set up compound conditions combining data from multiple devices, as well as time-based conditions (such as when data hasn't arrived for a certain period). It automatically executes actions like notifications and device control in response to detected events, automating IoT system operations.
Detector Models
The core of IoT Events is the detector model. Defined as a state machine (state transition diagram), it lets you visually design each device state and the transition conditions between them. For example, you can define three states - 'Normal,' 'Warning,' and 'Critical' - and build a model where the state transitions to 'Warning' when temperature exceeds 70 degrees and to 'Critical' when it exceeds 80 degrees. You can configure actions for each state transition or while in a state, enabling flexible control based on conditions.
Inputs and Actions
Data input to detector models can come via IoT Core's rule engine, direct submission to the IoT Events API, or integration from other AWS services. Available actions include sending notifications to SNS topics, invoking Lambda functions, sending messages to SQS queues, sending commands to devices through IoT Core, and writing data to DynamoDB. A single detector model can track multiple device instances individually, with independent state management for each device.
Things to Watch Out For
- Support ended on May 20, 2026. The console and APIs are no longer accessible; state monitoring must be re-implemented with Kinesis Data Streams and Lambda (official AWS migration procedures are available)
- If it was used for AWS IoT SiteWise alarms, follow the SiteWise migration procedure. This page is kept as a historical reference to support migration decisions
References (Official AWS Resources)
The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.
If this page and the official documentation disagree, treat the official documentation as authoritative.
